How to Verify a Roof Actually Got Hail Damage Before You Knock the Door

Every storm season the same thing happens. A cell pops on radar, a few crews see the warning, and by the next morning trucks are crawling neighborhoods that the hail core never actually crossed. The reps knock for two days, write a pile of "maybe" inspections, and come back with sunburn and three soft appointments that go nowhere. Meanwhile the street six blocks east that genuinely got worked over by 1.5-inch stones sits untouched until a competitor cleans it out.

The single most expensive mistake in storm restoration is not a bad close rate. It is knocking the wrong roofs. Door-knocking labor is your scarcest resource during the 30-day window when a storm is fresh in a homeowner's mind, and you only get to spend each rep-hour once. If you spend it on a roof that took pea-sized hail and bounced, you didn't just lose that hour. You also planted a story in that homeowner's head that "a roofer came by and there was nothing wrong," which is the exact objection the next legitimate contractor has to dig out of.

So the real question is not "how do I sell hail damage." It is the question a sharp owner asks before the trucks roll: how do I verify a roof actually got hail damage before knocking? You want to walk into a neighborhood already knowing the storm physics support real, documentable damage on most of those roofs, so your reps are confirming a thesis instead of fishing.

What follows is the workflow good storm teams actually use. It moves from the macro (did a damaging hail event even occur here, and exactly where) down to the micro (does this specific roof show the tells before I commit a rep to the door), and finally to the inspection that has to hold up when an adjuster is standing next to you. None of this replaces getting on the roof. All of it tells you which roofs are worth getting on.

Why "a storm came through" is not the same as "these roofs are damaged"

The word "hail" does a lot of lying in this business. A National Weather Service report that says hail occurred in a county tells you almost nothing actionable. Hail damage to asphalt shingles is a function of several variables that all have to line up, and most of the time at least one of them doesn't.

The variables that actually decide whether a roof is damaged:

• Stone size. This is the big one. Functional damage to most asphalt shingle roofs generally starts showing up around 1 inch (roughly quarter-size) and becomes consistent and obvious as you climb toward 1.25 to 1.75 inches and up. Below 1 inch you are usually looking at cosmetic marks, granule scatter, or nothing. Pea-size (0.25 in) and dime-size (0.7 in) hail rarely bruises a healthy shingle mat. This is a generalization, not a law of physics, because the other variables move the threshold.
• Density and terminal velocity. A 1-inch stone that is mostly slush hits softer than a 1-inch stone that is solid ice. Larger stones fall faster, so impact energy climbs steeply with size, not linearly. A 2-inch stone carries far more than twice the punch of a 1-inch stone.
• Wind. Hail driven sideways by a strong gust changes which slopes get hammered. Straight-down hail concentrates damage on the flattest pitches and horizontal surfaces. Wind-driven hail loads up the windward elevations and can spare the leeward side almost entirely. This is why you can have a genuinely damaged roof where the north and west slopes test positive and the south and east slopes look untouched.
• Roof material and age. An aged, brittle three-tab shingle that has already lost a chunk of its granule armor bruises at a lower threshold than a two-year-old laminate shingle. A 20-year-old roof might show functional damage from 1-inch hail that would only scuff a new roof. Soft metals like aluminum gutters, fascia, vents, and AC fins dent at much smaller sizes and are your early-warning indicators (more on that below).
• Exposure and obstruction. Tree cover, a higher adjacent structure, or even orientation can shadow part of a roof from the hail path.

Put those together and you get the practical truth: a storm can drop "hail" across a 10-mile-wide reported area while only a 1.5-mile-wide core actually carried stones large enough to bruise shingles. That core is the swath you want. Everything outside it is a roof full of cosmetic granule loss that no honest contractor should be writing up as functional damage, and that no adjuster is going to approve.

So step one of verification is not about any individual roof at all. It is about reconstructing where the damaging core actually went.

Step 1: Confirm a damaging event happened and map the real swath

Before a single rep gets dispatched, you reconstruct the storm. The goal is a defensible answer to two questions: did stones large enough to cause functional damage fall here, and where exactly is the line between "worth knocking" and "don't bother."

The free public data, and how to read it honestly

There are several public sources. Each has a specific blind spot, which is why you cross-reference them instead of trusting one.

