How to Verify Hail Date for an Insurance Claim Using NOAA Data

A homeowner calls and says hail damaged their roof on May 12. You file the claim. The adjuster pulls the records and pushes back: the closest verified hail event was actually May 13, and the homeowner's date doesn't appear in the NOAA database at all. The claim now has a credibility problem before anyone has climbed a ladder.

This is the most common preventable rejection in roofing claims. The date the homeowner remembers is rarely the date NOAA recorded — sometimes it is off by a day, sometimes the storm cell never produced damage-capable hail at their exact address. Getting this right before the claim hits the adjuster's desk is the single highest-leverage thing a contractor can do.

This guide walks through the exact verification workflow: which NOAA publishers carry the records, what to capture, what adjusters actually want to see, and the mistakes that cost contractors paid jobs.

Why the date matters so much

For a hail insurance claim, the date of loss (DOL) is the load-bearing fact. Three things depend on it:

Coverage validity — the policy in force on the DOL is the policy that pays. If the homeowner switched carriers or upgraded coverage, the wrong date can route the claim to the wrong company.

Statute of limitations — most states give homeowners one to two years from the DOL to file. Cite a date that is too old and the claim is barred outright.

Causation — the adjuster's job is to confirm that an actual hail event of damage-capable size hit this property on or near the claimed date. Without that, the loss is attributed to wear and the claim becomes a denial.

When the contractor brings a clean DOL backed by a NOAA record at intake, the rest of the inspection is just verifying physical damage matches what the storm could have caused. When the DOL is wrong or unsupported, every subsequent step is uphill.

The four NOAA hail data sources contractors should know

NOAA publishes hail observations through four independent systems. Each has a different purpose, a different latency, and a different weight with insurance adjusters.

NEXRAD Severe Weather Data Inventory (SWDI)

Radar-derived hail size estimates from the National Weather Service Doppler radar network. SWDI covers every detected hail event of 0.75 inches or larger from 2015 to present and produces a record per radar scan, so a single storm cell can generate dozens of records. Useful for confirming a storm passed over the property. Estimated hail size carries about a ±0.25 inch margin compared to ground measurements.

MRMS MESH (Maximum Expected Size of Hail)

A near-real-time radar product that ingests within roughly two hours of the storm. MRMS is the only source where a storm that hit yesterday shows up today. Important for active claims after a fresh event, but only retains data for a rolling window of about 16 days at the source. Historical retrieval requires the persistent NEXRAD record.

NOAA Storm Events Database

The National Weather Service's official ground-verified storm catalog, maintained by the National Centers for Environmental Information (NCEI). This is the gold standard. Each record is a physically observed hailstone — measured, reported by a trained spotter, NWS office, or law enforcement, and assigned a unique event ID. Storm Events lags the actual event by 60 to 90 days because the records go through a QC pass before publication, but for adjusters this is the source that carries the most weight.

CoCoRaHS (Community Collaborative Rain, Hail and Snow Network)

Volunteer observer measurements with photographic backup. Coverage is patchy in low-population areas but excellent in suburban Front Range, North Texas, and Midwest metros. Useful as a corroborating second source when SED has not yet published.

For a contractor's verification workflow, the playbook is: lead with a Storm Events ground-verified report, back it up with the matching NEXRAD radar timestamp, and use MRMS only when the storm is fresher than SED can publish.

The verification workflow, step by step

This is the procedure used end-to-end in the HailScore date-of-loss verifier and worth knowing manually even if you use a tool.

Step 1: Capture the homeowner's claimed date and exact address

Get the street address, not the ZIP. A single ZIP can span 50 or more square miles and one half might have been hit while the other half saw nothing. Ask the homeowner what they were doing when the storm hit, what time it was, and what they remember about hail size (golf ball, marble, quarter). Time of day matters because radar resolves storm cells to the minute and the homeowner's recollection helps narrow the match.

Step 2: Geocode the address to lat/lon

Every NOAA hail record is point-located. You cannot query the database by street address — it has to be a coordinate. Use any geocoder (Mapbox, Google, the US Census batch geocoder).

Step 3: Pull every hail event within a 5-mile radius and ±15 days of the claimed date

The five-mile radius captures the realistic spread of a storm cell. The ±15-day window catches off-by-a-day homeowner recollections, time-zone confusion, and lag between when the storm passed and when the homeowner noticed damage.

Query each of the four publishers separately. You will typically find Storm Events has the cleanest result (one or two records), NEXRAD has the largest (potentially hundreds of radar scans of the same cell), and MRMS has the freshest if the event is recent.

Step 4: Identify the closest verified event to the claimed date

Sort the results by date and then by distance from the property. The verified date of loss is usually the SED record closest in time to the homeowner's claimed date, with the smallest distance-to-property of the matches. If SED has not published yet (event is less than 90 days old), use the NEXRAD record with the highest estimated hail size in the time window as the primary citation.

Step 5: Capture the NOAA event ID

This is the single most important data point in the entire verification. Every Storm Events record has a numeric event_id field. NEXRAD radar records have a cell_id plus wsr_id (the radar station that detected the event) plus a timestamp. Write all of those down on the claim. An adjuster who wants to verify your work can query the same NOAA databases with the IDs and pull up the exact record you cited.

Step 6: Save the storm map and PDF

