Backflow testing
Backflow testing software built around how you already work.
Annual test notices driven by water authority deadlines, every device on every property, readings per check valve and relief valve, and a report the water purveyor accepts. Set up around how you already test.
The short answer
What software does a backflow testing business need?
A backflow testing company needs software that keeps an inventory of every device at every property, sends test notices ahead of the water authority's deadline, records the readings for each check valve and relief valve with the tester's certification and gauge details, and produces the test report for the water purveyor. Fieldproxy is set up around your own test form and process, with a technician app that works offline.
How the job runs
A backflow testing job, start to finish.
The stages your software has to follow, in the order the work actually happens.
- 1
Notice due
The water authority sets the annual deadline for each device. Customers are notified ahead of it, and those who do not respond get reminded before the date passes. - 2
Test booked
The test is scheduled, often with several devices at one property or several properties on one street, and the tester's route is built around them. - 3
Device tested
The tester confirms the device, records shutoff valve condition and the readings for each check valve and the relief valve, and marks it pass or fail. - 4
Repair and retest
A failed device is repaired (cleaned, rubber kit, springs, or replaced), the parts are recorded, and the device is retested before the result counts. - 5
Report submitted
The completed test report goes to the water purveyor in the format they accept, a copy goes to the customer, and the next year's due date is set.
What to record
The checklist for every job.
Whatever system you run on, these are the fields, readings and photos worth capturing every time. Use it as your checklist.
Per device (the asset record)
- Property address and exact device location (meter pit, mechanical room, fire riser)
- Device type: RP, DC, PVB, SVB, RPDA or DCDA
- Manufacturer, model, size and serial number
- Service type: domestic, fire line or irrigation
- Hazard served and water purveyor account or device ID
- Install date and annual test due date
- QR code tag on the device
Each test
- Tester name and certification number with expiry date
- Test gauge make, serial number and last calibration date
- Line pressure
- Check valve 1: closed tight (yes or no) and pressure drop in psid
- Check valve 2: closed tight (yes or no) and pressure drop in psid
- Relief valve opening point in psid (RP devices)
- Air inlet opening and check valve readings (PVB and SVB)
- Shutoff valves 1 and 2 condition
- Initial result pass or fail, repairs made, parts used, final result after retest
- Photos of the device and the data plate, tester signature
Office and compliance
- Notice sent dates and customer responses
- Report submitted to the purveyor (date and method)
- Gauge calibration certificates on file per gauge
- Tester certification renewals per tester
Where generic software breaks
Why template tools don't fit.
Most field service software is built for a generic service call. Backflow testing companies run a different job.
- The deadline comes from the water authority, not from your last visit. Generic recurring jobs repeat on an interval and lose the actual due date per device, so notices go out late or not at all.
- One property can have a domestic RP, a fire line DCDA and an irrigation PVB, each with its own due date and test form. A job-per-address system has nowhere to keep three devices apart.
- A test report is only accepted with the tester's certification number and a gauge that was calibrated in time. A notes field cannot stop a tech from submitting with an expired gauge.
- Fail, repair, retest is one story for the purveyor. In a spreadsheet the failed test and the retest end up as separate rows, and the report sent shows the wrong result.
How it's set up in Fieldproxy
Your process, set up as it runs.
We map how you run on a 30-minute call and configure it within 48 hours. These are the pieces it is built from.
Every device as an asset with a QR code
Test forms with required readings
Notices that run off the due date
Reports for the purveyor and the customer
AI for backflow testing companies
AI that does the admin, inside your workflow.
The AI agents work on your real jobs and customers, and you confirm anything that matters before it happens.
Books the annual tests
Groups the route
Closes the loop on paperwork
From $649 a month, one price per company, unlimited users.
Every AI agent included, AI credits charged separately. Live in days: the average migration takes about 10 days.
Questions
Backflow testing software, answered.
What software do backflow testing companies use?
Backflow testing companies need software that keeps an inventory of every device per property, sends notices before each water authority deadline, records check valve and relief valve readings with the tester's certification and gauge calibration, and produces the report for the water purveyor. Fieldproxy is set up around your own test forms and process, with an offline technician app on Android and iOS.
Can it track gauge calibration and tester certifications?
Yes. Each test records the gauge serial and calibration date and the tester's certification number. Gauge calibration and tester certification dates are tracked so you are reminded before either expires.
Can it send test notices before the water authority deadline?
Yes. Each device carries its own due date, and automations send notices and reminders ahead of it by email or SMS, then flag any device that is close to missing the deadline.
How much does Fieldproxy cost for a backflow testing company?
Fieldproxy is $649 per month per company with unlimited users, so every tester and office user is included. AI credits are charged separately, and every AI agent is included.
How hard is it to switch from our current system?
It starts with a 30-minute call about your devices, test forms and how you submit reports. Fieldproxy is configured to your process within 48 hours, and moving your properties, devices and test history over takes about 10 days on average.
See it set up for your backflow testing business.
A 30-minute call on how you run. We configure it within 48 hours and show it to you running, with the AI agents working on it.