Why the Handoff Matters -- and Where It Goes Wrong
When a leak detection visit identifies a confirmed or suspected finding, the next step is referral to the appropriate repair professional -- a licensed pool contractor, a plumber, a structural repair specialist. That referral is only as useful as the quality of the information being handed off. A vague finding description leads to a contractor who cannot locate what the detector found. An overstated finding -- one that includes cause speculation, repair prescriptions, or conclusions beyond the evidence -- leads to a contractor who may follow the wrong instructions or resent being told how to do their job.
The pool leak detector's communication role is to provide accurate, specific, evidence-based location information. Everything beyond that is the repair contractor's domain.
What to Communicate -- and What to Leave Alone
Communicate This
- "Active dye movement was observed at the skimmer throat -- approximately 2 inches below the waterline on the pool-side face."
- "Pressure test on the east return line showed a consistent 5 PSI drop over 15 minutes across three verified test runs."
- "Water was observed entering the inspection hole when the pipe was flooded -- location approximately 14 feet from the equipment pad."
- "Acoustic signal was strongest at the marked location on the deck -- signal consistent with active water movement underground."
- "Temporary epoxy patch was applied at the confirmed location -- repair needed before it can be considered permanent."
Leave This to the Repair Contractor
- "The crack was probably caused by soil settlement" -- cause determination is not detection scope
- "You'll need to replace the entire skimmer" -- repair prescription is the contractor's call
- "The pipe is definitely Schedule 40 and should be easy to repair" -- material assessment belongs to the person doing the work
- "This will probably cost around X to fix" -- pricing is the contractor's domain
- "The previous contractor installed this wrong" -- cause attribution creates liability
The Report as the Primary Communication Tool
A well-prepared pool leak detection report gives a repair contractor everything they need to find and address what was identified -- without requiring the detector to be present or to verbally explain the job after the fact.
The report must include: the exact location of each finding described in terms the contractor can orient to on site (measurements from fixed reference points, depth descriptions, which fitting, which side), the evidence that supported the finding (what dye did, what the pressure test showed, what acoustic signals were present), the photos that confirm the location, and any temporary patches applied with their locations documented.
A repair contractor who can pick up the detection report and walk directly to the marked location without additional guidance is the goal. That clarity is what protects the detector -- if the contractor goes to the wrong location, the report is the reference point for resolving the misunderstanding.
Handling Questions the Repair Contractor May Ask
When a repair contractor contacts the detection company with questions -- "what caused this?" or "how deep is the pipe?" or "how should I approach the repair?" -- the professional response is to answer within scope and redirect outside it.
Within scope: "The signal was strongest approximately 18 inches deep at the marked location. The acoustic behavior was consistent with active water movement in pressurized pipe." Outside scope: "I would recommend approaching from the north side" or "you should use compression fittings instead of solvent weld here." The detector locates. The contractor repairs. Those are distinct professional roles and keeping them distinct protects both parties.
Trade Communication in the H.U.N.T.E.R. Report Phase
Prior repair contractors who evaluated or attempted repairs are worth noting in the intake -- their work history may be relevant context for what the detection found, but their conclusions should not override the current evaluation's evidence.
Understanding the scope boundary -- detection vs repair -- is what keeps the technician from inadvertently taking on responsibility for outcomes that belong to the contractor who does the actual work.
The narrowing process produces increasingly specific location information. That specificity -- measured distances from fixed reference points, depth estimates from acoustic or physical signals, directional descriptions -- is what makes the handoff useful to the next trade.
Test results documented in the report -- gauge readings, time intervals, signal behavior -- give the repair contractor objective evidence to reference if any question arises about what the detection actually found.
Photos in the report serve as the primary visual communication tool for the repair contractor. A photo of the marked deck location, the finding close-up, and any temporary patch let the contractor orient to exactly what was found without ambiguity.
The recommendation is clear and scoped: "repair of confirmed finding at marked location recommended -- refer to licensed pool contractor." What the repair entails is not specified beyond what the detection evidence shows.
The best handoff I can give a repair contractor is a report that lets them walk directly to the location without having to call me. Clear measurements from reference points, photos of what was found and where, notes on depth from acoustic signals or the inspection hole, and a marked location on the deck if excavation is involved. That is what makes the detection useful to the next person in the chain.
Where I see technicians overstep is when they start telling the contractor how to fix it. "You should replace the whole line" or "this is probably a root intrusion, you'll need to excavate ten feet." That is not detection. That is construction speculation. The contractor will determine what the repair requires when they open the system. My job is to tell them where to look and what the evidence showed. Their job is to decide what to do about it.
The scope boundary also protects the detection company. If a contractor follows a detection report, performs the repair at the indicated location, and the pool still loses water -- the report shows what the detection found and where. If the detection overstated something or implied a cause that turned out to be wrong, the company is in a much harder position. State what was observed. Document it accurately. Let the repair side speak for itself.
Frequently Asked Questions
Should a pool leak detector ever be on site during the repair?
This is a business decision, not a scope requirement. A detector who is also a licensed contractor may choose to oversee or perform repairs at a confirmed detection location. A detector operating as a detection specialist only has no obligation to be present during repairs and should be clear in the report that the repair is the contractor's scope. Being present during repair without contractor authorization or licensing could create liability for the repair outcome.
What if the repair contractor disputes the detection findings?
The report and photographs are the reference point. If a contractor goes to the marked location and does not find what was described, the detector's documented evidence -- gauge readings, photos, acoustic signal descriptions -- provides an objective basis for discussing what was found during the evaluation. This is one reason why thorough documentation is professional protection: it gives both parties a common factual reference when questions arise after the detection.
Is it appropriate to recommend a specific repair contractor?
Providing a list of qualified contractors the detection company has worked with successfully is a legitimate value-add for the customer. What should be avoided is a financial arrangement with a specific contractor that creates an incentive to refer to them regardless of fit -- which creates a conflict of interest. The referral should serve the customer's interest, not the detection company's revenue.
What if the detection findings are inconclusive -- how is that communicated to a contractor?
Honestly. "The pressure test on this line showed an inconsistent drop that could not be confirmed as a line failure -- further evaluation under different conditions is recommended before repair." A contractor who receives an inconclusive detection result can decide with the customer whether to proceed with exploratory work or wait for a follow-up evaluation. False confidence in the report serves no one.
Learn the Documentation That Makes Every Handoff Work
The H.U.N.T.E.R. Method's Report phase produces the evidence-based documentation that repair contractors need -- and nothing beyond what the detection actually found. Available in the Residential Pool Leak Manual and LBA live workshops.
View All LBA Courses Free Report App