Track leak events across roof, wall, and equipment junctions
Build a Record for an Intermittent Roof Leak
Use event patterns to guide an assessment when the symptom does not appear during every rain.
Document the actual condition
A stain that appears only in certain storms needs an event comparison, not a conclusion from one dry-day visit. Record rain duration, wind direction when reliably available, symptom delay, room, drying time, overflow observations, and whether the same area stayed dry during other events.
Set the inspection questions
Use the pattern to prioritize walls, transitions, valleys, edges, and penetrations while recognizing that absence of moisture during inspection does not prove watertightness. If controlled testing is appropriate, document method, interior observer, responsible parties, stopping rules, and risks; testing is not suitable for every assembly or condition.
Write a comparable scope
Keep diagnostic testing separate from permanent work unless the written basis and conversion are clear. The repair boundary should identify evidence, preparation, tie-ins, and remaining uncertainty. After work, retain later event notes and avoid declaring resolution until suitable weather observations support the conclusion.
Preserve the decision record
Use a simple event table with a row for every meaningful rain, including events when the location stayed dry. Negative observations can be as useful as leak reports when comparing duration, direction, and delay. Keep indoor humidity or plumbing events separate so the roofer can evaluate competing explanations without blending unrelated moisture records.
- Log meaningful dry storms as well as leak events
- Define testing stop rules before controlled water begins