How to Read a Hail Swath Map for Roofing Sales

A hail swath map looks like a weather product, and that is exactly why most roofing teams misread it. The colored ribbon across the county is not a map of damaged roofs. It is a model's best guess at where hail of a certain size probably fell, built from radar that never actually touched a single shingle. Treat the ribbon as gospel and you will spend a week knocking streets that took marbles while your competitor works the three blocks that took golf balls two counties over.

The gap between "where the map is red" and "where roofs are actually due" is where storm-restoration money is won or lost. A swath map gets you to the right side of town. It does not tell you which house on which street has a roof worn thin enough that this storm pushed it over the edge. Knowing how to read the map, and knowing exactly what it cannot tell you, is the difference between a canvass that books inspections and one that burns gas.

What follows is the way experienced storm crews actually use these maps: how the swath gets built, what each layer means, where the model lies, how to cross-check it before you commit a crew, and how to turn a ribbon of color into a street-by-street knocking plan. There are worked examples, a couple of checklists you can hand to a green canvasser, and an honest accounting of the edge cases that cost people money every season.

What a hail swath map actually is

Start with the plumbing, because the plumbing explains every mistake people make downstream.

Weather radar does not see hail. It sees energy bouncing back off whatever is in the air, and it infers size from how that energy behaves. A swath map takes a sequence of radar scans during a storm and stitches them into a single footprint: the path the storm's hail core traveled across the ground over the life of the cell. The color tells you the estimated maximum hail size at each point along that path.

The most common engine behind these products is MESH, Maximum Estimated Size of Hail. MESH is an algorithm that reads radar reflectivity at altitudes where the air is below freezing, weights it by how far above the freezing level that energy sits, and spits out a size estimate in inches. The National Severe Storms Laboratory developed the method, and a version of it runs inside the MRMS system that feeds many of the commercial hail maps roofers buy. When a vendor shows you a swath colored from quarter-size up through baseball, that color ramp is almost always MESH or a proprietary cousin of it.

Two things follow from this, and you should tattoo them on the inside of your eyelids:

First, the map is an estimate built from radar, not a measurement taken on the ground. MESH is good at telling you that something hail-sized came through and roughly how big. It is far less good at the exact inch, and it has known failure modes that put color where there was no damage and miss damage where it puts no color.

Second, the size on the map is the maximum estimated size in that radar pixel, not the average and not what fell on any specific roof. A pixel can read 1.75 inches because a handful of stones that big passed through the beam, while most of what actually hit the ground in that pixel was three-quarter-inch ice that a 3-tab shingle shrugs off. The map rounds up to the scariest stone.

The layers you are actually looking at

A usable hail map is not one image. It is a stack. When you open a vendor product or a public tool, learn to separate these layers in your head:

• The swath polygon or grid — the footprint itself, the ribbon of color. This is the MESH output binned into size categories.
• The size legend — the color-to-inches key. Pay attention to where the breakpoints sit. One vendor's orange might mean 1.25 inches; another's might mean 1.5. The colors are not standardized across products.
• The storm date and time — every swath belongs to a specific storm on a specific day. A county can have three overlapping swaths from three different days in one spring. Mix them up and your damage story falls apart on the first adjuster call.
• Reports overlay — ground-truth hail reports from spotters, often pulled from the Storm Prediction Center's database. These are dots where a human said "I saw hail this big." Gold, but sparse.
• Population or rooftop density — better products overlay where structures actually are, so you are not excited about a swath over a cornfield.

If your map tool only shows you one undifferentiated blob of color with no date, no legend breakpoints, and no reports, it is a toy. You need the layers to do real work.

How the swath gets built, in plain terms

It helps to picture what the algorithm is doing frame by frame. A weather radar sweeps the sky every few minutes. Each sweep produces a volume of reflectivity data, essentially a measure of how much energy is bouncing back from precipitation at various heights. Big hail returns a lot of energy, and it returns energy from high in the storm where the air is well below freezing. MESH keys on that: reflectivity that sits far above the freezing level is the signature of hail being held aloft by a strong updraft and growing.

