How to Find Storm Damage in Your Service Area (Workflow)
A repeatable 5-step workflow for surveying storm damage in your service area within 48 hours of a major event. From NOAA confirmation to prioritized knock list.
In the 48 hours after a major hail event, hundreds of roofers in the impacted region are simultaneously trying to identify damaged properties. The shops that win the next 30-60 days of work in that region are the ones with a structured workflow they can execute fast — not the ones reacting in chaos.
This post is the 5-step workflow I've seen work consistently for storm-belt residential roofers. It compresses the "identify damaged homes" step from weeks of canvassing to hours of triage.
The 48-hour window: why speed beats thoroughness
After a major storm event:
- Hour 0-12: social media + local news cover the event. Homeowners aware something happened.
- Hour 12-48: homeowners start checking their own roofs. Some find damage; some don't notice.
- Hour 48-96: the first contractors arrive door-knocking. Speed advantage starts compounding.
- Day 5-10: insurance claims start filing.
- Day 10-21: adjusters visit + contracts get signed.
- Day 21+: opportunity is largely gone.
Speed matters because:
- The homeowner picks the FIRST credible contractor they meet (recency bias)
- The 14-21 day adjuster window starts as soon as the claim is filed — you want to be named contractor BEFORE that
- Neighborhood cascade effects start within days — early homeowners who pick contractors influence later ones
The shops that show up Day 3-5 with documented damage signatures win. The shops that show up Day 14+ are competing with 5 others on price.
Step 1: Confirm the storm path
Within 24 hours of the event:
Sources to consult:
- NOAA Storm Events Database (
ncdc.noaa.gov/stormevents) — official confirmation of date/location/magnitude - HailTrace or Interactive Hail Maps — swath visualization with timing
- Local news + Twitter/X reports — supplementary confirmation
- Your local meteorologist's social — sometimes detailed real-time reports
What you're trying to identify:
- Exact swath (typically 1-5 miles wide, 5-15 miles long for hail)
- Hail size + magnitude
- Wind speeds (separate damage profile)
- Affected zip codes
The output: a list of 3-15 zip codes in your service area that took confirmed impact, with rough magnitude.
If your service area didn't get hit, skip the workflow — chasing storm work outside your reasonable service radius rarely pencils out.
Step 2: Define the survey grid
Within 48 hours of the event:
For each affected zip:
- Pull total residential property count (free at county appraisal districts)
- Filter for residential single-family homes (drop commercial, apartments, vacant lots)
- Identify the swath path through the zip — not every home in the zip was hit equally
You want the subset of residential homes inside the actual hail swath, not the entire zip. A 4-mile-wide swath through a 50-square-mile zip might affect 800 homes out of 4,000.
The output: a target survey area of 500-2,000 homes per affected zip.
Step 3: Visual survey via satellite
Within 72 hours of the event:
Wait for satellite imagery to refresh (typically 48-72 hours post-event in major metros, longer in suburban+rural). Then run AI satellite damage detection on the survey grid.
What you're looking for:
Tier 1 signals (90%+ accuracy, immediate door-knock):
- Visible tarp installation
- Missing shingle sections
- Tree debris on roof
- Visible work-in-progress (rare this fast)
Tier 2 signals (verify on ground):
- Granule displacement vs pre-storm baseline
- Circular impact bruising
- Ridge wear acceleration
The AI screen typically flags 5-15% of the survey grid as damaged candidates. For a 1,000-home survey, that's 50-150 potential prospects.
Manual alternative: drive the swath path, look for tarps from the street. Slower (4-6 hrs to cover a swath manually vs. 5 min for AI), but works without subscription tools.
Step 4: AI-flagged + verification
Within 96 hours of the event:
For each AI-flagged candidate:
- Cross-check against the storm path — does the property sit IN the swath, or near the edge?
- Check roof age — was this an old roof that took damage, or a new roof that shouldn't have? Both are valid prospects but the conversation differs.
- Visual spot-check in Google Earth — confirm the AI's read on what it saw
Drop obvious false positives:
- Commercial flat roofs flagged residential
- Multi-unit complexes (apartment buildings, condos)
- Properties with ambiguous damage signals + no recent imagery
The output: a clean knock list of 30-100 high-confidence damage candidates, ranked by combined signal strength.
Step 5: Prioritization + outreach within 7 days
Days 4-7 post-event:
Prioritization sequence:
- Tier 1 signals + roof age 15+ years: highest priority — visit Day 4-5
- Tier 1 signals + roof age under 15: high priority — visit Day 5-6
- Tier 2 signals + roof age 15+ years: moderate priority — visit Day 6-7
- Tier 2 signals + roof age under 15: marginal — visit only if time allows
Door-knock with the storm-event opener:
"Hi — I'm Jake from Roofbird. The [May 9] hail
went through your neighborhood — we tracked the
swath from NOAA. Yours is one of the homes we
saw with possible damage signatures from above.
Before you file a claim, or decide not to, I
wanted to offer a free 10-minute inspection so
you know what you're actually looking at."
(Full storm-event script in the door-knocking post.)
Expected outcomes from a 50-knock sequence Day 4-7 post-event:
- ~25-30 conversations (homeowner home + willing to talk)
- ~15-20 inspections scheduled
- ~8-12 inspections completed
- ~5-8 claims filed
- ~3-6 jobs signed within 21 days
That's typical for ONE rep + ONE day of organized canvassing per storm event. Multiple reps + multiple days scales the output.
Cadence: repeating for every major event
The discipline that separates shops that win storm-chase work consistently:
On every major event (whether you've spotted it yet or not):
- Get NOAA alert notification (free, set up once)
- Within 24 hrs: confirm storm path, define survey grid
- Within 72 hrs: run AI satellite scan
- Days 3-7: door-knock the top 50-100 candidates
- Days 7-14: complete inspections, help homeowners file
- Days 14-21: adjuster visits, contract signing
- Days 21-60: secondary canvas (homes that didn't engage initially)
- Days 60-90: post-mortem, adjust next event playbook
The shops doing this end-to-end on every storm book 5-10x more storm-event work than reactive shops.
Roofbird automates Steps 3-4 — AI satellite scan + prioritization for any defined service area within 72 hours of a NOAA-logged event. The free trial covers your specific area. See the DFW sample for what storm-damage output looks like.
The pre-event preparation that matters
Most shops scramble after every storm because they didn't prepare BEFORE. The pre-event work that compresses your reaction time:
Before storm season:
- Define your service area precisely (zip codes, square miles)
- Sign up for NOAA email alerts on those zips
- Subscribe to a hail map service (HailTrace or IHM)
- Set up baseline imagery scoring on your service area (most AI tools do this on first scan)
- Train your team on the storm-event opener
- Pre-print storm-event door hangers
Day of storm:
- Trigger your team alert (group chat, Slack, whatever)
- Lock in canvas schedule for Days 4-7
- Pre-book rep canvassing hours
48 hours post-storm:
- Execute Steps 1-3 of the workflow
- Triage AI output
- Build the prioritized knock list
- Brief reps on the route + script
When the next storm hits, you're not reacting — you're executing a pre-built playbook. That speed advantage is structural.
What to do this week (even before the next storm)
If you operate in a hail-belt region:
- Set up NOAA email alerts for your service-area zip codes (free, 5 min)
- Pick one AI satellite tool and run a baseline scan on your service area
- Print 100 storm-event door hangers with the right opener-language
- Write your team's storm-event playbook (Steps 1-5 documented)
- Run a tabletop exercise with your reps — "if a hail event hit zip [X] tomorrow, what's our day-by-day plan?"
The shops that have the playbook documented before the next storm capture the next 30-60 days of work. The shops that don't lose to whoever does.
— Jake
Written by
Jake Thompson
Have a question about anything in this post? Reach the Roofbird team at support@roofbird.ai.
Try Roofbird — 25 free leads in your area
See a sample dashboard for DFW first, no signup needed. Trial loads 25 free pre-scored leads in your own service area.
More for roofers
How to Generate Roofing Leads Without Cold Calling: 7 Methods Ranked by Cost and Close Rate
Seven proven ways to generate roofing leads without cold calling — ranked by realistic cost-per-lead and close rate. From free GBP optimization to satellite roof scoring. No shared leads, no phone room.
How Solo Roofing Contractors Get Leads Without Angi or HomeAdvisor (7 Methods That Actually Work)
Seven proven ways to generate roofing leads without paying Angi or HomeAdvisor's marketplace tax — ranked by cost, effort, and lead quality for solo contractors and small crews.
Best Alternatives to EagleView for Roofing Measurements and Lead Generation (2025)
Honest breakdown of EagleView alternatives for roofers — Hover, Roofr, Nearmap, GAF QuickMeasure, and AI prospecting tools. Covers both measurement accuracy and lead generation, because most comparison articles only cover one.