
The real problem with recurring plumbing service plans
Most shop owners don't lose money on the first visit. They lose it on the second call when nobody can prove the first one happened. A recurring plumbing service plan sounds simple on paper. Every quarter, or every six months, you send a tech to check a water heater, flush a tankless, inspect a PRV, or look at a sump pump. But once you've got ten or twenty of those customers spread across town, the paper trail gets messy fast.
A tech gets busy. He forgets to write down the house pressure. The photo of the expansion tank never gets saved. The customer signs a card, then it sits in the glove box until Friday. Next month, somebody asks why the backflow area on a commercial sink wasn't checked on the last visit, and you're stuck guessing. That is a terrible place to be.
Recurring service visits are not about fancy software. They're about keeping a clean record for every stop. Who was there. When they arrived. How long they stayed. What parts they looked at. What they found. What pictures they took. If you run plumbing maintenance contracts, that record is the whole game.
What a good recurring visit record actually includes
When a plumber lands on a maintenance stop, you want more than a time punch. You want the visit tied to the work.
At a minimum, the record should show:
- the truck's GPS check in at the job site
- the tech name
- the date and time on site
- a checklist for the work done
- photos before and after, when they matter
- customer signature, if you use one
- notes on parts, readings, and anything left behind
For plumbing, that means real field detail. Not fluff. If the visit is for a tankless water heater, the tech should record inlet water temperature, outlet temp at the fixture if relevant, error codes on the unit, flush chemicals used, and whether the isolation valves held. If he's checking a sump pump, I want a wet test photo, float switch notes, and a short note about discharge line condition. If it's a backflow area in a small commercial space, I want the shutoff condition, visible leaks, pressure readings, and a clear photo of the assembly before he packs up.
That is the kind of record that stops arguments later.
Why calendar reminders alone fall short
A calendar reminder tells you a visit is due. It does not tell you what happened after the truck pulled in.
I've seen shops try to manage recurring plumbing service visits with a spreadsheet and a stack of paper checklists. It works until it doesn't. One tech skips a photo because his phone is dead. Another forgets to write the water pressure on the test sheet. Someone at the office marks the account as complete because the customer said, "Yeah, I think he came by." Then a month later the homeowner says the sump pump hasn't been tested in a year.
Now you're not just dealing with a service issue. You're dealing with your own missing record.
That is why the visit needs to start with check in and end with proof. Not a vague note. Real proof. GPS check in at the site. Time on site. Photos from the job. Completed checklist. Customer signature if you use it. If the tech replaces a supply line or cleans a filter screen, the record should show that. If he finds rust on the water heater drain pan or a slow drip at the trap primer, that should be in the notes with a photo.
A simple setup for recurring plumbing service visits
If you're setting up recurring plumbing service visits for the first time, keep it plain.
Start with the customer record. Put in the address, contact name, and the service interval. Quarterly makes sense for some houses. Every six months makes sense for others. Some commercial jobs need monthly eyes on a lift station, a mop sink, or a mechanical room drain. Don't overbuild it. Just make the interval match the equipment and the account.
Then build the checklist by visit type.
For example:
- water heater flush
- tankless service
- sump pump test
- PRV inspection
- fixture leak check
- visible pipe and trap inspection
- shutoff valve test
Each item should be something a tech can actually mark off on site. Not a fuzzy line like "general maintenance." That's how you end up with a useless record. If the job is a water heater flush, ask for what matters. Sediment amount. Valve condition. Leak at the drain. Expansion tank pressure if you're checking it. Photos of the label, the hoses, and the finished area.
Then make sure the tech knows the record is part of the visit. No "I'll fill it out later." Later is where details go to die.
The photo that saves the argument
A lot of maintenance fights come down to one simple thing. Did the tech really look at it?
Say a customer calls after a recurring visit and says the basement floor drain still backs up. If the visit record shows a photo of the cleanout cap, the surrounding area, and the standing water gone after the tech snaked it, you've got something solid to point to. If the record includes notes that the line was slow but flowing and the customer was told to watch it, that matters too.
Same with a water heater. If the drain pan was already rusted through and the tech photographed it, that's proof of condition at the time of service. If a shutoff valve was frozen and not touched, note that. If a pressure reading came in high and the PRV was left alone because the owner wanted to think about replacement, that should be in the record.
The point is not to cover yourself with words. The point is to show what the technician actually saw.
Why the tech name and time on site matter
People think the only important thing is that the work got done. That sounds fine until two different guys have touched the same account.
If the record says Tech A was on site from 8:12 to 8:44, and Tech B was there the following quarter, you can see who did what. That matters when one guy is better at tankless flushes and another is better at old cast iron drain lines. It also matters when a customer says the wrong person showed up. You've got the name, the check in, and the elapsed time.
Time on site also tells you if the visit was realistic. A plumbing maintenance stop that took six minutes probably wasn't a real inspection. If the record shows a long enough visit, plus photos and checklist completion, that tells a much better story.
And yes, your techs will grumble at first. Fine. Most guys grumble when you ask them to write anything down. But once they know the record protects them when a customer points fingers, they get it.
Recurring service contracts get easier when the proof is built in
If you're looking at plumbing maintenance contract software, the feature list can get noisy fast. Ignore the shiny stuff and ask one question. Does it keep the visit record clean every time a truck shows up?
For a plumbing shop, that means recurring service visits tied to:
- GPS check in
- time on site
- photos
- checklists
- tech name
- customer signature
- notes on parts, readings, and defects
That's the stuff you use when a customer asks, "When was the sump pump last tested?" or "Who checked the water heater in March?" You don't want to be flipping through email threads or asking the office to dig through a filing cabinet.
You want to pull up the visit and see the full history. That is the value. Not some fancy dashboard. Just a clean record of the work your shop actually did.
A quick example from the field
Say you've got a condo property with a recurring plumbing service plan. Every three months, a tech checks the common area water heater, the mop sink, and the basement ejector pump.
On one visit, the tech finds a small leak at the heater drain valve, the water pressure reads 82 psi, and the ejector float switch cycles normally. He snaps a photo of the leak, marks the pressure reading in the checklist, and notes that the valve should be replaced at the next service window. He checks in by GPS when he arrives, stays 38 minutes, and the customer signs at the end.
A month later, the property manager says the basement smelled damp before your last visit and asks what was done. You pull up the record. There it is. Time on site. Tech name. Pressure reading. Photo of the valve. Checklist item marked complete on the pump. No guessing. No arguing over memory.
That's the kind of paper trail that keeps a maintenance contract from turning into a headache.
What to watch for when you set this up
Don't build recurring visits around hope. Build them around what your tech can prove without slowing the job to a crawl.
Keep the checklist short enough that a real plumber will use it. Make the photos specific. Ask for readings only when they matter. And make sure every recurring stop ends with the same basics. Check in. Do the work. Record the proof. Leave the customer with something solid.
If you get that part right, your maintenance contracts stop living in somebody's memory and start living in the job record.
Common questions
What should be in a recurring plumbing service record?
Use the basics that prove the visit happened. GPS check in, tech name, date, time on site, checklist items completed, photos, customer signature, and notes on readings or parts.
How do I set up recurring plumbing service visits without a messy spreadsheet?
Start with the customer, the service interval, and a short checklist for each visit type. Then make the tech finish the record on site, not back at the shop.
What kinds of checks belong on a plumbing maintenance checklist?
It depends on the account, but common items are water heater flushes, tankless service, sump pump tests, PRV inspection, shutoff valve checks, visible leak inspection, and drain condition notes.
Why do photos matter on maintenance contracts?
Photos show what the tech actually saw. A rusted drain pan, a leaking valve, or a clean sump pit is hard to argue with when the record includes a picture from the visit.
How does time on site help with recurring service plans?
It shows the visit was real and gives you context for the work. A proper maintenance stop takes time. If the record says five minutes, you know something got missed.