Getting Stuck Is Not Failure -- Guessing After Getting Stuck Is
Every experienced leak detector has had jobs where the visual evaluation found nothing, the pressure tests held, the dye went nowhere, and the pool was still clearly losing water. This is not a rare edge case. It is a normal part of the work. The question is not whether it will happen -- it is what the technician does when it does.
The wrong response is to escalate to excavation without sufficient evidence. The wrong response is to declare a suspected finding that cannot be supported by what was actually observed. The wrong response is to leave and never follow up.
The right response is to change strategy. When active testing is exhausted, switch to state-based diagnosis. Use time as a tool. Let the system declare itself.
When active inspection and testing cannot locate the source, the professional move is not to push harder -- it is to change the mode of inquiry entirely.
The State-Based Diagnostic Reset Protocol
This is not a shortcut or a last resort. It is a deliberate diagnostic strategy for converting uncertainty into information. Each step introduces a new system state and observes the result -- removing technician interpretation and letting the pool's behavior reveal what testing could not.
Plug All Lines, Shut Down the Pump, Mark the Water Level
Install plugs in every line accessible at the pool -- returns, skimmer, main drain, cleaner, features. Shut the pump off completely. Mark the water level at the skimmer and with a reference mark on the pool wall. Set up a bucket test alongside. Wait -- overnight if possible, or a minimum of several hours.
Remove All Plugs, Keep System Static, Mark Again
Remove all plugs. Keep the pump off. Mark the water level again and observe over the same time period. Compare rate of loss to Step 1.
Start the Pump, All Lines Open, Observe Loss Rate
Start the pump and run the system normally. Mark the water level and observe over the same time period. Compare to Steps 1 and 2.
When to Stop, Shut Down, and Come Back
There are jobs where the state-based protocol also does not produce a clear answer within one visit. This happens when loss rates are very slow, when environmental conditions -- rain, auto-fill, sprinkler overspray -- are introducing variables that contaminate the test, or when the system's configuration makes clean isolation impossible.
The correct move in these cases is to stop, document the current state clearly, and schedule a follow-up under better conditions. This is not failure. It is professional control. Shutting the pool down and coming back when conditions support a clean test is far more defensible than committing to an excavation or a conclusion that the evidence does not support.
Document what was tested, what the results were, and what conditions prevented a clear conclusion. That documentation is what makes the return visit credible and the recommendation defensible.
State-Based Diagnosis and H.U.N.T.E.R.
When active testing cannot locate the source, the diagnostic reset stays within the H.U.N.T.E.R. framework -- it does not abandon it.
During the wait period of a state-based test, revisit the intake information. Does the customer's description of when they notice loss align with any of the system states being tested?
State-based diagnosis requires understanding how each system state changes the pool's hydraulic behavior. Plugged vs unplugged, pump on vs off -- these are system states, not random conditions.
Each state comparison narrows the investigation. Holds plugged, loses unplugged = fitting or line-end issue. Loses both = structural. Loses more with pump = pressure side. The narrowing continues through state changes.
State-based testing is still testing -- it is just using time and system isolation as the instruments instead of dye or pressure gauges. The evidence it produces is objective and measurable.
The result of each state test is documented -- water level marks, time intervals, comparison to the bucket test. These measurements are evidence, even when they show which system state is not producing loss.
A recommendation based on state-based test results is more defensible than one based on inconclusive active testing. "The pool holds when fully isolated and loses when the pump runs" is a documented finding.
When I get stuck, the first thing I do is the static drop test. I plug everything, shut the pump down, mark the water level at the skimmer and on the wall, set up a bucket test next to the pool, and I walk away. That time gives me space to reset mentally -- to get my thoughts back together and see what is actually going on without the pressure of being on the job in real time.
When I come back, I read what the pool did. If it did not lose water with everything plugged and the pump off, I know the loss has something to do with the line connections or the pump interaction. I take out the plugs and let it sit again. If it still does not lose, I run the pump. If I get a loss with the pump running, I know the system is leaking when it is active. Now I have a direction -- and I evaluate that direction specifically before I go any further.
The important thing I teach is that stopping is not weakness. Stopping and coming back with a plan is control. The technician who forces a conclusion because they feel pressure to have an answer is the one who ends up excavating in the wrong spot. Time is a diagnostic tool. Using it correctly is a skill, not a delay.
Frequently Asked Questions
How long should the static drop test run?
Overnight produces the clearest results when loss rates are slow. A minimum of 4 to 6 hours gives enough time to detect meaningful loss in most residential pool situations. The bucket test must run alongside for the same duration so evaporation can be subtracted from the total drop. Shorter time intervals may not produce detectable results if the leak rate is small.
What if the pool has an auto-fill device that interferes with the test?
The auto-fill must be disabled before any water level marking test is performed. An active auto-fill replaces lost water and makes it impossible to measure loss. Document that the auto-fill was disabled and when it was disconnected. If the auto-fill cannot be disabled due to the system configuration, note this as a testing limitation in the report.
Is shutting the pool down and coming back a professional or unprofessional response?
It is professional -- and it should be framed that way. A technician who leaves the pool in a documented state with a clear follow-up plan, who explains to the customer what was tested and what conditions prevented a clear conclusion, and who returns under better conditions to continue the investigation has performed correctly. The unprofessional response is forcing a conclusion that the evidence does not support.
Should the customer be charged for a follow-up visit when no leak is found on the first visit?
This is a business and pricing decision that depends on the company's service agreement and the scope of the original engagement. LBA does not advise on specific pricing or contract language. What is important is that the customer understands before the follow-up what will be done, what it will cost, and what the purpose of the additional visit is. Clear communication prevents disputes about billing when a job requires more than one visit to produce a conclusive result.
Learn the Full Diagnostic System -- Including What to Do When You Get Stuck
The H.U.N.T.E.R. Method and the Diagnostic Reset Protocol are taught in the Residential Pool Leak Manual and LBA live workshops. Getting stuck is part of the job. Knowing what to do next is the skill.
View All LBA Courses Free Report App