A visual map showing the storm path with hail-size dots over an overhead of the property is high-leverage evidence. Save it as part of the claim file. If you use a tool that generates this automatically (the HailScore $9.95 storm-history report does), save the PDF; if not, screenshot the NCEI Storm Events Database map view.

What adjusters actually want to see

From conversations with adjusters and reviewing what gets paid vs. what gets denied, four things consistently show up in the strongest contractor-side evidence packages:

A NOAA event ID they can independently verify — not a screenshot of a generic weather app

The hail size at the closest verified point to the property, with the source noted (SED ground report vs. NEXRAD radar estimate)

The radar timestamp at peak hail for the storm cell, ideally with the WSR-88D station ID

A spatial visualization showing the storm's path over the property

The framing matters. Insurance adjusters and courts that hear hail-related disputes have grown increasingly skeptical of proprietary hail-damage scores from third-party vendors. Under the Daubert standard for expert testimony, analyses built on opaque proprietary models can be challenged on the grounds that the underlying methodology is not independently reproducible. Testimony grounded in publicly available raw NOAA records — radar event IDs, Storm Events database citations, NWS station timestamps — does not have that vulnerability. Citing NOAA event IDs directly puts the contractor's claim on the strongest evidentiary footing available.

Common mistakes that cost contractors paid jobs

Watching contractors lose otherwise-valid claims, the same handful of errors come up repeatedly.

Citing a forecasted date instead of an observed event. A weather app predicting hail at 4:00 PM on May 12 is not evidence that hail occurred. The verification has to come from a record of actual observation (radar or ground), not a forecast.

Citing distance to storm centroid instead of distance to property. Hail does not fall only at the center of a storm cell. A property six miles from the centroid might have been directly in the swath. Always measure point-to-point.

Conflating wind and hail event types. Storm Events records hail, thunderstorm wind, high wind, and tornado as separate event types. A claim for hail damage citing a "Thunderstorm Wind" event in NOAA is going to confuse the adjuster at best and look careless at worst.

Using TV news date vs. NOAA date. Local news often reports a storm by the day it hit the metro area; NOAA records the timestamp in UTC. A storm that hit Denver at 11:30 PM local time on May 12 is in the NOAA database as May 13. Off-by-one day from this is extremely common and entirely preventable.

Using ZIP-code-level tools. A ZIP-only lookup tells you what happened somewhere in 50 square miles, not what happened at the property. For insurance claims this is not specific enough.

Free tools vs. paid verification

The free path: go to the NCEI Storm Events Database, query by state and date range, manually map the results against the property, and capture the event IDs by hand. Works. Takes 30 to 60 minutes per address if you know what you are doing and have done it before.

The HailScore path: the free address check on the HailScore homepage returns the storm timeline, the closest events with NOAA citations, and an interactive map in about five seconds. The $9.95 storm-history report generates a multi-page PDF with the NOAA event IDs, NEXRAD station IDs, and storm map ready to attach to a claim. For shops doing volume, the Team and Firm subscription tiers include the dedicated date-of-loss verifier that runs the four-publisher query in parallel and surfaces the result in roughly two seconds.

The hands-on workflow above is the same in both cases — the only difference is whether you are doing the queries yourself or having the tool surface them.

When to skip the verification and just file

If the storm is recent, well-publicized, and obviously catastrophic (the May 2024 Highlands Ranch hailstorm, the Plano 2017 storm, anything that made the national news), the carrier is often already paying out without contractor-side date verification. In those cases, the value of a NOAA-cited workflow is on the supplemental and the holdout claims — the properties on the edge of the swath where the adjuster might otherwise deny.

For everything else, the 60 seconds spent verifying the DOL before filing pays for itself the first time it converts a denied claim into a paid one.

Frequently asked questions

Does an adjuster have to accept NOAA records as evidence?

In practice, NOAA Storm Events records are the most widely accepted hail evidence in the US insurance market. NWS-verified ground reports are admissible in state court and routinely cited in arbitration. NEXRAD-derived hail size is treated as supporting evidence — credible, but understood to have a ±0.25 inch margin.

What if the homeowner cannot remember the date?

Run a date-blind query: pull every verified hail event within five miles of the property in the past one to two years. The visible damage on the roof usually narrows it. A roof with two clearly distinct sets of dents might have damage from two storms — capture both.

Can I use HailScore data for insurance claims in any state?

Yes. NOAA data covers all 50 states and is the same regardless of jurisdiction. Specific carriers may have preferred third-party data vendors, but the underlying NOAA records are universally accepted.

What about claims older than five years?

NOAA Storm Events goes back to 1950. Earlier records have less geographic precision (some pre-1996 records are county-level rather than point-located), but for any event 1996 or newer the date and location are reliable. The HailScore lookup tool covers 2015 to present; for older records, query the NCEI Storm Events Database directly.

Does HailScore tell me how to win a claim?

No tool can predict claim outcomes. The HailScore workflow is purely about establishing that a hail event of damage-capable size occurred at the property on the claimed date, with NOAA-grade citations the carrier can verify. What the carrier does with that evidence is up to them.

---

The contractors who consistently get paid on hail claims are the ones who treat date verification as the first technical task of the inspection, not an afterthought. The data is free, the workflow is straightforward, and the upside — fewer denied claims, faster supplements, better adjuster relationships — compounds for the life of the business.

If you want to skip the manual queries, the HailScore date-of-loss verifier runs the same four-publisher workflow in two seconds, and the $9.95 storm-history PDF is built to drop straight into a claim file.