Operations guide · scheduling
Backflow testing schedule: plan the due date around the actual assembly and site
There is no universal backflow testing calendar. Many programs use annual schedules, but the due date, seasonal timing, retest window, and who receives the report are controlled by the local water system or authority. Build the schedule from the actual notice and assembly record.
The due date belongs to the receiving program
Use a water-system notice, property record, or direct confirmation as the source of truth for a due date. Portland, for example, describes annual testing and asks commercial customers to follow the schedule in their reminder letters. That is a useful workflow example, not a national deadline.
Seasonal context matters. Irrigation assemblies may be easiest to access before seasonal use, but a preferred field season does not change the actual program deadline or any required retest timing.
Sources for this section: Portland Water Bureau: Testing backflow prevention assemblies; City of Fort Worth: Backflow and cross-connection control; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Make one schedule row per assembly, not per address
| Keep | Why | Refresh when |
|---|---|---|
| Assembly identity and location | Why:A single property can contain several separately protected services. | Refresh when:An assembly is replaced, moved, or reidentified. |
| Receiving program and due date | Why:The report destination and deadline are program-specific. | Refresh when:A new notice, policy, or account instruction arrives. |
| Access and service notes | Why:Isolation and access can affect tenants, irrigation controllers, operations, or fire protection. | Refresh when:The site contact, hours, or service use changes. |
| Prior test and repair history | Why:The next visit starts with context instead of a disconnected PDF. | Refresh when:A test, repair, replacement, or retest is completed. |
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Best Practices Guide; Portland Water Bureau: Testing backflow prevention assemblies.
A calmer recurring workflow
Inventory early
Match notices and expected due dates to the actual tag, serial, and service before routes are booked.
Confirm local instructions
Check the recipient, tester eligibility, form, and submission method for the upcoming cycle.
Coordinate access
Identify who can open rooms, isolate service, notify occupants, or follow any site impairment process.
Close the loop
After testing, retain the report and repair/retest result against the same assembly, then record the next known due-date source.
Sources for this section: Portland Water Bureau: Testing backflow prevention assemblies; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Use reminders as prompts, not as compliance decisions
BackflowPass can preserve field history and supports due-date planning in its reporting workflow. That is useful for organizing a route or a property record.
A reminder cannot establish a legal deadline or tell you which form a utility currently accepts. Reconfirm the current rule with the program that will receive the report.
Sources for this section: Portland Water Bureau: Testing backflow prevention assemblies; 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.