Backflow Test Reports and Utility Submittals for Plumbing Shops

A backflow test is not finished when the gauge comes off the assembly.

It is finished when the water supplier, property owner, customer contact, and any authority that has to receive the report can trace the same record: which assembly was tested, where it sits, who tested it, what the numbers were, what failed, what was repaired, what was retested, and when the report was submitted.

That is where small plumbing shops lose time. The field work may be fine, but the paperwork is scattered:

• the customer's annual notice is in an email thread;
• the assembly serial number is in a blurry phone photo;
• the tester certificate number is written differently on each report;
• the utility portal confirmation is not saved to the job file;
• the customer thinks the shop "sent it in," but the water supplier rejects the report for a missing field;
• a failed test turns into an argument because the quote did not explain repair and retest pricing.

The fix is not a thicker binder. It is one clean workflow that connects the work request intake, plumbing quote, plumbing work order, plumbing service report, inspection report, and construction submittal form. The test report is the compliance record. The job file is how your shop proves the record was built correctly.

Treat the utility notice as a job document

Backflow testing usually starts with a utility notice, not a plumbing diagnosis. A restaurant, small office, dentist, apartment owner, irrigation customer, car wash, medical office, shop, or warehouse receives a notice that an assembly is due for periodic testing, often annual under the local program. The owner forwards it to you and asks, "Can you take care of this?"

Your intake form should capture the notice before anyone quotes the job.

AWWA's cross-connection policy statement says water utilities or other responsible authorities should implement and maintain cross-connection control programs, and EPA's Cross-Connection Control Manual explains the basic public-health problem: a pressure change can let non-potable water or contaminants move back into a potable system. For a small plumbing shop, the practical lesson is that the local program controls the report format, tester credential rules, timing, and correction path. Your paperwork has to follow that program, not a generic national form you found years ago.

Put the notice in the job file. If the customer cannot provide it, have the intake note say that the shop is working from customer-provided account details and that the utility may require additional information. That one note prevents the common argument where the customer thought you were responsible for identifying every assembly on the property without being given the utility record.

Quote the testing work and the failure path separately

The easiest backflow dispute is also the most avoidable:

"You said the test was $125. Why is the invoice $480?"

Testing, repair, and retesting are different scopes. The plumbing quote estimate should separate them before the technician rolls.

Do not hide all of that inside "backflow certification." Some customers use that phrase loosely, but many programs work from test reports, maintenance reports, portal submissions, or completion records. A failed assembly still took technician time, gauge setup, access coordination, and reporting judgment, even if the final accepted record has to wait for repair and retest.

If a repair changes the price or scope, use a change order before the tech rebuilds the assembly. If the customer wants a replacement device instead of a repair, move that into a revised plumbing proposal or plumbing contract agreement. Backflow work looks small, but a failed reduced pressure assembly on a commercial service can quickly become a permit, shutdown, parts, and replacement job.

This is the same paperwork discipline as signed change orders: test the approved scope, price the new scope, then get written approval before the extra work starts.

Put the tester, gauge, and assembly on the work order

The plumbing work order should not say only "annual backflow test."

It should dispatch a specific certified tester to a specific assembly with a specific reporting requirement.

Use fields like these:

ASSE International's backflow prevention tester certification material covers cross-connection control programs, test gauges, assembly field-test procedures, troubleshooting, documentation, tester responsibilities, and safety. Austin Water also points testers to the University of Southern California's Cross Connection Manual for approved testing methods. Your work order should reflect that level of procedure. It tells the technician what standard of documentation is expected before the job is closed.

If the assembly is in a vault, meter pit, mechanical room, or congested commercial space, pair the work order with a site assessment checklist or safety inspection checklist. If the work involves digging to expose or replace a buried assembly, use the utility locate photo log workflow before the shovel or saw touches the ground.

Build the field report around identity, results, repairs, and submission

Your backflow test packet needs to prove four things. The utility form or portal controls the official fields; your shop file fills in the job context around that form.

1. The assembly identity is right

Record enough detail that the water supplier can match the report to its inventory and the customer can find the same assembly next year.

Capture:

• customer name and service address;
• utility account or premise ID if provided;
• assembly ID, hazard ID, tag number, or inventory number;
• device type, manufacturer, model, size, and serial number;
• exact location, including building, room, wall, meter, irrigation zone, fire line, or fixture served;
• installation orientation or unusual access condition when useful;
• photo of the assembly and tag before testing.

"2 inch RP in back room" is weak. "2 inch RP, Watts 909, serial ######, domestic service, west wall of Suite B mechanical room, tag 23-1197" is a report a future tester can use.

2. The test results are complete

Use the local utility's approved form or portal fields. Do not abbreviate away required values just because your shop knows what they mean.

