12.2 Purveyor Notification and Record Retention

12.2 Purveyor Notification and Record Retention

Quick Answer: Many water purveyors and authorities having jurisdiction (AHJs) require annual assembly tests by a deadline, submitted by a currently certified tester. Notify the customer before testing when shutoffs will interrupt service. Retain report copies per local rules. On fails, notify the customer and the purveyor as the program requires—with higher urgency for health-hazard assemblies. Learn the pattern (deadline → notify → test → report → retain → escalate fails); do not invent a specific city’s ordinance text on the exam or in the field.

The program is larger than your gauge

Field testing exists inside a cross-connection control program. The purveyor (water utility) or AHJ decides which assemblies must be tested, how often (commonly annually), who may test (certified testers such as ASSE 5110 holders), how results are submitted, and what happens after a fail. Your professional value is not only technical skill—it is reliable participation in that program: on-time reports, honest fails, and documentation the utility can audit years later.

Because rules are local, this section teaches the pattern, not a fake municipal code number. On the job, read the current program handbook, portal instructions, and any customer letter the purveyor mailed. On the written exam, expect questions about roles, deadlines, notification, retention, and fail escalation, not the exact ordinance of one city.

Annual tests and purveyor deadlines

Typical program shape:

1. Inventory of testable assemblies at a premises (often from survey or installation records).
2. Annual test due date tied to install anniversary, calendar year, or a fixed program month.
3. Qualified tester performs the field test with a calibrated gauge.
4. Report submitted to the purveyor/AHJ by the stated deadline (paper form, email, or online portal).
5. Follow-up if the assembly fails, is missing, or the report is late.

As a tester, plan work before the deadline—not the afternoon the portal closes. Customers often call late; still document attempts and advise them that late reports can trigger notices, fees, or water-service actions under their local program. You do not invent those penalties, but you should not shrug and say “the utility won’t care.”

Customer notification before testing

Shutting shutoffs interrupts service downstream of the assembly. That can stop:

• Domestic water to fixtures and appliances.
• Process water in commercial kitchens, labs, or manufacturing.
• Irrigation controllers mid-cycle.
• In poorly designed systems, unexpected interactions with booster pumps or thermal expansion.

Notify before you isolate. A short professional script prevents most conflict:

• Who you are and why you are there (annual backflow test required by the water purveyor/program).
• Which water will be off and for roughly how long.
• That some spillage or relief discharge can occur (especially on RPs).
• That you need clear access, no vehicles blocking vaults, and animal/security issues resolved.
• That if the assembly fails, water may need to stay off or limited until repair—depending on hazard and local rules.

For multi-tenant buildings, coordinate with the property manager, not only the person who hired you. For healthcare, food processing, or other sensitive sites, ask about critical loads and whether testing must occur after hours. Those details are customer coordination, not a license to skip the test.

Record retention: keep what the program expects

“I emailed it once” is not a records system. Typical retention expectations include:

• A copy of each submitted report (paper or electronic).
• Gauge calibration certificates covering the test dates.
• Notes on access problems, unsafe conditions, or customer refusals.
• Documentation of fail notifications (who was told, when, and how).

Retention periods vary by utility, employer, and state. Some programs specify multiple years; employers may keep longer for liability. Build a habit: same-day file naming (site-date-serial), backup electronic copies, and calibration records in the same folder structure. When a purveyor auditor calls six months later about one serial number, you should find that form in minutes.

Do not rely solely on the customer “keeping the yellow copy.” Customers lose papers. Your retained copy is your professional defense that the test was done correctly and on time.

Failed assemblies: dual notification and public-health urgency

A fail is not only a mechanical problem—it is a compliance and public-health event.

Customer notification. Tell the owner or responsible party clearly:

• Which assembly failed.
• Which element failed and the measured value vs criterion (same objective language as the report).
• That repair must be done by a qualified person (often an ASSE 5130 repairer or equivalent local qualification) and that a retest will be required.
• Any immediate operational limits you are authorized to state (for example, do not restore if the program requires the service to remain off until repaired—follow local instruction, do not invent it).

Purveyor notification. Many programs require the tester, the customer, or both to submit fail results promptly—sometimes faster than annual pass reports. Health-hazard assemblies (for example, those protecting against sewage, toxic chemicals, or medical processes) deserve extra urgency because a failed RP or other high-hazard protector means the potable system may be one reverse-flow event away from contamination. Use the program’s fail pathway: portal flag, phone call to the cross-connection office, same-day form, or whatever the handbook specifies.

Never hide a fail to “give the customer time to shop for a cheaper repairer.” Delayed fail reporting can leave a known-bad assembly in service without the purveyor’s knowledge.

Pre-test notification patterns and emergency-response awareness

Two related situations show professional maturity:

1. Planned testing with service interruption. Advanced notice, access confirmation, and a restore plan after testing. Verify shutoffs reopen fully, no continuous relief discharge remains, and the customer confirms service is back before you leave.

2. Assemblies that must stay in service. Some sites claim they “cannot shut down.” Your response pattern:

• Explain that a proper field test requires isolation of the assembly under test procedures you are certified to perform.
• Do not invent a nonstandard “test under full flow” method that invalidates results.
• Escalate to the customer’s management and, when appropriate, the purveyor for direction—after-hours testing, temporary bypass by qualified personnel, or documented deferral under program rules.
• If a true emergency (active fire, medical crisis, hazardous spill response) is underway, stop, prioritize life safety, and resume only when authorities and the customer authorize safe access.

Emergency-response awareness also means recognizing when your test created a problem: stuck shutoff, broken stem, relief valve stuck open flooding a vault, or inability to restore water. Have contact paths for the customer, your supervisor, and the purveyor’s after-hours line if the program publishes one. Document what happened.

What not to invent

Written exams and job sites both punish invented specificity:

• Do not claim “City X always requires 48-hour notice” unless that is actually in the local program you work under.
• Do not invent fee amounts, shutoff durations, or criminal penalties.
• Do not tell a customer that a fail “doesn’t need to be reported if you repair this week.”

Instead, teach and practice the universal pattern: deadline → customer notice → test → honest report → submit → retain → escalate fails with health-hazard priority. Then overlay the real local handbook for the utility you serve.

Linking reports to Chapter 12.1

Notification and retention only work if the report content is complete (Section 12.1). A purveyor cannot act on a fail you never documented. A customer cannot authorize repair without clear element-level results. Keep administrative discipline and measurement discipline as one workflow: finish the form before you load the truck, submit before the deadline, file the copy before the next job.

That administrative half of ASSE 5110 is how annual testing actually protects distribution systems—not only how the relief valve should open on a gauge.