The algorithm computes a size estimate for every grid cell in that single scan. Then it does the same for the next scan, and the next, across the whole life of the storm. The swath you see is the running maximum: for each point on the ground, what was the largest size estimated in any scan as the storm passed over. That is why a swath looks like a continuous painted stripe even though the storm was only over any given point for a few minutes. You are looking at an accumulation of moments, each one a separate radar guess, welded into one footprint.

Three consequences fall out of that construction. One, the swath is only as good as the radar coverage during those minutes; a gap in scans or a beam blocked by terrain leaves holes. Two, because it is a running maximum, the swath inherits every over-estimate along the way; one bad scan that read high paints a pixel high for the whole event. Three, the swath has no idea how long the storm dwelled over a point, so two pixels colored the same can represent thirty seconds of hail or fifteen minutes of it. Dwell time matters enormously for roof damage and the size legend says nothing about it, which is why storm speed, covered later, is a layer you read separately.

Hail size is the whole game, so read the legend like a contract

The single most important number on the map is estimated hail size, because size is what correlates with roof damage. Everything else is context.

Here is the rough physical reality, and the size thresholds that matter for an asphalt shingle roof:

The National Weather Service treats one inch as the official severe hail threshold, and that line matters because it is roughly where functional shingle damage stops being the exception and starts being the rule, especially on roofs that already have some age and wear on them. Below an inch you can still get damage, but it is concentrated on roofs that were already vulnerable. Above an inch and a half, you are looking at a swath where most roofs of any real age took a hit.

Maximum versus typical, and why the legend can fool you

The legend tells you the category maximum for each color band. A pixel shaded for 1.5 inches is telling you the model thinks the biggest stone in that pixel hit about an inch and a half. It is not telling you the median stone was that size.

This is the difference between a great storm and a dud that looks great on the map. Two swaths can both light up orange:

• Swath A: a tight, intense core where the bulk of stones were 1.25 to 1.5 inches, falling hard and at a steep angle.
• Swath B: a sprawling, marginal area where one rogue 1.5-inch stone passed through a pixel but the typical fall was three-quarter-inch.

The map paints them the same orange. Swath A is a week of replacements. Swath B is a week of "sorry, this roof looks fine." You cannot tell them apart from color alone. You need the supporting evidence, which is why the back half of what follows is about cross-checking rather than only looking at the ribbon.

The five layers of a swath you have to read in order

When a real storm chaser-turned-sales-manager opens a swath, they are not only looking at "how red is it." They read it in a sequence. Train your team to do the same.

1. Size — where does it cross the damage threshold

Find the contour where the swath crosses one inch, then find where it crosses one and a half. Those two lines, not the outer edge of the color, are your real working boundaries. Inside the 1.5-inch line is your A-zone: knock first, expect functional damage on most aging roofs. Between 1.0 and 1.5 is your B-zone: real opportunity but you will get more "no damage" calls, so lead with inspection not replacement. Below 1.0 is your C-zone: work it only if it is your existing service area or the roofs there are old.

2. Edges — the swath has a soft side and a hard side

Hail does not stop at a clean line, but the damage gradient across a swath is steep and it is asymmetric. The leading and right-flank edge of a moving supercell's hail core usually has the sharpest cutoff and the biggest stones, because that is where the strongest updraft was. The trailing edge fades more gradually. Practically: the edge of the color is fuzzy, so plan to knock a few blocks past where the color ends on the hard side, and discount the soft trailing edge.

The fuzzy edge cuts both ways. The model bins to a grid, so a street that sits right on a color boundary might have taken the same hit as the street one band up. Never tell a homeowner "the map says your street is fine." The map's resolution is coarser than a city block.

3. Direction and speed — the storm's motion is written in the swath shape

A long, thin, straight swath means a fast-moving storm that dumped hail and kept going. A short, wide, blobby swath means a slow or nearly stationary cell that sat and pounded one area. The slow blob is usually the better storm for you: more total time dropping hail on the same roofs means more accumulated damage, and often larger stones from a sustained updraft.

Storm motion also tells you about wind-driven damage. A fast storm drives hail at a low angle, which hammers the windward slopes hard and can leave leeward slopes nearly untouched. That matters when you inspect: on a fast-mover, check the side of the roof facing where the storm came from, and check soft metals, screens, and siding on that same elevation as corroborating evidence.

