Emergency Roof Repair: What to Do When Disaster Strikes

During a roof emergency, keep people clear of unsafe rooms, damaged ceilings and electrical hazards. Document visible conditions only where safe and obtain qualified help rather than attempting exterior temporary repairs.

Observe without entering a hazard

Describe what is visible from safe ground or an unaffected room. Stay away from bulging ceilings, unstable materials and wet electrical equipment. Do not puncture a water-loaded ceiling or climb onto the damaged roof.

Separate interior protection from roof work

Move belongings or collect drips only if the area is safe. Exterior covers, temporary attachments and access to the roof require appropriate people, equipment and methods. Generic instructions to stretch a tarp do not make that work safe.⁠^[1]

Confirm the actual response

Ask the company contacted whether it is available, what it can assess safely and whether the proposed work is temporary or permanent. An unanswered inquiry or a website phone number does not reserve an emergency visit.

Document the loss and communicate

Keep dated photographs, notes, earlier repair records, receipts and communications. Ask the insurer how the policy applies and what information is needed. Do not infer coverage or a settlement amount from the size of the visible stain.

Verify the contractor and agreement

Match the company in the proposal with relevant license records and ask for appropriate insurance evidence. Read the scope, payment terms and responsibility for damage. Avoid treating a promise of a quick fix as proof of qualifications.⁠^[1]⁠^[2]

Use temporary work to inform a permanent plan

The assessment should explain the water path and which components need attention. A repair may be sufficient on an otherwise serviceable roof; a repeated or widespread problem may justify a broader proposal. A leak alone does not establish the answer.⁠^[1]

Keep a useful record afterward

Record what was done, which areas remain unchanged and what follow-up is needed. Future maintenance should follow the actual system and condition, not an assumed package or availability promise.