How Do You Document a Structural Pool Leak?
Good documentation separates what was observed from what was confirmed. It protects the customer, the technician, and the repair decision -- especially when structural work, excavation, or follow-up contractors are involved.
Learn the H.U.N.T.E.R. Method →Document a structural pool leak by recording the customer history, pool type, water-loss behavior, operating conditions during inspection, defect location, dye test results, pressure test results if performed, photos, videos, areas not inspected, limitations, repair recommendation, and a verification plan. The report must clearly separate what was observed from what was confirmed -- those are not the same statement.
Why Documentation Matters on Structural Leaks
Structural leak documentation is more critical than documentation on a simple fitting or plumbing leak. A structural finding may lead to crack repair, waterproofing, excavation, deck removal, drain work, or inspection by a contractor who will not be present when the original diagnosis was made.
If the report uses vague or overclaiming language, it can lead to wrong repairs, customer disputes, or liability. If the report is too thin, it fails to communicate what was actually found and tested.
A strong report is specific, honest about limitations, and gives the next person -- contractor, homeowner, or insurance adjuster -- a clear picture of exactly what was inspected and what was confirmed.
What Every Structural Leak Report Should Contain
Every item below is a field in a complete structural inspection report:
The Professional Diagnostic Process -- What to Record at Each Step
Record the Customer's Water-Loss History
The customer's account is part of the permanent record. Document:
- When the loss started
- Approximate volume lost per day or per week
- Whether the pool is filled manually or by autofill
- Whether loss changes with pump operation
- Whether any repair, renovation, or deck work preceded the leak
- Whether a prior technician inspected the pool
Document the Pool and System Conditions
Before testing, record baseline conditions:
- Pool type: gunite, fiberglass, or vinyl liner
- Interior finish: plaster, pebble, tile, liner, etc.
- Equipment type and general condition
- Plumbing layout if visible
- Visible structural conditions including cracks, separation, rust staining, hollow plaster, tile displacement
- Water level at the start of inspection
Explain Why Each Area Was Tested
The report should state the reasoning, not just the result. Tie the inspection focus to the evidence:
- "Water loss appeared to slow near the deep-end floor-to-wall transition -- that area was dye tested first."
- "Customer reported loss occurring only at night with pump off -- shell and fittings below skimmer level were prioritized."
- "Crack was observed near the shallow-end light niche -- both the crack and the light niche were dye tested."
This narrative shows that the inspection was methodical and logical, not random.
Record All Test Conditions
- Pump: on or off during testing
- Water: still or moving during dye testing
- Autofill: on or off during level testing
- Valves: position during testing
- Lines isolated or tested together
- Dye test: performed or not performed
- Pressure test: performed or not performed
- If pressure tested: starting PSI, ending PSI, duration
- Weather or water temperature if relevant to test conditions
State Confirmed Findings With Precise Language
This is where most weak reports fail. The language must be exact -- no more, no less than what was confirmed.
See the wording table in the next section for specific examples.
State Limitations Explicitly
Every inspection has things that could not be tested. Name them:
- "Main drain cover could not be removed -- interior of main drain sump was not visible."
- "Underground plumbing behind the north wall was not pressure tested."
- "Conditions behind the shell were not visible and are not reflected in this report."
- "Autofill was active during the customer's normal water-loss period -- baseline may reflect autofill compensation."
Recommend Repair and Verification Method
State what repair is recommended and how to verify it was successful. Do not leave the verification step open-ended.
- Post-repair dye testing at the confirmed leak point
- Post-repair pressure test on the same line that failed
- 24-hour level test after repair under the same conditions as the original inspection
Precise Report Wording -- What Works and What Doesn't
The difference between a defensible report and a liability is the precision of the language used to describe findings.
| Situation | Correct Wording | Avoid |
|---|---|---|
| Dye pulled into a crack | ✓ Use "Dye testing showed active water movement into the crack at the deep-end floor-to-wall transition." |
✗ Avoid "The crack is leaking." |
| Dye did not pull | ✓ Use "Dye testing did not show active water movement at the crack at the time of inspection." |
✗ Avoid "The crack is not leaking." (too absolute) |
| Line held pressure | ✓ Use "Return line held [X] PSI for [Y] minutes during the test period." |
✗ Avoid "All plumbing is good." |
| Line failed pressure test | ✓ Use "Return line dropped from [X] PSI to [Y] PSI over [Z] minutes." |
✗ Avoid "Pipe is broken." |
| Area not inspected | ✓ Use "Underground plumbing on the north side was not pressure tested. Conditions there are unknown." |
✗ Avoid Omitting the limitation entirely. |
| Overall pool condition | ✓ Use "Inspected areas showed [specific results]. Conditions behind the shell and in uninspected areas are not reflected in this report." |
✗ Avoid "The whole pool is structurally failed." |
The H.U.N.T.E.R. Method as a Documentation Framework
Record the customer's water-loss history -- when it started, how much is lost, autofill status, and prior repairs. This becomes part of the permanent record.
Document the pool type, interior finish, equipment layout, visible structural conditions, and the plumbing configuration before testing begins.
In the report, explain why each area was tested. Tie the focus to the customer history, water-level behavior, or visible evidence.
Record all test conditions: pump status, water movement, autofill status, valve positions, dye test performance, pressure test data including PSI and duration.
State confirmed findings using precise language. Separate observed defects from confirmed leaks. Name limitations explicitly.
Include repair recommendation and post-repair verification method in the report. The verification plan is part of the documentation, not an afterthought.
Beginner vs. Professional Difference
Writes opinions. Notes what they saw and what they think is wrong. Leaves out test conditions, limitations, and precise wording. The report cannot be used as a defense if the diagnosis is challenged.
Writes evidence. Photos, test conditions, test results, limitations, and a repair path with verification. The report stands on its own -- even months later, even when another contractor is doing the work.
Common Documentation Mistakes
- Calling a crack a structural leak without dye evidence
- Not photographing the dye pull -- written description alone is weaker
- Failing to record pump status during testing
- Failing to record autofill status during level testing
- Not recording the starting water level
- Not identifying nearby fittings or penetrations
- Omitting limitations -- this is a major liability exposure
- Mixing suspected defects with confirmed leaks in the same sentence
- Making guarantees about hidden underground conditions
- Providing a repair recommendation with no verification plan
Tools Used in Structural Leak Documentation
About Jeff David
Jeff David is the founder of HUNTER Leak Institute and Leak and Subsurface Locators, LLC. He is a licensed pool contractor in Florida and an FSPA Palm Beach Chapter Board Member at Large. Jeff teaches the H.U.N.T.E.R. Method for pool and spa leak detection -- including report language, documentation standards, and how to separate what a technician observed from what testing actually confirmed. Strong documentation is a core part of professional practice, not an optional add-on.
Learn Professional Leak Documentation Standards
HLI training covers the full documentation workflow -- from field notes to report language to post-repair verification. Learn to write reports that protect both the customer and your business.
View Training Resources Get the Operational Kit