4. Date — anchor every swath to one storm

Write the storm date on everything. Your inspection notes, your photos, your route sheets. When a county has multiple events in a season, the date is what keeps your damage documentation honest and what keeps your story consistent if an adjuster asks when the damage occurred. A roof that shows weathering inconsistent with a single recent date invites the "this is old, pre-existing" objection. Pick the storm, document to that storm.

5. Ground truth — find the dots

Overlay the actual hail reports. The Storm Prediction Center maintains a database of severe weather reports, and the National Centers for Environmental Information archives them. A spotter report of 1.75-inch hail sitting inside your orange swath is the corroboration that turns a model guess into a confident knocking decision. A swath with zero ground reports anywhere near it deserves more skepticism, because nobody on the ground confirmed what the radar inferred.

One caution on reports: they are sparse and biased toward where people live and watch the sky. A swath crossing a dense suburb will collect reports; the same swath over rural land may have none even if the hail was identical. Absence of reports over empty country is not evidence the hail was small. Weight reports heavily where they exist, but do not invert their absence into a reason to skip an otherwise strong, structure-covered swath.

Where the map lies: MESH failure modes every pro should know

This is the part competitors' blog posts skip, and it is the part that actually saves your gas money. MESH and the swath products built on it have predictable blind spots.

It over-reads in high-shear, wind-driven storms. Strong horizontal winds can throw radar size estimates high. You get a scary swath and underwhelming ground damage.

It under-reads at long range from the radar. Radar beams climb as they travel out. Far from the radar site, the beam is sampling high in the storm and can miss the low-level reality, shrinking or losing a swath that actually dropped big hail. If your storm is 80 miles from the nearest radar, distrust a weak reading more than a strong one.

It gets confused by storm structure. Mesocyclones, multi-cell mergers, and storms with unusual vertical structure can produce reflectivity patterns that the algorithm size-estimates poorly. Same-day, same-region storms can read very differently for reasons that have nothing to do with what hit the ground.

Pixel resolution is coarse. MESH grids are on the order of a kilometer. A kilometer is many city blocks. The map cannot resolve why one street took it and the next was spared, and it cannot capture the microbursts and pockets that make hail damage so patchy at the street level.

It does not know roof age, slope, or material. This is the big one. The map models the hazard. It is completely blind to the vulnerability of the thing being hit. A 1.25-inch hit on a 22-year-old 3-tab roof at the end of its life is a replacement. The same hit on a four-year-old architectural roof might be cosmetic. The map paints both pixels identical orange.

That last failure mode is the one worth dwelling on, because it is where the real opportunity hides and where the next section comes in.

The map shows the storm. It cannot show which roofs were due.

Here is the mental model that separates teams that grind from teams that close: a roof failing under hail is a collision of two things. The hazard, which is the storm, and the vulnerability, which is the roof's age, material, slope, and prior wear. The swath map is a near-perfect tool for the first variable and completely silent on the second.

Walk a marginal 1.0-to-1.25-inch swath and you will see it plainly. The brand-new roofs in the new-construction subdivision came through fine. The 18-to-25-year-old roofs in the established neighborhood three streets over are the ones with mat fractures and granule loss. Same hail. Different outcome. The variable that decided it was age and wear, and the map had nothing to say about it.

This is the gap where a tool like RoofPredict earns its place in the workflow. The swath map tells you where the hail went. A roof-age and storm-modeling layer tells you, address by address inside that swath, which roofs were already aging out before the storm arrived. RoofPredict reads aerial imagery to estimate a roof-age range per address, and it models storm exposure per individual roof rather than per kilometer-wide radar pixel. Overlay that on the swath and the patchwork resolves: inside your A-zone, you can sort the roofs that were already in the back third of their life from the ones that just got reroofed, and knock the due ones first.

Be clear-eyed about what that does and does not give you. The age output is a range, not a birth certificate, because aerial imagery can date a roof's general era but not the day it was installed. The storm model gives you odds that a given roof was hit hard, not proof that it was damaged. Nothing replaces a ladder, a chalk line, and a trained eye on the actual slope. What it does is change the order you knock and the confidence you bring to the door. Instead of working a swath left to right and burning hours on roofs that were never going to qualify, you work the intersection of "storm hit here" and "this roof was due," which is the densest vein of real opportunity in any storm zone.

