Tester guide · report correction
Why a backflow test report gets rejected—and how to correct the record responsibly
A rejected report is a request to reconcile information, not a reason to rewrite the field result from memory. Start with the receiving program's stated reason, compare the report with the physical assembly and supported records, and preserve the original readings and retest history.
Ask the recipient what needs correction first
A water program may need an identity correction, missing local field, credential or registration confirmation, an accepted form, a delivery correction, or clarification about a repair/retest sequence. The reason belongs to the receiver, so get it in writing or through its current process before changing the report.
Official report rules illustrate how much can be required. Washington's report-content rule covers facility and assembly identity, readings, repair information, tester details, and gauge information. Your program may use a different set of fields.
Sources for this section: Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Portland Water Bureau: Testing backflow prevention assemblies.
Correct data from evidence, not a cleaned-up story
| If the issue is | Reconcile against | Preserve |
|---|---|---|
| Assembly identity | Reconcile against:The physical tag, service, location, and supported installation or program record. | Preserve:Why the identity was corrected and the report version involved. |
| Missing field | Reconcile against:The original field notes, instrument record, or responsible tester—not a guessed replacement value. | Preserve:The original record and the added supported detail. |
| Repair or retest clarity | Reconcile against:The complete initial result, work performed, and final retest record. | Preserve:Both the original failure and the later outcome. |
| Recipient or form | Reconcile against:The current water-system instruction or notice. | Preserve:Delivery details and confirmation for the corrected version. |
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Do not turn correction into erasure
Do not replace an observed failed reading with a final passing result, detach a repair from its retest, or guess a serial number simply to complete a portal. A complete history is more useful to the owner, receiving program, and next tester than a superficially clean PDF.
When the missing fact cannot be supported, ask the receiving program or responsible professional what corrective path it accepts. A new inspection or retest may be necessary; this guide cannot determine that requirement.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Best Practices Guide; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Keep the report sequence visible in the field record
BackflowPass keeps repair and final-retest fields with the original test workflow so the PDF can show the sequence rather than only the final result. It also retains test history for the record owner according to the selected workflow and plan.
It does not tell a tester what a particular utility will accept as a correction or alter an already submitted authority record. Confirm the recipient's current process before resubmitting.
Sources for this section: Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Sources and review boundary
This guide was reviewed on August 22, 2026. It links to primary public sources where possible and labels state and local examples as examples. It is educational material, not engineering, legal, installation, certification, or water-system approval advice.
- EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention
Program elements, including records for testing, repair, personnel, and assemblies in service.
- EPA: Cross-Connection Control Best Practices Guide
EPA guidance on cross-connection-control program responsibilities, testing, and records.
- Portland Water Bureau: Testing backflow prevention assemblies
A current public-water-system example of annual notices, owner coordination, tester reporting, and a submission timeline.
- City of Fort Worth: Backflow and cross-connection control
A current utility example covering irrigation, certified tester registration, and reports for new, altered, replacement, and removed assemblies.
- Washington State Department of Health: Backflow prevention assembly field test report
An official example of a state field-report resource; its requirements are not a national form.
- Washington Administrative Code: field test report content
A detailed state example of report fields covering identity, readings, repair, tester, and gauge information.
- Texas Commission on Environmental Quality: Cross-connection control and backflow prevention
A state example of a receiving authority's program and report materials; do not treat it as a national procedure.
Continue with the right next question
Related field references
Backflow prevention assembly guide
The practical distinction between testable assemblies, non-testable devices, air gaps, and the pressure reversals cross-connection programs manage.
RPZ vs. DCVA vs. PVB
A source-led comparison of the major assembly families, their protection limits, and why local hazard approval controls selection.
Backflow test report guide
Common report record blocks, local-form acceptance, failed-test history, and the submission checks a generic PDF cannot answer.
Failed backflow test guide
How to preserve the original result, confirm the local corrective path, document repair or replacement, and retain a complete retest record.
Backflow testing checklist
A job-readiness checklist for procedure, access, assembly identity, gauge records, report review, and filing—not a replacement field procedure.
Cross-connection control program guide
The authority, survey, approved protection, testing, recordkeeping, and corrective-action pieces behind a maintained program.
Fill this out on the phone instead.
The generator asks for exactly these fields, grades every differential as you type, opens repair and retest fields when something fails, and hands you the finished one-page PDF. No account, no install, works with no signal.