How to Document Storm Damage Before Calling a Roofer

Before you call a roofer, build a clean storm-damage packet: storm date, safe photos, room labels, exterior-side labels, visible collateral damage, interior leak signs, roof age, repair receipts, insurer questions, and the exact things you want the roofer to inspect. Do not climb on the roof, lift shingles, tarp the roof yourself, or try to diagnose the roof from a few photos. Your job is to document what you can safely observe, then help the roofer inspect the right areas first.

The packet should answer three questions without overstating anything: what happened, what you observed, and what needs professional follow-up. Keep weather context, property photos, insurance questions, and roofer questions clearly separated. That makes the first call more useful and gives you a calmer record if an adjuster, insurer, mortgage servicer, warranty reviewer, or second contractor later asks what you saw.

Start with the safety boundary

Document only after the severe-weather threat has ended. The National Weather Service after-severe-weather guidance says people should keep monitoring trusted weather information because additional storms may still be possible, and property damage should be assessed only after the threat has passed. NWS also warns about downed power lines, damaged buildings, and scams after property damage.

For this checklist, safe documentation means ground-level exterior photos, interior photos from safe rooms, and notes. It does not mean ladder work, roof walking, tarp work by an untrained homeowner, electrical work, or entering an unsafe structure. OSHA roof inspection, tarping, and repair guidance treats roof work as a worker-safety activity involving ladders, work above ground, power lines, tools, and steep or deteriorated surfaces.

Stop documenting and deal with safety first if you see active water entry near electrical fixtures, a sagging ceiling, exposed wiring, gas odor, structural movement, broken glass, downed lines, or an unstable room. Use qualified help for dangerous building systems or roof-access work. A missing photo is better than a homeowner injury.

What the packet can and cannot do

Use this table before you start collecting evidence.

This distinction matters because storms create confusing evidence. A dented gutter, ceiling stain, or neighborhood hail report may be important, but it does not decide causation, repair scope, warranty eligibility, coverage, or payment by itself.

Storm Packet Quality Score

Use a quick score before sending anything. The score does not decide whether the roof is damaged. It tells you whether the packet is clear enough for a roofer, insurer, agent, warranty reviewer, or second contractor to understand later.

Interpret the score:

The score rewards restraint. A packet that says "unknown" in the right places is stronger than a packet that makes confident claims from weak evidence. Storm recovery creates pressure to decide quickly, but a clean packet is useful because it separates facts from decisions.

The Storm Packet Rule

The best packet is boring. It does not argue. It does not diagnose. It does not try to sound like an adjuster, engineer, roofer, attorney, or weather expert. It says what happened, what you saw, what you photographed, what you could not inspect safely, and which questions need a qualified answer.

Use four folders or four sections in a notes app:

1_event-context
2_safe-photos
3_records-and-receipts
4_questions-for-reviewers

Keep each item in the right place. A weather alert goes in event context. A ceiling stain goes in safe photos. A dryout invoice goes in records and receipts. A coverage question goes in questions for the insurer or agent. A roof-surface question goes in questions for the roofer.

That separation protects the usefulness of the packet. If everything is thrown into one text thread, the roofer has to guess which photos are orientation shots, which are close-ups, which rooms are affected, and which statements are only homeowner concerns. If the packet is organized, the roofer can inspect faster and the homeowner can avoid repeating the same story to every person who later asks.

A Five-Minute Triage Before Photos

Before taking photos, decide whether this is a documentation task or an emergency task.

The goal is to avoid the common mistake of treating a dangerous situation like a paperwork exercise. A photo is useful only if taking it is safe.

Event Log Template

Write the event log before details fade. Keep it factual.

Property:
Date:
Approximate start time:
Approximate end time:
Weather observed by homeowner:
Hail observed: yes / no / unknown
Wind observed: yes / no / unknown
Heavy rain observed: yes / no / unknown
Falling branches or debris: yes / no / unknown
Rooms affected:
Exterior areas affected:
Immediate safety issues:
Temporary protection used:
Insurer/agent contacted:
Roofer contacted:
Open questions:

Avoid guessing. "Hail observed in driveway around 7:40 p.m." is useful. "Quarter-sized hail destroyed the roof" is not a safe homeowner conclusion unless the size was actually measured and the roof was inspected. If you do not know, write "unknown."

If there were multiple storms in the same week, do not merge them. Create a separate event line for each date. The goal is to keep the timeline clean enough that a roofer, insurer, agent, or later reviewer can follow which event prompted which observation.

Gather these seven items before the first call

1. Storm date, time, and event type. Write down the date, approximate time, and what you observed: hail, wind, heavy rain, falling limbs, flying debris, overflowing gutters, or sudden interior water. Add local warnings, neighborhood reports, or safe hailstone photos if you have them. If you are unsure, write "unknown" instead of guessing.

2. Four orientation photos. Take wide ground-level photos of the front, back, left side, and right side of the house. These images are not glamorous, but they are the map for every close-up that follows.