The honest framing on the claims side matters too, and it is worth saying plainly because it keeps you out of trouble. You document the roof's condition and write the estimate. The insurer decides coverage. The homeowner owns the claim. A swath map and a roof-age layer help you find and prioritize the roofs worth inspecting. They are evidence-gathering and routing tools, not a promise of a covered claim, and any honest storm operator should present them that way at the door and in the file.

From map to knocking plan: a step-by-step workflow

Reading the map is half the job. Turning it into a route a crew can run is the other half. Here is the workflow start to finish.

Step 1: Confirm the storm is real and worth chasing

Before anyone loads a ladder, answer three questions:

1. Does the swath cross the 1.0-inch line over actual rooftops, not open land? Pull the population or structure overlay.
2. Are there ground-truth hail reports inside or adjacent to the swath corroborating the size?
3. Is the swath inside, or within reasonable drive time of, your licensed service area? Chasing across state lines drags in registration, licensing, and contractor laws you may not be set up for.

If you cannot answer yes to the first two, the swath is a maybe, not a go. Many a crew has chased a long thin marginal swath that the radar over-read in a wind-driven storm and found nothing on the ground.

Step 2: Draw your zones

On the swath, mark the 1.5-inch contour and the 1.0-inch contour. Everything inside 1.5 is A-zone. Between 1.0 and 1.5 is B-zone. Below 1.0 but with old housing stock is C-zone. This zoning, not the raw color, is what you assign crews against.

Step 3: Sort A-zone by roof vulnerability

Within the A-zone, you want to knock the due roofs first. The crude way is by neighborhood age: county assessor data and a drive-through tell you which subdivisions went up in the late 1990s and early 2000s, which puts a lot of original roofs at 20-plus years. The sharp way is a per-address roof-age layer that ranks the actual roofs, so you are not assuming a whole subdivision aged uniformly when half of it already reroofed after the last storm.

Step 4: Build the route, not merely the list

A list of addresses is not a route. Sequence the knocks so a canvasser walks a tight loop with minimal backtracking, working one side of a street then the other. Target roughly contiguous blocks of 40 to 80 doors per canvasser per shift in dense suburban stock. Hand each canvasser a defined polygon, not the whole zone, so two reps do not double-knock the same street and so you can measure who worked what.

Step 5: Knock the corroborating evidence first

Send a scout or your sharpest rep to a few A-zone addresses first to verify ground truth: are soft metals dented, are downspouts and gutter aprons dimpled, is there granule wash at the downspout outlets, are AC condenser fins flattened on the storm-facing side? Confirming real, fresh, directional damage on the first few roofs validates the whole zone. Finding nothing tells you the radar over-read and you should redeploy before you waste a crew-week.

Step 6: Document to the storm date

Every inspection ties back to the storm date you anchored in Step 1. Date-stamped photos, a chalk-circled damage map of the slope, soft-metal corroboration, and a clean estimate. Consistency to a single dated event is what holds up.

Step 7: Measure and re-zone daily

Track knock-to-inspection and inspection-to-signed by zone and by canvasser. If B-zone is converting better than A-zone, your size read or your age sort was off; adjust the next day. The swath is static. Your deployment should not be.

A worked example: reading one real-shaped swath

Walk through a composite example so the abstractions land. Suppose a late-May supercell moves west to east across a metro's north side. The swath you pull the next morning looks like this:

• A 14-mile-long, 3-mile-wide ribbon, oriented west-to-east, with a slight bend to the southeast near the end.
• A core of 1.75-to-2.0-inch coloring for about 5 miles in the middle, tapering to 1.0-to-1.25 inch on both ends.
• The southeast bend at the tail end shows a renewed pocket of 1.5-inch color where the storm slowed.
• Two SPC hail reports inside the core: one at 1.75 inches, one at 2 inches. No reports on the west tail.
• Structure overlay shows the western third is mostly open land and a business park; the core and the southeastern bend sit over residential subdivisions.

How a pro reads it:

The western third is noise. Big-looking color over a business park and fields is not your storm. Skip it regardless of the legend.

