Records, Reporting, and Program Evaluation
Records
A defensible program keeps inventory records, hazard classifications, device records (make, model, serial, location), test and repair reports, tester certifications, notices, and enforcement actions. Records must be accurate, complete, retrievable, and retained per policy. Candidates should understand data fields and audit trails.
Reporting
Reports go to the AHJ, water utility, and property owner. Know required content: device identification, test results, tester name and certification, date, and pass/fail status. Understand confidentiality and public record considerations.
Program evaluation
Evaluate using performance metrics: percentage of devices tested on time, failure rates, repeat failures, inventory completeness, response times, and compliance rates. Use results to target education, enforcement, and resource allocation. Recognize continuous improvement and risk-based prioritization.
Traps
- Keeping records but never analyzing them.
- Missing serial numbers or tester certification on reports.
- Failing to follow up on overdue tests.
- Assuming a high pass rate means a healthy program; it may mean weak testing.
Worked example
A program finds 30 percent of devices overdue. Evaluation shows the cause is poor owner notification. The fix: automated reminders, clearer notices, and follow-up enforcement. Track the overdue rate monthly to confirm improvement.
Rule of thumb
If it is not documented, it did not happen. Then use the data to improve the program, not just to file it.