3. Exterior close-ups you can take safely. Photograph visible damage on gutters, downspouts, vents, window screens, siding, fences, garage doors, A/C equipment, vehicles, patio furniture, and ground debris. IBHS hail guidance explains that collateral signs such as dents or spatter marks on metal and outdoor items can help frame a hail question. Treat those photos as clues, not proof.

4. Interior room photos. Take one wide photo of the room, then a closer photo of the stain, drip, damp drywall, damaged insulation, cracked paint, or water trail. Label the room and the direction. "Upstairs bedroom, ceiling near west wall" is much more useful than "leak photo."

5. Roof and property history. Add the roof age if known, roof material, prior roof repairs, warranty paperwork, older inspection reports, recent gutter or flashing work, and known pre-storm conditions. This gives the roofer context before anyone tries to separate storm concerns from older wear, installation issues, maintenance problems, or product questions.

If your notes raise a product or defect question rather than a storm question, keep that as a separate issue and use the related RoofPredict guide: How to Identify Manufacturer Recall Shingles.

6. Insurance and repair records. Keep policy number, claim number if one exists, insurer or agent contact notes, receipts, temporary-protection records, cleanup receipts, and estimates. CFPB disaster property guidance supports contacting the insurer if covered property appears damaged and taking photos or videos when possible. NAIC claims guidance supports documenting losses and keeping receipts.

7. Unknowns for the roofer. Write the questions you cannot answer safely: "Need roof checked above dining room stain," "west gutter dented but roof not inspected," "large limb hit rear slope," "hail reported nearby, need soft-metal and shingle review," or "old patch near chimney may need comparison."

Use a photo order a stranger can follow

Do not send a roofer 80 unlabeled close-ups. Use an order that a person who has never seen your house can understand.

Step 1: orientation. Take the four side photos first: front, back, left, right. If the house has obvious sections, add simple names such as "front garage," "rear patio," or "left chimney side."

Step 2: exterior evidence. Take close-ups of visible exterior signs. Do not zoom so far in that the location is impossible to recognize. If the dent, crack, or stain is small, take one medium shot and one close-up.

Step 3: interior evidence. For each affected room, take a wide shot, then the close-up. If water is active, document from a safe distance and prioritize mitigation. Do not move wet insulation, open ceiling cavities, or enter an attic if the area is unsafe.

Step 4: temporary protection and receipts. If qualified help covers an opening, boards a window, removes a fallen limb, dries a room, or performs emergency mitigation, save the before photo, after photo, invoice, date, and company name.

Step 5: unknowns. Finish the set with a short note that separates what you saw from what you need inspected. This prevents accidental overclaiming.

Here is a simple photo label format:

If file names are too much, use a notes app with the same labels. The point is not perfection. The point is making the first inspection easier to follow.

The Photo Map: Wide, Medium, Close

For each visible issue, use the same sequence:

1. Wide photo: shows where the issue sits on the property.
2. Medium photo: shows the object or area.
3. Close photo: shows the detail.

Example:

Front wide: front of house from sidewalk.
Front gutter medium: left front gutter run.
Front gutter close: visible dent near downspout.

This pattern keeps close-ups from becoming mystery pictures. A close photo of a dent, stain, missing screen, or fallen branch is easier to use when the roofer can see where it belongs.

Use the same method indoors:

Bedroom wide: room and ceiling area.
Bedroom medium: ceiling area near west wall.
Bedroom close: stain edge and drip mark.

If the room is dark, take one photo with the light on and one without flash if safe. Do not move wet material, cut drywall, open attic spaces, or stand on furniture to get a better angle. The packet is not a repair job.

Room-By-Room Interior Log

Interior water signs often become confusing because homeowners photograph the stain but forget the room, floor, wall direction, or timing. Use a simple room log.

Do not force a roof conclusion from an interior sign. A stain may relate to roof covering, flashing, siding, window details, plumbing, HVAC, condensation, or an old condition. The log simply helps the roofer start in the right area.

Collateral Evidence Without Overclaiming

Collateral evidence means damage or marks on items around the roof: gutters, downspouts, siding, window screens, soft metals, vents, fences, A/C fins, vehicles, patio furniture, or outdoor equipment. These signs can help frame a hail, wind, or debris question, but they are not a roof-surface decision.

Use a ledger:

This ledger is useful because it preserves clues while keeping the homeowner out of the causation role. A roofer or insurer may ask about collateral signs. You can show them without overstating them.

A short homeowner scenario

Imagine a homeowner in a two-story house after a hail and wind storm. The next morning, they see dents on the right-side downspout, a torn window screen, small debris near the back patio, and a new ceiling stain in an upstairs bedroom. They cannot see the roof from the ground.

A weak packet would say, "Hail destroyed my roof," followed by a dozen close-up photos with no labels. That forces the roofer to rebuild the story from scratch and may create insurance confusion before anyone has inspected the roof.

A stronger packet would say:

