The Pressure Is Real -- and It Is Dangerous
Every pool leak detection technician feels it on some jobs: the customer who hovers. The homeowner who says "I've had two other companies out here and they couldn't find it." The property manager who mentions the owner is getting frustrated. The customer who paid for the visit and makes it clear they expect a result -- not a process.
This pressure is not imaginary. It is one of the most powerful forces working against accurate diagnosis in the field. A technician who responds to it by forcing a conclusion -- calling a suspected fitting a confirmed finding, recommending excavation on insufficient evidence, or declaring a result to satisfy the customer rather than the evidence -- has allowed the emotional environment to override the diagnostic system. That is when mistakes happen.
The Four Forms of On-Site Pressure
Expectation Pressure
The customer assumes that paying for a leak detection visit means a leak will be found and identified. When the process takes longer than expected or produces uncertainty, their expectation starts to feel like a demand.
Trust Erosion Pressure
"Two other companies couldn't find it." This phrase communicates that the customer's trust is already damaged. The technician feels pressure to succeed where others failed -- and that pressure distorts judgment.
Time Pressure
The customer needs to be somewhere. The technician has another job scheduled. The pool has been down for weeks. Every form of schedule pressure increases the temptation to move faster than the evidence supports.
Emotional Contagion
A distressed customer transfers distress. A frustrated homeowner makes the technician want to resolve the frustration -- by finding something. That impulse, unchecked, produces motivated diagnosis instead of objective diagnosis.
What Happens When the Technician Yields to Pressure
A technician who yields to on-site pressure makes the same cognitive error as confirmation bias -- except the theory being forced is not formed from a pre-screen answer. It is formed from the emotional need to produce a result. The technician looks for something to confirm. A slightly suspicious fitting becomes a finding. An ambiguous pressure result becomes a recommendation. The report reflects what the customer needed to hear, not what the evidence actually showed.
This is how professional reputations collapse. Not dramatically, through obvious mistakes, but quietly, through a pattern of motivated conclusions that eventually produce a wrong excavation, a failed repair, or a pool that continues to lose water after a finding was declared.
The Professional Response -- Before the Visit and On Site
What to establish at the arrival interview
The moment the technician walks to the pool with the homeowner is the moment to set expectations. Not defensively -- professionally. Explain what the process covers, how long it takes, and -- critically -- that no active leak evidence observed is a valid, professional outcome, not a failure.
Promise diligence. Do not promise a finding. A technician who promises diligence and delivers it has fulfilled their professional commitment regardless of the result. A technician who promises a finding and cannot deliver it has created a dispute.
"What I'm going to do today is go through the full systematic process -- starting externally, then underwater, then the plumbing system. I'll document everything I find. At the end, I'll give you a clear picture of what the evidence showed. I want to be upfront with you -- there are jobs where we go through the full process and no active leak evidence is observed in the areas we tested. That's a real outcome, not a failure. If that's where we land, I'll explain exactly what was tested and what it means."
When Agreement Creates Stability
When a customer understands the process and agrees to its terms -- including the possibility of a no-leak-found result -- the pressure dynamic changes. The customer is no longer waiting for a conclusion. They are observing a process they understand. A technician who explains each step as they go, shares what they are observing without premature conclusions, and delivers a clear end-of-visit explanation has built trust through transparency rather than through a result.
Agreement before the process begins is what makes an inconclusive result professionally defensible. A customer who was told "no leak found is a possible outcome" and understood that going in will accept a no-leak-found report far more readily than one who felt a finding was guaranteed.
Professional Neutrality in H.U.N.T.E.R.
The H.U.N.T.E.R. Method is a structural defense against motivated diagnosis. Each phase requires specific evidence before proceeding -- which makes it harder for pressure to short-circuit the process.
Emotional cues from the customer -- frustration, distrust, urgency -- are observed but not acted upon diagnostically. They inform how to communicate, not what to conclude.
The arrival interview is the moment to establish professional neutrality and set expectations. Once that is done, the method runs on evidence -- not on what the customer hopes to hear.
Narrowing follows evidence and system logic -- not the customer's belief about where the leak is. A customer who is certain it is the skimmer does not change the testing sequence.
Testing does not accelerate because the customer is impatient. The test takes the time it takes. Rushing a pressure test or cutting a dye observation short to satisfy impatience is where errors enter.
Evidence is what gets documented -- not what the customer wanted to find. "Active dye movement was observed" is evidence. "Customer believes this fitting is leaking" is not.
The recommendation follows the evidence. When evidence is clear, the recommendation is clear. When evidence is inconclusive, the recommendation reflects that honestly -- including next steps or diagnostic reset options.
The frustration a customer feels when water loss continues and answers take time is completely understandable. They are paying for a pool they cannot enjoy. They have probably already filled it multiple times. They have already called someone who could not find it. By the time I arrive, their patience is thin and their trust is conditional. I understand that. I do not take it personally. What I do is explain the process clearly at the beginning so the customer knows what to expect -- including that "no active leak evidence observed" is a real and professional outcome.
What I cannot do is let that frustration change what I write in the report or what I recommend. A diagnosis made under customer pressure is not a real diagnosis. It is a performance. And when the pool continues to lose water after I performed a finding instead of conducting one, that customer's frustration turns into something I cannot recover from -- because I told them I found something when the evidence did not fully support it.
The agreement is the key. When the homeowner and I agree on the process before I start -- on what the tests cover, what a no-leak-found result means, and what the next steps would be -- the pressure dynamic changes completely. Now we are both watching the process unfold. I am not performing for them. I am working with them. That changes everything.
Frequently Asked Questions
What should a technician say when a customer insists they know where the leak is?
Acknowledge what the customer observed -- "That's helpful context and I'll make sure to evaluate that area" -- and continue with the full systematic process. The customer's belief about the leak location is intake information, not a diagnostic finding. Skipping the rest of the evaluation because a customer was certain about one area is how a second leak gets missed and how trust collapses when the pool continues to lose water after the repair.
Is it ever appropriate to rush the process because a customer has time constraints?
If time constraints prevent a complete evaluation, the technician should say so clearly before starting -- not skip compartments silently. "I have two hours before another commitment -- what would you like me to prioritize, and should we schedule a follow-up to complete the full evaluation?" is professional. Rushing through steps without telling the customer is not.
What if the customer disputes the no-leak-found result?
Return to the pre-visit agreement. If the customer was told before the process began that no active leak evidence observed is a valid outcome, and the report documents what was tested and what the tests showed, the result is defensible. If the customer was not told this in advance, the technician faces a harder conversation -- which is why establishing it at the arrival interview is essential, not optional.
How does Jeff David handle situations where he cannot find the leak?
Jeff uses the static drop test protocol -- plugging all lines, marking the water level, and using time as a diagnostic tool to let the pool's behavior reveal what active testing could not. He explains this to the customer as the next step in the diagnostic process, not as a failure. When appropriate, he schedules a follow-up under better conditions rather than forcing a conclusion before the evidence supports one.
Learn to Protect the Diagnosis From Outside Pressure
Professional neutrality, customer communication, and diagnostic discipline are all components of the H.U.N.T.E.R. Method taught through Leak Business Academy training.
View All LBA Courses Free Report App