How to Find Storm Damage in Your Service Area (Workflow)

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.

Start with the free US hail map — every NOAA hail and storm report in your service area, updated daily.

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. If you want the tool-by-tool version of the same problem, I wrote up how to find storm-damaged roofs in your area separately.

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:

1. The homeowner picks the FIRST credible contractor they meet (recency bias)
2. The 14-21 day adjuster window starts as soon as the claim is filed — you want to be named contractor BEFORE that
3. 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.

This is also the step where most shops waste the first 48 hours. If you search the area you work in Roofbird — a town, a suburb, a ZIP, or a street — it reads the neighborhoods in view and ranks them before you draw anything, so the first scan isn't a guess. For each block it reports the housing era, what share of roofs read as weathered, how many homes are actually there (counted from building footprints, not estimated from area), whether hail has hit in the last 12 months, and how walkable the block is. Scattered acreage on long driveways gets called out as bad canvassing even under a perfect storm, because a morning is measured in doors per hour. Click a suggestion and it draws the area for you; you can drag the corners or draw your own polygon from scratch. When nothing in view clears the bar it says so plainly rather than offering you three neighborhoods to skip.

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 (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

A screen typically flags a minority of the survey grid as damaged candidates. For a 1,000-home survey that is a workable knock list rather than a thousand doors.

The catch nobody warns you about: a top-down tile can be years old. A contractor in Missoula drove nine doors off his own list and eight of them had already been re-roofed. His neighborhood had been ranked from a July 2016 aerial photograph while a 2025 street-level shot of the same houses sat unread. The roofs had not changed since we read them; the picture had. Street-level imagery is newer than the aerial on about 85% of roofs, by roughly five years.

So Roofbird reads the overhead tile AND a ground-level Street View of the façade together into one combined assessment, and checks every shortlist against the newer picture before you see it. Anything already done is moved down and said out loud, and the houses that genuinely cannot be judged — behind tree canopy, set too far back from the road — are labeled as exactly that rather than mixed in with the confident ones. Where the street camera could see the roofs, what it reported matched what the contractor found on the ground 4 of 4; where it could not, 0 of 5. Where the aerial and the street photo disagree, the newer one wins and both dates are shown. A roof whose own description says it was recently replaced never reaches the top of a list.

The Street View read also catches side-visible wear a top-down tile can't: granule loss, algae streaking, curling shingles, patched sections, rusted flashing. It compares the roof against its immediate neighbors from a wider centered view — if the houses either side have visibly been re-roofed and this one hasn't, that's flagged, because a street where the neighbors have already gone new is the strongest social proof in the trade.

Manual alternative: drive the swath path, look for tarps from the street. Slower (4-6 hrs to cover a swath manually vs. minutes for a scan), but works without subscription tools.

Step 4: AI-flagged + verification

Within 96 hours of the event:

For each flagged candidate:

1. Cross-check against the storm path — does the property sit IN the swath, or near the edge?
2. 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.
3. Visual spot-check — confirm the 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.

Here is where the ranking itself matters more than the list. Every lead carries two numbers. NEED is how badly the roof needs replacing — condition and roof age only. NOW is whether anything is forcing a decision on THIS house: visible active damage like a tarp, missing shingles or exposed decking, hail damage on this specific roof, a purchase in the last 18 months, patching already attempted, or neighbors who have re-roofed. Alongside it sits a one-line "why now" in plain words.

Neighborhood hail deliberately does NOT raise the NOW score. Every home in the scan shares it, so it cannot separate one door from the next. It belongs in the pitch, not the ranking. This is the opposite of how most storm-chasing lists work, and it's why the ranking is trustworthy: most homes in a settled neighborhood honestly have no trigger, and Roofbird says so rather than inventing urgency to look busy. Where a hail event is on record, it also shows roughly how long the homeowner has left to file an insurance claim, based on the typical notice deadline in that state. That is an estimate of a typical state deadline, not a legal one — verify with the carrier.

Each roof is placed against the roofs either side of it — replace-now, worn, midlife, or already done — because a roof only means something next to its neighbors, and a number nobody can repeat at a door was never the point. Alongside it sits a plain-English verdict in a roofer's words and the specific reasons behind it, plus the roof's size in squares, how many planes it has and how steep it is. Each lead shows roof material, condition, estimated roof age (read off the shingles, not the building's year built), wear signs, both images, an estimated squares and job-value range, and a ready-to-say door pitch.

The full property record shows on every lead for free, as soon as it's scanned: owner name, whether they live there or it's an absentee/rental owner, estimated market value and confidence, year built, last sale date and price, beds/baths, living square footage, lot size, stories, garage, annual property tax, and mortgage lender. Roofbird also estimates the owner's equity — how much of the home they actually own — because equity is what decides whether someone CAN say yes. When the deed record can't support an estimate it says so instead of guessing. Only the phone and email sit behind a one-click unlock, and every number is DNC-scrubbed and labeled. You can read more on how the contact details and DNC screening work.

Step 5: Prioritization + outreach within 7 days

Days 4-7 post-event:

Prioritization sequence:

1. Active damage signals + roof age 15+ years: highest priority — visit Day 4-5
2. Active damage signals + roof age under 15: high priority — visit Day 5-6
3. Secondary signals + roof age 15+ years: moderate priority — visit Day 6-7
4. Secondary 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.)

What one rep with an organized day of canvassing typically produces in the Day 4-7 window is a stack of conversations, a smaller stack of booked inspections, and a handful of signed jobs inside three weeks. Treat the ratio as a planning assumption you calibrate on your own doors, not a promise. Multiple reps and multiple days scale 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):

