Program Development and Administration
Building a program
A cross-connection control program needs legal authority, administrative structure, hazard assessment, device requirements, tester certification, inspection and testing, recordkeeping, enforcement, and public education. Candidates should understand the program cycle: inventory, classify, require protection, verify installation, test, track, and re-evaluate.
Key administrative concepts
Know premises inventory (survey all service connections), hazard classification (high/low), device tracking (serial numbers, locations, test dates), tester approval (certification, calibration, conflict-of-interest rules), permits, fees, and noncompliance procedures (notice, re-test, termination). Understand containment vs. internal program scope and the role of ordinance in granting authority.
Traps
- Assuming a program is only about testing; it starts with inventory and hazard classification.
- Ignoring tester independence and calibration records.
- Failing to define enforcement steps and timelines.
- Overlooking public education and stakeholder communication.
Worked example
A utility discovers 400 unmapped service connections. The correct sequence: inventory, classify hazards, notify owners, require installation or verification, schedule testing, record results, and follow up on failures. Enforcement begins only after documented notice.
Rule of thumb
No inventory, no program. You cannot protect what you have not identified. Track every assembly by location, type, hazard, and test history.
Administration tip
Document decisions and keep a clear audit trail; regulators and auditors look for consistency between ordinance, procedure, and records.