• Storm observed around 7:30 p.m. on May 29.
• Hail and wind reported nearby; NOAA/NCEI context to be checked later.
• Front, back, left, and right orientation photos attached.
• Right-side downspout dent and torn screen photographed.
• Upstairs bedroom ceiling stain photographed from wide and close views.
• Roof not inspected by homeowner.
• Questions for roofer: inspect right slope, ridge caps, soft metals, flashing above upstairs bedroom, and any safe attic indicators.
• Questions for insurer or agent: what documents are needed, whether a claim number should be opened before permanent repairs, and how temporary mitigation receipts should be handled.

That packet is not longer because it is wordy. It is better because it separates observations, context, and decisions.

Keep storm history in the right place

NOAA/NCEI Storm Events Database records can help you research storm-date and area context. That context belongs in your packet, especially when you are trying to remember which storm happened on which date or when a roofer asks what event prompted the call.

But storm history is not roof proof. A weather record does not show whether your exact roof surface was damaged, whether the damage is new, whether that event caused the condition, whether the roof needs repair or replacement, or whether a policy covers the loss. Treat storm data as one column in the packet, beside photos, roof age, inspection findings, receipts, and insurer instructions.

If you use NOAA/NCEI context, label it plainly:

Weather context:
NOAA/NCEI storm record checked for county/date context.
This is not a roof inspection, damage diagnosis, or coverage decision.

That sentence keeps the record useful without turning it into an overclaim.

How To Use Weather Context Safely

Weather context should answer a narrow question: what event might the homeowner be talking about? It should not answer whether the roof is damaged.

Use this format:

Storm context checked:
Source:
County/city area:
Date:
Event type:
What the homeowner personally observed:
What the homeowner did not observe:
Why this matters for the roofer:

Example:

Storm context checked:
NOAA/NCEI county event record and local NWS warning history.
County/city area:
Example County, near north side of town.
Date:
May 29.
Event type:
Hail/wind context reported in area.
What the homeowner personally observed:
Heavy rain, hail hitting windows, debris in yard.
What the homeowner did not observe:
No roof surface inspection.
Why this matters for the roofer:
Please inspect soft metals, right slope, ridge, and area above upstairs stain.

That is a useful note. It is not a claim conclusion.

If a homeowner uses screenshots from a weather app, keep them in the packet but label them as homeowner-provided context. Do not treat screenshots as official storm proof unless the relevant reviewer says they are acceptable for that purpose.

The Pre-Roofer Handoff Script

When you call or email the roofer, send a short note that makes the inspection easier.

Hi [Name],

We had severe weather around [date/time]. I have not been on the roof and do not want to diagnose anything myself. I organized safe ground-level and interior photos so your inspection can start in the right places.

Packet summary:
- Storm date/time:
- Exterior signs:
- Interior signs:
- Collateral signs:
- Roof age if known:
- Prior repairs if known:
- Temporary protection or receipts:
- Areas I could not inspect safely:

Questions for inspection:
1.
2.
3.

Can your report label photos by roof area or elevation and separate observations, possible causes, and recommendations?

This script does two important things. It gives the roofer useful information, and it makes clear that the homeowner is not asking the roofer to rubber-stamp a homeowner diagnosis. That reduces confusion before the inspection begins.

The Packet Index

If the situation has many photos or documents, make an index at the top.

Packet index
1. Event log
2. Front/back/left/right orientation photos
3. Exterior issue photos
4. Interior room photos
5. Collateral item photos
6. Roof age and old repair records
7. Temporary protection receipts
8. Insurer/agent questions
9. Roofer inspection questions
10. Unknowns and safety limits

The index keeps the packet readable. It also lets you send different parts to different reviewers. A roofer may need the photos and roof history. An insurer or agent may need receipts and claim-process questions. A warranty reviewer may need product paperwork. A mortgage servicer may need claim-payment documents later. Keep the files organized so you do not send sensitive documents to the wrong place.

Call-Ready Summary Card

Before the first roofer call, reduce the packet to one card. This prevents the call from turning into a long photo tour.

Storm date/time:
What I personally observed:
Safety issues:
Interior signs:
Exterior signs:
Collateral signs:
Roof age/prior repairs:
Temporary protection or receipts:
Areas I did not inspect:
Top inspection questions:
Insurer/agent questions:
Documents attached:

Here is a filled example:

Send the card before sending every file. The roofer can ask for the full folder, but the summary tells them where to start. It also gives the homeowner a clean script if multiple contractors call back.

The card should not include private policy pages, bank records, legal notes, or unrelated documents. Share sensitive records only with the reviewer who needs them and only when you intend to share them.

Who Gets Which Packet

The same storm record should not be sent to every person in the same form. A roofer, insurer or agent, warranty reviewer, mortgage servicer, and future buyer may need different parts of the file. Sending too much can create privacy risk and confusion. Sending too little can slow the review.

Use this sharing matrix:

If you are unsure, send the call-ready summary first and ask what the reviewer needs next. Keep a private master file with everything, then make smaller shareable packets for each reviewer. That discipline protects the homeowner and makes the record easier for professionals to read.

The Privacy Pass Before You Share The Packet

Before sending the packet, make two versions: a private master packet and a share packet. The private master packet can hold everything you may need later. The share packet should contain only what the recipient needs for the next step.

