Contractor guide · team workflow
Backflow reporting for teams: preserve the field record through the office handoff
A team workflow fails when it turns a field result into a loose PDF with no durable connection to the assembly, tester, repair history, or receiving program. The useful handoff is structured: field identity and measurements first, office review and local delivery next.
Build the handoff around the assembly record
EPA's guidance treats records for assemblies in service, testing, repair, and personnel as part of a coherent cross-connection-control program. For a contractor team, the same principle is practical: one field record should show what was tested, who tested it, what the gauge observed, and what happened next.
The office should review and route a completed record; it should not reconstruct readings from a text message or overwrite the failed initial test after a repair.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Best Practices Guide; Washington Administrative Code: field test report content.
Give each handoff one clear owner
| Stage | Owner | Completion evidence |
|---|---|---|
| Site and assembly match | Owner:Field tester | Completion evidence:Tag, service, location, and record identity reconciled at the site. |
| Readings and retest history | Owner:Field tester | Completion evidence:Family-specific values and repair/retest sequence captured without erasing the first result. |
| Program and recipient review | Owner:Office or assigned coordinator | Completion evidence:Current recipient, required local form, and delivery method confirmed. |
| Retention | Owner:Assigned record owner | Completion evidence:Final report and delivery proof kept with the same assembly history. |
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.
Workflow checks that reduce rework
- Use the physical tag to select or create the record before entering readings.
- Keep initial failures, repairs, and final retests in one sequence instead of publishing a clean final status alone.
- Check required tester, gauge, signature, and recipient fields before the report leaves the team.
- Retain the version delivered and any confirmation, but ask the actual program about acceptance rather than assuming export equals submission.
Sources for this section: Washington Administrative Code: field test report content; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
BackflowPass supports the field record and shared history
BackflowPass's paid plans add cloud history, company branding, saved assemblies, and crew sharing to the free field workflow. The tester still enters manual readings, reviews the result, captures signatures, and exports the report from the actual job.
The product does not assert that it sends reports to every water program, validates team credentials, or substitutes for a contractor's quality review. Build those local checks into the office handoff.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington Administrative Code: field test report content.
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.