For many reports, the field data may include:

• date and time of test;
• initial test result;
• check valve readings;
• relief valve opening point, where applicable;
• air inlet or shutoff readings depending on assembly type;
• pass/fail status;
• tester name, certification or license number, employer, phone, and signature;
• gauge make/model/serial or ID;
• gauge calibration date;
• comments required by the utility or state program.

Do not treat the gauge field as optional unless the program says it is optional. A calibrated test kit is part of the credibility of the report. If the utility rejects reports for expired gauge calibration, the service ticket should not be closed until the gauge record is fixed.

3. Failed tests have a repair and retest trail

The failed-test path should be visible.

Write:

• what failed;
• whether the assembly was cleaned, rebuilt, repaired, or left failed;
• parts or kit numbers used;
• who approved repair work;
• whether the repair required shutdown, permit, replacement, or return visit;
• retest date and final result;
• whether the utility requires a failed report, repair report, passing retest, or all of them.

This is where local rules vary. Washington's drinking-water rule for cross-connection control requires purveyors to build testing, inspection, quality-control, reporting, and recordkeeping requirements into their programs. Austin Water tells testers to submit complete Test and Maintenance Reports through its online system and lists the fields that must be included. NYC DEP, Seattle Public Utilities, Denver Water, and other suppliers each publish their own forms, portals, schedules, and approval paths.

So the shop rule should be simple:

The technician records the failed result, the office follows the utility's failed-report rule, and the customer receives a written repair or replacement path.

Do not bury the failure in a phone call. Use the plumbing service report for the customer-facing work summary and the plumbing inspection report when the finding needs a stronger condition record with photos, readings, and recommendations.

4. The submittal is saved, not just sent

The submittal record matters because customers usually judge the job by the utility's status.

Your office should save:

• final signed test report;
• portal confirmation, email receipt, or upload screenshot;
• date submitted;
• person who submitted it;
• utility response or rejection if any;
• corrected resubmittal if required;
• customer handoff email with the final report attached;
• next due date or recommended reminder date.

For larger commercial customers, send the report with a construction transmittal or submittal form, even if the job is small. That gives the property manager a clean "sent to whom, when, for what" record instead of a loose PDF attachment.

The tag is a field cross-reference, not the whole record

Many assemblies carry a field tag. Some utilities require tags. Some customers expect them. Some testers use shop tags even when the program record lives online.

The tag should never be the only record.

Use it as a field cross-reference:

If the tag is missing, faded, wrong, or belongs to a different assembly, photograph it and note the correction. Do not assume the old tag is correct. A wrong tag can send next year's tester to the wrong device and can cause the office to submit the right test under the wrong asset ID.

For properties with multiple assemblies, create a simple asset list in the general inspection report: device ID, location, type, size, serial number, water supplier account, due month, and service notes. That list turns annual testing from a hunt into a route.

Special properties need special notes

Some accounts are not just "test and go."

This is where the work order safety briefing belongs in plumbing work. A tester opening a fire riser, entering a vault, climbing to an equipment area, or shutting down water to an occupied business needs more than a calendar event.

A one-page backflow submittal packet

For a small shop, the cleanest process is a one-page packet used on every annual test.

The packet can be digital. What matters is that each step is tied to the same job number and assembly ID.

For single-device customers, this keeps annual testing from becoming a loose reminder. For multi-device accounts, it creates a repeatable account file. The next year, your dispatcher already knows the device count, locations, usual access problem, preferred shutdown window, and which reports the utility accepted.

That is what customers are really buying when they ask you to "handle the backflow." They are not just buying a gauge reading. They are buying a finished compliance handoff.

Sources

• American Water Works Association, Cross-Connection Policy Statement
• AWWA M14-2024, Backflow Prevention and Cross-Connection Control: Recommended Practices, Fifth Edition
• U.S. EPA, Cross-Connection Control Manual, EPA 816-R-03-002
• ASSE International, Backflow Prevention Assembly Tester certification outline
• USC Foundation for Cross-Connection Control and Hydraulic Research, Manual of Cross-Connection Control and tester resources
• Washington Administrative Code 246-290-490, Cross-connection control
• Austin Water, Backflow Prevention Assembly Tester information
• Seattle Public Utilities, Backflow Assembly Testing
• New York City Department of Environmental Protection, Cross-Connection Controls
• Denver Water, Cross-Connection Control and Backflow Prevention Program
• Texas Commission on Environmental Quality, Backflow Prevention Assembly Tester licensing

---

This article is for general information and is not legal, engineering, plumbing-code, licensing, or compliance advice. Verify all requirements with the water supplier, authority having jurisdiction, state licensing board, engineer, or qualified counsel before acting.