This matters after storms because homeowners often send the whole folder in a hurry. A roofer may need the storm date, safe photos, roof age if known, prior roof repair notes, and inspection questions. The roofer usually does not need bank records, full policy pages, claim-payment documents, legal notes, mortgage letters, family notes, unrelated room photos, or every screenshot from a group text. Oversharing can create privacy risk and make the useful evidence harder to find.

Use a simple privacy pass:

Do not edit photos in a way that changes the evidence. If a photo contains private information in the background, either retake the photo safely, crop a copy while preserving the original, or send a different angle. Keep the original file in the master packet with its date. The share packet can be a cleaner copy, but the master packet should preserve the record.

Phone photos can also carry extra metadata such as time, device, and sometimes location. That metadata may be useful for your own record, so do not delete the original. If you do not want extra location details shared outside your own file, use the phone's sharing settings or export a copy before sending. Keep a note that the original is saved privately.

Use this naming pattern:

master-private/
  event-log.md
  original-photos/
  receipts-private/
  insurer-agent-notes/
  warranty-private/
  full-timeline.md

share-roofer-v1/
  00-call-ready-summary.pdf
  01-orientation-photos/
  02-exterior-signs/
  03-interior-room-photos/
  04-roof-age-prior-repair-context/
  05-inspection-questions.md

The private folder is allowed to be messy at first. The share folder should be clean enough that a roofer can open it and know where to start.

Here is a short message that sets the boundary without sounding difficult:

I made a short share packet for the inspection: event date, safe photos, room labels, roof age if known, prior related repairs, and inspection questions. I kept policy/payment/private documents out of this first packet. If a specific document would help your inspection or estimate, please tell me exactly what you need and why.

That message helps both sides. It tells the roofer the packet is intentionally limited, not incomplete by accident. It also gives the roofer permission to ask for a specific missing item instead of digging through irrelevant files.

If you are already in an insurance process, keep the insurer or agent lane separate. A claim number, adjuster appointment, policy-copy question, deductible question, depreciation question, mortgage-payment question, or payment-release question belongs in the insurer or agent lane unless you intentionally decide to share it with the roofer. The NAIC claims guidance and CFPB disaster guidance support careful records, photos, receipts, and insurer contact. That is different from sending every private claim document to every contractor.

For roofing companies, a privacy-aware packet is easier to work. The intake team can ask for roof age, storm date, safe photos, affected rooms, prior roof work, and inspection questions without encouraging homeowners to upload sensitive policy or payment documents. RoofPredict can support that boundary by keeping roof age, storm exposure, homeowner report fields, appointment routing, and CRM follow-up in the contractor workflow while leaving private claim, legal, and payment documents outside the inspection packet unless the homeowner intentionally shares them.

The privacy pass is also a quality check. If you cannot explain why a file belongs in the share packet, leave it in the master packet until a reviewer asks for it. A smaller, labeled packet usually gets a better first inspection conversation than a huge folder full of mixed photos, policy pages, receipts, screenshots, and guesses.

What To Save From The Roofer's Visit

The packet starts before the first call, but it should keep going after the roofer arrives.

Save:

• inspection date and company name;
• inspector name if provided;
• areas inspected and not inspected;
• labeled roof photos from the roofer;
• written inspection summary;
• estimate or scope if provided;
• temporary repair recommendation;
• warranty comments, if any;
• insurance routing comments, if any;
• open questions after the visit.

Keep the roofer's inspection report separate from your pre-call packet. Your packet says what you observed safely. The roofer's report says what the roofer observed or recommended. Mixing them together can make the record harder to read later.

If the roofer's report is unclear, use the related inspection-report guide. Do not stretch the storm packet into an argument about the report.

Clean Up The Packet After The Roofer Visit

After the roofer leaves, do a short cleanup pass before the next conversation. The goal is not to rewrite the story. The goal is to separate homeowner observations from roofer findings and make the next question clear.

Use this after-visit checklist:

Example status line:

After roofer visit:
ABC Roofing inspected the right slope, chimney area, and visible gutters on May 31. Roofer provided 12 labeled photos and a written estimate. Attic access above upstairs bedroom was not inspected. Estimate excludes interior drywall, hidden decking, and warranty review. Homeowner needs insurer/agent process instructions and a revised estimate question about flashing scope.

That status line is stronger than "roofer confirmed storm damage" because it says what was reviewed, what was not reviewed, what was excluded, and what still belongs to another reviewer.

If The Roofer Visit Leaves Open Items

A first roofer visit does not always answer every storm question. Weather may block roof access. A steep slope may need a different crew. A second story, solar array, skylight, chimney, attic area, or interior room may need another trade or a follow-up appointment. Treat that as an open-item record, not as a failed packet.

Ask the roofer to name the limit plainly:

Then add one short open-items note to the packet:

Roofer open items
Visit date:
Roofer/company:
Areas inspected:
Areas not inspected:
Reason not inspected:
Photos received:
Recommendations received:
Temporary protection:
Questions still open:
Next appointment or reviewer:

