Report workflow
Backflow report submission: confirm the owner and proof of filing
Submission responsibility must be explicit: the tester, contractor, owner, or portal may file the result.
Submission responsibility must be explicit: the tester, contractor, owner, or portal may file the result. The completed record pairs the right assembly with a passing or failed status and proof of delivery.
Do not transmit property or tester data through an unverified link. Escalate when the listed portal, account, or assembly does not match the official notice.
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
Use the issuer website or notice to identify the authorized portal, email, or recipient.
- 02
Define the specific scope
Confirm property, assembly, tester, date, and result before submission.
- 03
Prove the closeout
Save confirmation, receipt, or correspondence and resolve rejections before the deadline.
Identification notes
What to look for
- The official issuer controls portal, format, and account requirements.
- A tester report may need an owner action before it is accepted by the program.
- Repair records and retests must remain linked to the original asset.
Safe observations
What you can check without taking it apart
- Use the official contact to verify portal domains.
- Keep the completed test form before uploading.
- Record who is responsible for correcting a rejected filing.
Stop conditions
Move to qualified help when
- The portal is not linked by the issuing program.
- The submitted report cannot be matched to the device on site.
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