The 5-mile core over residential is your A-zone, and it is confirmed by two ground reports of 1.75-to-2.0-inch hail. This is a replacement-grade core; on roofs of any real age you expect functional damage. Knock here first, lead with inspections that will frequently become replacements.

The southeastern bend, where the storm slowed and re-intensified to 1.5 inches, is a sleeper A/B zone. A slowing storm pounds the same roofs longer, so even at a slightly lower max-size read, accumulated damage there can rival the core. Worth a scout team early to confirm. If the soft metals are dimpled there, treat it like A-zone even though the color is a band lower.

The 1.0-to-1.25-inch eastern tail is B-zone: real but marginal, more no-damage calls, work it after the core with an inspection-first pitch and prioritize the older subdivisions.

Now add the vulnerability layer. Inside the core, the subdivision on the north edge went up in 2019 with architectural shingles; the one on the south edge dates to 2001. Same 1.9-inch hail. The 2001 stock is your densest opportunity, the 2019 stock will produce more cosmetic-only inspections. A per-address roof-age range lets you knock the 2001-era roofs and the scattered un-reroofed homes in the newer subdivision first, instead of treating the whole core as uniform.

That read turns a 14-mile ribbon into a ranked, three-zone plan with a scout-confirmed sleeper and an age-sorted A-zone. That is the difference between using the map and being used by it.

Common mistakes that cost storm teams money

The same errors show up season after season. Run your team against this list.

Chasing color over rooftops instead of over roofs. Excitement at a big red swath that sits over farmland, water, or industrial land. Always pull the structure overlay first.

Treating max size as typical size. Knocking a marginal swath as if every roof took the worst stone in the pixel. Lead with inspections, not replacement promises, anywhere below 1.5 inches.

Believing the edge is a wall. Telling a homeowner just outside the color that their roof is fine. The grid is coarser than a block; inspect the fringe, do not write it off.

Ignoring storm motion. Inspecting the wrong slopes on a fast wind-driven storm and missing the windward-side damage, or missing that the leeward slopes legitimately have little.

Mixing storm dates. Stacking damage from two events into one story. Anchor to a date and document to it.

Distrusting the radar at long range the wrong way. Dismissing a weak reading 80 miles from the radar when the beam was sampling high and the ground hit may have been bigger. Weak far-from-radar readings deserve a scout, not an automatic skip.

Assuming neighborhood-uniform roof age. Treating a whole subdivision as the same vintage when a chunk of it reroofed after the last storm. Sort by actual per-address roof age, not by the year the subdivision was platted.

Over-promising at the door. Turning a swath map and a forecast into a claim guarantee. The map shows odds and exposure. The insurer decides coverage. Say so.

Double-knocking and under-measuring. No defined polygons per rep, no tracking by zone, so you cannot tell a bad zone read from a bad rep. Assign polygons; measure conversion by zone daily.

A canvasser's pocket checklist for the door

Hand this to every rep. It connects the map to what they verify on the ground.

• Confirm the address is inside the zone I was assigned, not the next polygon over.
• Note the storm date I am working; every photo and note ties to it.
• From the ground, scan storm-facing soft metals: gutters, downspouts, fascia, vents, AC fins. Fresh dents are my corroboration.
• Look for granule wash at downspout outlets and in splash zones.
• Check the roof's apparent age and slope; an older, steeper, storm-facing slope is the highest-probability damage.
• If the first few roofs on this block show no fresh directional damage, flag the zone to my manager before knocking 40 more.
• Present inspection, not a guaranteed claim or a free roof. I document; the insurer decides; the owner owns the claim.

What the swath cannot tell you: real damage versus look-alikes

The map gets you to the slope. It cannot tell you whether the marks on that slope are hail or something that only resembles it, and this is where green crews lose credibility fast. An inspector who calls every dark spot hail will get their inspections kicked and their reputation dinged. Train the difference.

Genuine hail bruising on an asphalt shingle is a roughly round impact where the mat is fractured beneath the surface; the spot often feels soft or has lost granules in a circular pattern, and the hits are random in spacing and consistent in direction across a slope. Fresh hits show a clean, un-weathered exposure where granules were knocked off. The directionality is the tell: real hail from one storm hammers the slopes facing the storm and largely spares the opposite slopes, and the soft metals on the storm-facing elevation will corroborate it.