Use the roofer's words when possible. If the roofer says "rear upper slope not inspected because access was unsafe," keep that wording. Do not rewrite it as "rear roof has storm damage." If the roofer says "stain may relate to flashing but needs attic review," keep the uncertainty. Do not change it to "flashing leak confirmed" unless the qualified report says that.

This open-item step helps the next reviewer. A second contractor can see exactly what the first roofer could not inspect. An insurer or agent can see which documents exist and which are pending. A warranty reviewer can see whether the question is product-related, installation-related, weather-related, or still unknown. The homeowner can keep moving without turning uncertainty into a conclusion.

For RoofPredict, open items should become task fields, not loose notes buried in a text thread. A roofing team should be able to mark uninspected slope, missing photo, attic follow-up, temporary protection, homeowner document request, insurer question, and next appointment. That makes the packet useful after the first visit instead of ending at the appointment request.

If The Roofer Finds No Storm Damage

Sometimes the useful result is "no storm damage found in the inspected areas." That can be a good outcome, but it should still be documented carefully. The phrase does not mean every hidden area is clear, every interior sign is explained, or the homeowner should throw away the packet. It means the roofer did not find storm damage under the inspection scope and conditions described.

Ask for the finding in writing:

A clean note might say:

Roofer inspected front, right, and rear slopes on June 1, plus visible gutters and soft metals. No storm damage was reported in inspected roof areas. Rear upper slope above dormer was not walked due to pitch. Upstairs bedroom stain remains unresolved; roofer recommends monitoring after next heavy rain and further review if stain expands.

That note is stronger than "roofer said no damage" because it preserves scope and limits. It also keeps the homeowner from converting a reassuring result into a broader conclusion than the roofer actually gave.

If the roofer points to a non-storm issue, move the packet to the right lane. A maintenance item belongs in a maintenance or repair follow-up. A product question belongs in a warranty or manufacturer packet. A confusing inspection report belongs in the report-reading workflow. A pricing question belongs in the estimate workflow. Do not keep forcing the file through the storm lane after the evidence points somewhere else.

Second-Roofer Handoff Without Restarting

A second roofer can be useful when the first visit leaves a major open item, a large scope recommendation lacks support, a roof area was not safely inspected, or the homeowner needs another qualified view before approving work. The second handoff should be neutral. It should not ask the second roofer to prove the first roofer wrong.

Send a focused packet:

Use a short message:

I am asking for a second roofing review of one open item: [specific item]. The first packet and report are attached for context. I am not asking you to comment on coverage or to attack another contractor. I need your own observations, photos, limits, and recommendation for this item.

This protects the homeowner and the contractor. The second roofer gets enough context to avoid repeating confusion, but the assignment is still their own inspection and judgment. If the second report disagrees, compare the reports by inspected areas, photos, limits, confidence language, and scope. Do not decide from tone alone.

RoofPredict can support this handoff by keeping the first packet, first report, open item, second appointment, second report, and final decision lane in one workflow. It should not label one contractor right or wrong. The useful product role is document control and follow-up routing, not dispute resolution.

The Decision Record Before The File Moves Forward

After the roofer visit, a no-damage finding, a second opinion, or an insurer conversation, the homeowner needs one small decision record. This is not a claim argument and it is not a legal file. It is the handoff note that says where the issue belongs next and what evidence supports that route.

Use one row per issue:

The record should be boring. Boring is good. It means the next person can see the issue, the evidence, the lane, the owner, and the next step without reading a long text thread.

Here is a usable final note:

Storm documentation decision record
Property:
Event date:
Packet version:
Roofer visit date:
Primary issue:
Evidence saved:
Areas inspected:
Areas not inspected:
Current lane:
Owner:
Next action:
Question still open:
Documents not yet received:
Follow-up date:

This record is especially useful when the answer is not dramatic. Many storm calls end with "monitor," "repair a small area," "route to warranty," "ask insurance process questions," or "no storm damage found in inspected areas." Those outcomes are easier to trust when the file shows how the decision was reached.

For a roofing company, this is where a homeowner-facing intake packet becomes an operational workflow. The lead may start as "storm damage," then resolve into inspection needed, estimate needed, second appointment needed, insurer question pending, warranty route, gutter route, or monitor only. RoofPredict should help the team separate those lanes so follow-up is specific and credible.

What to ask insurance before you sign anything

If covered property appears damaged and you may need a claim, CFPB guidance supports contacting the insurer and asking for a policy copy if needed. NAIC guidance supports documenting losses, keeping receipts, contacting the insurer or agent, and understanding that the adjuster process may be part of the claim.

Before hiring a roofer for more than an inspection, ask your insurer or agent process questions:

• Do I need a claim number before permanent repairs?
• What temporary protection is expected or allowed?
• What documents and photos should I preserve?
• Does my policy have a special wind or hail deductible?
• Should I get more than one estimate?
• How should I handle emergency repair receipts?
• Are there limits on signing repair contracts before an adjuster sees the property?
• Are there mortgage-servicer steps if claim funds are issued jointly?

