State program reporting

Oregon’s March 31 Deadline: What AnnualCross-Connection Program Reporting Looks Like

Oregon requires every community water system to report on its cross-connection control program each year by March 31. The rule is Oregon-specific, but the operating lesson travels: reliable backflow compliance depends on complete records, clear ownership, and proof that the work was finished.

Read MoreShow Less

Updated July 29, 2026. Template: Compliance Article.

Primary keyword: oregon cross connection annual summary report march 31

March 31Water-system staff, engineers, compliance-minded property readersUnited States

Key Takeaways

  • Oregon requires every community water system to submit a Cross Connection Annual Summary Report each year.
  • The Oregon Health Authority states that the annual report is due by March 31.
  • The state provides both an online reporting option and a form-based submission option, then lets systems check whether a report has been entered.
  • Oregon’s deadline does not apply to Southern California properties, where the serving water supplier controls the exact testing and paperwork requirements.
  • Property owners can borrow the same operating discipline by keeping one reliable record for each assembly, due date, test, repair, retest, and report submission.
What Oregon Requires Each Year

The Oregon Health Authority’s current Annual Summary Reports page says the Cross Connection Annual Summary Report is required for every community water system in Oregon. Each system must report requested information about its cross-connection control program every year, using the reporting options provided by the state.

The same page states that the report is due by March 31 each year. For the current reporting cycle shown on the page, Oregon offers an online SmartSheet option and a form that can be submitted by email, fax, or mail. The state also provides a way to check whether the report has been entered.

That deadline belongs to Oregon community water systems. It is not a California testing deadline, and it does not replace the notice or instructions issued by the water supplier serving a Southern California property. Its value for owners and facility teams is the example it sets: cross-connection control is treated as a recurring program with records, reporting, and follow-through.

Why Reporting Matters as Much as the Field Test

A backflow test happens at a physical assembly, but a compliance program has to answer a larger set of questions. Which assemblies are active? Which ones were tested? Which failed? Were repairs and retests completed? Was the final result sent to the right authority? A report forces those details into one accountable record.

Historical research summarized in a U.S. EPA issue paper helps explain why that discipline matters. The paper cites a survey in which 91 percent of respondents had cross-connection control programs, yet only 49 percent required backflow incidents to be reported to state primacy agencies. Most respondents were community water systems. The survey is historical and does not describe current Oregon performance, but it illustrates a durable distinction: having a program on paper is not the same as consistently capturing what happened.

For a property owner, the equivalent gap appears when the annual test is completed but the report, repair, retest, or submission confirmation cannot be found. The field work and the documentation should be managed as one job.

What Property Owners Can Borrow From the Annual-Report Model

Southern California owners do not file Oregon’s report, but they can use the same annual-review habit. A short assembly register makes it easier to prepare for testing, answer a utility notice, and prove completion.

  • List every assembly by property, location, serial number, size, type, and serving water supplier.
  • Record each utility-issued due date rather than applying one assumed date to every assembly.
  • Track the scheduled test date, completed test date, pass-fail result, repair, replacement, and required retest.
  • Keep access instructions for locked cages, rooftops, irrigation areas, tenant spaces, fire systems, and equipment rooms.
  • Save the final test report with the portal, email, or other submission confirmation.
  • Review the register before the next annual cycle so missing records are corrected before a notice becomes urgent.
Use the Serving Utility’s Rules in California

Backflow requirements are administered through state rules and local water-supplier programs, so the exact deadline, form, tester qualifications, submission method, and enforcement process can differ by location. A date published by another state or city should never be copied onto a California property’s calendar without confirmation.

Start with the notice for the actual property. Match the address, assembly information, account, and due date to the device in the field. If the notice is unclear, contact the serving water supplier for the controlling requirement.

Then schedule early enough to leave room for access issues and corrective work. An assembly that fails may need repair or replacement followed by a passing retest. Completing the first appointment on the due date can still leave the overall compliance job unfinished.

Turn the Notice Into a Completed Record

Backflow Test Pros helps Southern California homeowners, commercial owners, HOAs, and facility teams move from a utility notice to completed testing and clear documentation. When an assembly does not pass, the next step can include repair or replacement coordination and retesting.

Bring the property address, serving water supplier, notice, assembly details, and due date to the scheduling conversation. For sites with multiple assemblies, identify each device separately so one completed test does not hide another open requirement.

The goal is simple: finish the field work, resolve any failure, and keep the paperwork together. That is the property-level version of the program discipline Oregon’s annual report makes visible.

Questions About Annual Cross-Connection Reporting

These answers keep the Oregon example in its proper scope and focus on practical next steps.

Does the March 31 deadline apply to California property owners?

No. March 31 is the annual summary reporting deadline stated by the Oregon Health Authority for Oregon community water systems. California owners should follow the date and instructions issued by the water supplier serving their property.

Is an annual program report the same as an individual backflow test report?

No. Oregon’s annual summary covers a community water system’s cross-connection control program. An individual property’s test report documents the result for a specific assembly. The exact submission process is set by the responsible authority.

What records should a multi-assembly property keep?

Keep a separate record for each assembly with its location, serial number, type, due date, test result, repairs, retests, final report, and submission confirmation.

What should I send when requesting backflow service?

Send the property address, water-supplier notice, assembly information, due date, access notes, and any prior test or repair records available.

Related Service And Compliance Pages
These links are chosen from the existing service catalog so the article can hand readers off to the right next step without pretending the blog post itself is the service page.

Make the Annual Test a Finished Job

Backflow Test Pros can help complete the field work, resolve failed assemblies, and keep the service documentation organized.