Nearly every deadline a business carries was written by a government. A board sets your renewal, an agency sets your filing date, a court sets your window, or a contract you signed and read sets a term. Backflow testing belongs to none of those categories, and that is the whole reason it behaves so strangely. The requirement to test the assemblies on your property is imposed by the company that sells you water — your water purveyor — acting under a state drinking-water program that obliges the utility, not you, to run a cross-connection control program. The duty arrives second-hand. It was handed down.
Two consequences follow, and both catch competent property teams. The first is that there is no public register you can search to find your own due date. It is not on a state licensing portal or a federal database; it sits in your utility's records, and most owners learn about it from a letter in the post. The second is that the consequence for ignoring it is aimed at something other than the thing that lapsed. A boiler certificate expires and the boiler stops. An elevator permit expires and the elevator stops. A quarter-inch test cock on an irrigation line goes untested, and the remedy available to the utility is to shut off water to the entire premises — a device worth a few hundred dollars closing a building worth millions.
Underneath both sits a third oddity. This obligation is not held by a person or a company. It is bolted to a pipe. It never renews and cannot be transferred, and it conveys with the building, which means a new owner or an incoming tenant inherits every assembly's clock on day one — including the assemblies nobody has told them about. Here is how backflow compliance actually works to track, and how to keep every assembly tested and every report filed.
General information, not plumbing or legal advice — requirements are set by your water purveyor and your state's drinking-water program. See the sources in section 11.
1. What is backflow prevention testing?
A backflow prevention assembly is a mechanical device installed where your plumbing connects to the public water main, at any point where something other than clean drinking water could be pulled or pushed back into the supply. That point is called a cross-connection, and you have more of them than you would guess: an irrigation system standing in fertilizer-treated soil, a fire-sprinkler line full of water that has sat stagnant for years, a boiler dosed with treatment chemicals, a soda-fountain carbonator, a mop sink, a dental chair, a car wash. When pressure in the main drops — a hydrant opens, a line breaks — water can travel the wrong way. The assembly is the thing standing between that and the neighborhood's drinking water.
Because it is mechanical, and because it fails silently, it has to be proved working on a schedule rather than assumed working. That proof is a field test performed by a certified backflow assembly tester, and the resulting report is what your water utility keeps on file as evidence that the connection is protected. Remindax helps you track each assembly's test-due date and whether its report has been filed, and reminds you before each falls due; it doesn't test assemblies, certify testers, calibrate gauges, or file reports with your purveyor.
If you are on the other side of this work — the contractor performing the tests rather than the owner receiving them — the obligations you carry are different ones, and they are covered on plumbing license and backflow tester credential tracking: the license to work, the tester's own certification, and the calibration of the gauge that produced the readings. Those are credentials that travel with people and businesses. This page is about the obligation that stays with the building after everyone has gone home.
1.1 What compliance involves, per assembly
- →A test at least annually. Each assembly is field-tested at least once every twelve months, and separately at installation, after any repair, and generally after it is relocated. Some purveyors require it more often for higher-hazard connections.
- →Performed by a certified tester. The person doing it holds a state-recognized backflow assembly tester certification. Being a licensed plumber is not the same qualification, and in several states the tester credential is licensed separately.
- →A report that reaches the water utility. The completed test-and-maintenance report is filed with the purveyor. This is a transmission, not a filing you keep — the utility's copy is the one that determines your status.
- →Tracked device by device. Each assembly is its own compliance object, usually carrying a serial number and an identifier the utility assigns to it, with its own due date independent of every other device on the property.
Frequencies, tester qualifications, report formats and enforcement all vary by water purveyor and by state drinking-water program. Confirm what applies to your properties at the sources in section 11. This is general information, not plumbing or legal advice.
This is the structural fact worth carrying through the rest of the page. Federal guidance on cross-connection control is addressed to public water systems, and one of the things it helps them do is draft a local ordinance. State drinking-water programs then require utilities to operate such a program and give them the authority to enforce it against their customers. So by the time the requirement reaches you, it has passed through two hands and become a condition of water service — closer in kind to a term of supply than to a permit. Which is why two identical buildings a mile apart can owe genuinely different things: not because one is in a different state, but because they buy water from different sellers.
2. How often does a backflow preventer need testing?
At least annually — and typically measured as no more than twelve months from the last test rather than from a calendar anniversary. Also at installation, after repair, and usually after relocation. Some purveyors test higher-hazard connections more often.
A certified backflow assembly tester recognized by your state or purveyor. Several states license or accredit this separately from the plumbing license.
A test-and-maintenance report is completed and signed by the tester and provided to the water utility. Many purveyors use their state's prescribed form and set their own submission deadline after the test.
A failed assembly is repaired and retested, and the utility is typically notified. Where an unprotected hazard is found, a purveyor may withhold or discontinue service to that connection until it is corrected.
The first line of that box hides a practical trap. Because the interval is commonly measured from the date of the last test, the due date drifts. Test an assembly on March 3 one year and February 24 the next because that is when the tester could come, and you have quietly moved that device's deadline nine days earlier for every year that follows. For a property manager doing that across forty assemblies over five years, no two of them are due in the same week any more. Nobody decided this; it is the arithmetic of a rolling interval meeting a real scheduling calendar. What it means for tracking is that the annual backflow test cannot be handled as an annual event on a company calendar. It is forty individual dates that each move a little, every year, in a direction nobody records.
The step that fails most often is not the test. It is the report. An assembly can be tested on time, by a properly certified tester, and pass cleanly — and still sit in the utility's records as overdue, because the paperwork never arrived. This is worth separating carefully from the more familiar problem of keeping proof. Many compliance records exist to be retained: you hold onto them, and one day an inspector asks. A backflow test report is not that. It has to be delivered, to a named recipient, who maintains the only version of your status that counts. You can be fully compliant in fact and non-compliant in the records that matter, and nothing on your property will indicate which.
Notice who that recipient is. In most compliance relationships the body that holds your file and the body that can hurt you are the same organization, and you accept that because it is a regulator doing a regulator's job. Here the party you must report to is a commercial supplier you buy something from, and the leverage it holds is the ability to stop supplying it. That combination — the record-keeper and the utility being one and the same — is what gives a missed backflow test report to the water utility a sharper edge than the paperwork itself suggests.
3. Why tracking backflow assembly dates matters
Four properties combine here that do not usually appear together, and each one defeats a different part of how properties normally keep track of their obligations:
There is nowhere to look it up
No state portal or national register lists your assemblies or their due dates. The authoritative record is your purveyor's, and most owners find out where they stand when a letter arrives.
The report is a separate act
A passed test that never reached the utility leaves the assembly showing as overdue. Tested and reported are two states, and only one of them is visible on site.
A certified tester has to be booked
Maintenance cannot do this on the morning it is due. It needs a certified tester with an appointment, and enough slack afterwards to repair and retest a failure.
The penalty is out of proportion
The failed item is one valve. The lever available to the utility reaches the whole premises, which makes an overlooked device a continuity problem rather than a paperwork one.
The fourth point is the one that changes how seriously the first three should be taken, so it is worth stating plainly. Most compliance enforcement is contained: it acts on the thing that failed. A vessel that has not been inspected is taken out of service, and the rest of the building carries on. A device that has not been recertified is taken out of use until it is corrected, and the shop stays open. That proportionality is so consistent across regulated equipment that property teams stop noticing it as a design choice, and start treating it as a law of nature — a device problem stays a device problem.
Backflow is the exception, for a reason that is defensible once you see it from the utility's side. The purveyor is not primarily trying to punish you; it is trying to protect the main. It has no way to isolate the untested assembly on your irrigation line without cutting the service that feeds it, and it has a public-health duty to everyone downstream of a possible contamination. So the remedy it reaches for is the only one it actually controls: the connection itself. From your chair that looks wildly disproportionate. From the main it is the minimum action available.
Almost every other date a business tracks arrives attached to a document somebody obtained on purpose. A license was applied for, a policy was bought, a permit was issued. Backflow assemblies are not like that. They get installed by a contractor during a fit-out, added with an irrigation system, put in when a fire line goes up, and every one of them silently creates an annual obligation that outlives the project and the people on it. A building can quietly accumulate assemblies for decades. That is why the first task on a new property is almost never a renewal — it is an inventory, and until it is done you cannot know how many deadlines you are already carrying.
4. Who needs to track backflow testing
Anyone responsible for a premises with a protected connection carries this, whoever ends up performing the test — and the more assemblies there are, the less likely it is that one person can name them all:
Commercial property & facilities managers
The classic version of the problem: dozens of devices across a portfolio, each with its own drifting date, each answering to whichever utility serves that address.
Learn More
Multi-family & HOA
Where the assemblies are spread across landscaping, mechanical rooms and fire lines, and the shutoff would land on residents rather than on an operation that can close for a day.
Fire-suppression & irrigation
Two systems that generate assemblies as a side effect of being installed, and whose own service intervals have nothing to do with the assembly's separate annual date.
Learn More
High-hazard premises
Medical, dental, dialysis, laboratory and chemical sites, where the hazard classification can pull the interval tighter than annual and the assemblies are rarely all in one room.
Learn More
Plumbing & mechanical contractors
Holding schedules for many clients at once — and carrying a second calendar of their own, for the credentials that let those tests count in the first place.
Learn More
New owners & incoming tenants
Who inherit every assembly on the site the day they take it on, at whatever point each device happened to be in its cycle, with no handover document that reliably lists them.
The thread running through all six is that responsibility does not follow the work. Whoever performs the test, the duty to have it done and reported stays with the premises and whoever holds it — and that is a different distribution of accountability from most of a building's calendar, where the party doing the work usually also owns the consequence of not doing it. For the wider view of every recurring premises obligation alongside this one, see certification tracking software.
5. What happens when a backflow test is missed
The sequence is usually gradual and then abrupt. A purveyor that finds an assembly overdue generally writes first, giving a period to get it tested. If nothing arrives, it writes again, more firmly, and names a date. What sits at the end of that sequence is not a fine schedule — or rather, not only one. It is the authority to discontinue water service to the connection, and to withhold it until a passing test is on file. Fines and, in the event of an actual contamination, real liability sit alongside that, but they are not the part that reorganizes a facilities team's week.
What makes this worth systematic attention rather than occasional attention is how ordinary the path into it is. Almost nobody arrives at a shutoff notice by deciding not to test. They arrive by one of four routes, none of which feels like negligence at the time.
The report that never went in. The tester came, the assembly passed, somebody was handed a form in a plant room. In the utility's file, nothing happened. This is the failure that most rewards tracking, because it is the only one where the work was done and paid for and the exposure remains complete. It also cannot be found by inspection: walking the property tells you the device is there and looks fine, and tells you nothing at all about what your purveyor believes.
The assembly nobody knew about. A fire line went in nine years ago, or an irrigation zone was added behind the building, and the device that came with it was never written down anywhere the current team can see. It has been generating an annual obligation ever since. The letter that eventually arrives is not a warning about a date you missed; it is an introduction to equipment you did not know you owned.
The failure with no time left behind it. The test was booked correctly, near the due date, and the assembly failed — which is a normal outcome for a mechanical part with rubber in it that has been sitting in a wet pit for a year. Now parts have to be sourced, a repair scheduled, and a retest arranged, and all of that has to happen inside whatever grace the purveyor allows. Booking the test on time is not the same as leaving room for it to go wrong.
The tester whose credential had lapsed. The rarest and the most frustrating, because everything on your side was right. A test performed by someone without a current certification, or with a gauge whose calibration had expired, may not be accepted — and the year of protection you believed you had turns out to be undocumented. That risk lives on the contractor's side of the relationship, which is exactly why it is tracked from the tester's chair as well as from yours.
This is what separates a backflow lapse from most of a building's other exposures. A missing fire-extinguisher tag is visible. An expired certificate on an elevator wall is visible. Here the only place your compliance status exists is inside the utility's records, and you have no live view into them. There is nothing on the device that says whether its last report was received, nothing in the building that changes when it wasn't, and no routine walk-through that would ever surface it. The gap runs from the day the paperwork went astray until the day a letter arrives — which can be most of a year — and for that entire period the property looks, to everyone standing in it, completely fine.
Set against that, the tracking problem is small and entirely solvable. Every one of the four routes above is defeated by the same two things: knowing what assemblies exist, and knowing for each one both when it is next due and whether its last report was actually filed. Neither requires expertise. They require that the information exist somewhere other than in the memory of whoever happened to be on site.
6. How Remindax keeps every assembly tested and reported
The shape of the problem is a long list of individual devices, each with a date that drifts and a second state that nothing on site reveals. Four pieces address exactly that:
Every assembly in one dashboard
Each device with its location, its serial and utility-assigned number, its backflow test due date and whether its report has gone in — status at a glance. Pairs with Locations and Equipment asset profiles.
Lead time, not a due-date alarm
Staged alerts far enough ahead to book a certified tester and still absorb a failed test and a retest — by Email, SMS, and WhatsApp, to the people who actually make the booking.
Tested and reported held apart
The test being done doesn't close the item. The report reaching your purveyor is tracked as its own step, so a passed test with missing paperwork can't read as finished.
Across every property
A portfolio's assemblies in one place, grouped by site, so a device at a building nobody visits often carries the same visibility as one in the head-office plant room.
Remindax tracks dates. It is not a backflow testing service, not plumbing-dispatch software, and not a utility cross-connection control platform — it doesn't test assemblies, certify testers, calibrate gauges, or file reports with your water purveyor. What it does is make sure each assembly's date and its report status surface before the utility raises them. For the wider picture see office admin tracking or compliance tracking — tracking and reminders, not facilities management and not a GRC suite.
7. Why spreadsheets fail for backflow tracking
A spreadsheet gets the first part right and then fails at the second, which is why it survives so long before anyone notices. Listing assemblies in rows with a date beside each is a genuinely reasonable model of the inventory. The trouble starts with what goes in the status column, because the obligation has two states and the column has one. Somebody writes the date the tester came. That records that a test happened. It says nothing about whether the report reached the purveyor, and the sheet will go on presenting that row as complete for the next twelve months.
Then the dates drift. Because the interval runs from the last test rather than from a fixed anniversary, every row's next-due date has to be recalculated after every test, by hand, correctly, every year. In practice the column gets bumped forward a year and the drift accumulates silently until a device is being tested thirteen or fourteen months apart. Nothing in the sheet objects, because a spreadsheet has no opinion about intervals — only about the numbers someone typed.
And it cannot help with the thing that matters most, which is lead time. A date in a cell is a fact about the future that nobody is looking at. It does not know that a certified tester needs booking three weeks out, that a failed assembly needs parts and a second visit, or that the person who used to walk this list left in the spring. An automated register holds each assembly's next test date, recalculates from the test that actually happened, keeps the report as a separate open item until it is filed, and tells the right person early enough that a failure is still recoverable — which is the only version of this that keeps the water on across more than one address.
- ✗One cell that can't tell tested apart from reported
- ✗Next-due dates recalculated by hand after every test
- ✗No lead time to book a tester or absorb a failed retest
- ✗Assemblies added during fit-outs that never reach the list
- ✗A file that leaves with the person who maintained it
- ✓Test and report tracked as two states, not one
- ✓Each device's next date carried forward from the test that happened
- ✓Staged reminders early enough to book, fail, repair and retest
- ✓Every backflow assembly due date held per property, with its utility number beside it
- ✓Alerts by Email, SMS, and WhatsApp to more than one person
8. Key takeaways
- ✓The requirement comes from your water purveyor as a condition of service, under a state drinking-water program that obliges the utility to run a cross-connection control program — so there is no central register listing your own due date.
- ✓Each assembly is tested at least annually by a certified tester, plus at installation and after repair, with the interval usually measured from the last test rather than a calendar anniversary.
- ✓The test report has to reach the utility to count. A passed test that was never filed leaves the assembly overdue in the only records that decide your status.
- ✓The enforcement lever is aimed past the device: a purveyor can discontinue water service to the premises until a passing test is on file, which makes one small valve a continuity risk.
- ✓The obligation attaches to the property rather than to a person or a company, so it conveys with the building — and the first job on a new site is an inventory, not a renewal.
Never risk a shutoff over a missed test
Track every assembly's test and report — automatically. Remindax holds each device's date and report status per property and reminds the right people with enough lead time to book a certified tester.
GDPR-ready · AWS secure cloud · Encrypted storage · Setup in under 5 minutes
9. Frequently Asked Questions
At least annually, and also at installation and after any repair. The interval is commonly measured as no more than twelve months from the last test rather than from a fixed calendar date, so a device's due date drifts as testing dates move. Your water purveyor sets the frequency that applies, and some higher-hazard connections are tested more often.
Your water purveyor does, as a condition of water service, acting under a state drinking-water program that requires utilities to run a cross-connection control program. That is why there is no national register listing your own due dates - the authoritative record is the utility's, and two nearby buildings served by different utilities can owe different things.
Yes. The completed test and maintenance report has to reach your purveyor to count. A passed test that was never filed still leaves the assembly showing as overdue in the only records that decide your status, and nothing on the property indicates that it happened.
A certified backflow assembly tester recognized by your state or your water purveyor. Several states license or accredit that credential separately from the plumbing license, so holding a plumbing license is not automatically the same qualification.
A purveyor generally writes first with a period to comply. Where it is not resolved, the utility can discontinue water service to the connection until a passing test is on file - alongside fines, and, in the event of an actual contamination, liability.
Per assembly. Each device is its own compliance object with its own due date, usually carrying a serial number and an identifier the utility assigns to it, so a single property can hold many separate deadlines.
In practice yes. The obligation attaches to the assemblies on the property rather than to a person or a company, so a new owner or tenant takes on every device at whatever point it happens to be in its cycle. An inventory is usually the first task, because handover documents rarely list them all.
No - Remindax tracks each assembly's test-due date and whether its report has been filed, and reminds you. Testing is performed by a certified tester and reports are filed with your water purveyor.
Yes - every assembly across a portfolio in one place, grouped by site, each with its own reminders, its utility-assigned number, and its own report status.
Yes - a forever-free plan, no credit card required.
Backflow requirements are set by your water purveyor under your state's drinking-water program, and they differ from one utility to the next — frequencies, accepted tester credentials, report forms and enforcement all vary. Remindax tracks the dates and reminds you; it doesn't test assemblies, certify testers, or file reports. Confirm what applies to your properties at the sources below; this is general information, not plumbing or legal advice.
11. Sources & references
This page summarizes public requirements and isn't plumbing or legal advice. Cross-connection control is administered locally: your water purveyor sets the requirements and deadlines that actually apply to your property, under your state's drinking-water program. The state sources below are included to show how much the details differ from one program to the next — confirm your own with your purveyor.
- •EPA — Cross-Connection Control Manual (EPA 816-R-03-002) — the federal technical reference, written for health officials and water systems; it includes model ordinance provisions and program administration, which is how the requirement reaches customers.
- •Washington State Department of Health — Cross-Connection Control and Backflow Prevention — a state program's rules on testing at installation, after repair and at least annually, and on purveyor authority over service.
- •TCEQ — Cross-Connection Control and Backflow Prevention (Texas) — including the test and maintenance report form and the twelve-months-from-last-test framing of the annual interval.
- •California State Water Resources Control Board — Backflow Tester and Cross-Connection Control Specialist certification — how one state recognizes and accredits the tester credential that a valid test depends on.
- •New York State Department of Health — Backflow prevention assembly testing FAQ — a plain-language account of the customer's side, including the periodic letter from the water system requesting a test.
- •Your water purveyor's cross-connection control program — the authority that actually sets your testing frequency, your accepted testers, your report form and your submission deadline, and the only place your current status is recorded. Ask them directly which assemblies they have on file for your address.