Product guide · reporting workflow
Backflow testing software: evaluate the field-reporting workflow before you switch
Backflow testing software should make a certified tester's field record easier to complete and preserve. It should not promise universal compliance, choose a site's assembly, issue credentials, or claim that a PDF will be accepted without confirmation from the receiving water system.
Start with the job—not a feature checklist
The core job is to turn a qualified field test into a complete, reconcilable record while the assembly, tag, gauge, and site contact are still in front of the tester. The hard parts are usually identity, family-specific readings, tester and gauge evidence, failed-test history, signatures, and the particular program's accepted report and submission requirements.
A system that creates a polished PDF but loses the serial number, final retest readings, local form requirement, or submitted-file history has not solved the reporting problem. Evaluate the workflow against the programs you actually file with.
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Austin Water: Backflow Prevention Assembly Tester Information.
A practical software evaluation checklist
| Workflow area | Question to test | Why it matters |
|---|---|---|
| Assembly identity | Question to test:Can the workflow retain type, make, model, serial, size, location, and service without retyping? | Why it matters:The report must match the actual assembly record, including after annual retests. |
| Field readings | Question to test:Does each supported assembly family show only the relevant reading set and retain values as entered? | Why it matters:RP, DCVA, PVB, and SVB records do not have the same evidence. |
| Failure and retest | Question to test:Can it preserve the initial failure and complete final retest rather than overwrite history? | Why it matters:Program reviewers and owners need a coherent corrective timeline. |
| Tester and gauge | Question to test:Can it record the credential, local registration, gauge identity, and calibration information the recipient expects? | Why it matters:A valid test can still be rejected when required credentials or gauge details are absent. |
| Local acceptance | Question to test:Can it produce or export the exact accepted form and delivery format for the current program? | Why it matters:No workflow should call a report compliant before the recipient accepts it. |
| Field conditions | Question to test:Can a tester complete the essential record when connectivity is poor and safely finish the file later? | Why it matters:Basements, vaults, mechanical rooms, and outdoor sites are not dependable office networks. |
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Austin Water: Backflow Prevention Assembly Tester Information; USC Foundation: Field-test training tools.
What BackflowPass does
BackflowPass is a browser-based field-report generator for certified backflow assembly testers. Its visible workflow supports RP, RPDA, DC, DCDA, PVB, and SVB reports; captures facility and assembly details, gauge readings, initial and final results, repair and retest information, and signatures; and generates a one-page PDF. The application is designed to remain usable after it has loaded when a jobsite has no signal.
The product's rules and report structure are deliberately bounded. BackflowPass is independent software: it is not ASSE-, USC-, state-, or purveyor-certified; it does not validate credentials, determine local acceptance, approve a replacement, or submit to every authority. A tester remains responsible for checking the current local procedure and form.
Sources for this section: USC Foundation: Field-test training tools; Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Run a five-record trial before migrating a whole route
Choose real receiving programs
Pick reports that will go to the water systems and jurisdictions you actually serve, including their current accepted forms.
Use different assembly families
Include the families and service conditions that expose the fields your team will need—not five versions of the same easy test.
Include one failure/retest scenario
Verify that the original result, corrective work reference, and final readings remain distinct and exportable.
Test offline and handoff conditions
Try the workflow in the least reliable connectivity setting and confirm how records are retained, exported, and delivered.
Have the recipient validate the output
Do not infer acceptance from how the PDF looks; ask the intended water system or program before changing production workflow.
Sources for this section: Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington State Department of Health: Backflow prevention assembly field test report; Austin Water: Backflow Prevention Assembly Tester Information.
Good fit and explicit boundaries
BackflowPass is a fit for a certified tester who needs a focused field record and PDF for a supported assembly family. It is not represented as a water-purveyor program platform, credential registry, universal jurisdiction-form library, billing system, or engineering design tool.
That boundary is useful when comparing options. A broad management system can be appropriate when a program needs customer notices, jurisdiction-specific submission integrations, large asset inventories, or regulatory administration. A focused field tool can be appropriate when the immediate job is completing an accurate report at the assembly.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Washington State Department of Health: Backflow prevention assembly field test report; 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
Definitions, assembly/device distinction, program elements, and incident-response context.
- USC Foundation: Field-test training tools
Current Foundation materials distinguish the RP, DC, PVB, and SVB field-test families.
- Washington State Department of Health: Backflow prevention assembly field test report
An official example of report guidance; its required and optional fields are specific to Washington.
- Texas Commission on Environmental Quality: Cross-connection control and backflow prevention
Shows that alternate forms and submission requirements are controlled by the receiving water system.
- Austin Water: Backflow Prevention Assembly Tester Information
A current local example of receiving-system report fields and submission workflow.
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.