Describe the symptom
Record meter movement, moisture, sound, temperature, odor, pressure, drainage, or pool-level behavior and when it occurs.
Evidence before repair
Leak Detection Process
A six-stage process for moving from an unexplained symptom to a documented repair decision.
Map the systems
Identify meters, valves, fixtures, buried routes, pools, equipment, drainage, irrigation, condensate, and property boundaries.
Isolate competing sources
Use controlled water use and accessible isolation points to separate pressurized, drainage, pool, appliance, envelope, and past-moisture explanations.
Test and correlate
Apply the methods appropriate to the system and look for repeatable results rather than a single unexplained instrument reading.
Document the finding
Record the likely zone, evidence, test conditions, access limits, uncertainty, and the next step needed before repair.
Scope repair separately
Compare access, pipe repair, excavation, restoration, permits, drying, remediation, and utility coordination as separate authorized work.
Questions and decisions
Leak detection process questions
Testing sequence, documentation, access, and uncertainty.
Does every request use every tool?
No. Tools are chosen after the symptom and system boundary are defined. Using every instrument can add time without improving evidence.
What should a detection result contain?
It should state the test conditions, observations, likely zone or system, limits, and the next step needed before repair.
Can testing require a shutdown?
Yes. Meter, pressure, line, fixture, commercial, and pool tests may require controlled water use, isolation, or equipment changes.
Who approves access or destructive work?
The property owner or authorized manager must approve access. Destructive access is outside this pre-launch detection scope unless separately contracted.
What happens when the source remains uncertain?
The result should explain the remaining possibilities and the most useful next test or access step rather than present an unsupported conclusion.
Prepare the service request
Prepare the symptom before the test plan.
Share what changed, when it happens, the systems that may be involved, and any access or shutdown limits.
Request Leak Detection