1. Get NOAA alert notification (free, set up once)
2. Within 24 hrs: confirm storm path, define survey grid
3. Within 72 hrs: run the satellite scan
4. Days 3-7: door-knock the top 50-100 candidates
5. Days 7-14: complete inspections, help homeowners file
6. Days 14-21: adjuster visits, contract signing
7. Days 21-60: secondary canvas (homes that didn't engage initially)
8. Days 60-90: post-mortem, adjust next event playbook

The shops doing this end-to-end on every storm book far more storm-event work than reactive shops. The gap is structural, not effort — it comes from having the list before anyone else has drawn a polygon.

Roofbird automates Steps 3-4 — the satellite read plus prioritization for any defined service area within 72 hours of a NOAA-logged event. It also tells you which blocks to scan first, before you draw anything. Scanning new ground and ranking every roof in it is free at any size; reading a roof properly, both photographs and the property record together, is 1 credit per 8 roofs. The free trial is 10 credits, no credit card, no expiry. 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)
• Run a baseline scan on your service area so you know what normal looks like
• 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 the scan 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:

1. Set up NOAA email alerts for your service-area zip codes (free, 5 min)
2. Run a baseline scan on your service area so you have a before picture
3. Print 100 storm-event door hangers with the right opener-language
4. Write your team's storm-event playbook (Steps 1-5 documented)
5. 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.

FAQ

Q: Can I just buy storm-damage leads instead of building this workflow?

A: You can, and it's worth understanding what you're buying. Pay-per-lead marketplaces like Angi, HomeAdvisor and Thumbtack sell the same shared lead to several contractors at once, and they don't know your territory — they sell you whoever filled in a form. Roofbird is the opposite: it reads every roof in your service area from satellite and street-level imagery, ranks each one against its neighbors, and hands you the ones worth knocking. Leads are exclusive because you sourced them. Searching roofs that have already been read is free, instant and unlimited. Reading a roof properly — both photographs and the property record in one go — is 1 credit per 8 roofs, and the owner's name, phone and email is 7/8 of a credit a roof, so a read plus the owner comes to about 1 credit a house. There is no quota and no per-lead fee.

Q: How does Roofbird decide which roofs in a storm area to put at the top?

A: Two scores. NEED is how badly the roof needs replacing, based on condition and roof age read off the shingles. NOW is whether anything is forcing a decision on that specific house: visible active damage, hail damage on that specific roof, a recent purchase, patching already attempted, or neighbors who have re-roofed. Neighborhood hail deliberately does not raise NOW, because every home in the scan shares it and it can't separate one door from the next. Where a hail event is on record, Roofbird also shows roughly how long the owner has left to file a claim based on the typical state notice deadline — treat that as an estimate and verify with the carrier, not as legal advice. If you want to see what the output actually looks like on a real area, there's a live scored area you can look at without signing up.

— Jake