Field Notes
Failed backflow test repair records before the retest
A failed assembly needs a clean record chain: test result, isolation status, repair action, parts, retest, and the report sent to the water program.
Direct answer
A failed backflow test record should show the original test result, the assembly identity, the hazard or service protected, whether the assembly was left in service or isolated under the local program rules, what repair was performed, which parts were changed, who performed the work, and the retest result after repair.
Do not treat a failed test as a single note that says repaired. The useful record is a chain. It lets the tester, repair technician, owner, water purveyor, inspector, and office see what failed, what changed, and why the assembly was returned to service.
Local cross-connection rules control the deadlines, forms, tester qualifications, shutdown requirements, high-hazard response, and reporting path. This field note helps organize the record, but it is not a substitute for the adopted program manual, authority instructions, manufacturer repair procedures, or licensed trade requirements.
The record starts before the repair
The repair record should start while the failed test is still fresh. Capture the test kit, assembly tag, serial number, location, line pressure when required by the form, check valve readings, relief valve reading for an RP assembly, shutoff condition, and the exact failing step.
If the tester writes only failed, the repair technician inherits a guessing problem. If the tester writes check valve 1 held at 0.6 psid after flushing, relief valve opening point acceptable, debris visible at cover, the next person has a usable starting point.
A failed test can also affect service, hazard protection, owner notification, and local reporting deadlines. Those are not afterthoughts. Record who was notified, when they were notified, and whether the assembly was isolated, bypassed under an approved procedure, repaired immediately, or left under a written compliance path.
Minimum failed-test packet
Use the local test form first. Then add a field packet that supports the form rather than replacing it.
The packet should be short enough that a route tech can complete it and complete enough that the office can defend the sequence later.
| Record item | Field detail | Why it belongs |
|---|---|---|
| Assembly identity | Type, size, make, model, serial number, tag, location, service protected | Prevents the wrong assembly from being repaired or reported |
| Original test | Date, tester, kit ID if required, line pressure if required, readings, failing step | Shows the basis for repair instead of a vague fail note |
| Status after fail | In service, isolated, shut down, approved bypass, owner notified, water program notified | Addresses protection and compliance questions before repair |
| Repair action | Cleaning, rubber kit, spring, seat, check module, relief valve parts, shutoff repair, replacement | Shows what changed between fail and pass |
| Parts evidence | Part numbers, kit labels, removed debris, damaged parts, photos before reassembly | Connects the invoice and retest to actual field work |
| Retest | Date, readings, pass result, tester, report submission path | Closes the record chain |
Before repair checklist
Before taking the assembly apart, make the record safe and useful. The technician should know whether they are allowed to repair that assembly, whether water service needs coordination, whether the hazard can remain unprotected, and which report form the local program expects.
A repair that creates a pass but leaves no record can still fail the office. The water program may need the retest report. The owner may need proof of downtime. The next annual tester may need to know which parts were changed.
- Confirm the assembly, tag, and location against the failed test report.
- Photograph the assembly before disassembly, including tag and orientation.
- Record whether the owner or responsible site contact approved the shutdown.
- Check the local rule for failed-test deadlines and notification path.
- Confirm manufacturer repair instructions and required replacement parts.
- Keep removed parts identifiable until the repair note is complete.
- Do not close the ticket until the retest result and submission status are recorded.
Repair and retest must stay connected
The repair note and retest should read as one chain. If the repair note says cleaned check 2 and replaced rubber kit, the retest should show the readings that prove the assembly passed after that work. If the assembly fails again, keep that second result in the same record trail rather than overwriting the first attempt.
This is especially useful when the first repair finds debris, fouled rubber, a damaged seat, or a shutoff that will not hold. The next person needs to see whether the failure was corrected, changed, or still present.
Do not invent a local deadline. Some programs give specific repair and retest windows, some distinguish high-hazard conditions, and some require immediate protection or water-service action. Use the adopted local manual and current utility instructions.
What good reporting looks like
A good report is specific without turning into a novel. It names the assembly, names the failing symptom, names the repair, and names the final result.
Weak: RP failed, repaired, passed.
Strong: RP assembly tag BFP-014 at boiler feed failed relief valve opening point on annual test. Owner notified and boiler feed isolated under site procedure. Removed debris from relief valve, replaced relief valve rubber kit per manufacturer kit label, retested same day. Final readings recorded on test report and submitted to utility portal.
The strong version is not longer because it is padded. It is longer because it answers the questions people ask when there is a compliance deadline, service complaint, invoice dispute, or repeat failure.
Photos that help
Photograph the tag, nameplate, installation orientation, failed-test setup if your procedure allows it, the opened cover, fouled or damaged parts, kit label, reassembled assembly, and final test report. Do not photograph customer-sensitive information that does not belong in the packet.
Photos should support the written record. A close-up of a rubber disk means little if the packet does not say which assembly it came from. A tag photo means little if the final report uses a different tag. Keep photo names or captions tied to the assembly and repair step.
Common mistakes
The first mistake is leaving the original failure vague. A future technician cannot learn from a record that says bad check.
The second mistake is treating cleaning and part replacement as the same thing. If the assembly was cleaned only, say so. If parts were replaced, list the part or kit information.
The third mistake is failing to record the assembly status between failure and retest. For some hazards, the question is not only whether it eventually passed. The question is whether protection was maintained or restored under the local program.
The fourth mistake is closing the service ticket before the retest report is submitted. A passed assembly can still become an administrative problem if the report never reaches the water program.
Compliance and safety limits
Backflow records sit inside a local cross-connection control program. The water purveyor, plumbing authority, state rules, tester certification rules, owner policy, and manufacturer instructions control the work.
Do not use this checklist to bypass required tester qualifications, confined-space rules, lockout, pressure relief, traffic control, hot-work controls, water shutdown coordination, or manufacturer repair instructions. If a failed assembly protects a high-hazard condition or cannot be repaired immediately, follow the local program direction and notify the responsible parties under that procedure.
Sources checked
- U.S. EPA, Cross-Connection Control ManualUsed for the repair, replacement, retest, and high-hazard limitation themes.
- Newport News Waterworks, Cross Connection Control Program ManualUsed for report-field examples such as device identity, line pressure, and test-report detail.
- California State Water Resources Control Board, Cross-Connection Control Policy HandbookUsed as a current state-program example showing backflow protection, field testing, repair, recordkeeping, and incident response expectations vary by authority.