These are process questions, not legal advice. Deadlines, duties, deductibles, covered causes, depreciation, and payment rules vary by policy and state. If the situation is urgent, unsafe, disputed, or expensive, get instructions from the insurer, agent, qualified contractor, and other appropriate professionals.

What to ask the roofer on the first call

CFPB contractor guidance recommends researching contractors, comparing bids, checking credentials, keeping written records and receipts, and avoiding pressure tactics. FTC home improvement guidance also warns consumers to be careful with contractors who pressure, demand payment up front, or ask people to sign quickly.

Use the first roofer call to test whether the company works from evidence:

• Can you inspect without me climbing onto the roof?
• Will your inspection photos be labeled by roof area or elevation?
• Will you separate storm concerns, age, installation issues, and maintenance items?
• Can you provide a written inspection summary before any repair contract?
• Are you licensed or registered where required, insured, and local?
• Do you provide references or recent local projects?
• Will you explain what is urgent, what can wait, and what is uncertain?
• If insurance may be involved, how do you keep inspection findings separate from coverage decisions?

If the caller wants a signature before inspection, refuses to provide contact information, has no local history, or pushes a large upfront payment without a written contract, slow down. That does not mean every storm-response contractor is bad. It means you should verify before committing.

A Separate Question List For Each Reviewer

Do not ask every person every question. That creates confusion.

Ask the roofer:

• What roof areas did you inspect?
• What areas were not inspected and why?
• Which photos support each finding?
• Which items are urgent, repair, monitor, or further evaluation?
• Are there interior, gutter, siding, fascia, or decking items outside your roof scope?

Ask the insurer or agent:

• Should I open a claim before permanent repairs?
• What photos, receipts, estimates, and mitigation records should I keep?
• Are there policy deadlines, deductible rules, or claim-process steps I should know?
• How should I handle emergency receipts?
• Should I wait for an adjuster before signing a non-emergency repair contract?

Ask a warranty reviewer or installer, if warranty is relevant:

• Which product or workmanship documents are needed?
• Does temporary work affect the warranty?
• Who should inspect before permanent repair?
• What photos or samples should be preserved?

Ask yourself:

• What did I personally observe?
• What did I infer?
• What do I still not know?
• Which photos are safe, labeled, and dated?

The point is routing. Roofers, insurers, agents, warranty reviewers, and homeowners each have different roles. A good packet respects those roles.

For terminology help before the conversation, use the related RoofPredict guide: How to Talk to a Roofer Without Knowing Roofing Terms.

If the visible issue is mostly gutter or downspout damage, keep this workflow focused on documentation and use the related decision guide later: Should You Replace Gutters When You Replace Your Roof?.

What not to say before inspection

Neutral wording protects you. It also makes the roofer's job easier.

This is not about weakening your record. It is about keeping observations separate from conclusions.

The RoofPredict pre-roofer handoff

RoofPredict is contractor-facing software, not a homeowner insurance file, warranty file, legal record system, or roof inspection. A roofing team using RoofPredict can combine roof age, storm exposure, branded homeowner reports, inspection requests, and CRM follow-up with the homeowner's safe observations.

The best handoff is one page:

1. Property address and contact information.
2. Storm date, approximate time, and event type.
3. Weather context, labeled as context.
4. Roof age, material, warranty status if known, and prior repairs.
5. Exterior photo map: front, back, left, right.
6. Interior room-by-room leak or stain notes.
7. Collateral evidence photos: gutters, downspouts, A/C, siding, windows, vehicles, fence, patio.
8. Receipts and temporary-protection notes.
9. Insurance company or agent questions.
10. Inspection questions for the roofer.
11. Unknowns that need professional inspection.

The handoff should make the roofer's inspection more efficient. It should not claim that RoofPredict, a photo packet, or a weather database has already determined roof damage or coverage.

For a roofing team, the strongest version of this workflow is a clean intake record:

Property:
Storm date:
Roof age signal:
Storm exposure signal:
Homeowner photos received:
Interior symptoms:
Collateral signs:
Prior repair notes:
Inspection priority:
CRM next step:
Report needed:

That record is not a damage decision. It is a way to decide who needs a call, what the inspector should review, and what the homeowner has already provided. RoofPredict can help organize roof age, storm exposure, branded reports, and CRM routing around that workflow. The field inspection and written explanation still belong to the roofing professional.

Version Control For The Storm Packet

Storm records change. You may add photos, receive a roofer report, open a claim, get a claim number, find an older roof invoice, or receive a revised estimate. Save versions instead of letting messages scatter across texts, email, and downloads.

Use simple file names:

2026-05-29_storm-event-log.txt
2026-05-29_orientation-photos.zip
2026-05-29_interior-room-photos.zip
2026-05-30_roofer-inspection-report.pdf
2026-05-30_roofer-photo-index.pdf
2026-05-31_temporary-protection-receipt.pdf

Keep a version note:

This is useful even if no claim is filed. It helps you explain what happened, what changed, and what you asked someone to review.

