How To Prioritize Neighborhoods After A Hail Swath

A hail swath should kick off a triage workflow, not a sales claim that every roof in the path is wrecked. The fast answer: pull the radar-estimated swath, overlay it on your service area, separate weather context from anything property-specific, strip out unsafe or off-limits routes, match what is left to the crew you actually have, and then rank neighborhoods by a mix of estimated hail energy, roof age, route density, and prior-customer presence. Work the highest-confidence, oldest-roof, easiest-to-service blocks first. Skip the brand-new subdivisions even if they sit dead center in the swath. Hand the field team a per-home reason for being there, not a blanket promise.

The reason this matters is simple: a swath is a weather signal, and weather signals lie at the property level. A radar product like MESH (Maximum Estimated Size of Hail) can tell you, fairly well, where a storm's hail core tracked and roughly how big the stones got aloft. It cannot tell you whether the 1994 three-tab roof on the corner lot took a beating while the 2023 architectural roof two doors down shrugged it off. Same swath, same block, two completely different work orders. The whole game of post-hail prioritization is closing that gap between "the storm passed here" and "this specific roof is due," using the few things you can actually know before anyone climbs a ladder: estimated hail size, roof age, exposure, and your own history with the address.

Get the order right and a single storm pays for the month with clean, documented, welcome inspections. Get it wrong and you burn three days knocking new roofs in a no-soliciting suburb, train your reps to overpromise, and hand a plaintiff's attorney a roomful of evidence. The difference between those two outcomes is almost never how hard the crew works. It is the quality of the prioritization done before the trucks roll.

Below is the full system: how to read the swath sources honestly, how to score neighborhoods, how roof age changes everything, how to stay safe and legal, and how to hand a clean route to the field. It is written for the manager building the morning board and the rep working the door, and it assumes you want repeat customers and referrals, not a one-storm smash-and-grab.

