Leak Inspection Report SOP
Use this when: Reports differ by technician, and managers or insurers keep coming back with questions.
Owner: [operations lead] On site: 1. Record the address, unit, date, who gave access and who reported the leak. 2. Photograph the visible damage before starting. 3. Note the method and equipment used at each test point. 4. Record readings and where each one was taken. 5. Mark the suspected source on a plan or photo. Report, within [your target time]: 6. Summary: what was found, and how confident you are. 7. Evidence: photos and readings. 8. What couldn't be accessed or tested. 9. Recommended next steps, by trade. 10. Have a second person review it. 11. Send it to the agreed contact and file it by address.
Before you use this: Separate what you observed from what you suspect. Reports may be used for insurance or disputes.
Fill in the items in square brackets and adapt this to your business. It's a starting point, not legal or professional advice.
More for leak detection and infrastructure
Strata and Property Manager Intro Call Script
You want to become the go-to leak detection company for a property manager.
AI Prompt to Turn Technician Notes into a Draft Report
A technician's rough notes need to become a clean draft for review.
More sops
New Listing Launch SOP
A listing agreement is signed and you need every launch to happen the same way.
RFI Logging and Tracking SOP
Questions to the design team are getting lost, or nobody can say which ones are still open.
Service Call Close-Out SOP for Technicians
Job notes, photos and follow-ups vary from one technician to the next.
Check your key numbers with the Operator ScorecardSAZ's leak detection and infrastructure practice