Common Packet Mistakes

Avoid these mistakes:

• sending only close-up photos with no orientation;
• mixing weather screenshots, roof photos, receipts, and claim questions in one text thread;
• labeling every mark as hail or wind damage before inspection;
• omitting roof age and prior repair history;
• forgetting room names for interior stains;
• failing to save receipts for temporary protection;
• asking the roofer to answer coverage questions;
• asking the insurer or agent to diagnose the roof;
• treating storm records as property-specific roof proof;
• waiting too long to write down the event timeline;
• climbing the roof for a better photo.

Most of these mistakes come from rushing. A ten-minute packet structure is faster than rebuilding the story later from scattered photos.

After the roofer sends an inspection report, use the related guide How to Read a Roofer Inspection Report as a Homeowner to separate observations, opinions, recommendations, photos, and insurance or warranty routing notes.

If the process later turns into an estimate review, move to the estimate-specific guide instead of stretching this packet into a pricing article: How to Read Xactimate Estimates Like a Pro. If a contractor later needs to explain why Xactimate pricing differs by month, market, or job condition, use How Xactimate Pricing Varies: A Roofer's Guide.

Pre-call checklist

Before you call, gather:

• storm date, approximate time, and what you observed;
• four orientation photos: front, back, left side, right side;
• close-up photos of visible exterior issues, labeled by location;
• interior photos by room, including ceiling stains, drips, damp areas, or safe attic observations;
• collateral evidence photos, such as gutters, downspouts, A/C equipment, windows, siding, fences, or vehicles;
• roof age, roof material, prior roof repairs, warranty documents, and any older roof photos;
• policy number, claim number if one exists, insurer or agent contact notes, and deductible questions;
• receipts for emergency work, temporary protection, cleanup supplies, or repair services;
• a short list of what you need the roofer to answer;
• a separate list of insurance-process questions that only the insurer or agent should answer.

Use neutral labels. "Back-left gutter dent, photo taken May 29" is useful. "Hail destroyed the back roof slope" is a conclusion unless the roof has been inspected and documented. Good labels make the roofer's inspection more efficient and keep your own file easier to explain if you later speak with an adjuster, insurer, mortgage servicer, warranty reviewer, or another contractor.

If the roofer asks for photos before coming out, send the packet with the same limits. These photos show what you observed safely. They do not replace an inspection, and they should not be used to diagnose hidden roof conditions without a qualified person looking at the roof.

One-Page Packet Worksheet

Copy this before you call.

Property:
Homeowner contact:
Storm date/time:
Weather observed:
Safety issues:

Roof age/material if known:
Prior repairs:
Warranty paperwork:
Old photos/reports:

Exterior orientation photos:
Front:
Back:
Left:
Right:

Exterior issue photos:
Interior room photos:
Collateral evidence photos:
Temporary protection:
Receipts:

Questions for roofer:
1.
2.
3.

Questions for insurer/agent:
1.
2.
3.

What I did not inspect:
What I am not claiming:
Next appointment:

The two most important lines are the last two. "What I did not inspect" keeps uncertainty visible. "What I am not claiming" keeps the packet from drifting into diagnosis, coverage, warranty, or legal conclusions.

The First 72 Hours After The Call

The packet should not stop when the appointment is scheduled. The first three days after the storm often include new stains, drying work, contractor calls, insurer calls, and revised questions. Keep adding facts without changing your original notes.

Use this 72-hour log:

Do not edit the original event log to make it cleaner. Add a dated note instead. If the stain grew on day two, write that. If a room dried out after mitigation, write that. If a contractor corrected your assumption, write that too. A clean record is not a perfect record. It is a dated record.

This matters for homeowners because storm recovery produces many conversations. A roofer may ask when a stain first appeared. An insurer or agent may ask when temporary protection happened. A second contractor may ask whether a mark was present before the storm. You may not know every answer, but dated notes are better than memory.

When New Evidence Appears After You Send The Packet

Storm damage records often change after the first call. A stain may spread. A room may dry out. A branch may be removed. A roofer may send labeled photos. An insurer or agent may ask for a different document. Do not rewrite the original packet. Add a dated update.

Use this update note:

Update date/time:
What changed:
Where it was observed:
Photo/video label:
Who reported it:
Safety issue:
Reviewer notified:
Open question:

Examples:

This process keeps the packet credible. The first version remains the first version. Updates show what changed later. That is more useful than a cleaned-up story that hides uncertainty.

A "Do Not Infer" List

Before sharing the packet, add a short list of things the packet does not prove. This feels cautious, but it makes the file more credible.

This packet does not prove:
- that the roof surface is damaged;
- that the damage is new;
- that hail, wind, or debris caused a specific roof condition;
- that repair or replacement is required;
- that insurance coverage applies;
- that warranty coverage applies;
- that hidden damage exists;
- that a specific contractor scope is correct.

This packet does show:
- what the homeowner observed safely;
- when the homeowner noticed it;
- where photos were taken;
- what records and receipts exist;
- what areas need professional review.

