Backflow testing scheduling software for annual deadlines and dense routes

Backflow testing is recurring work with a deadline someone else sets. The water utility, under state and local rules, decides that each assembly gets tested every year, sends the owner a reminder and expects a report back. Your job is to get a certified tester to every assembly before its due date, and to file the paperwork on time.

That sounds simple until you count. A test is short, the addresses are spread across the whole service area, and a large share of the year's work arrives in the same few weeks because the utility mails its reminders in batches. Backflow testing scheduling is mostly a fight against the drive.

Where the deadlines come from

The rule comes from your state and your local water system, not from one national schedule. As one example, the Portland Water Bureau says, as of October 2026, that "State law and Portland City Code require backflow prevention assemblies to be tested at least once each year," that tests must be done "by a state-certified backflow assembly tester," and that the tester submits the report "within 10 business days" (Portland Water Bureau, testing requirements). Residential customers there are told to test "each spring when you receive your reminder letter."

Your rules may differ. Frequency, tester certification, report deadlines and which assemblies are covered vary by state and by water system, so check with the utility that serves each customer. What tends to stay the same is the shape: a fixed annual cycle, a reminder from the utility, and a report deadline after the test.

Why the drive dominates

A residential irrigation assembly or a commercial domestic-water assembly is a short visit compared with most trades. That changes the arithmetic of the day. For a plumber running a two-hour repair, a 25-minute drive is a small share of the day. For a tester running short tests, the drive can be as long as the work.

The number of tests a tester can do in a day is roughly:

Tests per day = H ÷ (T + D)

where H is working hours on the road, T is the average time on site and D is the average drive between stops.

The test did not get faster. The tester got six more tests out of the same day because the stops were closer together. That is schedule density, and in backflow testing it matters more than in almost any other trade because T is so small.

The reminder-letter surge

When the utility mails reminders in waves, demand arrives in waves. Say you hold 2,400 annual assemblies and 60 percent of the owners respond in a 10-week spring window. That is 1,440 tests in 50 working days, or about 29 a day. At 10 tests per tester per day, you need three testers on it full time. At 16, you need two.

Run your own numbers:

Testers needed = (N × S) ÷ (W × P)

where N is assemblies, S is the share that falls in the surge, W is working days in the surge and P is tests per tester per day. The technician capacity calculator does the same kind of sum for a whole board.

Two habits flatten the wave:

1. Book last year's customers before the letters land. You know each assembly's due month from last year's test. A recurring service record with the address and due month lets you offer a time weeks before the reminder arrives, when your board is still open.
2. Fill a street, not a calendar. When one customer on a street books, the neighbours with assemblies due the same season are the cheapest tests you will run all year. Offer them nearby times first.

Booking times a tester can reach

Most backflow customers book in two ways: they call after the reminder letter, or they pick a time online. Either way, the risky moment is the same. A time that is empty on the calendar may not be reachable from where the tester will be.

Picture a tester with tests at 9:00 and 9:40 on the east side. A customer on the far west side asks for 10:15. The calendar is empty at 10:15, so it gets booked. The drive is 45 minutes, so the tester arrives at 11:00, and every test after it slides. Zone days are one fix: east side Monday, west side Tuesday. Zone scheduling is simple and works, but it makes the west-side customer wait for Tuesday even if a tester will be two streets away on Monday afternoon.

The other fix is to check the drive when the time is offered. CrewLink's booking page offers only start times a qualified tech can actually make, counting their other jobs and the drive at that hour from the previous job, not from the shop. Addresses outside every tech's area become an out-of-area request for the office instead of a fake slot. That is the idea behind travel time scheduling. CrewLink is in early access and is built for companies running 5 to 50 trucks.

Commercial accounts and multi-assembly sites

Commercial work behaves differently. A building may have several assemblies: domestic water, fire line, irrigation, a boiler feed. Access goes through a facilities manager, and some tests mean a short water shutdown that the building has to agree to. Fire sprinkler systems can have a backflow assembly on the fire line, which is why fire protection companies often run backflow tests alongside their inspections.

For these, plan the visit length from the number of assemblies on site, and book the shutdown window with the building before you promise a tester's time. A multi-assembly site is a good anchor for a day: put it first, then fill the rest of the day with nearby residential tests.

Repairs found during testing

Some tests fail. The relief valve discharges, a check does not hold, or the assembly needs a rebuild kit. That turns a 20-minute test into a repair visit, often by a licensed plumber, and a retest afterwards. If your testers are also plumbers, decide in advance whether a failed test is repaired on the spot or rebooked. Repairing on the spot protects the customer's deadline but wrecks the rest of the route. Rebooking protects the route but adds a second trip.

A middle path: carry common rebuild kits, allow repairs that fit inside a fixed time box, and rebook anything longer into an open slot near the customer later that week. Track how often each happens. That ratio tells you how much slack the route needs.

The paperwork deadline is part of the schedule

If your utility gives testers a fixed number of days to submit results, the report is a task with a due date, not an afterthought. A tester who runs 16 tests a day and files reports on Friday is carrying up to 64 open reports at once. Build the filing time into the day or the week, the same way you build in drive time.

Common questions

How many backflow tests can one tester do in a day?

Divide hours on the road by the average time on site plus the average drive. With 20-minute tests over 8 hours, a scattered route with 25-minute drives gives about 10 tests, while a clustered route with 10-minute drives gives about 16. The drive moves the number more than the test does.

How often do backflow assemblies need to be tested?

Most water systems require at least an annual test, plus tests after installation or repair, but the rule is set by your state and local water system. Portland, for example, requires a test at least once a year as of October 2026. Check with the utility that serves each customer.

How do backflow companies handle the spring rush?

By booking known customers before the reminder letters arrive, grouping tests by street or neighbourhood, and adding testers for the surge based on the arithmetic of assemblies, surge share and tests per day.

Should failed backflow tests be repaired on the same visit?

It depends on how long the repair takes and what follows it on the route. Small repairs that fit a fixed time box can be done on the spot. Longer rebuilds are often better rebooked into an open time nearby so the rest of the day's tests stay on schedule.