What PoolBoss Says
Document every pool service visit with a timestamped record showing who serviced the pool, when, what was done, and the condition before and after. Photos tagged as-found and as-left carry the most weight. If a customer later claims damage or an injury, a consistent visit history is the strongest evidence you have that the work happened as described.
The call that costs you money is not the one about a cloudy pool. It is the one three weeks later: a cracked skimmer lid, a stained deck, a guest who slipped on the pool surround, and a homeowner who is fairly sure your tech is responsible.
Nothing in that conversation is about chemistry, and nothing in it gets settled by what you remember. What settles it is what got written down at the time - the condition on arrival, the condition on departure, who was standing there, and what they noticed. What follows is what a defensible visit record contains, which disputes each part of it actually answers, and the things good records genuinely cannot do for you.
At a glance
Key takeaways
- Capture five things at every stop: completion time, the technician, what was performed, the as-found and as-left condition, and any note about something that looked wrong.
- Treat the arrival and completion photo pair as the core of your damage defense - it is the only part of the record that speaks to condition.
- Write hazards down the same day, in the notes, along with the fact that you told the homeowner. A verbal mention leaves no record at all.
- Keep visit records and chemical records straight: condition and timing answer a damage claim, readings and doses answer a water-quality claim.
- Do not oversell your own documentation. Records make your position stronger; they do not decide fault or replace being properly covered.
- Make the record a byproduct of completing the visit rather than an evening admin task, or it will be thinnest during the weeks you most need it.
- Check that photos are consistent across your whole book, not just the difficult accounts - the gap always turns up on the stop you did not think mattered.
What a defensible pool service visit record contains
Five things, and four of them have to be captured at the pool rather than typed up later: when the visit was completed, which technician completed it, what they performed, what the property looked like when they arrived and when they left, and any note about something that seemed off. Miss the condition pair and you have a record that proves service happened but says nothing about the state you found the place in - which is the half that matters when the dispute is about damage.
A three-tech company running 140 weekly accounts produces roughly 600 visit records a month. None of them are worth much as evidence if they get filled in from memory on Friday afternoon. The value is almost entirely in the record being created at the pool, by the person standing there, while the details are still true.
- The completion timestamp, to the minute. A scheduled date shows what you planned; a completion time shows what happened.
- The technician who did the work. A visit tied to a named person is one somebody can actually speak to about that day.
- What was performed - brushed, vacuumed, filter cleaned, readings taken. Specific tasks, not "serviced."
- The as-found and as-left condition, ideally as two photos. This is the pair that answers a damage claim.
- Anything that looked wrong on arrival, written the same day: a loose handrail, a cracked lid, standing water on the deck.
Damage claims are about condition, not attendance
A damage claim asks a question a completion timestamp cannot answer: what did the property look like before your technician got there? Attendance disputes and damage disputes sound similar on the phone and are settled by completely different parts of the record. One needs proof somebody came. The other needs proof of the condition you walked into and the condition you left behind.
A three-tech company in Mesa services about 140 residential accounts across the Phoenix metro. Two weeks after a routine stop, a homeowner in Gilbert calls about a cracked pool light and thinks the tech did it. The owner opens that visit: completed at 10:52 a.m., the technician named, and two photos - one at arrival, one at completion - showing the same light, unchanged, in both. The call is over in about a minute. Not because photos are a legal shield, but because a specific record from that morning is much harder to argue with than either person's memory of an ordinary Thursday.
If the dispute is really about whether anybody showed up at all, that is a different record and a different conversation - how to prove a pool was serviced covers that one directly. Everything here assumes attendance is not in question and the argument has moved on to what happened while your tech was on the property.
An accident on a serviced property asks a third question
When somebody is hurt at a property you service, the part of your record that matters is whether you noticed the hazard and whether you said anything about it. A slip on wet decking, a guest cutting a foot on broken tile, a child reaching the water through a gate that no longer latches - in each case the useful history is a dated note saying the condition existed and was passed on to the homeowner.
That makes the notes field worth more than most operators treat it. A tech who writes "gate latch not catching, told homeowner" on a Tuesday has created something no amount of later explanation can replicate. A tech who mentions it verbally and moves on has created nothing. The same holds for hazards you cannot fix and were never hired to fix: the job is to record that you saw it and passed it along, not to repair it or to rule on whose problem it is.
Set the expectation with your crew in plain terms - if you would mention it to the homeowner, write it down. Three sentences is plenty, about ten seconds of typing per stop, and notes are the only part of a visit record that captures judgment rather than measurement.
A visit record is not a chemical record
These are two different defenses answering two different accusations. A visit record answers what happened at the property - who, when, condition, notes. A chemical record answers what went into the water: the seven readings a full test covers, from free chlorine and combined chlorine through pH, total alkalinity, calcium hardness, cyanuric acid, and salt on a salt pool, plus whatever was dosed.
Keeping them straight matters, because the wrong record is no help at all. A homeowner claiming a stained deck needs your condition photos. A homeowner claiming the water irritated a child's skin or ruined a swimsuit needs your readings and doses, and chemical records for a water-quality claim covers that side properly. Most software captures both on the same visit, which is exactly why operators blur them together - but when a specific claim lands, you reach for one or the other.
What good records genuinely cannot do
Records make your position stronger. They do not make you right, and they do not make a claim go away. Being clear about the limits is worth doing, because operators who oversell their documentation to themselves get surprised at the worst possible moment.
A visit history does not decide fault - it shows condition and timing, and somebody else still weighs that against everything else in the picture. It does not stop a homeowner from being upset or from pursuing it anyway. It cannot fill in a gap after the fact: photos on four stops out of five sounds diligent, but on a 140-pool weekly book that still leaves roughly 1,450 visits a year with no condition record, and the accounts most likely to dispute something are exactly the ones where you will wish the habit had been universal. And it is not a substitute for being properly covered; documentation and coverage do entirely different jobs.
Your service agreement is separate paperwork doing separate work - scope, access, what you are and are not responsible for. That lives in whatever system you keep contracts in, and a signed service agreement on file is worth having regardless of what your visit history shows. The record establishes what happened; the agreement establishes what you agreed to.
The record that creates itself
Most operators have thin documentation for a practical reason, not a lazy one: good documentation used to mean extra paperwork at the end of a long day. It does not have to. If the record is a byproduct of the technician completing the stop on their phone, it exists whether or not anybody was thinking about liability that morning.
That is the bar worth setting. The timestamp comes from marking the visit done, the technician is whoever is logged in, the readings come from the form they already fill in, and the photos are two taps that add about twenty seconds to a stop. In PoolBoss the visit becomes an automatic record of every service visit built that way, with arrival and completion photos tagged as such, and the customer gets their copy without anyone remembering to send it. Completed visits also leave an entry in an append-only activity log, so a record cannot be quietly changed months later - which is what makes a history credible rather than merely present.
The real test is whether your documentation survives a busy week. Anything that depends on remembering to do it will be thinnest exactly when a route goes sideways, and that is the week somebody calls.
FAQ
Frequently asked questions
How long should I keep pool service visit records?
Storage is not the constraint, so the simplest workable policy is to keep everything. A 140-pool weekly book generates roughly 7,280 visit records a year, and even with photos attached that is a trivial amount of data - there is rarely a practical reason to delete a visit history at all. The reason operators ask is that disputes surface on very different clocks: a billing question usually arrives within a month or two, while a property-damage or injury claim can show up long after the visit has left everyone's memory. A record you deleted on a schedule is a record you do not have on the day it would have helped. Where a hard requirement does exist it comes from outside your own policy - health-department rules on commercial and semi-public pools, or a retention term written into a commercial contract - so check what applies to those specific accounts and make sure your practice covers it.
What do I do if a damage claim comes in weeks later and there is no photo from that visit?
Lead with what the record does have and do not stretch it. A completion timestamp, the technician who was there, the tasks performed, and the notes from that day are still a real account of the visit, and in many disputes that is enough to move the conversation from accusation to comparison. Say plainly that there is no photo from that stop rather than talking around it - a homeowner who catches you overstating the record stops believing the parts that are solid. Then check the claim against your visit history before anything else, because a surprising number of these turn out to reference a week the property was skipped or serviced by somebody else. Finally, treat the gap as a process signal: if photos are inconsistent, make them a required step at completion rather than a good habit, and the same call goes much better next time.
Does good visit documentation replace liability insurance?
No. They do different jobs, and treating one as a substitute for the other is how operators end up exposed. Documentation shows what happened at a property on a given day; it does not absorb the cost of something going wrong. What good records actually do is change which disputes turn into claims at all - a homeowner who can see the arrival and departure condition of their own pool often drops a $300 complaint before it escalates, and the ones that do escalate at least start from facts rather than from two people's recollections. Think of the record as the thing that keeps small disputes small. It is not a legal shield, it does not decide who was at fault, and nobody should build their risk planning around it. Keep the documentation because it settles arguments cheaply, and treat coverage as an entirely separate decision.
What should my technicians actually write in their visit notes?
Anything they would mention to the homeowner if the homeowner were standing there, in three sentences or fewer. The useful notes are specific and dated: "skimmer lid cracked, already broken on arrival," "gate latch not catching, told homeowner," "pump louder than last week." Each of those describes a condition and, where it matters, who was told. The useless note is "serviced pool," which adds nothing the completion timestamp did not already say. Two habits are worth training in particular. First, note pre-existing damage the moment it is seen rather than after somebody complains - a note written weeks before a claim is worth far more than the same observation offered afterward. Second, note when a task could not be done and why: a locked gate, a dog in the yard, equipment already running on arrival. About ten seconds of typing per stop covers nearly every situation that later becomes a phone call.
What do I do when my tech notices damage that was already there?
Record it that day and tell the homeowner that day - those two steps together are what make it pre-existing rather than disputed. A photo of the cracked tile or chipped coping, attached to that visit with a note saying it was found on arrival, converts a future argument into a settled fact. Timing is the whole game: the same photo taken after a homeowner complains looks like a defense, while the one taken before looks like a record. Tell them however you normally communicate - a line in the service report, a text, a note at the equipment pad - and keep it factual rather than defensive. "Noticed the tile at the waterline is chipped on the north side, wanted to flag it" is plenty. You are not diagnosing the cause or accepting responsibility, and you should not speculate about how it happened. You are creating a dated observation, which is the part that helps later.
Who should be able to edit a visit record after it is marked complete?
As few people as possible, and never silently. A visit record's value comes from being created at the time by the person doing the work - if it can be quietly rewritten a month later, its credibility drops for everybody, including you. Legitimate corrections do happen: a reading typed into the wrong field, a photo attached to the wrong stop, a visit marked complete by mistake. The right handling is to allow the fix but keep a trace of it, so the history shows the original entry and the correction with a timestamp on each. Practically, that means limiting edit rights on completed visits to an owner or admin rather than every technician, and preferring software that keeps an append-only log of changes over anything that overwrites a field with no record. If you cannot tell whether a visit record has been edited, you cannot fully lean on it in a dispute.