What A Hail Swath Actually Tells You (And What It Doesn't)

Start with vocabulary, because sloppy language is where bad routes are born. A "hail swath" in the modern sense is usually a time-accumulated map of radar-estimated hail size. The most common engine behind it is NOAA's Multi-Radar/Multi-Sensor system (MRMS), which blends data from many radars, surface observations, lightning, satellite, and short-term forecasts into gridded products. One of those products is MESH, the Maximum Estimated Size of Hail. As NSSL's hail detection page explains, MESH estimates hail size from the radar reflectivity a storm produces above the freezing level, and forecasters accumulate it over a window — one hour, one day — to produce the colored swath you recognize.

That is a powerful triage layer. It is also an estimate built from what the radar saw in the cloud, not a record of what hit the shingle. Three honest limits to keep in front of the team:

• MESH measures aloft, not at the ground. Stones melt, get blown sideways, or fall in pockets. A swath colored for 1.75-inch hail does not mean every yard under it caught 1.75-inch stones. Wind, melting layer height, and storm motion all shift what actually lands.
• Radar resolution is coarse relative to a roof. A radar pixel covers a chunk of a neighborhood, not a parcel. The swath is a heat map, not a property report.
• Bigger isn't the only thing that matters. A landmark 2025 study from the Insurance Institute for Business and Home Safety found that repeated exposure to sub-severe hail — stones between roughly 0.7 and 1 inch — can accelerate asphalt-shingle aging and leave a roof far more vulnerable to the next storm. In their testing, shingles that had taken natural weathering plus sub-severe impacts were roughly ten times more susceptible to damage from a later severe event. Coverage of the study ran in the Insurance Journal. The takeaway for routing: a neighborhood that has been pelted by small hail over several seasons can be "due" even when today's swath looks unimpressive, and a brand-new roof under a big swath may be fine.

For context on the official thresholds, the National Weather Service treats a storm as severe when it produces hail at least one inch in diameter (quarter-size) or wind gusts of 58 mph or greater; NWS severe weather definitions lay that out. That one-inch line is a warning threshold, not a roof-damage threshold. Roofs can be aged by smaller hail and can survive larger hail depending on shingle, age, and angle. Never tell a homeowner the warning size proves their roof is damaged.

So what does the swath genuinely earn you? It narrows the search. It tells you which side of town to focus on, where the storm's energy concentrated, and which blocks deserve a closer look. It is the first filter, not the verdict.

The Source Ladder: Rank Your Evidence Before You Rank Neighborhoods

Before a single neighborhood moves toward a route, label where its evidence came from. Storm-response teams constantly blend a radar estimate, a screenshot from a vendor app, a preliminary spotter report, and a homeowner phone call into one undifferentiated pile — and then route off the pile. That is how a group-chat screenshot ends up driving a 40-house canvass. Force the evidence into a ladder.

The ladder keeps you honest in two directions. It stops you from overstating a radar estimate as fact, and it stops you from ignoring the strongest evidence you have — a homeowner who called you. A preliminary SPC report sitting near your service edge is a reason to research, not a reason to roll. A verified Storm Events record from three weeks ago is great for documentation but useless for today's timing. And a prior customer inside the swath outranks a perfect radar pixel over a stranger's house, because the work is welcome and the relationship already exists.

The discipline here is naming the source out loud on the board. "MRMS swath, north side, checked 7:10 a.m." is a usable note. "Storm hit the north side" is not — it has quietly promoted an estimate to a fact. Reps and schedulers inherit whatever certainty the board projects, so the board has to project the right amount.

Roof Age Is The Hidden Axis Most Teams Ignore

Here is the part that separates a smart route from a spray-and-pray canvass. Two variables decide whether a roof is worth your time after a storm: how hard it got hit, and how much life it had left. The swath gives you a rough read on the first. Almost nobody systematically tracks the second — and the second is often the bigger lever.

Think about why. Most asphalt shingle roofs are built to deliver useful service for roughly 20 to 30 years, with three-tab products on the shorter end (often 15 to 20 years) and architectural and premium products longer. The National Roofing Contractors Association and manufacturers like Owens Corning both note that real-world lifespan swings widely — by something like 40% — depending on climate, slope, ventilation, and install quality. A 22-year-old three-tab roof in a hot, sun-baked subdivision is already brittle; granules are gone, the mat is dry, and a modest hail event can finish the job. A 4-year-old architectural roof under the same swath has tough, flexible shingles that may take the same stones with cosmetic dings and no functional damage.

Now layer that against the IBHS small-hail finding. An older roof that has absorbed several seasons of sub-severe hail is sitting at the bottom of its service life with compromised impact resistance. When a real swath finally crosses it, it fails in ways an adjuster can document. The new roof next door does not. So the highest-value houses after a storm are, predictably, the older roofs inside the harder-hit part of the swath — and the lowest-value are new roofs anywhere, even dead center.

This is exactly the gap RoofPredict is built to close. It pairs an estimated roof-age range for individual homes with storm physics modeled per roof — hail trajectory and wind impact at that specific structure, rather than only "the swath passed over this ZIP." The output is a per-house signal for which roofs a storm likely wore out, so a crew can skip the 2023 builds and spend the day on the 2003 ones. Worth stating plainly, because overclaiming here is how trust dies: RoofPredict does not inspect roofs, does not diagnose damage, and does not certify remaining life. The age is a planning range, not an exact build date, and the storm score is a prioritization aid, not an inspection. It tells you where to point the ladder, not what you'll find when you get up there.

If you do not use a tool for this, build the age axis manually. County assessor data sometimes carries an "effective year built" or last permit; your own CRM holds every roof you have ever touched; and a windshield read of granule loss, curling, and color fade gives a rough vintage. The point is to stop treating the swath as the only input. A neighborhood priority that ignores roof age is leaving the best houses unworked and wasting days on roofs that will pass inspection.

The Neighborhood Priority Scorecard

Once a neighborhood clears the source ladder, score it. The goal of scoring is not to make a radar estimate sound more certain than it is. It is to decide where you can deliver timely, documented, welcome work — and in what order. Use a simple 0/1/2 per factor and sum it. Keep the weather score from dominating; a perfect swath over a place you cannot safely or legally service is still a hold.

A neighborhood with older roofs, clear swath overlap, a handful of past customers, tight density, safe access, and approved scripts should beat a bigger but newer, scattered, half-researched area every time. The numbers are a tiebreaker and a discussion-ender, not an oracle.

Two rules keep the scorecard honest. First, roof age and prior relationship can pull a neighborhood up even with a modest swath, because that is where documented damage and welcome conversations actually live. Second, safety and compliance are veto factors, not point factors — a zero in either column holds the whole neighborhood regardless of how high the rest scores. You do not average your way past a downed power line or a no-knock ordinance.

Give the team plain language for the tiers:

• Priority 1: older-roof, in-swath, safe, staffed, script-ready, welcome. Work it now.
• Priority 2: promising but missing one thing — density, relationship, or a source detail. Work it next.
• Hold: do not touch until the named reason clears.

And kill this language on sight, because it is both false and legally radioactive: "Priority 1 means everyone has damage." "Priority 1 means insurance will pay." Priority describes your readiness to serve, never the condition of a roof or the outcome of a claim.

A Worked Scoring Pass

Four neighborhoods, same storm, same morning board:

North Ridge is Priority 1 not because anyone proved damage, but because it stacks older roofs, clear swath energy, existing relationships, safe access, and available crews. Lakeview gets held twice: the evidence is a screenshot, and even if the storm was real, a subdivision full of three-year-old roofs is the wrong place to spend a hail week. Old Mill has genuine homeowner demand and the right roof age, and it still waits — safety vetoes urgency, every time. Write down why each one landed where it did. "Held for safety" and "deferred for capacity" and "new construction, low age value" are three different reasons that route to three different next steps, and recording them stops you from re-litigating the same board tomorrow.

Reading The Swath Map Without Fooling Yourself

Managers stare at the same colored map and walk away with different plans. A few field habits keep the read honest.

Look for the gradient, not the headline color. The most workable blocks are often along the tight gradient where estimated hail jumps from moderate to large over a short distance — that edge tends to separate roofs that got functional damage from roofs that got cosmetic dings. A uniformly red blob tells you less than a sharp boundary does.

Cross-check the swath against storm motion and wind. Hail driven by strong wind hits the windward roof slopes hardest and can travel well past where the radar core sat. If the swath ran with a strong rear-flank wind, expect the worst damage on the storm-facing elevations and don't be surprised by damage just outside the colored edge.

Treat vendor hail maps as a convenience layer over the same NOAA physics, not a second opinion. Most commercial hail-map products are repackaging radar-derived estimates. They are genuinely useful for speed and overlays, but they inherit every limit of the underlying estimate. Save the source and timestamp regardless of which app drew the polygon.

Separate today's storm from the season. If you work a region that takes repeated hail, the IBHS small-hail finding means cumulative exposure matters. A block that has been nibbled for three seasons may be riper than today's single swath suggests. Your CRM and roof-age data carry that history; the live map does not.

Mind the clock and the time zone. Radar products, SPC reports, and your CRM may each stamp time differently — UTC, local, issued-time, report-time. Mislabel it and you will merge two storms into one route or split one storm into three. Put the time basis on the board next to the source.

Safety Holds Are Not Optional

No swath is worth a fall or a brush with a live wire. OSHA's roof inspection and storm-work guidance catalogs the obvious hazards — ladders, steep and slick surfaces, damaged decking, power lines, slips, trips, and falls. A post-hail route must never expect a rep to climb a roof off a door knock, and crews do not work through active weather to hit a number.

Use an explicit hold whenever any of these are live:

The single best safety habit is to ask, before releasing any route, "what would stop this?" A new warning, an emergency order, flooded streets, a full inspection calendar — any of those should change the board mid-day. A good route list is alive. It updates as the facts and the crew change.

Staying Legal: Canvassing Rules And The Insurance Line

Two legal fronts trip up storm-response teams. Handle both before the trucks roll.

Solicitation and canvassing ordinances

Door-to-door commercial solicitation is regulated locally and the rules vary house-to-house across city lines. Common requirements include solicitor permits or registration, posted hours (often roughly 9 a.m. to 9 p.m.), "do not knock" lists, and ordinances that require a canvasser to leave immediately when a no-soliciting sign is posted. Some towns run a Green River-style ordinance that bars uninvited commercial door-to-door entirely. Courts have struck down permit schemes for non-commercial canvassing, but commercial sales — which is what a roofer does — is frequently regulated more tightly. The practical move: before a neighborhood becomes a route, confirm the local rule, pull any required permit, respect posted signs, and stick to lawful hours. The Federal Trade Commission also enforces a Cooling-Off Rule that gives buyers three days to cancel many door-to-door and off-site sales of $25 or more; your contracts and scripts should honor it rather than pressure around it.

And respect the obvious consumer-protection reality after a storm. The FTC's post-disaster scam guidance and the NAIC's after-the-storm guidance both warn homeowners about high-pressure repair pitches and about signing away insurance benefits. Being the calm, documented, no-pressure contractor in a neighborhood full of storm-chasers is a competitive edge, not a constraint.

The public-adjusting line you cannot cross

This is the one that ends companies. A roofer documents the condition of a roof and provides an estimate to repair or replace it. A roofer does not adjust, negotiate, manage, settle, maximize, or "fight" a homeowner's insurance claim — that is public adjusting, and in most states it requires a separate license. In June 2024 the Texas Supreme Court decided Texas Department of Insurance v. Stonewater Roofing, holding that a roofer who advertised itself as an insurance-claims specialist and whose contracts authorized it to negotiate with insurers on the homeowner's behalf was acting as an unlicensed public adjuster — and that the licensing statute did not violate free-speech or due-process rights. The opinion is on Justia. The lesson reaches well past Texas: most states draw the same line.

So train the boundary into every script. The contractor's job is to show up with the facts — photos, measurements, a roof-age range, dated documentation — that support the homeowner's own claim. The insurer decides coverage. Build the "say this, not that" into muscle memory:

SAY THIS                                  NOT THAT
--------------------------------------    --------------------------------------
"We reviewed official weather data for     "Your neighborhood got hit, so your
 this area and are offering free            roof is damaged."
 documentation inspections."

"We'll document what we find with          "We'll get your claim approved."
 photos and measurements you can give
 your insurer."

"Your insurance company decides            "We handle the whole claim and fight
 coverage. We provide the estimate          the insurance company for you."
 and documentation."

"The deductible is yours to pay under      "Don't worry about your deductible,
 your policy."                               we'll cover it / waive it / eat it."

"A hail swath shows where a storm           "Everyone inside this swath
 tracked. It doesn't tell us whether         qualifies."
 your specific roof was damaged."

Every line on the right is a real way roofing companies get sued, fined, or shut down. Offering to waive, cover, or rebate a homeowner's deductible is insurance fraud in many states — the deductible is the homeowner's obligation, full stop. Calling yourself an "insurance claims specialist" in your marketing is the exact move that sank Stonewater. The safe lane is wide and profitable: document conditions honestly, hand the homeowner a clear report, and let the adjuster adjust.

Narrow The Route Before You Widen It

Big swaths tempt teams to open too much ground. Resist it. A tight route you can actually service beats a sprawling one that produces missed calls and vague promises.

A sane first-pass order for almost any storm:

1. Past customers and inbound requests inside the swath.
2. Older-roof blocks with clear swath overlap and safe access.
3. Dense zones you can inspect within capacity this week.
4. Research zones near the swath edge.
5. Everything held for safety, compliance, source, or low age value.

That order keeps the homeowner experience near the center. You start where you have a relationship or a request, then expand only as fast as source quality, roof-age data, and crew capacity allow.

The CRM Goldmine Most Roofers Forget After A Storm

The best post-hail list you own is not the swath. It is your own customer and estimate history. Every roof you have ever inspected, quoted, or replaced is a dated record of a roof at a known age in a known location. When a swath crosses an area where you have years of past estimates, you are sitting on a ranked re-engagement list before you draw a single route.

Think about the homeowner you quoted four years ago who decided to wait. Their roof is four years older now, and a storm just crossed their block. That is a warm, documented, welcome call — not a cold knock. Or the customer whose roof you replaced eight years ago: their warranty questions and their neighbors are both worth a touch. Pulling these contacts and overlaying them on the swath is the single highest-yield hour a manager spends after a storm, and it is exactly the kind of targeting RoofPredict is meant to sharpen — mining an old CRM of past estimates and customers, matching it against the storm, and surfacing which of your own prior contacts now sit inside a worn-roof, in-swath block. The tool points; your team still makes the honest call and does the honest inspection.

A short CRM pull after every notable storm:

• Past estimates, last 5+ years, inside the swath, sorted by roof age.
• Prior customers near warranty milestones in the swath.
• Anyone who declined a quote and whose roof has aged since.
• Referral sources and past reviewers in the affected blocks.

Work that list before the cold canvass. The conversations are easier, the close rate is higher, and the inspections are welcome rather than tolerated.

Regional And Climate Variation Changes The Math

A prioritization system that works in the Texas hail alley is not identical to one that works in the upper Midwest or the high plains, and a manager who runs the same playbook everywhere will misread the swath. Climate shapes both how roofs age and how hail behaves, so it shapes how you rank.

In hot, high-UV regions — Texas, Oklahoma, the desert Southwest — asphalt shingles bake. The asphalt dries and the mat grows brittle years earlier than the same shingle would in a temperate climate, which is part of why NRCA and manufacturers note real-world lifespan can swing by roughly 40% on climate alone. In those markets, a 15-year-old roof may already behave like a 22-year-old roof elsewhere, so your roof-age threshold for "due" should drop. A swath that crosses an older sun-baked subdivision is a higher-value target than the same swath over a cooler-climate neighborhood of the same vintage.

In the central and northern plains — the heart of the country's hail activity, and the focus of the multi-institution ICECHIP field campaign IBHS helped fund in 2025 — repeat hail is the dominant story. Neighborhoods take small and mid-size hail season after season. Cumulative damage matters more than any single event, which means your CRM history and roof-age data carry even more weight than the live swath. A block that looks unremarkable on today's map may be the ripest one in town because it has been chipped at for five years.

In freeze-thaw climates, ice and thermal cycling already stress shingles and flashing before hail ever arrives, so a modest swath can tip an already-compromised roof. And in coastal or mixed-wind regions, the wind component of a storm can matter as much as the hail; wind-driven hail concentrates on windward slopes and lifts or creases shingles in ways that read very differently from straight-down impact. Modeling wind impact per roof, on top of hail, is exactly why per-structure storm physics beats a flat swath overlay in these markets.

The practical move is to set your roof-age and swath-energy thresholds for your climate, not a national average, and to revisit them as you learn which blocks actually produce documented damage. Two markets, two completely different priority boards off the same-looking radar image.

The Door Conversation And The Branded Homeowner Report

Prioritization decides which doors you knock. What happens at the door decides whether the work was worth it. The reps who do well after a storm are the calm, specific, low-pressure ones — the opposite of the storm-chaser stereotype homeowners have been warned about. Two tools make that easier: a per-home reason for being there, and a documented report the homeowner can keep.

Give every rep a per-home talking point instead of a script that treats every house the same. "We reviewed the storm data for your area and your roof's age range suggests it's worth a free documentation inspection" lands very differently from a generic "storms came through, want your roof checked." The first is specific, honest, and respectful of the homeowner's time; it also signals you did homework rather than just driving the swath. This is one of the most genuinely useful things a targeting tool earns a crew — RoofPredict can hand a canvasser a per-home reason and a branded homeowner report, so the conversation starts from a real, address-specific fact rather than a blanket pitch.

The branded report matters because it changes the homeowner's role. Instead of being sold to, the homeowner receives documentation — photos, measurements, a roof-age range, the storm context — that they own and can take to their insurer. That keeps you cleanly on the right side of the public-adjusting line: you documented conditions, the homeowner decides what to do, and the insurer decides coverage. It also builds trust, because a homeowner who holds a clear, professional report is far more likely to refer you and to call you again in a few years when the roof finally fails.

A simple door framework that respects both the homeowner and the law:

AT THE DOOR
1. Identify honestly: name, company, why this address specifically.
2. Offer, don't assert: a free documentation inspection, not a verdict.
3. Respect the answer: no-soliciting sign or "no thanks" ends it politely.
4. Document, don't diagnose at the door: schedule a safe inspection.
5. Leave something real: card, branded report, or scheduled time.
6. Never: claim damage, promise coverage, mention the deductible,
   or pressure a same-day signature.

The reps who internalize that framework convert the prioritization work into welcome inspections and referrals. The ones who skip it convert good targeting into complaints. Same list, opposite outcome.

Daily Storm-Response QA

Storm boards rot fast. New reports, new calls, new field notes, and shifting weather all change the picture by mid-morning. Run a short quality check before the first route releases, and again if a new source materially moves the swath. This is a control point, not a second strategy meeting.

If a route fails any row, it does not release. The most common failures are boring and preventable: an old screenshot, an unlabeled radar image, a wrong time zone, a neighborhood that bleeds outside the swath, a missing script, or a list bigger than the office can answer. Catch them here, not in a deposition.

The Clean Handoff: Route To Inspection

The route hands the inspector context, never conclusions. The inspector needs to know why the appointment exists, what started it, what the homeowner asked for, and what to photograph — not a pre-written verdict that the roof is totaled.

A solid handoff carries:

• The swath source summary, with URL and timestamp.
• Event time and lookup time, with time zone.
• Roof-age range or CRM history for the address.
• Homeowner request or contact status.
• Safety and access notes.
• The named inspection owner.
• The photo checklist and documentation standard.
• Any interior concern the homeowner mentioned.

The handoff says "hail swath context plus a 19-year roof plus a homeowner who called." It never says "roof damaged because the swath crossed the subdivision." Weather context explains why you are looking; the inspection records what is actually there. Keep that line bright and the whole operation stays defensible.

A workable photo and documentation standard for the inspector:

HAIL INSPECTION DOCUMENTATION CHECKLIST
[ ] Wide shots of all roof slopes (label N/S/E/W)
[ ] Close-ups of any impact marks with chalk + scale reference
[ ] Test-square photos (count marks within a marked area)
[ ] Soft metals: gutters, downspouts, vents, flashing, A/C fins
[ ] Window screens, fascia, garage door, mailbox (collateral)
[ ] Ridge, hip, and field shingle condition
[ ] Existing wear vs. fresh impact (note granule loss / aging)
[ ] Roof age read: granule loss, curling, manufacturer markings
[ ] Date/time stamp and address on the file
[ ] Homeowner-reported interior leaks or stains (note, photograph)
NOTE: Document conditions. Do not promise coverage or claim outcomes.

After the inspection, hold the same discipline. Photos, measurements, and written notes go in the file and into the homeowner's hands so they can take them to their insurer. The route board never converts a swath into a promise about approval, payment, or replacement.

Common Mistakes That Wreck A Storm Run

• Routing on the swath alone. Ignoring roof age means working new roofs and skipping the worn ones the storm actually finished. The swath is one of two axes, not the whole map.
• Promoting estimate to fact. "The storm hit" instead of "the radar estimate covers this area" trains the whole team to overstate, all the way to the door.
• Opening more territory than you can service. A sprawling route produces missed calls, rushed inspections, and a brand reputation for chaos. Narrow first.
• Skipping the CRM. Cold-knocking strangers while warm past-customers in the same swath go untouched is leaving the easiest work on the table.
• Crossing the public-adjusting line. Any script that has the company managing, negotiating, or guaranteeing a claim is a lawsuit waiting for a plaintiff. Document; don't adjust.
• Touching the deductible. Offering to waive, cover, or rebate it is fraud in many states. It is the homeowner's to pay.
• Ignoring local canvassing rules. No-knock lists, permits, and posted hours are not suggestions. One complaint can close a whole town to you.
• Letting the board go stale. A route that doesn't update for a new warning, a full calendar, or a fresh report is a route working yesterday's storm.

Putting It Together: A One-Page Storm Morning

Here is the full sequence a manager can run in under an hour after a notable hail event:

POST-HAIL MORNING SEQUENCE
1. Pull the swath (MRMS/MESH or vendor). Save URL + timestamp + time zone.
2. Overlay swath on the service-area map. Trim to what you can serve.
3. Label every source on the ladder (radar / report / verified / request).
4. Pull the CRM: past estimates + customers inside the swath, sorted by roof age.
5. Add roof-age data to each candidate block (tool, assessor, or windshield).
6. Score each neighborhood: hail energy, age, relationship, density,
   safety, compliance, capacity.
7. Apply vetoes: any safety or compliance zero = HOLD.
8. Rank: P1 (old roof, in-swath, safe, staffed, welcome) first.
9. Confirm local canvassing rules + pull permits where required.
10. Attach the approved script to every open route.
11. Run daily QA. Anything that fails a row does not release.
12. Hand crews context + photo checklist, never conclusions.
13. Re-check the board midday for new warnings, calls, or capacity changes.

That is the whole system. The swath points you at the right side of town. Roof age and your own history point you at the right houses. Safety and compliance keep you out of trouble. Capacity keeps the work honest. And a clean handoff keeps the inspection — and the insurance conversation — exactly where the law wants it: with the homeowner and their insurer, supported by your documentation. Do it that way and the storm builds your reputation instead of risking it.

Sources checked: June 18, 2026.

More storm-targeting guides

• The Storm Targeting Playbook: Work the Path, Skip the Circus — storm work that starts from the roofs, not the hype
• How to Find Old Roofs in the Storm Path Before Your Competition Knocks — old roofs inside the swath are the shortlist
• How to Use Storm Data to Plan Roofing Canvassing That Actually Closes — plan canvassing from verified storm data

FAQ

Does a hail swath prove my roof is damaged?

No. A hail swath is a radar-estimated map showing roughly where a storm's hail core tracked and how big the stones got aloft. It does not measure what actually hit your specific roof, and it cannot account for wind, melting, or the age and condition of your shingles. A roof under a big swath can be fine, and a roof near the edge can be damaged. Only a safe, documented inspection can record the actual condition of your roof.

Should roofers always work the center of the swath first?

Not necessarily. The center shows the highest estimated hail size, but the best targets combine swath energy with old roof age, prior-customer relationships, route density, safe access, and legal canvassing. A new subdivision in the dead center of a swath usually yields little documented damage, while older roofs along a sharp swath edge often do. Smart teams down-rank new construction and prioritize worn roofs inside the affected area, then expand outward as capacity allows.

Why does roof age matter more than swath size for prioritizing?

Because damage depends on both how hard a roof got hit and how much life it had left. Older asphalt shingles are brittle, low on granules, and far easier to damage, especially after several seasons of small hail, which IBHS research shows can age shingles and leave them roughly ten times more vulnerable to a later severe event. A 20-year-old roof and a 3-year-old roof under the identical swath produce completely different outcomes, so age often beats swath size as a targeting signal.

What is MESH and how accurate is it for roofing?

MESH is the Maximum Estimated Size of Hail, a NOAA MRMS radar product that estimates hail size from the reflectivity a storm produces above the freezing level. Accumulated over time, it draws the colored hail swath roofers use. It is a strong tool for finding where a storm tracked and focusing your search, but it estimates hail aloft at coarse radar resolution, not what landed on any specific parcel. Treat MESH as a triage layer, never as property-level proof of damage.

Can my roofing rep tell a homeowner the swath means their roof is damaged?

No. A rep can honestly say the company reviewed official weather data for the area and is offering documentation inspections to homeowners who want them. A rep cannot say the swath proves damage at that specific home, because it does not. Saying "your neighborhood got hit, so your roof is damaged" overstates the data and trains homeowners and adjusters to distrust you. The honest framing keeps the company credible and the homeowner's claim, if any, on solid footing.

Can a roofing company handle or negotiate my insurance claim?

No, not in most states. Adjusting, negotiating, settling, or managing a claim on a homeowner's behalf is public adjusting and requires a separate license. The 2024 Texas Supreme Court decision in Texas Department of Insurance v. Stonewater Roofing confirmed that a roofer advertising as an insurance-claims specialist and negotiating with insurers was acting as an unlicensed public adjuster. A roofer's proper role is to document conditions, provide an estimate, and give you the photos and measurements that support your own claim. Your insurer decides coverage.

Is it legal for a roofer to offer to cover or waive my deductible?

No. The deductible is the homeowner's obligation under the policy, and a contractor offering to waive, cover, rebate, or absorb it is committing insurance fraud in many states. Be wary of any storm-chaser who pitches free deductibles, no-cost roofs, or pressure to sign on the spot. A legitimate contractor documents your roof honestly, gives you a clear estimate, and lets you and your insurer handle coverage and your deductible.

Do roofers need a permit to canvass door-to-door after a storm?

Often, yes. Commercial door-to-door solicitation is regulated locally, and many cities require a solicitor permit or registration, restrict hours, maintain do-not-knock lists, and require canvassers to leave when a no-soliciting sign is posted. Some towns ban uninvited commercial canvassing outright. Rules change at every city line, so a roofing team should confirm the local ordinance and pull any required permit before routing a neighborhood. The FTC's three-day Cooling-Off Rule also applies to many door-to-door sales.

How can a contractor target the right homes without buying leads?

By sharpening the outbound work they already do. Start with your own CRM: past estimates and customers inside the swath, sorted by roof age, are warm and welcome contacts. Overlay roof-age data and the storm's path on your service area, skip new construction, and focus on older roofs in the affected blocks. Contractors who use tools like RoofPredict pair an estimated roof-age range with per-home storm physics to flag which roofs a storm likely wore out, so canvassers spend the day on the right houses instead of cold-knocking everyone.