A backflow test report is more than paperwork — it's a legal document that proves a device is protecting public water from contamination. New testers and property managers often struggle to interpret what the values actually mean. This guide walks through every field on a standard backflow test report, what the numbers indicate about device performance, and how to spot the small mistakes that get reports rejected by city inspectors.
The Anatomy of a Backflow Test Report
Test reports vary by jurisdiction, but every compliant report contains four core sections:
- Identification — who, what, where, when
- Device data — make, model, size, serial
- Test results — measured PSID values
- Certification — tester signature, license, gauge calibration
Missing any of these sections is the #1 reason reports get rejected. Our report errors guide covers the most common rejection reasons in detail.
Section 1: Identification Fields
Property Address
Must match what the city has on file exactly. "123 Main St" vs "123 Main Street" can trigger a manual review and delay processing by weeks.
Customer / Owner Name
The property owner of record, not the tenant or property manager. Cities cross-reference this with utility billing records.
Water Account Number
Required by most large cities. This is the customer's water utility account, found on their water bill. Without it, automated submission systems often reject the report.
Test Date and Time
Must be the actual date of testing. Backdating reports is a serious certification violation and can result in license revocation. Our complete report content guide explains why timestamping matters legally.
Section 2: Device Data
Manufacturer and Model
The brand (Watts, Febco, Ames, Wilkins, Apollo) and specific model number. The model number is critical because it tells the city what type of device is installed and what the test criteria should be.
Serial Number
Unique to each device. This is how the city tracks individual assemblies over time. Mistyping a serial number creates a "ghost" device in city records and orphans the prior test history. Modern software with camera-based serial scanning dramatically reduces this error.
Size
The pipe size in inches (3/4", 1", 1.5", 2", 3", 4", 6", 8", 10"). Affects testing procedure and whether the device meets the property's required level of protection.
Type
The device classification:
- RPZ / RPBA — Reduced Pressure Zone, the highest protection
- DCVA — Double Check Valve Assembly
- PVB — Pressure Vacuum Breaker
- SVB — Spill-resistant Vacuum Breaker
- AVB — Atmospheric Vacuum Breaker (no testing required, but documented)
For when each is required, see our RPZ vs DCVA comparison.
Hazard Level
"High hazard" means contamination would cause illness or death (sewage, chemicals). "Low hazard" means contamination would be aesthetically objectionable but not directly harmful. Some cities require RPZs on all high-hazard cross-connections regardless of other factors.
Section 3: Test Results — The Numbers That Matter
This is where most confusion happens. Every device type has specific values that determine pass/fail.
For RPZ Devices
| Field | What It Measures | Pass Criteria |
|---|---|---|
| Check Valve #1 PSID | Pressure differential across the first check | ≥ 2.0 PSID |
| Check Valve #2 PSID | Pressure differential across the second check | ≥ 1.0 PSID |
| Relief Valve Opening Point | PSID at which relief valve opens | ≥ 2.0 PSID before CV1 closes |
| Buffer (CV1 - Relief Open) | Margin between CV1 reading and relief opening | ≥ 3.0 PSID typical |
If Check Valve #1 reads 1.8 PSID, the device fails — even if everything else looks fine. There is no "close enough" in backflow testing.
For DCVA Devices
| Field | What It Measures | Pass Criteria |
|---|---|---|
| Check Valve #1 PSID | Tightness of first check | ≥ 1.0 PSID, hold for 60 seconds |
| Check Valve #2 PSID | Tightness of second check | ≥ 1.0 PSID, hold for 60 seconds |
For PVB Devices
| Field | What It Measures | Pass Criteria |
|---|---|---|
| Air Inlet Opening Point | PSID at which air inlet opens | ≥ 1.0 PSID |
| Check Valve PSID | Pressure across check valve | ≥ 1.0 PSID after air inlet opens |
Section 4: Apparent Condition Codes
Most reports require the tester to rate the device's visible condition:
- Good — Clean, no leaks, properly installed, accessible
- Fair — Minor cosmetic issues, still functional
- Poor — Significant wear, leaks, accessibility problems, recommend replacement
Document accessibility issues in the notes — they're often the source of follow-up disputes.
Section 5: Certification Block
Tester Name and License Number
Must match the certified tester's official records exactly. License must be current — expired licenses void the report. Our certification renewal guide covers what happens when licenses lapse.
Gauge Make, Model, Serial, and Calibration Date
Most jurisdictions require gauge calibration within the past 12 months. Some require 6 months. The calibration certificate must be available on request. See our gauge calibration guide for state-by-state requirements.
Tester Signature
Wet signature, electronic signature with audit trail, or in some jurisdictions a digital signature certificate. Stamps without signatures are typically not accepted.
Common Errors That Get Reports Rejected
- PSID values that exceed gauge accuracy — Reporting 2.07 PSID when your gauge only reads to 0.1 PSID is a red flag
- Pass result with sub-minimum values — Software should flag this automatically; manual reports often slip through
- Mismatched device type and test fields — Reporting "Check Valve #2" data on a PVB (which doesn't have one)
- Test date in the future — Yes, this happens, often from default-today date pickers and timezone bugs
- Missing customer water account number
- License expired between test date and submission date
What City Inspectors Actually Look For
Inspectors review reports in this order:
- Is the device on file at this address?
- Did the test happen within the required window?
- Is the tester license valid?
- Are the PSID values consistent with a passing test?
- Is the gauge calibration current?
- Is the form complete?
A report that fails any one of these gets bounced back, often weeks later. Software that validates these checks before submission catches 95%+ of issues at the point of testing instead.
Reading Failed Reports
When a device fails, the report should clearly indicate:
- Which specific test condition failed (e.g., "CV1 only held 1.4 PSID")
- Whether repair was attempted on-site
- Recommended next steps (parts, replacement, retest)
- Required retest deadline (typically 30-90 days depending on city)
Our what to do when a device fails walkthrough covers the next steps in detail.
Frequently Asked Questions
Can I edit a report after submission?
In most jurisdictions, no. Submitted reports are legal records. To correct an error, you typically file an amended report referencing the original. Our errors guide covers the amendment process.
What if the city's submission portal won't accept my report?
Most rejections fall into three buckets: missing required field, invalid format, or device not on file. Software with automatic city submission validates against each city's specific requirements before sending.
How long should I keep test reports?
Minimum 5 years in most jurisdictions, 10 years in several states. We recommend keeping all reports indefinitely in cloud storage for liability reasons. Storage is essentially free; lost records are expensive.
Are digital reports as legal as paper?
Yes, in all 50 states. The Electronic Signatures in Global and National Commerce Act (E-SIGN) and the Uniform Electronic Transactions Act (UETA) both recognize digital signatures as legally equivalent to wet signatures. Our digital vs paper deep dive covers the legal framework.
Want to see what a perfect report looks like? Try the FlowCert demo to fill out a sample report and see the validated output instantly.