Look-alikes that get mistaken for hail and should not be:

• Blistering. Raised bumps from gases escaping the asphalt, often hollow, with no fracture beneath and no matching damage to soft metals. Frequently uniform across all slopes, including ones the storm never faced.
• Granule loss from normal aging. Diffuse, slope-wide thinning rather than discrete round impacts. Common on south and west exposures from sun, not from ice.
• Mechanical or foot-traffic marks. Scuffs and shiny spots in lines or along walk paths, not random.
• Manufacturing or installation defects. Patterned, repeating, or tied to fastener lines.

The reason this connects back to the map: a swath that reads marginal, say 1.0 to 1.25 inches, is exactly where inspectors are most tempted to call aging and blistering as hail to make a roof qualify, because the storm gave them just enough cover to imagine it. That is how you end up with denied claims and an adjuster who distrusts your whole file. Let the swath and the soft-metal corroboration set the bar. If the storm-facing gutters and downspouts are clean of fresh dents, be very skeptical of "hail" on the shingles below them.

The pitch at the door, tied to what the map gives you

Reading the map well only pays if the conversation at the door converts. The swath gives you a true, specific, non-hypey opening that beats generic "we are in the area" scripts.

Lead with the specific storm and date, because specificity reads as competence. Something like: "A hailstorm came through your neighborhood on the night of the 22nd. We have been inspecting roofs on these blocks because that storm was carrying hail large enough to damage roofs that have some age on them, and a lot of homeowners do not realize anything happened until a leak shows up months later. I would like to do a free inspection and show you photos of whatever I find, good or bad."

Notice what that does and does not promise. It states the storm happened, which is true. It says the hail was large enough to damage aging roofs, which is honest about vulnerability rather than implying every roof is wrecked. It offers an inspection, not a claim, not a free roof, not a guaranteed approval. The homeowner stays in control of any claim, the insurer decides coverage, and you have set yourself up as the documenter rather than the promiser.

Common objections and honest responses:

• "My roof looks fine from the ground." "It usually does. Hail damage on asphalt is rarely visible from the ground; it shows up as bruising in the mat that you only see on the slope. That is exactly why a quick inspection is worth it."
• "Are you saying I will get a new roof?" "I cannot promise that, and you should be wary of anyone who does. What I can do is document the condition and give you an honest estimate. Your insurer decides coverage and you own the claim. My job is to find and document what is actually there."
• "How do you know the storm even hit my house?" "I am working from the storm's hail map and the reports from that night, which put hail of a damaging size over these streets. The map gets me to the right neighborhood; the inspection tells us what your specific roof took, because two roofs on the same street can come out very differently depending on age and condition."

That last answer is worth memorizing, because it is the honest two-sentence version of everything covered here: the map is the hazard, the roof is the vulnerability, and only the inspection resolves the specific house.

Public tools versus paid swath products

You do not need to buy a hail platform to read a swath, but you should know what the free and paid tiers give you.

Public and free. The NOAA and National Weather Service ecosystem gives you the raw ingredients. The Storm Prediction Center publishes daily storm reports including hail. The National Centers for Environmental Information archives storm events and lets you pull historical hail reports by location and date. MRMS-derived products surface MESH-based swaths. These are authoritative, free, and slower to assemble into a clean canvassing map. They are excellent for corroboration and for building your storm date history.

Paid platforms. Commercial hail-mapping vendors package MESH-style swaths with clean legends, address search, date filtering, structure overlays, and exportable territories. You are paying for convenience, speed, and integration, not for fundamentally better physics. The underlying size estimate is still radar-derived and carries the same failure modes. A paid map that does not show you ground reports and storm dates is not worth more than the free tools.

The layer the maps do not include. None of the swath products, free or paid, model the vulnerability side. They model the hazard. That is the deliberate gap a roof-age and per-roof storm layer fills, and it is why the smartest storm teams run a swath product for the hazard and a roof-intelligence layer for the vulnerability, then knock the overlap.

Reading swaths for the long game, not only the next week

Most teams use swath maps reactively: a storm hits, they pull the map, they chase. The teams that compound revenue use them two more ways.

