Keep one register of every assembly you test, with customer, location, type, serial number and the water supplier's due date, send reminders at fixed intervals before each date, and let AI draft the reminder letters and plain-English cover notes. The certified tester produces and signs the results; the water supplier's own filing rules decide where and when they go.
"Backflow testing software" mostly means platforms built for water suppliers, with a smaller number aimed at dedicated testers. A plumbing firm that tests a few hundred assemblies for its own customers usually needs something lighter: a register it trusts, reminders that go out on time and customer paperwork that reads clearly. AI helps with the writing and the tidying. It never touches a test reading.
Throughout, picture a three-van plumbing business with 180 assemblies on its books, spread across 112 customers and four water suppliers. Customers are a mix of restaurants, small offices, apartment blocks and a few irrigation systems. The owner does the admin on Thursday afternoons.
Three ways to hold the register, and when each one fits
Every reminder system starts as a list: which assembly, where, due when. The only real choice is where the list lives.
| Option | What it is | Cost | Fits when | Watch for |
|---|---|---|---|---|
| Spreadsheet and calendar | One row per assembly, a due-date column and a monthly filter. AI-drafted letters are merged or pasted. | Nothing beyond the email you already use | Under about 100 assemblies and one person doing the admin (my rule of thumb, not a standard) | Someone has to open it every week, or it quietly stops working |
| Your job or field-service software | Each assembly becomes a recurring job or service plan with automatic client reminders. | Included in some plans, a higher tier or add-on in others, so check yours | You already book, invoice and message customers in it | Reminder wording is often fixed. You paste in AI-drafted text, and you confirm the plan includes recurring jobs and automatic client messages |
| Specialist backflow platform | Tester-facing tools for scheduling, test forms and report submission | Mostly unpublished; ask for a quote | Your water supplier requires testers to use it, or you manage several hundred assemblies | Some are built for utilities first, so test the tester features, ask about data export and use your own 20 assemblies in the trial |
Two specialist examples, taken from their own pages in late October 2026. SwiftComply sells backflow software mainly to water and wastewater utilities. Its FAQ describes pricing as typically a one-time implementation fee plus an annual subscription, its pricing page offers a tailored quote rather than prices, and the FAQ adds that some programmes pass a small per-test fee to testers instead of the utility paying the subscription. Its tester page matters more to a plumbing firm: each tester needs their own account, opened from the water supplier's enrolment link, with a testing certification and current test-kit calibration certificates uploaded, and the supplier must approve the account before the first report goes in. Where a fee applies, the page says you only pay for tests that pass.
Syncta offers one version for water suppliers and a "Backflow Tester Solution" covering scheduling, routing, submitting and managing tests, and its site mentions sending reminders when tests are due; it shows no prices either, only a demo and a free-trial option. I have not tested either with a small firm's data, so treat them as places to start asking questions, not recommendations.
The first question to put to every water supplier is whether testers must submit through a particular portal. If they must, you will hold that account whatever you decide, and the register can live inside it. If they need not, start with the spreadsheet and move up only when the weekly admin tells you to. I also run a one-to-one AI implementation consultation for mapping this kind of set-up, but the first version is an afternoon's work you can do yourself.
Build the register: the fields that make reminders possible
Reminders depend entirely on the columns behind them. These are the ones I would insist on, each with the reason it earns a place.
| Field | Why it is there |
|---|---|
| Customer, contact and the contact's role (owner, manager, tenant) | The reminder must reach the person who can authorise a test, not the clerk who pays the invoice. |
| Site and the assembly's location, such as "plant room, rear wall" | The tester finds it without a phone call. |
| Assembly type and size | Different types are tested differently and take different amounts of time. Guides written by plumbing firms quote roughly 10 to 30 minutes for a standard device and longer for large multi-zone systems, so use your own timings when you offer slots. |
| Make, model and serial number | Supplier records match on serial number, and a replaced assembly must be updated. |
| Supplier's assembly or account number, if it issues one | It usually belongs on the report. |
| Last test date and result | Drives the follow-up path: passed, failed or repaired. |
| The supplier's due date | Do not just add 12 months to the last test. Some suppliers set a fixed compliance date for each assembly and send their own notice ahead of it, so copy their date, not yours. |
| Which supplier's rules apply | Points to the one-page rules sheet described below. |
| Access notes and water-off permission | Water to the line the assembly serves is usually off for part of the visit, which matters if a kitchen is mid-service. |
| Status: reminder sent, booked, passed, failed awaiting repair, filed | Filters turn the register into a weekly to-do list. |
Most firms already have this information; it is just scattered across old invoices, the supplier's annual notice list and somebody's memory. An assistant is good at turning that mess into rows, provided you stop it from guessing. This prompt does that:
Convert these notes into one row per assembly with columns: customer,
assembly type, size, location, serial number, last test date, due date, flags.
Do not guess. If a value is missing or ambiguous write FLAG in that cell and
say in the flags column exactly what is unclear. Never invent a serial number.
NOTES:
[paste the old list here]Here is a messy input and the kind of first pass that prompt should return:
| Messy note | Row the assistant returned | Flags worth keeping |
|---|---|---|
| "Rest. A - 2in RPZ rear kitchen - last test 3/14 - due Mar - ser on inv 4471" | Restaurant A, reduced-pressure assembly, 2 in, rear kitchen, last test 14 March, due March, serial: look up on invoice 4471 | Year missing; due day missing |
| "Office block unit 4 - PVB irrigation 1in - tested June last yr" | Office block, unit 4, pressure vacuum breaker, 1 in, irrigation, last test June (previous year), due FLAG | Exact test date missing, so the due date cannot be set |
| "Flats B - 4in DCVA fire line, make? - 10-2 test" | Apartment block B, double check assembly, 4 in, fire line, make FLAG, last test FLAG | 10-2 could be 10 February or 2 October; make unknown |
The flags are the valuable part. The first note shows why you never let an assistant fill gaps: "3/14" can only be 14 March, but nothing says which year. The third shows a genuinely ambiguous date, which you resolve from the signed report or by phoning the customer. Once the flagged cells are cleared, the register is ready to drive reminders.
A reminder ladder that starts before the supplier's own notice
Water suppliers often send their own notices. One supplier's page, for example, says its annual notification goes out within a 45-day window of the compliance date, to give customers time to arrange a test; yours may write earlier, later or not at all. If your first reminder lands 60 days out, you are the first voice the customer hears and the supplier's letter reads as confirmation of what you said. That is the thinking behind this ladder, which is my suggestion rather than a standard.
| Touch | When | Channel | What it does |
|---|---|---|---|
| 1 | 60 days before the due date | Heads-up with three booking options and the assembly's location, so the customer can say yes with one reply | |
| 2 | 30 days | Email and text | Offers the next free slots; confirms the contact is still right |
| 3 | 14 days | Text, plus a phone-call task for you | Slots are filling; asks about access and water-off timing |
| 4 | 7 days | Final reminder that quotes what the supplier's own notice says about the due date | |
| Overdue | The day after | Phone, then email | Earliest available slot, plus the supplier's late-results rule if it states one |
A customer who books at touch 1 leaves the ladder, so the real message count is lower than the maximum. With 112 customers and four scheduled touches, the ceiling is 448 messages a year before any overdue calls. Written by hand at five minutes each, that is 37 hours; drafted once as templates, merged from the register and given a 30-second glance each, it is nearer four. Treat both figures as a sum to rerun with your own times.
The first reminder is the one to get right. This prompt gives the assistant everything it needs and nothing it should not decide:
Write a reminder email from a plumbing company to a customer whose annual
backflow test is due. Facts: customer first name [first name]; site [site];
assembly location [location]; due date [date]; three booking options
[option 1, option 2, option 3]; our phone number [number]. The tester will
need access to the assembly and will switch water off to the line it serves
for part of the visit: leave a placeholder [water-off window: ask the tester].
Plain, friendly English, under 120 words. Do not mention fines, penalties or
the water supplier's rules unless I paste them below. Do not use the word
"compliant".A typical result reads well on the first pass: it greets the customer by first name, names the location, lists the three slots and asks for a one-line reply. Two things need editing. It will sometimes add a line such as "to stay on the right side of regulations", which is vague and unsupported, so replace it with the supplier's own wording or delete it. And it will happily write that the visit causes "no disruption", which a kitchen manager will not enjoy discovering is untrue. Keep the water-off placeholder and fill it from the tester.
Cover notes for pass, fail and repaired: words only, never results
The test report is the tester's certified record. A typical published test and maintenance report form covers the assembly type, make, model, serial number and size; its location and what it serves; the reason for the test; the initial test readings; any repairs and parts used; the retest readings; the test gauge's make, serial number and date last checked for accuracy; and the tester's name, licence number, expiry and signature, with a line certifying the information as true at the time of testing. Nothing in that list is for an assistant to write.
| AI may | AI must not |
|---|---|
| Draft a cover note that repeats the tester's result in plain words | Enter, change or round any test reading |
| Explain what a pass or a fail means for the customer's next step | Decide that an assembly passed or failed |
| Draft a repair-quote message after a fail, using the tester's remarks | Fill in the tester's licence number, expiry or signature fields |
| Summarise a month of results into a one-page list for a property manager | Write "compliant", "certified" or "approved" unless the signed form says so |
| Draft emails to the supplier asking about filing rules | State the supplier's deadline from memory; copy it from the supplier's own notice |
For a pass, give the assistant only the facts a customer needs:
Write a short cover note for a customer who has just had an annual
backflow test. Facts: first name [first name]; site [site]; assembly
[type, size, location]; test date [date]; result as recorded on the signed
report: PASSED; next due date [date from our register]; the signed report
is attached; results are being submitted to the water supplier by
[the tester / the customer / us], as the supplier's rules require.
Plain English, under 110 words. Do not add any technical claims, readings
or the word "compliant".A typical draft from that prompt, after a light edit:
Hi [first name], the annual backflow test on the 2 in reduced-pressure assembly in the rear plant room at [site] was carried out on [date] and passed, as recorded on the signed report attached. Its next test is due by [date], and we will remind you about 60 days before. The results have been submitted to your water supplier by [the tester / us]. Any questions, call us on [number]. [your name]
Two checks before it goes. The assembly description must match the signed report word for word: if the register says 1.5 in and the report says 2 in, the report wins and the register gets corrected. And delete anything the assistant adds of the "your water is now fully protected" kind, because a passed test records how the assembly performed on the day, nothing more.
The repaired case is the one customers misread. An assembly that failed, was repaired and then passed its retest should be described in that order, with both dates: "failed its initial test on [date]; the tester replaced [part, as written in the report's repairs section] and it passed the retest on [date]." A draft that simply says "passed" hides the repair the customer paid for, and it no longer matches the report the supplier receives, which records the initial readings, the repair and the retest.
A fail needs a second prompt, and this is where I would check the draft hardest. It takes the same facts but swaps the result for FAILED, adds the tester's remark about what needs repair, a reference for your repair quote and a placeholder: [the supplier's deadline for repair and retest, copied from its notice]. A first draft can easily say "the water supplier requires repair within 30 days". The assistant has no way of knowing that figure, so it is invented; the real deadline lives in the supplier's notice, and when you do not have it the right sentence is "we will confirm the supplier's deadline in writing". The placeholder in the prompt prevents that failure.
The same principle runs through other trades where a person signs and AI drafts around the edges, for example Electrical Installation Certificate: What AI Can Draft and You Must Sign. If a reminder system also needs your own tester's licence expiry and the test gauge's accuracy-check date to be tracked, those belong in a compliance calendar, because an expired licence or an out-of-date gauge makes a signed report worthless.
Find each water supplier's filing rules before the first batch
Filing rules vary, and the differences matter more than any software choice. Two published examples show the kind of thing a local rule can say. One supplier asks testers to submit results online within five days of the test and, if a failed assembly cannot be repaired the same day, to send the failing results first and the passing results by the due date. A report form used elsewhere asks for a signed and dated original for each assembly tested and tells testers to keep records for at least three years. Other suppliers set different deadlines, or only want the signed report by the compliance date. None of these is the rule where you work until your own supplier says so, and you cannot guess which applies, so ask. Nine questions, once per supplier, build a one-page rules sheet.
| Question for the supplier | Why it matters |
|---|---|
| Must testers register with you, and how? | Decides whether you need a portal account before the first test. |
| Does the tester or the property owner submit results? | Puts the filing step on the right person's checklist. |
| Where do results go: portal, email, post or your own form? | A wrong channel can mean a result is treated as not received. |
| By when: so many days after the test, or by the compliance date? | Sets the internal deadline for the tester's paperwork. |
| Do you require your own form, or is any test report accepted? | Saves re-typing and rejected forms. |
| What do you want after a failed test, and by when? | Drives the fail path: failing results, repair deadline and retest deadline. |
| When do you send customers their own notice? | Lets you time your first reminder to come first or alongside. |
| How long must test records be kept? | Sets your retention rule for signed reports. |
| Is there a filing fee per test, and are there fees or consequences for late results? | A per-test fee belongs in your test price; the late rules tell you what a reminder may truthfully say, and nothing more. |
An assistant will happily write the email that asks these questions. Give it the nine and ask for a short, polite message that can go to a supplier's cross-connection or water-quality contact. Paste the replies back and ask for a one-page rules sheet in a fixed layout, one per supplier. Then check the sheet against the supplier's own website, because a reply from a clerk and a page from the supplier do not always agree, and the page is the one that counts.
One year for a three-van firm: 180 assemblies, 112 customers
Here is how the first year might run, in sums you can redo with your own figures.
- Setup, about six hours spread over a month. Clean the old list with the prompt above, write the four reminder templates and one cover note per result, and send the nine questions to each of the four suppliers.
- Reminders. Maximum 448 messages (112 customers by four touches), realistically fewer because booked customers leave the ladder. Hand-written at five minutes each that is 37 hours; templates plus a glance is about four.
- Revenue sensitivity. If a test is priced at $95 (an illustrative price, not a benchmark), 180 tests are worth $17,100. Every five percentage points of on-time bookings is 9 tests, which is $855. The reminders do not create the work, they stop work quietly slipping into next year.
- Failures. Suppose 11 of the 180 assemblies fail their first test. Each needs a fail note, a repair quote and a retest booking, which is 33 items to produce. The cover-note prompt makes the fail note a two-minute job as long as the tester has written the repair remark first.
None of these figures is a promise. They are sums to rerun on your own register to decide whether the setup hours pay back. With 180 assemblies the answer is probably yes; with 25, probably not.
Where reminder systems go wrong: stale registers and wrong recipients
- A replaced assembly. The old serial number stays in the register, the reminder quotes it, and the customer says "we replaced that last spring". Update the serial number from every signed report, because the tester's paperwork is the source of truth.
- The wrong contact. Reminders go to the accounts clerk who pays your invoices, while the owner who authorises work never sees them. The role column in the register prevents this.
- Due-date drift. A firm that adds 12 months to the last test date can end up a month out from a supplier that sets a fixed compliance date. Copy the supplier's date from its notice.
- Merge accidents. A batch of letters carrying another customer's site name goes out because a column shifted. Send a preview batch to yourself, and keep a "ready to send" status that only you can set.
- Over-confident wording. A cover note that says "fully compliant" reads like a certificate. The may and must-not list stops it, and so does reading each note once before it leaves.
- Privacy. Full test reports pasted into a free consumer chatbot carry customer names and addresses with them. Paste only the fields the prompt needs, and check the model-training switch in the privacy settings of whichever assistant you use. Business plans exclude customer content from model training by default.
A monthly check that shows the system is working
Once a month, spend 20 minutes on five questions. How many assemblies fall due in the next 60 days, and how many of those have a booking? Which reminders went out, and who has not replied? Which failed assemblies are still awaiting repair or retest? Has each signed report been filed, and how many days did it take from test to filing? Pick five signed reports at random and compare them with the register: does the serial number, date and result match?
If the answers are good, the register is doing its job. If they are not, fix the register first and the templates second, because a letter drafted perfectly and sent to the wrong person is still a missed test. For the wider picture of reminder work in your trade, see Fire Protection Software: Inspection Reports and Reminders With AI, Alarm Maintenance Contracts: Renewal Letters and Reminders With AI and, for turning findings into customer reports, Leak Detection Reports: AI Turns Findings and Photos Into Customer Reports.
Questions plumbers ask about backflow reminders and reports
Can AI read a backflow test report and decide whether it passed?
No. Pass or fail is the certified tester's decision, recorded on the signed report. AI can draft a cover note that repeats the tester's result in plain words, but it should never be asked to interpret readings or fill the certification fields. If a reading looks wrong, the tester is the person to ask, not the assistant.
How far ahead should I remind customers of a backflow test?
I'd start about 60 days before the supplier's due date, then repeat at 30, 14 and 7 days, with a phone call at 14 days if nobody has booked. That is my suggested schedule, not a rule. Check when your water supplier sends its own notice (one supplier's page says it sends its notice within a 45-day window of the due date) and make sure yours goes first or alongside.
Who files the test results, the plumber or the property owner?
It depends on the water supplier. One supplier's published rule, for example, has the tester submit results online within five days of the test, while other suppliers may simply ask for the signed report by the compliance date. Ask each supplier, write the answer on a one-page rules sheet and build that step into your job checklist.
Do I need specialist backflow software or will a spreadsheet do?
A spreadsheet is enough for a small book of assemblies. Specialist platforms start to make sense when your water supplier requires testers to submit through one, or when you manage a few hundred assemblies and the weekly admin eats the saving. Prices are mostly unpublished, so ask for a trial with your own data before you commit.
Further reads
- How a Plumber Can Save Five Hours a Week on Admin With AI — More weekly admin a plumbing firm can hand to AI.
- AI Automation for Plumbers: Package Prices and What Should Be Included — What a plumbing automation package should include and cost.
- AI Service Plan Reminders for Heating and Cooling Customers — The same reminder-ladder idea for heating and cooling plans.
- Chasing Unpaid Invoices With AI: Polite Reminders for Trades — Polite chasers once a test has been done and invoiced.
- 10 ChatGPT Prompts for Plumbers: Call-Backs, Quotes, Complaints — Ten prompts for repair quotes and call-backs after a failed test.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: SwiftComply's home, pricing and tester pages and Syncta's home page (October 2026), water-supplier pages on annual test notices and reporting deadlines, and a published backflow test and maintenance report form.