Those statements are not meant to weaken your position. They help everyone read the packet correctly. A roofer can still find roof damage. An insurer can still open a claim process. A warranty reviewer can still ask for product documents. The packet simply stays in its lane.

When The Packet Is Too Large

If you have dozens of photos, send a summary first. Large unorganized uploads often slow the first call.

Use this format:

Summary:
- 4 orientation photos
- 6 exterior issue photos
- 3 interior room photos
- 2 collateral item photos
- 1 temporary-protection receipt
- 1 event log

Most important inspection questions:
1. Check roof area above upstairs bedroom stain.
2. Check right slope and right gutter/downspout area.
3. Identify any safe next step if roof access is limited.

Then attach the files or share a folder if the contractor can receive it securely. Do not send private policy documents, claim documents, or unrelated financial records unless the recipient needs them and you intend to share them.

What Makes This Packet Useful For A Roofing Team

A roofing team does not need a homeowner to diagnose the roof. It needs a better starting point.

A strong packet helps the team:

• prioritize urgent water-entry calls;
• route the right inspector;
• know which slope, room, or exterior side to inspect first;
• compare homeowner observations with roof age and storm exposure context;
• prepare a clearer inspection report;
• avoid losing details in text messages;
• send a more useful follow-up summary after the visit.

That is why this workflow fits RoofPredict. The product context is not "AI decides the roof." The useful context is: roof age, storm exposure, homeowner report, inspection request, route or CRM status, and a follow-up record that keeps the inspection conversation moving.

Source limits

FAQ

Should I call a roofer or insurance first?

It depends on the damage, urgency, policy, and insurer instructions. If covered property appears damaged, CFPB and NAIC guidance support contacting your insurer or agent and asking what documents are needed. A roofer inspection can help identify roof conditions, but the claim process belongs to the insurer and policy.

Should I wait to take photos until the roofer arrives?

No. Take safe photos as soon as conditions allow. CFPB, NAIC, and Ready.gov guidance support documenting damage, receipts, and recovery records. Do not delay urgent safety steps just to get better photos.

Do I need roof photos?

You need useful photos, not dangerous photos. Ground-level exterior photos, interior leak photos, and collateral evidence are appropriate for a homeowner packet. Roof-surface photos should come from a qualified inspection.

Does storm history prove storm damage?

No. NOAA/NCEI storm records provide date and area context. They do not prove that a specific roof was damaged, that damage is new, that a policy covers it, or that repair or replacement is required.

What if I only have interior photos?

Use them, but label them carefully by room, date, and location. Interior photos can show a water symptom; they do not prove the exact roof entry point without qualified inspection and other evidence.

Should I send every photo to the roofer?

Send the organized packet or a short summary first. Prioritize orientation photos, clear exterior issue photos, room-labeled interior photos, collateral signs, receipts, and the exact inspection questions.

Should I include claim numbers, policy pages, or payment records in the roofer packet?

Usually not in the first share packet. Keep private insurance, payment, mortgage, legal, and unrelated personal records in a master packet unless you intentionally choose to share a specific item. The roofer usually needs safe photos, roof age if known, prior related repairs, temporary-protection notes, and inspection questions.

What should I avoid saying to the roofer?

Avoid conclusions you cannot support yet. Say "we had hail nearby and I documented these signs" instead of "hail destroyed the roof." Ask the roofer to inspect, photograph, label, and explain the findings.

What should I keep after temporary protection or emergency dryout?

Keep before photos, after photos, invoices, dates, company names, receipts, and notes about what was done. Ask your insurer or agent how those records should be handled if a claim process is involved.

What if the damage changes after I send the first packet?

Do not rewrite the original packet. Add a dated update with what changed, where it was observed, who observed it, the new photo or video label, who was notified, and what question remains open.

What if I already opened a claim before calling a roofer?

Keep the claim number and insurer or agent instructions in the insurer/agent section. Still keep the roofer packet separate: safe photos, roof age, prior repairs, inspection questions, and what the roofer should inspect. Do not ask the roofer to decide coverage.

Should I send weather screenshots to the roofer?

You can include them as homeowner-provided context, but label them as context only. Weather screenshots and storm databases do not prove property-specific roof damage, repair scope, coverage, or warranty eligibility.

Can RoofPredict decide whether the storm damaged my roof?

No. RoofPredict can support a roofing team's roof age, storm exposure, homeowner report, inspection request, and CRM workflow. It does not inspect the roof, decide causation, determine coverage, approve warranty claims, or replace qualified professionals.

What if the roofer says there is no storm damage?

Ask the roofer to document what was inspected, what was not inspected, which photos support the finding, and whether any non-storm issue needs a different lane. Save the packet instead of deleting it. A no-storm-damage finding is useful, but it should stay tied to the inspection scope and limits.

How should I ask a second roofer for another opinion?

Send a neutral packet with the storm date, safe observations, first roofer visit date, relevant photos, the first report or estimate if you choose to share it, and the exact open question. Ask for the second roofer's own observations, photos, limits, and recommendation, not an attack on the first contractor.