Failure closeout
Backflow test retest: close the repair and reporting loop
A retest is the documented follow-through after a failed result or service event when the governing program requires a passing verification.
A retest is the documented follow-through after a failed result or service event when the governing program requires a passing verification. Keep the failed finding, repair scope, retest, and filing tied to the same assembly.
Do not assume a repair invoice is a passing retest. Escalate if the failure mode, model, or required filing path is unclear.
Interactive check
Turn observations into a next step
This narrows the route. It does not replace an on-site test, manufacturer instructions, or local requirements.
Evidence sequence
Move in this order
- 01
Establish the exact record
Keep the original failed test and identify the exact assembly before authorizing work.
- 02
Define the specific scope
Confirm who repairs, who retests, and whether the same provider can perform both actions under the local program.
- 03
Prove the closeout
Retain the passing retest and proof of submission or acceptance with the original notice.
Identification notes
What to look for
- The failed report identifies the test date, assembly, and finding to be resolved.
- Repair scope must identify the exact model and component path rather than a generic kit.
- The retest result and accepted filing create the final compliance record.
Safe observations
What you can check without taking it apart
- Ask whether a retest deadline applies after repair.
- Keep model photos before parts are ordered.
- Confirm the assembly remains accessible for the return visit.
Stop conditions
Move to qualified help when
- A repair is proposed without a component-level diagnosis.
- There is no confirmed retest or filing responsibility.
Boundary check
Do not confuse this path with
- A generic service listing does not establish program eligibility.
- A device family is not enough to identify compatible parts.
- This page does not replace a qualified assessment or authority approval.
Official local layer
Your utility sets the rule
Use the governing utility or authority requirement and exact manufacturer documentation to validate this specific decision path.
Evidence ledger
What this decision path is built on
Use the governing utility or authority requirement and exact manufacturer documentation to validate this specific decision path.
- 01U.S. EPA · EPA-CCC-001Cross-Connection Control ManualBackflow, backsiphonage, device families, hazard protection, testing, and program responsibility. Verified 2026-08-02.
- 02Watts · WATTS-RPZ-009Series 009 reduced pressure zone assemblyRPZ construction, relief discharge, installation constraints, service literature, and local-code warning. Verified 2026-08-02.
Continue the case
Related next steps
CONTENT REVIEWED · 2026-08-02