Product guide · analog gauge workflow
Using an analog gauge? Your backflow report app should still fit the job
A traditional analog gauge should not force a certified tester back to a clipboard and a second round of entry. A useful reporting workflow preserves the readings you observed, keeps them with the right assembly, and leaves local procedure and form acceptance where they belong: with the receiving program.
Manual entry is still a field workflow
Yes: a reporting app can be useful with a traditional analog differential gauge. The practical requirement is not a hardware connection. It is a field flow that lets the certified tester enter the readings actually observed, ties them to the identified assembly, and makes the completed record reviewable before the tester leaves the site.
A pass or fail label can help while the gauge is still connected, but the measured number matters just as much. A report that records only a final status is difficult to reconcile when a property owner, program reviewer, or next year's tester needs to understand what was tested and what happened after a failure.
Sources for this section: Washington Administrative Code: field test report content; Washington State Department of Health: Backflow prevention assembly field test report.
What the app should preserve from the first entry
- Facility, water purveyor, service, and exact assembly location—not a shorthand that the next tester has to decode.
- Assembly type, make, model, serial number, size, and the information visible on the tag.
- The observed readings for the actual assembly family, entered while the gauge, hoses, and assembly are still in front of the tester.
- Tester credential and test-kit identification, including the calibration information the receiving program expects.
- Initial failed readings, repair notes, and complete final retest readings as separate parts of one record.
- Signatures and a readable report that can be reviewed before it is saved, shared, or submitted.
Sources for this section: Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; USC Foundation: Field-test training tools.
What to check before choosing an analog-gauge reporting app
| Field need | Question to ask | Why it matters |
|---|---|---|
| Manual readings | Question to ask:Can I enter the value I observe from my analog gauge? | Why it matters:The reporting workflow should support the equipment you already use. |
| Assembly-specific fields | Question to ask:Does the form change for RP/RPZ, DC/DCVA, PVB/SVB, and detector assemblies? | Why it matters:Each family has its own reading set and report context. |
| Failure and retest history | Question to ask:Are the initial readings retained after repair and retest? | Why it matters:A later pass should not erase the original result. |
| Field conditions | Question to ask:Can I complete the essential record with poor signal and finish the handoff later? | Why it matters:Vaults, mechanical rooms, and outdoor sites are not dependable office networks. |
| Export and filing | Question to ask:Can I review a legible report and confirm the recipient's current requirements? | Why it matters:A polished PDF is useful, but the receiving authority controls acceptance. |
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
A practical analog-gauge workflow from test to report
Read the tag before opening a saved record
Confirm the assembly type, make, model, serial number, size, service, and location at the site. A prior record is a starting point, not proof that the assembly in front of you is unchanged.
Choose the actual assembly family
RP/RPZ, DC/DCVA, PVB/SVB, and detector assemblies do not use the same set of readings. The form should follow the assembly rather than asking you to work around a generic pressure worksheet.
Enter what the gauge showed
Record the measured value while the test setup is still in place. That is more dependable than trusting memory or transcribing a handwritten note at the end of a long route.
Keep a failed initial test visible
If the assembly does not pass, preserve the original readings before documenting repair work and the complete retest. The record should explain the sequence rather than presenting only the final outcome.
Check the receiving program before filing
Confirm the accepted form, recipient, submission method, and any local tester-registration requirement with the water system that will receive the report.
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
How BackflowPass fits an analog-gauge workflow
BackflowPass is a browser-based field-report workflow for certified testers who enter readings manually. Select the assembly type, enter the values observed, review the app's baseline pass/fail math, capture signatures, and produce a one-page PDF report. The current workflow supports RP/RPZ, DC/DCVA, PVB, SVB, DCDA, and RPDA records, including repair and retest information.
The workflow is deliberately bounded. BackflowPass does not read an analog gauge for you, replace an accepted field procedure, validate credentials, determine a water system's current form, or decide whether a report will be accepted. It helps preserve a disciplined field record; the tester remains responsible for the test and the local filing decision.
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; 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.
- 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.
- Washington Administrative Code: field test report content
A detailed official field-report checklist for facilities, assemblies, readings, repairs, test kits, and tester attestation; use as a Washington example, not a national form.
- 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.
Continue with the right next question
- Use the full software evaluation checklistCompare the wider reporting workflow before changing how a whole route is managed.
- Review test-kit and calibration contextKeep gauge acceptance and calibration records separate from the reporting app decision.
- Check report and submission requirementsConfirm what the receiving water system expects before treating any PDF as ready to file.
- Try the BackflowPass field workflowStart a test and see how manual readings, signatures, and report fields fit together.
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.