Historical layering. Pull every hail swath over your service area for the past several years from the archive. Neighborhoods that took multiple sub-replacement hits over a decade are full of roofs that are quietly cooked: each marginal storm shaved a little life, and they are now primed to fail on the next event or simply due to age. Cross that history with current roof age and you have a list of due roofs you can work even in a quiet season.

Aging-out routes between storms. Storm work is feast or famine. The roofs that are aging out do not wait for a storm. A roof-age range across your whole territory gives you a non-storm canvassing route: the roofs in the back third of their service life are due regardless of whether hail just fell. When the season is dry, you knock age, not weather. When a storm hits, you overlay the swath and re-rank. The map is one input to a year-round system, not a once-a-season fire drill.

Turning a swath read into a 48-hour deployment

The map read is worthless if you cannot move on it fast. Storm restoration rewards speed, because the first credible, honest crew on a street books the inspections and the late arrivals knock doors that already have a sign in the yard. Here is how a tight operation compresses the time from "storm hit overnight" to "crews knocking the right zone by afternoon."

Hour 0 to 2, the morning after. Pull the swath and the ground reports. Confirm the 1.0-inch line crosses real rooftops. Mark A, B, and C zones. Pull roof-age data across the A-zone so you know which blocks hold the due roofs. Decide go or no-go. A disciplined no-go on a wind-over-read marginal swath saves more money than any single good day of knocking earns.

Hour 2 to 4, scout and validate. Send one or two sharp people to a handful of A-zone addresses to confirm ground truth: fresh directional soft-metal damage and shingle bruising on the storm-facing slopes. This is the single highest-leverage two hours of the whole operation. Confirm the zone is real before you commit the whole team. If the scouts find nothing, you just saved a crew-week; re-read the map for a stronger pocket or stand down.

Hour 4 to 8, deploy. Cut the validated A-zone into per-canvasser polygons of 40 to 80 doors. Brief the team on the storm date, the pitch, the objection answers, and the look-alike traps so nobody over-calls damage. Put your strongest closers on the densest due-roof blocks. Knock.

End of day one, measure and re-zone. Pull knock, inspection, and signed numbers by polygon. The map was your hypothesis; the conversion data is the test. A zone that under-converts despite strong color is telling you the radar over-read or the roofs were newer than you assumed. Shift people the next morning to where the numbers, not the colors, are strongest.

This cadence is why the vulnerability layer matters operationally and not only conceptually. When you can rank the due roofs inside the A-zone before sunrise, your hour-4 deployment goes to the highest-probability blocks first instead of working the zone alphabetically and discovering the good streets on day three. In storm work, the difference between day-one and day-three on the right street is often the difference between a signed contract and a competitor's lawn sign.

A simple deployment table

Safety and licensing realities you cannot skip

Reading the map well also means deploying responsibly, because two failures sink storm operations regardless of how good the swath read was.

Roof safety. Storm-damaged roofs are slick with loose granules and hidden soft spots. OSHA's fall protection rules apply to your crews on steep and elevated work, and storm restoration concentrates exactly the conditions that cause falls. A great swath read does not matter if a crew member goes off a wet 8/12. Build fall protection into every inspection, not only the tear-off.

Licensing and registration. Chasing a swath across a county line is easy on a map and hard in law. Many states require contractor licensing or storm-restoration registration, and several have specific rules governing roofing contracts signed in the wake of a declared storm, including rescission windows and prohibitions on advancing or rebating a homeowner's deductible. Know the rules of the jurisdiction the swath sits in before you knock a door there. The map does not stop at the state line, but your license might.

Bringing it together

A hail swath map is a high-quality answer to one question: where did the storm's hail core travel and roughly how big were the biggest stones. Read it well and you get to the right side of town, the right zone, the right edge, and the right storm date. Read it badly and you chase color over cornfields and promise homeowners a covered claim the radar never earned.

The discipline is in remembering what the map is silent on. It does not know which roofs were already due. It does not know roof age, slope, material, or prior wear. It rounds up to the scariest stone and bins the world into kilometer pixels that are blind to the street-by-street patchwork of real damage. The pros cross-check it against ground reports, scout it before they commit a crew, sort it by roof vulnerability, and measure their conversion daily so a bad read gets corrected by Tuesday.

