Field guide · detector assemblies
DCDA and RPDA backflow test reports: keep the detector assembly record specific
A detector assembly report should not flatten a fire-service assembly into an ordinary domestic record. The main and bypass components, service context, local fire impairment procedures, and receiving-program fields all deserve deliberate confirmation before testing and filing.
Why detector assembly records need their own review
DCDA and RPDA labels point to detector-assembly configurations often associated with fire services. The report needs to identify the correct assembly and distinguish the relevant main and bypass information rather than silently treating it as a single generic check valve.
Because fire protection involves its own impairment and coordination needs, do not schedule isolation or testing from a web article alone. Follow the site's fire-protection process and the receiving water program's current requirements.
Sources for this section: EPA: Cross-Connection Control Best Practices Guide; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington Administrative Code: field test report content.
Record the configuration before the test starts
| Confirm | Why it belongs on the record | Avoid |
|---|---|---|
| Service and location | Why it belongs on the record:Fire services can sit beside domestic or irrigation assemblies on the same property. | Avoid:Assigning a record by address alone. |
| Main and bypass identity | Why it belongs on the record:Model, serial, size, and meter-related details may differ across the assembly components. | Avoid:Copying one component's tag to every field. |
| Accepted procedure and fields | Why it belongs on the record:The local program determines its required reading and form detail. | Avoid:Adapting a standard DCVA or RPZ page without confirmation. |
| Coordination notes | Why it belongs on the record:The test can affect an active protective service. | Avoid:Treating test access as ordinary equipment access. |
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.
A conservative field-to-report workflow
Confirm the job scope
Identify the assembly family, components, service, recipient, and local procedure before any planned impairment.
Coordinate the site
Use the facility's required fire-protection and access process; record the correct physical location and site contact.
Enter the observed data
Keep measurements, tightness checks, component identity, repair details, and retest results with the same detector assembly.
Review and file locally
Verify the report against the receiving program's current requirements before sending it or calling the work closed.
Sources for this section: EPA: Cross-Connection Control Best Practices Guide; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; City of Fort Worth: Backflow and cross-connection control.
What BackflowPass can and cannot organize
BackflowPass supports DCDA and RPDA selection in its field-report workflow and records family-specific readings, repair/retest information, signatures, and a PDF report. It is useful for preserving the field record in the same place as the assembly identity.
It does not manage fire-system impairment, diagnose fire-system performance, decide a required procedure, or submit an authority's specific form. Those are site and jurisdiction decisions.
Sources for this section: 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.