Hail Damage Map: How to Use NOAA + Alternatives for Roofing

Every roofer in the hail belt has a hail map app on their phone. The problem: hail maps are great at telling you a storm happened, and bad at telling you which specific homes need a new roof.

Skip the app-shopping: Roofbird publishes a free interactive US hail map — every NOAA hail report from the last 12 months with size, county, and date, updated daily. No signup.

This post is about what you can actually do with hail data — which maps are worth using, which are oversold, and how to layer imagery on top to convert "storm hit this county" into "knock these 30 specific addresses."

Why hail maps lie

A hail map is a probability distribution, not a damage map. The two diverge in three ways:

1. Reported size vs. impact size. Most hail maps report the largest hailstone observed in an event. But a county that "got 2-inch hail" might have had 2-inch hail at one spotter location and dime-sized hail two miles away. The map shows you the headline; the on-the-ground reality is patchier.

2. Swath gaps. Hail comes down in narrow swaths — typically 1-5 miles wide, sometimes 10+ miles long. A map showing "hail across this county" usually means a single swath crossed it. Most of the county was unaffected.

3. Roof material variance. A 1.5-inch hail event might destroy a 22-year-old asphalt roof and leave a 5-year-old impact-resistant shingle perfectly fine. The map doesn't know about your prospects' roof condition.

These three together mean a hail map alone gets you to a county, not to specific addresses. You need to verify against imagery of the actual roof, or in person, to find the homes that were genuinely hurt.

NOAA Storm Events Database (the free baseline)

URL: ncdc.noaa.gov/stormevents

NOAA is the source of truth for severe weather. Every commercial hail map ultimately pulls from NOAA plus its own spotter network.

For roofers:

1. Go to the query interface
2. Filter by your state + recent date range (last 14 days for storm-chase relevance)
3. Filter event type: "Hail"
4. Export the result as CSV

You'll get a row per event with: date, county, town, lat/lon, hail size, event narrative.

Strengths:

• Free, official, comprehensive
• Includes both spotted hail (citizen reports) and radar-derived hail (algorithmic estimates from Doppler)
• Coverage everywhere in the U.S.

Weaknesses:

• 24-72 hour reporting lag for some events
• Spotter network is sparse in rural areas — events may be under-reported
• Interface is government-grade ugly (the data is good, the UX is not)

Use case: the baseline data layer for any hail-watch workflow. Even paid tools should be cross-checked against NOAA.

HailTrace + Interactive Hail Maps (commercial alternatives)

The two most-used commercial hail maps for roofers.

HailTrace

URL: hailtrace.com

Paid tool. Pulls NOAA data plus its own radar-derived hail estimates and spotter reports, and visualizes hail swaths overlaid on satellite imagery.

Pros:

• Fast reporting lag, much faster than NOAA's web interface
• Property-level overlay (you can click a hail swath and see addresses inside it)
• API for integrations

Cons:

• The bill is a recurring subscription, which is a fixed cost every month whether or not a storm hits your territory
• Property-level "hail did hit this house" is still probabilistic, not confirmed damage

HailTrace does not publish a public rate card; you'll get a number on a call, and it scales with what you want to see. Read what you're actually buying with a hail recon subscription before you commit.

Interactive Hail Maps (IHM)

URL: interactivehailmaps.com

Similar concept — NOAA plus spotter overlays — with a simpler interface and a lower entry point.

Pros:

• Cheaper than HailTrace, and priced in tiers you can see before you call
• Decent visualization
• Mobile-friendly

Cons:

• Less granular than HailTrace
• Smaller spotter network

Recommendation: if you're doing serious storm-chase work, HailTrace is the deeper tool. If you're a residential shop that occasionally chases post-storm, IHM is the better starting point. Either way, understand that both stop at the swath. Neither one tells you which roof on the block is shot.

Cross-referencing with insurance claim density

A signal that's better than hail data alone: insurance claim density.

When a hail event causes real damage, insurance claims spike in the affected zips within 30-60 days. Some state insurance commissioners publish aggregate claim data by zip; some don't. Where it's public, it's the closest thing to ground truth.

For Texas specifically, the Texas Department of Insurance publishes some aggregate hail claim data. Not real-time, but useful for confirming which areas your prospects are actually filing claims.

The cross-check: if NOAA says a county got hit but claim density 60 days later is normal, the storm probably wasn't as damaging as the map suggested. Skip that area for storm-chase prospecting.

Satellite verification: the layer most roofers skip

Here's the unlock: reading the roof itself from imagery can tell you, at the property level, which roofs in a hail-impacted zip actually show post-storm damage signatures.

What that read picks up after a storm:

• Circular bruise patterns (visible from above on impact-resistant shingles)
• Granule displacement (lighter patches where hail knocked granules off)
• Missing tabs (visible from above on severe impacts)
• Tarp installation (homeowners doing emergency repair = high-intent prospect)

Roofbird reads the top-down overhead tile and a ground-level Street View of the façade together into one combined assessment. The ground-level read catches side-visible wear a top-down tile can't: granule loss, algae streaking, curling shingles, patched sections, rusted flashing. It also compares the roof against its immediate neighbours from a wider centred view — if the houses either side have visibly been re-roofed and this one hasn't, that's flagged, because a street where the neighbours have already gone new is the strongest social proof in the trade. How Roofbird scores a roof from imagery walks through the whole read.

The workflow:

1. NOAA or a commercial map identifies the hail swath
2. A read covers every roof inside the swath
3. The worn and damaged roofs get flagged, and the ones already replaced get moved down and said out loud
4. Those become your priority knock list

For DFW, the May 9 hail event in Mesquite is a good example. NOAA logged the event in a 4-mile swath, and a property-level read picked up the homes with visible damage signatures. The headline lead in our DFW sample dashboard — 2011 Rayburn Ave with a blue tarp on the roof — was one of them.

