How Pre-Existing Conditions Become Post-Visit Claims
Most customers who call a leak detection company back to report damage are not being dishonest. They genuinely did not notice the cracked fitting, the chipped tile, or the stained concrete section until they were walking the property after the visit -- when their attention was heightened by the awareness that work had just been performed. The connection they draw between the visit and the damage is automatic and feels entirely reasonable to them.
For the technician, the connection is equally clear in the other direction: that damage was there before I touched anything. But without documentation, neither party has evidence. The dispute becomes a conversation about credibility, and that is a situation no professional wants to be in with a customer.
Pre-existing condition documentation resolves this before it happens. It is not about distrust. It is about creating a shared record that protects the customer's expectations and the technician's professional standing.
The Types of Pre-Existing Damage Most Commonly Disputed
Cracked Return Fittings
Return fittings are handled during pressure testing plug insertion. A fitting that was already cracked before the visit may show more visible cracking after -- or the customer may simply notice it for the first time when the technician is working at that fitting.
Deck Cracks and Staining
A crack in the deck near the pool or a stained section of concrete that the customer never noticed becomes visible during the walkthrough that follows a leak detection visit -- when the customer is paying closer attention to the pool area than normal.
Equipment Damage
Worn pump lids, cracked filter tanks, corroded valve handles -- equipment that was already degraded may be noticed by the customer immediately after a visit when they are inspecting the equipment pad more carefully than usual.
Tile Chips and Missing Grout
Tile damage near the waterline -- where dye testing and underwater work takes place -- is easily attributed to a technician's activity even when the chip existed long before the visit.
Any condition that exists before the technician begins work must be documented before they begin work -- without exception. If a condition is noticed during testing that was not documented at arrival, stop and photograph it before continuing. Note when it was first observed.
Documentation is not an accusation. It is a professional record. Pointing out a cracked fitting to the customer while photographing it is not adversarial -- it is transparent and establishes a shared understanding of what exists before testing proceeds.
How to Document Pre-Existing Conditions Professionally
- Photograph the condition clearly -- close enough to show the specific damage, wide enough to show location context
- Include a reference object when possible -- a finger, a coin, or a marked probe near the damage gives the photo scale
- Note the condition verbally to the homeowner at the time of documentation -- this creates a shared awareness, not a dispute
- If the homeowner is not present, photograph the condition and note in the job record that it was observed at arrival with no homeowner present to confirm
- Save all arrival photos with timestamps -- the timestamp is what establishes the documentation as pre-visit, not post-visit
- Include relevant pre-existing conditions in the limitations section of the report -- conditions that affect testing scope should be noted in writing
Pre-Existing Condition Documentation in H.U.N.T.E.R.
Pre-existing condition documentation happens before any phase of active testing. It is part of the property understanding that makes the rest of the method trustworthy.
Some pre-existing conditions are mentioned by the customer on the intake call -- "there's a crack in the deck we've been meaning to fix." Note these and photograph them at arrival regardless of what the customer said.
Pre-existing damage informs the system map. A cracked return fitting may affect pressure test results. A worn pump lid may make it harder to assess equipment-side loss. These conditions must be understood before testing shapes conclusions around them.
Pre-existing damage can sometimes narrow the investigation -- a stained area of the deck near a fitting, a prior patch visible at the pool floor, or a previously repaired crack may be the location of a recurring leak rather than a new one.
Testing around pre-existing damage requires extra documentation. If a pressure test is run on a line that connects to a fitting with visible pre-existing cracking, the pre-test condition of that fitting must be in the job record before results are interpreted.
The report must clearly distinguish between what was found as a finding and what was pre-existing at arrival. These are different categories. Conflating them produces confusion and creates report accuracy problems.
If a pre-existing condition affects the recommendation -- for example, a worn fitting that should be addressed regardless of the current leak -- it can be noted as a separate observation in the report alongside the primary finding.
I have seen technicians get into disputes over things they had absolutely nothing to do with -- because they did not photograph the property before they started. A customer walks out after the visit, looks at the equipment pad, and sees a cracked valve handle. They have never looked at that valve handle in three years of owning the pool. But they are looking now, because someone was just working on their equipment, and the cracked handle is the first thing they notice. If the technician has a photo of that valve handle taken at arrival showing the pre-existing crack, the conversation takes fifteen seconds. Without it, the conversation takes much longer and has no good ending.
I teach technicians to point things out while they photograph them. Not in an accusatory way -- just professional transparency. "I'm noting this crack in your return fitting before I begin testing so it's in the job record as a pre-existing condition. I'll include it in my documentation." Most homeowners appreciate that. It tells them they are dealing with someone who is thorough and honest. The ones who push back on it are usually the ones who were planning to dispute something anyway -- and the photo makes that harder.
Frequently Asked Questions
Should the customer be present when pre-existing damage is documented?
Ideally yes. Pointing out a pre-existing condition to the homeowner while photographing it creates a shared verbal and visual record. Both parties have seen and acknowledged the condition before testing began. If the customer is not present at the start of the visit, document the conditions found at arrival and note in the job record that no homeowner was present at the time of documentation.
Does documenting pre-existing damage mean the technician is responsible for fixing it?
No. Documenting a pre-existing condition is an observation, not an acceptance of responsibility. The technician is noting what exists before their work begins -- not agreeing to repair it, guarantee it, or take ownership of it. If the pre-existing condition affects the scope of the leak detection work, that should be noted in the report's limitations section.
What if pre-existing damage is noticed during testing, not at arrival?
Stop and photograph it immediately. Note in the job record the approximate time and circumstances under which it was first observed. If possible, pause and tell the homeowner what you found and what its condition appears to be. A condition discovered mid-testing that was not documented at arrival is harder to establish as pre-existing -- but a timestamped photo taken as soon as it is noticed, with a note that it was observed without any technician activity at that location, is better than no documentation at all.
How does pre-existing damage documentation relate to the final report?
Pre-existing conditions that are relevant to the leak detection findings, that affect scope or testing limitations, or that the customer should be aware of for property maintenance may be included in the report as separate observations -- clearly distinct from the leak detection findings. Pre-existing conditions that have no bearing on the findings belong in the job record but do not need to appear in the customer report.
Professional Documentation Starts Before the First Test
Pre-existing condition documentation is one of the professional disciplines that separates trained leak detectors from operators who create liability through carelessness. The H.U.N.T.E.R. Method teaches documentation as discipline -- from arrival through final report.
View All LBA Courses Free Report App