Why Your Backflow Test Report Was Rejected and How to Fix It
Getting a notice that your backflow test report was rejected feels a lot like failing the test twice. You already scheduled the tester, paid for the visit, and thought the compliance box was checked. Then the utility says the report cannot be accepted.
Most of the time, that does not mean the assembly itself failed. It means the paperwork, tester credentials, or supporting details did not match what the utility needs to close the record.
EPA's Safe Drinking Water Act framework is the reason utilities take report accuracy so seriously. If a report is incomplete, tied to the wrong assembly, or submitted by a tester whose credential or gauge records are missing, the utility may refuse to accept it until the problem is corrected.
If you are new to the process, start with why backflow testing is required and keep our FAQs handy. If you already need local help, you can also find a local backflow tester before the deadline window gets tighter.
A rejected report is usually a records problem, not a plumbing emergency
Property owner reviewing a rejected backflow test report with a certified tester beside an outdoor backflow assembly
Utilities do not just want proof that someone visited the site. They need a report that matches the correct property, device, hazard, and tester.
Washington State's rule shows how detailed that can get: facility info, assembly location and serial number, accurate readings, field test kit details, tester certification, and a signed statement that the report is true, complete, and accurate. Austin Water similarly requires a complete and legible Test and Maintenance Report within five calendar days.
So a utility may reject a real test report over one missing field, one bad serial number, or one credential issue because the record is not reliable enough to close compliance.
The most common reasons utilities kick reports back
The exact rejection language varies, but the underlying issues are pretty consistent.
1. The assembly details do not match the utility record
The address may be right while the serial number is wrong, or the serial number may be right while the tester selected the wrong assembly type. If those fields do not match the utility record, the report may not post to the right device.
2. The report is missing required fields
Austin says incomplete or unsigned forms will not be processed. Missing owner information, no cause requiring protection, incomplete repair notes, or blank gauge fields can all stop a report from being accepted.
3. The tester's certification or gauge documentation is not current
Seattle Public Utilities says test reports cannot be submitted unless the tester's certification and test equipment calibration information are already in its system. So the test may have happened, but the utility still cannot accept the result.
4. The wrong utility form or submission path was used
Philadelphia publishes its own test and maintenance record, facility update form, installation permit form, and technician resources. Austin requires online submission through WEIRS rather than paper copies. Many utilities do not accept a generic invoice or a form designed for another jurisdiction.
5. The report shows a bigger compliance issue
Sometimes the problem is not the form itself. The utility may believe the assembly is unapproved, the installation details are incomplete, or the notes point to an unresolved repair or hazard condition. In that case, a corrected report alone may not fix it.
If you want context on how utilities keep these records straight, our article on how utilities track backflow test compliance is a good companion read.
What official programs actually require
Backflow test report, gauge calibration certificate, tester ID card, and utility compliance checklist on an office desk beside a laptop
Utilities are trying to prove that the right device was tested correctly by the right person using traceable equipment.
A few official examples make that clearer:
- Washington WAC 246-292-036 requires detailed facility, assembly, installation, test-reading, repair, field-test-kit, and tester-certification information, plus the tester's signature and certification that the report is true, complete, and accurate.
- Austin Water requires a complete and legible Test and Maintenance Report within five calendar days and says incomplete or unsigned forms will not be processed.
- Seattle Public Utilities requires reports to follow its guidelines and the Washington code, and it says test reports cannot be submitted if tester certification and calibration documents are missing from the system.
- Philadelphia Water Department maintains official forms, city-certified technician lists, and approved assembly resources, which signals that report acceptance is tied to the city's own compliance workflow.
If you are comparing how local processes work in practice, our pages for Austin, Texas, Seattle, Washington, and Philadelphia, Pennsylvania can help. Utility-specific summaries like Austin Water backflow testing and Philadelphia Water Department backflow testing are also useful before calling the utility.
How to fix a rejected report without making the problem worse
The fastest path is usually calm, specific, and document-heavy.
Step 1: Get the exact rejection reason
Do not work from a vague message like "report rejected" or "missing information." Ask what exactly is missing or mismatched.
Examples:
- wrong serial number
- no tester certification on file
- missing gauge calibration date
- incomplete repair notes
- unsigned report
- wrong utility form
- unapproved assembly or installation concern
You want the utility's actual reason in writing if possible.
Step 2: Compare the report against the device and the utility notice
Check the address, assembly location, assembly type, manufacturer, model, serial number, and due date. Then compare those fields with the utility notice and any previous accepted report.
Many rejection problems show up immediately once you put the documents side by side.
Step 3: Loop the tester in quickly
If the issue is a typo, omitted field, missing signature, or missing credential packet, the tester may be able to fix it quickly. If the issue involves unclear readings or wrong assembly identification, the tester may need to issue a corrected report or revisit the site.
That is one reason our guides on how to submit your backflow test report to your water utility and how to read a backflow test report and what the numbers mean are worth reviewing before you resubmit anything.
Step 4: Ask whether a corrected report is enough or whether a retest is required
Do not assume. Sometimes a utility only needs a corrected document. Sometimes it needs an updated form signed by the tester. Sometimes it needs a fresh test if the underlying issue affects report validity.
Step 5: Confirm acceptance after resubmission
Seattle explicitly tells owners to work with their tester and keep documentation confirming the results were submitted. A resubmission is not finished when the email is sent. It is finished when the utility confirms the record is accepted and closed.
When the problem is really the tester, not the property owner
A rejected report can expose a vendor-quality problem.
If the utility says the tester is not in the approved system, the calibration records are missing, or the form keeps coming in incomplete, the property owner may need to switch providers. That does not mean the tester is dishonest. But it does mean the tester may not be the best fit for that jurisdiction's compliance process.
This is where it helps to use a tester who already works regularly with the local utility. If you are shopping around, compare options through local pages like Austin, Texas, Seattle, Washington, and Philadelphia, Pennsylvania, and read how to choose a qualified backflow tester.
If the rejection is dragging toward a deadline, do not wait for the vendor relationship to sort itself out. Keep the utility informed while you line up a corrected submission or a replacement tester.
How to prevent the next rejection
Property manager and certified backflow tester correcting backflow paperwork on a laptop with organized assembly records on the desk
The easiest rejection to handle is the one that never happens.
A simple prevention checklist goes a long way:
- keep the last accepted report on file
- photograph the assembly and serial number before the test visit
- confirm the exact utility form or portal before scheduling
- verify the tester's certification and gauge calibration workflow for that jurisdiction
- ask the tester who is responsible for submission
- request a copy of the final submitted report the same day
- confirm utility acceptance a few business days later
Property owners and managers who treat backflow paperwork like asset records usually have fewer surprises than the ones relying on memory, loose invoices, or "the vendor probably handled it."
The bottom line
A rejected backflow test report usually means the utility could not verify the record well enough to close compliance. That can be caused by missing fields, wrong assembly details, missing signatures, missing calibration records, the wrong submission method, or a tester who is not aligned with the local utility's process.
The good news is that many rejections are fixable. Get the exact reason, compare the paperwork against the device, involve the tester quickly, and confirm acceptance after resubmission.
And if the real issue is that your current vendor keeps generating paperwork problems, it may be time to find a local backflow tester who already understands the jurisdiction you are working in.
Sources
This article references guidance and regulations from authoritative sources including:
- U.S. Environmental Protection Agency (EPA) - Overview of the Safe Drinking Water Act
- American Water Works Association (AWWA) - Cross-Connection Control & Backflow Prevention resources
- Washington State Legislature - WAC 246-292-036: Backflow preventer inspection and field test report content
- Washington State Department of Health - Cross-Connection Control and Backflow Prevention
- Austin Water - Backflow Prevention Assembly Tester Information
- Seattle Public Utilities - Backflow Assembly Testing
- Philadelphia Water Department - Cross-Connection & Backflow Compliance
- Centers for Disease Control and Prevention (CDC) - Preventing Drinking Water-Related Illnesses
Last updated: May 29, 2026