One thing worth being honest about: not every roof can be judged. Behind heavy tree canopy or set too far back from the road, the imagery simply doesn't settle it, and Roofbird labels those as exactly that rather than mixing them in with the confident ones. Where the street camera could see the roofs, what a contractor found on the ground matched four of four; where it could not, zero of five. A roof whose own description says it was recently replaced never reaches the top of a list. There's more on the limits in what AI can and can't see in a hail damage assessment from satellite.

Roofbird now tells you which blocks in a city are worth your morning before you draw anything — housing era, share of roofs reading worn, real home count from building footprints, hail in the last 12 months, and whether the block is walkable or scattered acreage. Leads carry two scores: NEED (how bad the roof is) and NOW (whether anything is forcing a decision on that specific house). Neighbourhood hail deliberately does not raise NOW, because every home in the scan shares it — it belongs in the pitch, not the ranking. It compares the roof against its immediate neighbours — the "everyone on this street went new except you" close. The full property record and an owner-equity estimate show free; only the DNC-scrubbed phone and email need a click. Where hail is on record, it shows roughly how long the owner has left to file a claim (estimate, verify with the carrier).

Roofbird cross-references hail events with what the imagery actually shows, so you get property-level leads instead of a county-wide swath. The free trial is 10 credits, no credit card, no expiry. Look at a live scored area first to see the output.

Building a 90-day hail-watch routine

The shops that win storm-chase work aren't the ones with the fastest reaction time alone. They're the ones with a sustained 90-day routine that doesn't get distracted between events.

Weekly (every Monday):

• NOAA pull: any hail events in your service area in the last 7 days?
• Commercial map check (if subscribed): any swaths intersecting your zips?
• Imagery read: any new tarp signatures, missing tabs, hail bruise patterns?

Within 48 hours of a significant event:

• Map the swath: identify the exact zip codes affected
• Read the roofs inside the swath
• Identify the top properties with visible damage signatures
• Prioritize by combined signal: damage + roof age + owner equity

Within 7 days:

• Door-knock the top of the list (the insurance adjuster window is closing)
• Leave door hangers at the next hundred

Within 30 days:

• Cross-reference your contact list with insurance claim density data
• Identify any properties where the homeowner has filed but not yet selected a roofer

Within 60 days:

• Re-canvas the swath — homes that didn't engage immediately often come around once neighbors start replacing
• Re-pull permit records to identify recent replacements (competitive intel)

Within 90 days:

• Post-mortem: which signals predicted closes best? Which zips were dead?
• Adjust the next event's playbook accordingly

The shops doing this systematically book more storm-chase work per event than reactive shops, because they're working a list instead of a rumor.

When to skip hail-chase entirely

Storm-chase work isn't right for every shop. Skip it if:

• You're in a non-hail-belt market (Northwest, much of the Northeast)
• You don't have a sales team that can respond within 48 hours of an event
• Your shop's brand positioning is "trusted local craftsmanship" — storm chasers have a reputation problem you don't want to inherit
• Your jobs average over $30k (luxury work) — storm-chase volume jobs dilute margins

Most residential roofers in TX/OK/CO/KS/FL/GA do benefit from storm-chase work, but it needs to be one of 2-3 channels, not the only one. If you're comparing the software side of this, the honest buyer's guide to hail and storm roofing lead software covers the whole field.

What to do this week

1. Bookmark ncdc.noaa.gov/stormevents and set a Monday calendar reminder
2. Subscribe to one commercial hail map (HailTrace or IHM) — your call on price
3. Add an imagery read to your stack so you're not relying on hail-zone-level data alone
4. Build the 90-day routine into your weekly schedule

The hail belt isn't going anywhere. The shops that win consistently are the ones with a systematic hail-watch process, not the ones who scramble after every event.

— Jake

---

Q: How quickly does Roofbird update after a hail event?

A: It depends on new imagery becoming available. The hail map data itself (NOAA-sourced) updates daily, and searching roofs that have already been read is free, instant and unlimited — so the moment a swath lands in your area you can ask which roofs inside it are worn, which already show a tarp, and which have already been replaced. Reading the actual photographs of roofs nobody has looked at yet costs 1 credit per 8 roofs and buys both cameras and the full property record together. For the fastest turnaround, pair that with a real-time hail alert tool like HailTrace.

Q: Can Roofbird tell me which homes in a hail swath have already filed insurance claims?

A: No. Roofbird reads imagery and public property records. Insurance claim data is not public at the address level in most states. The claim-density cross-check described above uses aggregated zip-level data from state insurance departments, not individual addresses. What Roofbird does show, where a hail event is on record, is roughly how long the homeowner has left to file under the typical notice deadline in that state — an estimate to verify with the carrier, not a legal deadline.

Q: Do I have to draw the area before I get anything useful?

A: No. Search the area you work — a town, a suburb, a ZIP, or a street — and Roofbird reads the neighbourhoods in view and ranks them, 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 is 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 still drag the corners, or draw your own polygon from scratch. Scanning new ground is free at any size. When nothing in view clears the bar it says so plainly rather than offering three neighbourhoods you should skip.

Q: What does a credit actually buy?

A: One meter: credits. Looking is free, acting costs. Asking, searching, sorting and saving lists are free and unlimited. Reading a roof properly — both photographs, from above and from the road, and the property record in one go — is 1 credit per 8 roofs. The owner's name, phone and email is 1 credit per 2 roofs. Opening a house completely is 1 credit. A failed lookup is refunded; a definitive "nobody listed" answer is charged once and cached so the same address is never charged again. The free trial is 10 credits, no credit card, no expiry, and after it there are no subscriptions — one-off packs only, and bought credits never expire. What a credit buys lays it out.