What to Do If Your Utility Says the Backflow Test Report Lists the Wrong Assembly Type
If your utility says the backflow test report lists the wrong assembly type, it is usually a device-identification and compliance-record problem.
Utilities track which type of assembly protects which hazard at which property. If the report says DCVA when the utility record says RPZ, or the report says one type when the site actually has another, the utility may treat the account as unresolved even if the field test itself was completed.
For broader context, keep why backflow testing is required, why your backflow test report was rejected, and our FAQs nearby.
Why utilities care about the assembly type so much
Property manager and certified backflow tester comparing a backflow test report that lists the wrong assembly type beside a commercial reduced pressure assembly, realistic daylight, no readable text
This is not just a naming issue.
EPA says the Safe Drinking Water Act protects public health by regulating the nation’s public drinking water supply. CDC likewise says harmful germs or chemicals can get into drinking water at the source or while the water is being piped to homes and businesses. Cross-connection control programs use test reports to document that the right protective device is installed, tested, and tied to the right property record.
Official requirements show how specific this gets.
Washington’s WAC 246-292-036 says a completed field test report must include the assembly’s physical location, assembly type, manufacturer, model, serial number, and size. Austin Water requires each Test and Maintenance Report to include the assembly’s physical address and location on the premises, plus the manufacturer, size, model number, and serial number. Seattle Public Utilities says reports must be completed according to its guidelines and the Washington code. Philadelphia’s official backflow test and maintenance record includes fields for location of assembly, manufacturer, model, serial number, size, and type.
Utilities need that detail because assembly type is tied to protection decisions.
Portland Water Bureau says the location of the assembly, service size, and hazard level of the connection determine which backflow assembly you should use. It also explains that a reduced pressure assembly can be used on low- or high-hazard connections, while a double check valve assembly is commonly used where the hazard does not pose a health risk.
So when a utility flags the wrong type, it may be asking a deeper question:
Was the right device actually tested for the right hazard?
For local context, our city pages for Austin, Texas, Seattle, Washington, and Philadelphia, Pennsylvania are useful starting points.
What a wrong assembly type usually means in practice
A wrong-type notice does not automatically mean the assembly failed. More often, it points to one of these situations:
1. The tester selected the wrong device type on the report
This is the simplest version. The tester may have clicked the wrong option in a portal or copied the wrong type from an older record.
2. The utility still has an old assembly type on file
If a property used to have one device type and now has another, the annual report can look wrong even when the current report reflects the actual assembly on site. This is especially common after replacement work or reconfigured plumbing.
3. The wrong assembly on a multi-device property was documented
Commercial sites, HOAs, schools, and mixed-use properties often have more than one assembly: domestic, irrigation, or fire-related. A test can get attached to the wrong record if the location description is weak.
4. The device category affects the utility’s hazard logic
An RP-type assembly and a DC-type assembly are not interchangeable in every program. If the hazard classification on file suggests one level of protection but the report shows another, the utility may stop and ask for clarification before it closes the record.
5. The report exposed a bigger record problem
Sometimes “wrong type” is just the first visible symptom: an outdated utility record, an unreported replacement, or a misidentified service line.
If the utility may be mixing up the device identity more broadly, also read what to do if your utility says the serial number on your backflow test report does not match their records and what to do if your utility says the backflow test report was filed under the wrong address.
What to do immediately when the utility flags the wrong type
Close-up of a certified backflow tester checking an assembly tag and test report while a property manager reviews utility records on a laptop, documentary style, no readable text
Move in this order.
1. Ask the utility what type it has on file
Use direct wording:
“What assembly type, location, and identifying details do you currently have on file for this address and this device record?”
You need the utility’s version before you can tell whether the issue is a typo, an old record, or the wrong assembly altogether.
2. Get the exact report that was submitted
Ask the tester for the actual filed copy, not a paraphrase. Confirm:
- service address
- physical location of the assembly
- assembly type
- manufacturer and model
- serial number
- size
- proof of submission if available
If the tester filed through a portal, ask for the PDF export or screenshot of the exact entry.
3. Verify the assembly on site
Take clear photos of:
- the full assembly
- the tag or nameplate
- the surrounding location
- any room label, riser label, irrigation marker, or service note that proves which line the device protects
That helps separate a report typo from a real device mismatch.
4. Ask whether the utility sees this as a report correction or a record correction
Do not stop at “wrong type.” Ask:
“Do you need a corrected report, an update to the device record, a facility update, or a new test tied to the correct assembly?”
Utilities do not all separate annual testing and device-record updates in the same way.
5. Confirm whether the issue affects the accepted level of protection
If the utility’s concern is just the wrong label in the form, a corrected report may solve it. If the installed device type does not match the hazard or the utility file, the problem may be bigger than the paperwork.
If the assembly was replaced or reclassified recently, review how to update utility records after replacing a backflow preventer before assuming a corrected PDF will close the loop.
When a corrected report is probably enough
A corrected report may be enough when:
- the physical assembly on site is clearly the right one,
- the utility agrees the record is otherwise correct,
- the wrong type appears to be a data-entry error,
- and the device location, serial number, model, and size all line up.
In that situation, the fix is often:
- confirm the actual assembly type on site,
- have the tester resubmit the corrected report,
- get confirmation that it posted to the right record.
If the mismatch is only in the report label, clean paperwork may be enough.
When the problem is bigger than a report typo
A corrected report may not be enough when:
- the utility record still shows an older device type,
- the assembly was replaced without the record being updated,
- the wrong line or wrong assembly was tested,
- the property has multiple device types and the report was attached to the wrong one,
- the hazard classification suggests a different level of protection than the reported device,
- or the utility believes the installed assembly itself may not match what the site requires.
Portland’s guidance says assembly choice depends on location, service size, and hazard level. That means a type mismatch can raise a real compliance question, not just a clerical one.
If a utility expected a higher level of protection for a particular hazard and the report shows a different assembly type, it may want more than a corrected report: supporting photos, updated inventory records, a facility review, or even a new test tied to the correct assembly record.
Philadelphia’s official test form shows why utilities slow down here: type is tied to the facility, address, account or meter number, and location of assembly.
If you are dealing with a complicated site, utility-specific pages such as Austin Water backflow testing and Philadelphia Water Department backflow testing are worth reviewing before you push the tester to “just resubmit it.”
A simple checklist to prevent this next year
Organized compliance binder with assembly photos, test reports, and a property manager confirming corrected utility records on a laptop beside a backflow device photo, realistic office lighting, no readable text
The easiest way to avoid wrong-type problems is to treat device identification as part of the test workflow, not as a back-office cleanup step.
Before the tester leaves, confirm:
- the exact service address,
- the assembly’s physical location,
- the assembly type,
- the manufacturer, model, serial number, and size,
- what hazard or system the assembly protects,
- who is submitting the report,
- and how you will confirm the utility accepted it.
For larger properties, keep a simple assembly log with the utility name, address, assembly location, type, make, model, serial number, size, protected system, and last passing test date.
The bottom line
If your utility says the backflow test report lists the wrong assembly type, do not treat it like a harmless wording problem.
Treat it like a record-identification problem with possible hazard implications:
- confirm what the utility has on file,
- compare it against the actual submitted report,
- verify the assembly on site,
- and ask whether the fix is a corrected report, a record update, or something bigger.
Sometimes the answer is simple. Sometimes the wrong type is a clue that the utility file, the report, and the physical assembly are no longer aligned.
The fastest path is getting the utility file, the report, and the physical assembly to point to the same device.
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 - Sample Backflow Preventer Inspection and Field Test Report
- Seattle Public Utilities - Backflow Assembly Testing
- Austin Water - Backflow Prevention Assembly Tester Information
- Portland Water Bureau - How to choose and install a backflow prevention assembly
- Philadelphia Water Department - Form 79-770 Backflow Prevention Assembly Test and Maintenance Record (PDF)
- Centers for Disease Control and Prevention (CDC) - About Drinking Water
Last updated: June 3, 2026