NOAA Storm Prediction Center (SPC) storm reports. The SPC publishes daily storm reports including hail, with reported sizes and locations. These come from spotters, law enforcement, and the public. Strengths: they are ground-truth observations of actual stones. Weaknesses: they are sparse and biased toward where people live and bother to call in. A report of 1.75-inch hail at an intersection tells you a big stone hit there, but the absence of a report two miles away does not mean nothing fell there. Reports are dots, not coverage.

NWS Local Storm Reports (LSRs) and warnings. Your regional NWS office issues severe thunderstorm warnings that often include an estimated or reported hail size, plus LSRs after the fact. The warning polygons and the estimated max hail size in the warning text are useful for bracketing the event timing and the storm's stated severity.

MESH and radar-derived hail products. This is where you get actual coverage instead of dots. Radar algorithms estimate a Maximum Estimated Size of Hail (MESH) from the storm's vertical structure, the height of the 50+ dBZ reflectivity core, and freezing-level data. NOAA's research and the National Severe Storms Laboratory have published extensively on MESH and the broader Multi-Radar Multi-Sensor (MRMS) system. MESH renders as a gridded swath, so you can see the shape and width of the probable damaging core, rather than only the spots where someone happened to report a stone. The honest caveat: MESH is an estimate derived from radar, not a measurement of stones on the ground. It can overestimate (especially with high reflectivity that isn't all hail) and the size it reports is a maximum, not what fell on every roof in the grid cell. Treat MESH swaths as a probability map, not proof.

The commercial hail-verification reports (the paid storm-data vendors) essentially package MESH-style radar analysis plus their own modeling into a per-address report. They are useful and many supplement carriers use similar data, but understand what you are buying: a modeled estimate. It tells you the odds were high that damaging hail fell at an address. It is not, by itself, evidence of damage on a specific roof. An adjuster will not approve a claim because a hail report says a big stone probably fell. The roof has to actually show it.

Reading the swath like a pro

When you overlay the radar swath, the spotter dots, and the warning polygons, you are looking for agreement. When MESH shows a 1.5-inch core, three SPC reports inside that core confirm golf-ball stones, and the warning called for 1.75-inch hail, you have a high-confidence damaging swath. Knock that.

When MESH shows a faint 0.75-inch smear, there are zero ground reports, and the warning was a generic severe thunderstorm with 1-inch "or greater" boilerplate, you have a maybe at best. That is the neighborhood that burns crews.

A few field rules that separate good swath reading from wishful thinking:

• Width matters as much as size. A narrow, intense core means the damage line can run right down the middle of a subdivision, putting the south side of a street in play and the north side out. Plan canvass routes to the swath, not to the subdivision boundary.
• The core moves. Hail cores travel with the storm, so the damaging line is often diagonal across a grid, not aligned to streets. Your route should follow the swath's actual track.
• Old storms muddy the water. If the area also took a storm 14 months ago, some roofs already carry old hail marks. Knowing the date of the swath you are working is what lets a rep tell fresh damage from old (covered next).
• Date the event precisely. You need the exact date because the inspection has to distinguish recent impacts from weathering, and because any eventual claim is tied to a date of loss. Working a roof and telling the homeowner "a storm," vaguely, is how you end up with a denial for wrong date of loss.

At the end of Step 1 you should be able to draw a line on a map and say: inside this line, stones were probably large enough to cause functional damage on aged or vulnerable roofs; outside it, don't send anyone. You have just eliminated most of the wasted door-knocking before it happens.

A quick decision table for Step 1

Use something like the matrix below to grade an event before you commit any labor. The point is to force the question "is this even worth working" before anyone is in a truck.

When the row reads mostly "strong," route crews. When it reads mostly "marginal," send one experienced rep to ground-truth a few frontages (Step 3) before you commit the team. When it reads "weak," the cheapest decision you can make is to not knock at all and save the rep-hours for the next event. Discipline at this gate is where most of the wasted canvassing gets prevented.

Step 2: Filter the swath down to roofs that can actually be damaged

Here is where most teams stop thinking and just start knocking everything inside the swath. That is a mistake, because two roofs under the identical hail core can have completely different outcomes. The 22-year-old three-tab roof is far more likely to show functional, approvable damage than the laminate roof installed last spring. Inside the swath, you want to prioritize the roofs that are both in the hail and vulnerable to it.

Age is the second filter, and it is huge

Shingle roofs get more hail-vulnerable as they age. Granule loss thins the protective layer, the asphalt oxidizes and gets brittle, and the mat loses flexibility. A stone that would bounce off a three-year-old roof can crack the mat of a 20-year-old roof. So even within a confirmed swath, the older roofs are where your functional-damage hit rate is highest.

The problem: you usually don't know the age of a roof from the street, and you definitely don't know it for a whole neighborhood. Pulling permits address by address is slow. Eyeballing from the curb is unreliable.

This is where roof-age intelligence from aerial imagery changes the canvass. By analyzing high-resolution aerial and satellite imagery over time, you can estimate a roof's age as a range per address, not a single date. "This roof reads as roughly 18 to 24 years old" is exactly the kind of signal that lets you rank a street. You combine that with the swath and you are no longer knocking a subdivision, you are knocking the intersection of "hail large enough to matter" and "roofs old enough to be vulnerable."

Be honest about what age estimation can and cannot do. It gives you a range, not a birth certificate. A roof estimated at 15 to 20 years might be a recently re-roofed structure that an imagery model hasn't fully updated, or a roof that looks aged due to algae rather than wear. The point of the range is prioritization, not proof. It tells your reps which doors to hit first, not what to write on an inspection form.

Material and exposure as tie-breakers

Within the swath, also weight toward:

• Visible soft-metal targets. Homes with prominent metal gutters, metal roof vents, ridge vents, turbines, swamp coolers, and exposed AC condensers give you cheap confirmation evidence from the ground (Step 3). A home bristling with dentable metal is easier to verify quickly.
• Open exposure. Roofs without heavy tree cover took the full hail load. Tree-shadowed roofs are noisier to read.
• Steeper-pitch caution. Very steep roofs and certain orientations may have shed wind-driven hail; the flatter the slope, the more direct the hits on a straight-down event. This is a soft factor, not a hard rule.

At the end of Step 2, your knock list is no longer "this ZIP got a warning." It is a ranked route: the older, exposed, soft-metal-rich roofs sitting inside the high-confidence part of the swath, knocked first; the newer roofs at the swath edge, deprioritized or skipped.

Step 3: Ground-truth confirmation you can do before you ever climb

Now you are standing on the sidewalk in front of a prioritized roof. You still haven't knocked. There is a surprising amount of verification you can do from the ground in 60 seconds, and good reps do all of it before they ring the bell, because it turns the conversation from "can I look at your roof" into "I can already see your gutters took hail, let me confirm what the roof did."

The soft-metal walk-around

Hail dents soft metal at sizes well below what bruises shingles, which makes metal your most reliable cheap indicator that real, sizable stones fell here. Look at, from the ground or with a small step:

• Gutters and downspouts. Round dents on the top of gutter runs and on the gutter apron. These dent at smaller hail sizes, so they confirm hail occurred but, on their own, don't prove functional shingle damage. They are corroboration, not the whole case.
• Metal fascia and drip edge. Dimpling on horizontal-facing metal.
• Roof vents, turbines, ridge vents, plumbing vent caps. These soft-metal accessories dent and ding cleanly. A dented turbine cap is a strong tell.
• AC condenser fins and the unit's top and sides. Mashed fins and dents on the AC are excellent corroborating evidence and they sit at ground level where anyone can see them.
• Window screens, garage doors, mailboxes, downspout extensions. Spatter and dents on these confirm directional hail and help you read which way the wind drove the stones.
• Hail spatter / oxidation marks. Fresh hail strips oxidation and dirt off metal and painted surfaces, leaving lighter spatter marks. Old spatter weathers and refills; fresh spatter is bright. This helps date the event.

The directional read matters: if every dent is on the west and south faces and the north faces are clean, you now know which roof slopes to inspect closely and you can predict that the north slope may test negative. That is the difference between a rep who finds the damage fast and one who spends 40 minutes hunting on the wrong elevation.

Collateral on the property

Look past the structure. Hail leaves a fingerprint across the whole lot:

• Shredded or holed leaves under and on trees and shrubs (if it's the right season).
• Damaged plants, broken branches, stripped garden beds.
• Dents in vehicles in the driveway, and on neighbors' cars.
• Mineral granules in driveway low spots, at downspout outlets, and in the splash blocks. A pile of granules where the downspout dumps tells you the roof shed granules during the event. This is a meaningful tell, though be careful: roofs shed some granules normally over time, so you're looking for fresh accumulation consistent with the storm date, rather than any granules at all.

What the neighbors tell you

If two houses on the block already have tarps, yard signs from another company, or fresh dumpsters, the swath is real and active here. That is both confirmation and a clock: a worked street means competitors are present and the window is closing.

By the end of Step 3 you can ring the bell already saying something specific and true: "I'm working this street because of the storm on [date]. I can see your gutters and your AC took hail. I'd like to confirm what your roof did." That is verification doing your selling for you, and it is completely UPPA-safe because you're documenting observable conditions, not promising an outcome.

Timing the canvass to the storm

Verification has a clock on it, and the clock changes how you sequence the curb work above. A few timing realities good teams plan around:

• The freshest window is the most honest window. In the first days after an event, spatter is bright, granule piles are obvious at downspouts, and bruises on the roof haven't re-oxidized. The same evidence gets harder to read after weeks of weather. Verifying early is both faster and more defensible.
• Collateral fades on its own schedule. Shredded leaves drop and decompose, dented cars get to a body shop, and homeowners hose granules out of the driveway. If you wait, you lose cheap corroboration you would otherwise have photographed.
• The competitive clock is real. A worked street (tarps, signs, dumpsters) tells you the swath is genuine and that other crews are converting it right now. Inside a confirmed high-confidence corridor, prioritize the streets that are still untouched over the ones already crawling with competitors.
• Don't outrun your verification to beat competitors. The temptation under competitive pressure is to skip the swath and age filtering and just knock fast. That is exactly how you end up writing cosmetic-only roofs. Speed comes from a tight route built on good Step 1 and Step 2 work, not from skipping it.

The sequence that holds up: reconstruct and rank the same day or night the storm hits, route to the swath, and have reps running the curb walk-around the next morning while the evidence is bright. You move fast because the office work already told the reps exactly where to go.

Step 4: The roof inspection that actually holds up

Everything up to now told you the roof probably has damage and earned the climb. The inspection is where you confirm it for real, and the bar is specific: you are looking for functional damage that an insurance adjuster, using their carrier's criteria, will recognize. Cosmetic marks don't count, and writing them up as functional is how you torch your credibility with both homeowners and carriers.

Get up there safely, or don't get up there

None of the verification matters if a rep gets hurt, and storm canvassing pushes people onto roofs fast and often. Treat roof access as a controlled task. OSHA's fall-protection standards exist because roofing is one of the most fall-prone trades, and a verification visit is not an excuse to skip basics: a stable, properly footed ladder extended past the eave, three points of contact, soft-soled footwear with grip, and a hard stop on wet, frosted, steep, or otherwise unsafe roofs. Hail events leave debris and slick granules on the surface, which makes the day after a storm exactly when footing is worst. If a roof is too steep or too high to inspect safely, verify what you can from the eave, a ladder, and the ground evidence rather than putting a rep where they shouldn't be. A drone or eave inspection that you can defend beats a fall you can't undo.

What to carry

A verification kit is short and cheap: chalk or a lumber crayon to circle hits, a tape measure and a coin for scale in photos, a phone or camera, a soft brush, and your documentation form or app. That's the whole inspection rig. The expensive part of verification was the thinking you did in Steps 1 and 2; the on-roof tools are deliberately simple so the rep focuses on reading the shingle, not fiddling with gear.

Functional vs. cosmetic: the distinction that matters

• Functional hail damage compromises the roof's ability to shed water or shortens its service life. On asphalt shingles this is a bruise or fracture: an impact that breaks or cracks the shingle mat (the reinforcing layer), usually with granule loss at the point of impact, and it feels soft or springy when you press it (like a bruise on an apple). The mat fracture is the key. Granule loss alone, without mat damage, is generally cosmetic.
• Cosmetic damage is surface-only: granule scuffing, marks that don't break the mat, blistering, or manufacturing imperfections. It looks bad and doesn't shorten roof life in a way carriers pay for.

New reps consistently get this wrong in two directions. They call blisters and mechanical scuffs "hail" (false positives that get denied and make them look incompetent), or they miss real mat fractures because they didn't press-test and chalk the hits.

A short field glossary of look-alikes that are not hail, because reps waste hours and credibility on these:

• Blistering. Round, popped bubbles in the asphalt from trapped moisture or manufacturing. They expose asphalt and lose granules, so they look hail-ish, but they have no soft bruise underneath and often cluster, where hail is random.
• Mechanical / foot-traffic damage. Scuffs and granule loss along the paths a worker would walk, around penetrations, valleys, and access points. Patterned, not random.
• Manufacturing defects and granule clumping. Uneven granule embedment from the factory. Tends to follow the shingle's run, not a random scatter.
• Normal weathering and granule shedding. Older roofs lose granules everywhere over time. General thinning is age, not an impact event.
• Algae and surface staining. Cosmetic discoloration that some reps misread as impact marks from the ground.

The test for all of them is the same: press for a soft, mat-fractured bruise and check whether the distribution is genuinely random across the slope. No bruise or a non-random pattern means it isn't hail, full stop.

The test-square method

The standard, defensible way to quantify hail damage is the 10-foot by 10-foot test square, which is also how most adjusters do it. You mark a 100-square-foot area on a representative slope, count the functional hail hits inside it, and document. Carriers commonly look for a threshold number of functional hits within a test square (the exact number varies by carrier and region) before they'll total a slope or roof. Your job on inspection is to find and document the genuine hits, not to manufacture a count.

A disciplined per-slope workflow:

1. Inspect every slope, but score each one separately. Wind-driven hail means slopes differ. Mark a test square on each slope, ideally in the area facing the storm's direction of travel that you identified from the soft-metal read.
2. Chalk the hits. Circle each suspected impact with chalk or a lumber crayon. This makes them photographable and lets you and an adjuster count the same marks.
3. Press-test suspected hits. A true bruise feels soft. Run a thumb across it. A mat fracture often has a shiny or fresh granule-stripped center and a soft halo.
4. Look for the random pattern. Real hail damage is randomly distributed across the slope with no directional pattern within the slope (the directionality is between slopes, from wind). If "hits" line up in rows, follow nail lines, or cluster on traffic paths, you're looking at foot traffic, mechanical damage, or manufacturing defects, not hail.
5. Check the soft accessories on the roof too. Hits on the metal vents, ridge caps, and flashing on the roof itself corroborate the field damage.
6. Confirm freshness. Fresh hits have exposed asphalt that hasn't re-oxidized and granules that look freshly displaced. Old hail hits weather over and the exposed asphalt darkens. This is how you avoid writing up a prior storm's damage as the current date of loss.

Documentation that survives an adjuster meeting

Verification doesn't end when you find the damage. It ends when you can prove it cleanly later. For every confirmed roof:

• Wide, mid, and macro photos of each damaged slope, with the chalked test square visible, plus a few close-ups with a tape measure or coin for scale next to a bruise.
• Photograph the soft-metal collateral (gutters, vents, AC) because that corroborates the date and the hail size.
• Note the slope orientation (N/S/E/W) for each test square so the wind-driven pattern is documented.
• Record the date of loss and tie it to the storm event you reconstructed in Step 1.
• Note shingle type and approximate age, since age supports functional damage on a borderline call.

Stay strictly inside your lane while documenting. You inspect and document conditions and provide a repair estimate. The homeowner files and owns any claim. The insurer's adjuster decides coverage. Never promise approval, never promise the homeowner pays nothing, never describe the work as "free," and never present a storm report or a hail estimate as proof of damage. Those moves are more than bad practice, they cross legal lines in many states around public adjusting and unfair claims practices, and they get contractors in real trouble. Your verification stack is strong precisely because it documents observable, photographable physical conditions and ties them to a real, dated, mapped weather event.

A worked example: reading one storm end to end

Walk through how this plays out on a single event so the workflow stops being abstract.

A late-spring supercell tracks across the north side of a metro on a Tuesday evening. Here's the verification chain a sharp team runs by Wednesday morning.

Macro (Step 1). The NWS issued a severe thunderstorm warning at 6:42 p.m. citing 1.75-inch hail. SPC storm reports show three confirmed observations along the track: 1.0 inch, 1.5 inch, and 1.75 inch, roughly a mile apart, forming a clear line running west-southwest to east-northeast. The radar-derived MESH swath shows a core of estimated 1.5 to 2.0-inch hail about 1.2 miles wide following that same line for about 9 miles, then weakening to under 1 inch as the storm moved east of the interstate. Read: high-confidence damaging swath along a 9-mile, 1.2-mile-wide diagonal corridor. East of the interstate, skip it.

Filter (Step 2). Inside that corridor sit four subdivisions. Roof-age intelligence shows Subdivision A (built late 1990s) reads heavily in the 20-to-26-year range, Subdivision B (built mid-2010s) reads 8-to-12, and two pockets in C and D read 16-to-22. Read: prioritize A first (old roofs squarely in a 1.5-to-2-inch core is the highest-yield combination), then the older pockets of C and D, then B last or not at all.

Ground-truth (Step 3). A rep parks in Subdivision A and walks three frontages without knocking. Every home shows dented gutters and dimpled vent caps. Two AC units have mashed fins. The dents concentrate on the south and west faces. A neighbor already has a competitor's yard sign. There are granules piled at two downspout outlets. Read: real event, sizable stones, wind from the south-southwest, competitors already here, clock running. Knock now, lead with the south/west slopes.

Inspection (Step 4). On the first roof, the rep chalks a test square on the south slope and finds a clear count of soft, mat-fractured bruises in a random pattern, granule-stripped centers, fresh asphalt. The north slope test square comes back nearly clean, consistent with the wind direction. The rep photographs both squares, the gutters, and the AC, notes a roughly 22-year-old three-tab, records the Tuesday date of loss, and documents everything for the homeowner to use with their carrier. Result: a verified roof, documented to survive an adjuster meeting, found in a fraction of the time because every prior step pointed here.

Notice what the team did not do: knock Subdivision B, knock east of the interstate, or write up the cosmetic granule scuffing they saw on a couple of the newer roofs. The verification stack told them where the real damage was and where it wasn't, and the "wasn't" is what protects the margin.

How RoofPredict fits into the verification stack

Most of the workflow above is legwork: pulling reports, overlaying swaths, ranking roofs by age, walking frontages. The slow, error-prone part is the middle, Step 1 and Step 2, where you turn a storm into a ranked, route-able knock list. That is the gap RoofPredict is built to close.

RoofPredict is a per-address intelligence tool for restoration teams. For a given territory it estimates roof age as a range per address from aerial imagery, and it models storm physics per roof rather than per ZIP. Instead of "this county got a warning," you get a house-by-house view of which roofs sit inside the damaging part of a storm's track and are old enough to be vulnerable, ranked so your crews knock the doors the storm most likely wore out and the roofs that are simply aging out. In practice it does Step 2 (and a lot of Step 1) for you, turning a swath plus a subdivision into a prioritized route before anyone gets in a truck.

What it is honestly not: it is not a lead-buying service, and it is not proof of damage on any specific roof. The roof-age output is a range, not a date, and the storm modeling is odds, not evidence. A homeowner's roof still has to be inspected and documented (Step 3 and Step 4) before anything goes to a carrier, and RoofPredict never handles, files, or approves claims, that stays where it belongs: the homeowner owns the claim, the insurer decides coverage, and you document conditions and provide an estimate. What it does is make sure the rep-hours you spend land on the roofs most likely to verify as real, which is the entire point of everything above. It ranks the doors. Your inspection still proves the damage.

Use it as the front of the funnel: model the storm and the roof ages to build the route, then run your soft-metal walk-around and your test-square inspection to confirm. The technology narrows where you look; your hands and eyes on the roof do the verifying.

What pros get wrong (the expensive mistakes)

A verification process is only as good as the discipline behind it. The teams that bleed money usually do it in a handful of predictable ways.

Treating any hail report as a green light

A county hail report, or even a paid per-address hail verification, says hail probably fell. It does not say the roof is damaged. Teams that dispatch the whole crew the moment a report drops end up knocking the cosmetic-only fringes of the swath. Always pair the report with the swath width and the roof-age filter before routing.

Knocking the subdivision instead of the swath

The core is a narrow, often diagonal line. When you route to subdivision boundaries, half your knocks land on roofs outside the damaging core. Route to the swath. Let the line cut a neighborhood in half if that's what the radar shows.

Ignoring roof age inside the swath

Two roofs under the same core, one new and one 22 years old, are not the same opportunity. Crews that knock newest-to-oldest by whatever house comes first waste their best canvassing hours on roofs that won't show functional damage. Rank by age within the swath.

Confusing cosmetic for functional

The fastest way to lose an adjuster's trust, and a homeowner's, is to chalk up blisters, granule scuffs, mechanical marks, or foot-traffic damage as hail. Press-test every hit. If it isn't a soft, mat-fractured bruise in a random pattern, it isn't hail. Walking away from a roof with honest "no functional damage here" is a long-term asset, not a lost sale.

Getting the date of loss wrong

If the area took two storms in 18 months and you write up old damage under the wrong date, the claim gets denied for date-of-loss mismatch and the homeowner remembers your company name as the one that caused the headache. Date your swath precisely and confirm freshness on the roof.

Crossing the UPPA / claims line

Promising approval, promising "you'll pay nothing," advertising a "free roof," or negotiating the claim for the homeowner are not aggressive sales tactics, they are legal exposure in many states and a fast path to a complaint. Stay in the contractor lane: inspect, document, estimate. Let the homeowner file and own the claim and the insurer decide coverage.

Skipping documentation because the damage is "obvious"

Obvious damage on the roof today is a he-said-she-said in three weeks when the adjuster shows up. Photograph the chalked squares, the soft-metal collateral, the slope orientations, and the scale references every single time. Verification you can't reproduce later isn't verification.

A field checklist you can hand to a crew

Print this. It compresses the whole workflow into something a rep can actually run.

Before dispatch (office):

• Confirm a severe warning or storm report with hail at or above ~1 inch on a specific date.
• Pull SPC/LSR ground reports and note reported stone sizes and locations.
• Overlay a radar-derived (MESH/MRMS) swath; identify the core where estimated size is 1.25 in or larger.
• Draw the high-confidence corridor; mark where it weakens below 1 in (do not knock there).
• Rank roofs inside the corridor by age range (older first) and by soft-metal/exposure.
• Build routes along the swath line, not the subdivision boundary.
• Record the exact date of loss for every rep to reference.

At the curb (before knocking):

• Walk the frontage: gutters, downspouts, vents, turbines, AC fins, fascia for dents.
• Note which elevations (N/S/E/W) the dents concentrate on.
• Check for fresh granules at downspout outlets and splash blocks.
• Look for collateral: shredded leaves, dented cars, damaged screens.
• Scan the block for competitor signs, tarps, dumpsters (real + active swath).

On the roof (verify):

• Mark a 10x10 test square on each slope, prioritizing storm-facing slopes.
• Chalk every suspected hit; press-test for a soft, mat-fractured bruise.
• Confirm a random pattern (reject rows, traffic paths, nail-line clusters).
• Check freshness: stripped granules, fresh asphalt, not weathered-over.
• Score each slope separately; clean slopes are a normal, honest result.
• Photograph wide/mid/macro with scale; capture chalked squares and soft-metal collateral.
• Record shingle type, approximate age, slope orientations, and date of loss.

Always:

• Document conditions and provide an estimate, nothing more.
• No promises of approval, no "free roof," no handling the claim.
• Walk away honestly from cosmetic-only roofs.

Putting it together

Verifying hail damage before you knock is not one check, it is a funnel that gets narrower and more certain at each step. You start with a wide question (did a damaging event happen, and where is the real core), filter to the roofs that can actually be damaged (age, exposure, soft metal), confirm from the ground before you commit a rep (the soft-metal walk-around and collateral), and finally prove it on the roof with a disciplined, documented test-square inspection.

The payoff is more than a higher close rate. It is the thing that compounds over seasons: a crew that only knocks roofs the storm actually wore out, that walks away clean from the ones it didn't, and that documents every confirmed roof well enough to survive an adjuster. That reputation, the contractor whose inspections are right, is worth more than any single storm. Verification is how you build it, one correctly-chosen door at a time.

FAQ

What hail size actually causes functional roof damage?

As a general rule, functional damage to asphalt shingles tends to start around 1 inch (quarter-size) and becomes more consistent as stones reach 1.25 to 1.75 inches and larger. Below 1 inch you are usually seeing cosmetic granule loss, not mat fractures. The threshold shifts with shingle age, stone density, and wind, so an aged, brittle roof can show functional damage at sizes a brand-new roof would shrug off. Treat 1 inch as a soft floor, not a hard line.

How do I find out where hail actually fell without paying for a report?

Cross-reference free public sources: NOAA Storm Prediction Center storm reports and NWS Local Storm Reports give you ground observations of stone sizes, and NWS severe thunderstorm warnings bracket the timing and stated max size. For coverage rather than scattered dots, look at radar-derived hail products (MESH within the MRMS system). Each source has blind spots, so trust the picture only where they agree. Public dots tell you a stone fell at a point; the radar swath tells you the probable shape and width of the damaging core.

Is a paid hail report enough proof to file a claim?

No. A hail verification report, free or paid, is a modeled estimate that damaging hail probably fell at an address. It is corroborating context, not evidence of damage on a specific roof. An adjuster approves based on documented physical damage to the actual roof, not on a report that says a big stone likely fell. Use the report to decide where to inspect, then let the documented roof inspection carry the claim.

How can I tell functional hail damage from cosmetic damage?

Functional damage is a bruise or fracture of the shingle mat, the reinforcing layer, usually with granule loss at the impact point, and it feels soft or springy when you press it. Cosmetic damage is surface-only: granule scuffing, blistering, or marks that don't break the mat. Press-test every suspected hit. If there's no soft, mat-fractured bruise underneath, it's cosmetic and carriers generally won't pay for it. Calling cosmetic marks functional is the fastest way to lose credibility with adjusters.

Why should I check gutters and AC units before climbing the roof?

Soft metals like gutters, downspouts, vent caps, and AC condenser fins dent at smaller hail sizes than it takes to bruise a shingle, so they are reliable, ground-level confirmation that sizable stones actually fell. They also show direction: if dents concentrate on the south and west faces, you know wind drove the hail and which roof slopes to inspect closely. On their own they confirm hail occurred, not that the roof has functional damage, so treat them as corroboration that earns the climb.

What is the test-square method and why does it matter?

It's the standard way to quantify hail damage and the same method most adjusters use: mark a 10-foot by 10-foot (100 square foot) area on a representative slope and count the functional hail hits inside it. Carriers often look for a threshold number of functional hits in a test square before totaling a slope. Score each slope separately because wind-driven hail damages slopes unevenly, chalk each hit so it's photographable, and reject any pattern that follows rows, traffic paths, or nail lines, since that isn't hail.

How do I avoid knocking neighborhoods the storm barely touched?

Route to the swath, not the subdivision. The damaging core is usually a narrow, diagonal line, often a mile or two wide, while the reported hail area is far broader and mostly cosmetic at the edges. Draw the high-confidence corridor where radar and ground reports agree on roughly 1.25-inch-plus hail, and only knock inside it. Then rank by roof age within that corridor so your best canvassing hours land on the older, more vulnerable roofs first.

Does roof age really change whether hail damages a roof?

Yes, significantly. As shingles age they lose granules, the asphalt oxidizes and gets brittle, and the mat loses flexibility, so an older roof bruises at a lower hail size than a new one. Under the same hail core, a 20-plus-year-old roof is far more likely to show functional, approvable damage than a roof installed a couple years ago. That's why ranking roofs by age inside a confirmed swath dramatically improves how many of your knocks turn into verified damage.

How can I estimate roof age across a whole neighborhood quickly?

Pulling permits address by address is accurate but slow. Aerial-imagery roof-age tools estimate age as a range per address by analyzing imagery over time, which lets you rank a street fast. Tools like RoofPredict combine that age range with per-roof storm modeling so you can prioritize the roofs that are both inside the damaging swath and old enough to be vulnerable. Remember it's a range for prioritization, not a birth certificate, so it tells you which doors to hit first, not what to write on an inspection.

What claims-related lines should contractors never cross during inspections?

Stay in the contractor lane: inspect, document conditions, and provide a repair estimate. Don't promise the claim will be approved, don't promise the homeowner pays nothing, don't advertise a 'free roof,' don't present a storm or hail report as proof of damage, and don't negotiate or handle the claim on the homeowner's behalf. In many states those moves cross into public adjusting or unfair claims practices and create real legal exposure. The homeowner files and owns the claim; the insurer decides coverage.