Reading Hail Timing and Size Reports for Next-Day Routes

Start with timing, not hail size

A 4.5-inch report in Sharon, OK means little if it landed after sunset and never reached your crew window. A 2.0-inch report at 4:10 p.m. can be the first stop for a next-day route. The first decision is always when the hail fell, then where it tracked, then how large it was.

Contractors lose time when they sort reports by size alone. A large stone at the edge of the market can sit behind a smaller but earlier swath that already has confirmed roofing demand. Next-day routing works better when you place the storms on a timeline and build the day around the earliest verified impact points.

NOAA local storm reports and warning-area timestamps give you the first cut. Pair those with radar-derived hail timing and you get a cleaner route order. The goal is not to chase every report. The goal is to put boots on the most likely work first.

Read the report clock before you read the hail size

Each report has a time stamp. Treat that as the anchor. A storm that produced 4.0-inch hail in Greenville, MO at the end of the afternoon belongs ahead of a later cell with 5.0-inch reports if your crews can only cover one side of the market before dark. The order changes once daylight, drive time, and crew count are added.

Use a simple sequence:

1. Sort reports by timestamp.
2. Group nearby reports into the same hail swath.
3. Note where the first report fell and where the last verified report ended.
4. Build routes from the leading edge of the swath inward.

That keeps a route from jumping back and forth across counties or metro edges. It also avoids sending an inspection team deep into a later report cluster before the earlier storm path has been covered.

When reports line up in time and space, the first addresses in the warning area usually deserve the first canvass passes. Later report zones can follow after the high-probability roof stock has been checked.

Treat hail size as a sorting tool, not the only filter

Hail size still matters. A 5.0-inch report in Dickens, TX belongs in the top tier of any next-day plan. A 4.0-inch report in Switz City, IN does too. But the size number should not be the only trigger.

Use the size report to sort storm priority into three working buckets:

• Large hail, roughly 2.0 inches and up
• Severe hail, 1.0 to 1.75 inches
• Marginal hail, below 1.0 inch but worth checking if timing, density, or path placement is strong

The biggest stones often mean fewer reports but stronger roof signal. Smaller stones can still produce a dense claim cluster if they fell over a built-up corridor with older roofs, tree cover, or a high concentration of exterior trades work.

Do not overbuild a route around one large report if the storm path was narrow and short-lived. Do not underbuild one because the largest report was only 1.75 inches if the timing shows a long, well-defined track across occupied structures.

Use the warning area first, then narrow to the hail swath

The NOAA warning area is the broad polygon. It tells you where the storm could have produced hail. It does not tell you where the hail definitely hit.

For next-day routing, start with the warning area to understand the market footprint. Then narrow to the hail swath from radar-derived detection and verified reports. That sequence keeps you from spending the morning on addresses that sat inside the polygon but outside the strongest hail path.

In practice, this matters most when a warning area covers multiple towns. A broad polygon can include several counties, but only one corridor may have the hail that matters for route setting. If the report timing shows the storm entered one side of the market at 3:40 p.m. and exited by 4:15 p.m., build around that window first.

Build routes from the first verified impact point

The first verified hail point usually gives the cleanest route spine. It marks where the storm began producing useful ground-truth. From there, you can map outward along the storm path and sequence the day by drive time.

A practical route stack looks like this:

• First stop: earliest verified hail report
• Second stop: adjacent addresses in the same swath
• Third stop: the next report cluster downtrack
• Fourth stop: isolated outliers only after the main line is covered

This approach works well when storms produce multiple large reports in different towns. A 5.0-inch report in Dickens, TX and a separate 4.0-inch report in Greenville, MO are not route neighbors. They are separate market decisions. Each needs its own local timing line, road plan, and crew assignment.

Do not route from one headline hail size to the next without checking travel separation. A same-day report in another state may be more serious on paper and still useless for a next-day plan in your current market.

Watch for late-day hail and overnight cleanup

Late-afternoon and evening storms change the route math. A report that lands near dark can still be high priority the next morning, but only if the hail path is clear enough to justify first-pass canvass.

If hail falls late, ask three questions before setting the route:

• Did the report come from the leading edge or the tail end of the storm?
• Is the swath continuous, or are the large stones isolated?
• Will daylight allow a full first pass before the next weather cycle?

A strong late-day report can push a crew to the front of the line even if it was not the largest hail of the day. That is because fresh roofing demand often sits where the storm ended most recently. Crews can cover those roofs before homeowners leave for work and before post-storm traffic builds.

Separate true path clusters from scattered hail chatter

Not every large hail report deserves route priority. Some are isolated. Some are duplicate reports. Some sit far outside the main damage pattern. NOAA reports help, but they still need storm-path context.

Look for these signs of a usable route cluster:

• Reports within a narrow time window
• Reports that step forward along the same corridor
• Similar hail sizes across nearby locations
• Radar-derived detections that match the timing line

If a 4.5-inch report appears in Sharon, OK but the surrounding reports are sparse and separated by wide gaps, treat it as a focus point, not a full-market route by itself. The same is true for a 4.0-inch report in Switz City, IN if the storm path was broken into smaller cells.

The most efficient routes usually come from clusters, not lone headline stones.

Turn timing into crew order

Once the reports are sorted, route order becomes a staffing question. Put the first crew on the earliest verified path. Put the second crew on the densest report cluster. Hold a third crew for spillover only if the storm line supports it.

A simple field order works well:

• Morning canvass on the earliest hail swath
• Midday inspections on adjacent neighborhoods with matched timing
• Afternoon follow-up on outlier reports with larger stones

This reduces wasted drive time and prevents your strongest inspectors from getting pulled into low-value corners first. It also gives production staff a cleaner handoff because the route reflects storm timing, not just map size.

What to pull from NOAA before the trucks roll

Before next-day routes are locked, pull three items from NOAA-linked data and verified storm records:

• Report time
• Report size
• Report location relative to the warning area and hail swath

That is enough to build an initial route spine. Add radar timing if available. Add street-level adjustments after the first field notes come back.

For contractors working multiple markets in the same day, this is the cleanest way to avoid route drift. Dickens, Sharon, Greenville, and Switz City are separate decisions. Each storm needs its own time line, its own size filter, and its own travel check.

The route rule that holds up best

Next-day contractor routes work best when the earliest verified hail comes first and the largest hail comes second. The storm clock sets the order. The hail size sets the priority. The warning area sets the outer boundary.

Use all three together, and the route usually tightens fast.