Pair the hazard map with a vulnerability layer, knock the overlap of "the storm hit here" and "this roof was due," document honestly to a storm date, present inspections rather than promises, and you turn a weather product into a sales system. The ribbon of color is where the work starts. Which roofs were due is where the work pays.

FAQ

What hail size on a swath map means a roof is likely damaged?

One inch is the National Weather Service severe threshold and roughly where functional shingle damage stops being the exception. Below one inch, damage concentrates on older or already-worn roofs. At 1.5 inches and up, functional damage is common across roof ages, and at 1.75 inches or larger you should expect widespread, replacement-grade damage on most roofs that have any real age on them.

What is MESH on a hail map?

MESH stands for Maximum Estimated Size of Hail. It is an algorithm developed by the National Severe Storms Laboratory that estimates hail size from radar reflectivity above the freezing level. Most commercial and public swath products color their maps using MESH or a proprietary version of it. The key word is estimated: it is a radar-derived model, not a ground measurement.

Does the color on a swath map mean every roof in that area is damaged?

No. The color shows the maximum estimated hail size in each radar pixel, not the typical stone size and not actual roof damage. A pixel can read 1.5 inches because a few large stones passed through while most of what fell was smaller. The map also cannot see roof age or condition, so two roofs in the same color can have completely different outcomes. Always inspect.

Why do roofs on the same street have different damage after the same storm?

Because hail damage is a collision of hazard and vulnerability. The swath map captures the hazard, the storm. It is blind to vulnerability: roof age, shingle type, slope, and prior wear. An aging roof at the end of its life can fail under hail that leaves a four-year-old roof next door merely cosmetically marked. Street-level microbursts and pockets add further patchiness the kilometer-scale map cannot resolve.

How do I turn a hail swath map into a canvassing route?

Confirm the swath crosses one inch over actual rooftops and is corroborated by ground reports. Draw zones at the 1.0-inch and 1.5-inch contours. Sort your A-zone by roof age so due roofs get knocked first. Build tight contiguous polygons of roughly 40 to 80 doors per canvasser, scout a few addresses to confirm ground truth, document to the storm date, and track conversion by zone daily so you can re-deploy.

Can a hail swath map be wrong?

Yes, in predictable ways. MESH can over-read in wind-driven, high-shear storms and under-read far from the radar where the beam samples high in the storm. Unusual storm structure can throw the size estimate off. The grid resolution is about a kilometer, far coarser than a city block. Always cross-check the swath against ground hail reports and a quick on-the-ground scout before committing a crew.

Free public hail maps or a paid hail platform — which should I use?

Public NOAA, National Weather Service, and Storm Prediction Center tools give you authoritative MESH swaths and ground reports for free, but assembling them into a clean canvassing map takes work. Paid platforms package the same radar-derived data with address search, date filters, and structure overlays for speed and convenience. The physics underneath is the same, so a paid map that hides ground reports and storm dates is not worth the premium.

How does roof-age data work with a hail swath map?

The swath map models where the storm hit. A roof-age layer like RoofPredict estimates a roof-age range per address from aerial imagery and models storm exposure per individual roof rather than per radar pixel. Overlaying the two lets you knock the intersection of where the storm hit and which roofs were already aging out. The age is a range, not an install date, and the model gives odds of a hard hit, not proof of damage, so it ranks your route rather than replacing an inspection.

Why does storm direction matter when reading a swath?

Storm motion is written in the swath shape and tells you where to inspect. A long thin straight swath means a fast mover that drives hail at a low angle, hammering windward slopes and sometimes sparing leeward ones. A short wide blob means a slow or stationary cell that pounded the same roofs longer, often producing heavier accumulated damage. Knowing the direction tells your crews which slopes and which soft metals to check first.

What should a canvasser verify on the ground that the map cannot show?

Fresh, directional damage to storm-facing soft metals: dimpled gutters, downspouts, fascia, vents, and flattened AC condenser fins. Granule wash at downspout outlets. The roof's apparent age, slope, and which elevation faced the storm. If the first few roofs on a block show no fresh directional damage, the radar may have over-read the zone, and that is a signal to verify before knocking the rest of the street.