How Storm Damage AI Detection Works (And What It Can Prove)

After a major hail event, roofers face a 14-day adjuster window to identify damaged homes, contact homeowners, and get named as preferred contractor. The shops that win consistently inside that window use AI to compress the "identify damaged homes" step from weeks of canvassing to hours of triage.

This post is about how that AI actually works. The two-pass detection methodology, the signals it picks up, the false-positive rates, and what the AI evidence can (and can't) prove for insurance claims.

Two-pass detection: the core methodology

Modern AI storm damage detection is fundamentally a CHANGE-DETECTION problem, not a single-image-analysis problem. The strongest signal isn't "this roof looks damaged in one image" — it's "this roof looks different now than it did 30 days ago."

The two-pass methodology:

Pass 1: Pre-storm baseline. AI maintains a recent baseline image + scoring of every property in the service area. Updated quarterly or after major imagery refreshes.

Pass 2: Post-storm comparison. After a storm event, AI pulls fresh imagery (typically 48-72 hours post-event once satellite refreshes) and compares to the pre-storm baseline. Differences = candidate damage.

The change-detection approach is meaningfully more accurate than single-image analysis for two reasons:

1. Baseline-anchored. A roof that looked rough before the storm but unchanged after isn't storm-damaged — just an old roof. Single-image analysis can't distinguish these; two-pass can.
2. Subtle changes detected. Granule displacement that's invisible without a baseline becomes obvious when compared frame-to-frame.

The downside: requires existing baseline coverage of the service area. New users don't get full two-pass benefit until the baseline is built (typically 1-2 weeks of running).

Signals AI detects post-storm

Layered from most-reliable to least-reliable:

Tier 1 signals (95%+ accuracy)

• Visible tarp installation (bright blue, unmistakable from satellite)
• Missing shingle sections (high contrast vs. intact roof)
• Visible work in progress (dumpsters, debris piles, scaffolding)
• Tree debris on roof (storm-related debris is distinctively-shaped)

These signals are visible from above with high confidence. Almost zero false positives.

Tier 2 signals (75-90% accuracy)

• Granule displacement (visible color/texture variation post-storm vs pre-storm)
• Circular impact bruise patterns (visible on certain shingle types)
• Ridge wear acceleration (compared to baseline)
• Color pattern change (storm-driven color shift)

These signals are visible but harder. AI confidence varies by imagery quality and material type.

Tier 3 signals (50-75% accuracy)

• Soft impact damage (visible only in oblique angles)
• Hail-impact "spatter" patterns on accessories (gutters, vents)
• Underlayment exposure (only if severe enough to be visible from above)

These signals are AI's "best guess" — should always be verified on ground before action.

Confidence scoring + false-positive rates

A well-built AI storm detector outputs confidence per property, not just a binary "damaged / not damaged."

Sample output:

Property: 2011 Rayburn Ave, Mesquite TX 75150

Storm damage signals detected:
  - Blue tarp visible (Tier 1, 99% confidence)
  - Granule displacement vs baseline (Tier 2, 78% confidence)  
  - No tree debris (negative signal)

Overall damage likelihood: HIGH (96% confidence)
Recommended action: Immediate door-knock; document for insurance

False positive rates by tier (in our validation):

• Tier 1 only: ~2% false positive (very reliable)
• Tier 1 + Tier 2: ~5% false positive
• Tier 2 only (no Tier 1): ~15-20% false positive (always verify on ground)
• Tier 3 only: ~30-40% false positive (treat as low-confidence flag)

The right rule: when an AI flags a property with Tier 1 evidence, trust it for door-knocking. When it flags with Tier 2 or 3 only, treat as a candidate that needs verification.

What AI evidence proves (and doesn't) for insurance

This is where it matters most. Insurance carriers treat satellite-derived damage evidence inconsistently — some accept it, some don't, most fall in the middle.

What AI evidence supports for an insurance claim:

• Pre-storm baseline (the roof looked X way before)
• Post-storm change (visible damage that wasn't there before)
• Storm-event location proof (specific property was in the swath, not just the county)
• Tarp/repair signals (homeowner is taking immediate action)

What AI evidence doesn't replace:

• Touch inspection (required for most carrier claim approvals)
• Adjuster verification (the carrier's representative makes the final call)
• Repair-vs-replace determination (requires hands-on assessment of underlying damage)

The strongest claim documentation packages combine:

• AI pre/post imagery comparison
• Ground-truth photos from the roofer's inspection
• NOAA storm event verification (location + date + magnitude)
• Permit history showing no recent replacement
• Material samples for very-old-roof claims

When all five are stacked, claim approval rates run 70-85% on legitimately-damaged properties. Without AI evidence, approval rates on the same properties typically run 55-70% — the AI evidence pushes 15-20% more claims through approval.

The screen-and-verify workflow for roofers

The practical integration:

Hour 0-24: NOAA logs storm event.

Hour 24-72: Wait for satellite imagery refresh (this is the bottleneck — depends on imagery provider).

Day 3-4: Run AI two-pass detection on the swath area. AI flags ~10-20% of properties with visible damage signatures.

Day 4-5: Triage AI output:

• Drop obvious false positives (commercial flat roofs, multi-unit complexes)
• Sort by combined Tier 1+2 signal strength
• Prioritize properties also showing other prospect signals (roof age 15+, neighborhood replacement cascade, etc.)

Day 5-7: Door-knock the top 30-50 properties. Use the storm-event opener.

Day 7-14: Inspect on-site:

• Verify the AI's Tier 1/2 signals
• Check for Tier 3 + sub-surface damage AI couldn't see
• Document with ground photos

Day 14-21: Adjuster visits. Your documentation package supports the claim.

The shops that move through this 21-day pipeline consistently book 5-10x more storm-event work than reactive shops.

Limitations to keep in mind

1. Imagery freshness is the bottleneck. AI can't see what the satellite hasn't captured yet. Most providers refresh 48-72 hours post-storm in major metros; sometimes longer in suburban+rural.

2. Sub-surface damage is invisible. AI sees only what's on the roof surface. Mat damage under intact tabs, soft decking, hidden leaks — all require ground inspection.

3. Material variance matters. Hail damage signatures look different on architectural asphalt vs 3-tab vs metal vs tile. AI tools tuned for one material may underperform on others.

4. Recent imagery isn't always representative. If the satellite image was captured between the storm and the homeowner's emergency tarp installation, the tarp won't show. Use NOAA event data + imagery timestamps to validate temporal correlation.

5. Confidence is probability, not certainty. Even Tier 1 signals at 99% confidence mean 1% false positives — out of 100 flagged properties, expect 1 to be wrong.

The 12-month direction

Where storm damage AI detection is going:

1. Multi-provider imagery integration. Tools combining Google + Nearmap + drone trigger-on-demand for highest-confidence properties. Already starting.

2. Real-time imagery from emerging providers (Planet Labs, etc.) that refresh daily instead of quarterly. Will compress the 48-72 hour bottleneck to under 12 hours.

3. Insurance carrier integration. Some carriers are building AI evidence into their adjuster workflows. Expect 1-2 major carriers to formally accept AI evidence in the next 12 months.

4. Cross-event change detection. AI maintaining ongoing change-detection across multiple storms — useful for repeated-impact properties where damage compounds.

What to do this week

If you operate in a hail-belt region:

1. Test AI storm detection on a recent historical event in your area
2. Calibrate confidence thresholds to your shop's risk tolerance
3. Build a 21-day post-storm playbook so you're ready when the next event hits
4. Set up NOAA email alerts for instant notification

When the next major storm hits your area, reaction speed determines who captures the work. Shops with pre-built AI workflows + documented playbooks are competing on hours, not days.

Roofbird's DFW sample dashboard shows what post-storm AI detection looks like in practice — the May 9 Mesquite event surfaced multiple properties with tarp signatures + AI-flagged damage. Free trial in your service area.

— Jake