Which Roofs Likely Qualify for a Storm Claim Before You Inspect

Every storm-restoration crew has had the same bad week. A hailstorm rolls through, the phone lights up a little, and you send three trucks out to canvass a subdivision because the radar lit it up red. Two days and forty knocks later, you have eleven inspections booked, eight roofs that are six years old with nothing on them, two that are genuinely beat up, and one homeowner who is now mad at you because you got their hopes up for nothing. You spent the gas, you spent the payroll, you burned a rep's morale, and the math on the week is ugly.

The contractors who win storm work are not the ones who knock the most doors. They are the ones who knock the right doors first, while the roofs are fresh and the homeowner is still thinking about the storm. The skill underneath that is prediction: looking at a street and forming an honest, defensible read on which roofs are likely to have real, documentable storm damage worth a homeowner filing on, before anyone gets on a ladder. You will never be perfectly right. You do not need to be. You need to be right enough, often enough, that your inspection-to-approval ratio stops bleeding you.

That is what we are going to work through here: how to predict which roofs likely qualify for a storm claim before you inspect, what actually drives that prediction (it is mostly two things, and one of them is not the radar), how to rank a list so your best crew hours go to the best roofs, and then how to document the ones that hold up so the file you hand the homeowner is clean. We will stay strictly on the side a roofer is allowed to operate on: you inspect, you document, you write an accurate estimate of the repair. The homeowner files. The carrier decides. We will be very clear about that line because crossing it is how good contractors lose their license or end up in front of their state's attorney general.

A word on the word qualify. A roof does not "qualify" for a claim in any sense you control. Coverage is a determination the insurer makes against a specific policy, and you are not a party to that policy. When a roofer says a roof "likely qualifies," what they actually mean — and the only thing they should mean — is: this roof probably took enough real, storm-caused damage that it is worth inspecting and documenting, and if the damage is what I expect, the homeowner has a credible basis to file. That is a prediction about physical condition and storm exposure. It is not a promise about an outcome. Hold that distinction in your head for the rest of this, because it is the difference between a defensible business and a problem.

What "likely qualifies" actually means in the field

Strip away the sales talk and a roof that is worth your inspection time has three things going for it at once. None of them is sufficient alone. Together they are a strong signal.

One: it was exposed to a storm capable of causing functional damage. Not "a storm passed nearby." A storm whose hail was large enough or whose wind was fast enough to functionally damage the specific roofing material on that house. Pea-sized hail does not bruise a healthy architectural shingle. One-inch hail might mark soft metals and start to matter on an aged roof. Inch-and-a-half and up is where you reliably see mat fracturing on asphalt. Wind works on a different curve — it lifts, creases, and tears tabs, and it does the most damage at edges, rakes, ridges, and anywhere the seal strip was already weak.

Two: the roof was in a condition to be damaged by that storm. This is the part newer reps miss completely. A three-year-old roof with a fully cured, strong seal strip and pliable shingles will shrug off a storm that destroys the eighteen-year-old roof across the street. Asphalt gets brittle as it ages and loses volatiles; the mat embrittles, granules loosen, and the impact energy that a young shingle absorbs elastically instead fractures the aged one. Age is more than a sales filter for "can this homeowner afford to care." Age changes the physics of whether the storm did anything.

Three: the damage is functional, not cosmetic, and it is attributable to this storm. Carriers and their adjusters draw a hard line between damage that affects the roof's ability to keep water out and shorten its service life (functional) versus damage that only affects appearance (cosmetic), and an even harder line on whether the damage came from the dated storm event versus years of wear, foot traffic, manufacturing defects, or a prior storm. You cannot see attribution from the street. But you can predict the conditions that make functional, attributable damage likely, and that prediction is most of the value.

So "likely qualifies" is the intersection: real storm energy × a roof old/worn enough to be hurt by it × a plausible path to functional, this-storm-attributable damage. When you are ranking a street, you are estimating that intersection house by house. The whole game is getting good at the estimate.

The two signals that do the heavy lifting: storm physics and roof age

If you only had two pieces of information about a house before you inspected it, you would want these two: what the storm actually did to that roof, and how old the roof is. Everything else is refinement.

Why the hail map is not the storm

Here is the mistake that costs crews entire days. A contractor pulls up a hail swath map — the colored polygon showing where hail of a certain size was reported or estimated — sees their target subdivision sitting inside the magenta blob, and treats every house in that blob as equally hit. Then they are baffled when half the inspections come up clean.

A swath map shows you where it hailed. It does not show you what happened on a given roof. Two houses three hundred feet apart can have wildly different outcomes from the same storm because the things that determine roof-level damage are local: the angle and direction the hail was driven (wind-driven hail hits the windward slopes hard and may barely touch the leeward ones), the slope and orientation of each roof plane, the height and exposure of the structure, tree cover, and the size distribution of the stones that actually fell on that footprint, which can vary block to block inside a single storm. A reported "1.75 inch" hail event is a sample of the largest stones someone measured or a radar estimate of the peak — it is not a guarantee that every roof under the polygon took inch-and-three-quarter impacts on its weak slopes.

Wind is even more directional. A straight-line wind event or the leading edge of a supercell loads one side of the neighborhood and one orientation of slope far harder than the rest. The houses whose front or back planes faced into the gust took the lifting and creasing; the ones turned ninety degrees often have nothing.

The practical upshot: you do not want to know "did hail fall here." You want to know, as close as you can get, what the storm did to this specific roof — what size impact, from what direction, on which planes. That is a per-roof model of the storm, and it is a different and far more useful thing than a swath polygon. When you can estimate impact at the roof level, you stop treating the whole subdivision as one undifferentiated blob and you start ranking houses inside it.

Why roof age is the multiplier

Now layer age on top. The same storm energy produces completely different results depending on the roof's condition, and age is the best single proxy for condition you can get without standing on the roof.

This is why a smart canvasser skips the new roofs. It is not snobbery about who can afford a job. It is physics: the new roof probably did not get hurt, so there is probably nothing to document, so the inspection is a waste of a slot you could have given to the seventeen-year-old roof two doors down that the same storm actually worked over.

The catch is that you usually cannot tell a roof's true age from the curb, and the public data lies to you in a specific, predictable way. The county's "year built" is the house's age, not the roof's. A 1994 house may be on its third roof. Zillow and most public records carry year-built, not re-roof date, and re-roofs are nearly invisible in those datasets unless a permit was pulled and digitized, which often it was not. So the rep who sorts a list by year-built is half-blind: they will knock houses with brand-new roofs because the house is old, and skip houses with original aging roofs because the house looks newer or the data is missing.

What you actually want is an estimated roof age expressed as a range — "this roof reads as roughly 16 to 20 years old" — derived from the roof's visible condition and history, not the house's birth certificate. A range is the honest unit here. Nobody can hand you an exact install date from imagery; anyone who claims to is overselling. A tight range is enough to rank.

Reading roof age off imagery (and where the read gets hard)

If you are estimating age by eye from aerial and oblique imagery, here are the cues a trained reader uses, roughly in order of reliability:

• Granule loss and surface mottling. As asphalt ages it sheds granules, exposing darker asphalt in patches. A roof that reads blotchy, with dark streaks and bald-looking areas around the field and especially along the drainage paths below valleys and penetrations, is reading old. A uniform, saturated color reads younger.
• Color and sheen uniformity. New shingles are color-consistent and have a faint sheen. Aged roofs go flat, dull, and uneven as the surface weathers and algae streaking (the dark vertical stains) sets in. Heavy algae streaking generally takes years to develop and pushes your estimate older.
• Visible patching and mismatched planes. A single slope that is a different color or texture from the rest of the roof is a partial re-roof or a prior repair — important, because it means a section of the roof is a different age than the surrounding field, and it complicates both your age estimate and any later attribution.
• Layered or thick edges. On obliques, a roof that looks unusually thick at the eaves may be a layover (a second layer shingled over the first). Layovers age differently and matter for the repair scope and for code.
• Style and product era. Three-tab versus laminate/architectural, and the specific product profile, can roughly bracket an era. A field of old three-tab on a house in a market that went all-architectural fifteen years ago reads older.
• Surrounding context. Decking sag, deteriorated flashing, rusted vents, and worn pipe-boot collars all corroborate an older roof when you can see them.

Where the read gets genuinely hard: a recent re-roof on an old house (looks new, public data says old), a recently cleaned or treated roof that looks younger than it is, premium long-life shingles that weather slowly, heavy shade that suppresses algae streaking, and imagery that is simply old or low-resolution. This is exactly why the honest output is a range with a confidence sense, not a single number — and why a roof you flag as "16–20, but it might be a recent re-roof" still earns an inspection slot, just with that caveat in the rep's pocket.

Building the prediction: a repeatable pre-inspection workflow

Here is the workflow a disciplined storm crew runs before sending a single truck. It turns a vague "the radar lit up" into a ranked target list. Run it in order.

Step 1 — Define the real storm footprint, not the headline. Pull the actual event data for the date in question: the storm reports and any hail/wind estimates for the area, and ideally a directional read on how the storm moved and where the strongest cells tracked. You are looking for the corridor where impacts were plausibly large enough to matter (roughly 1" hail and up for aged asphalt, higher for newer; damaging wind generally in the 58+ mph reported range, with the caveat that gusts at a roof can exceed the nearest official reading). Mark the corridor. Everything outside it is a much lower-probability bet and should sit at the bottom of the list.

Step 2 — Inside the corridor, model storm energy at the roof level where you can. This is where a swath polygon fails you and a per-roof storm model earns its keep. The question for each house is not "is it in the blob" but "what size impact, from what direction, likely hit which of its planes." If you have tooling that models hail trajectory and wind loading per roof, this is the step it pays off. If you are doing it by hand, at least reason about orientation: which slopes faced the incoming weather, which structures were exposed versus sheltered.

Step 3 — Estimate roof age as a range for each address. Not house age — roof age. Use whatever gives you a condition-based estimate: aerial and oblique imagery read for granule loss, patching, color uniformity, prior repairs; permit history where it exists; and any roof-age data product that returns an estimated range. Tag every address with its range bucket (0–5, 6–10, 11–15, 16–20+).

Step 4 — Score the intersection. Now combine. The highest-priority addresses are the ones where strong storm energy meets an aged roof. A simple, honest scoring frame that field crews actually use:

The top-right cell is where your best rep goes first thing in the morning. The bottom-left is where you do not waste a slot. The "age-only knock later" cells are your non-storm pipeline — old roofs worth a replacement conversation regardless of this storm, worked on a slower cadence (more on that below).

Step 5 — Sequence the route, not only the list. A ranked list still loses time if your rep zigzags across town. Cluster the high-priority addresses geographically so a rep can work a dense block of good roofs without windshield time between them. Density of good targets per block is what makes a canvassing day profitable, not raw door count.

Step 6 — Set the rep's expectation per door. Hand the rep the why for each address: "This one reads 17–21 years and the storm drove inch-plus hail onto the front slopes." A rep who knows why a door is on the list knocks with confidence and qualifies the homeowner faster, and a green rep who knocks the right doors closes, makes money, and stays — rep churn is a storm company's quiet killer, and feeding new hires good doors is half the fix.

A worked example

Say a storm tracks west-to-east across the north half of a suburb on a Tuesday afternoon, with hail estimated at 1.5" in the core and 0.75" on the southern fringe, driven by a strong northwest wind. You have a list of 240 homes in the affected ZIPs.

• Strip out the southern-fringe homes first — 0.75" hail rarely does functional damage to anything but the most decrepit roofs. That removes ~70 addresses from the priority tier (they go to "age-only later").
• Of the remaining 170 in the core corridor, your roof-age data flags 58 as 16+ years and another 41 as 11–15. The other 71 are 10 years or newer.
• Your per-roof storm read says the homes whose north and west planes were exposed took the worst of the wind-driven hail.
• Your top tier is now: the 58 aged roofs in the core whose exposed planes faced the weather — call it ~35 addresses — clustered into three tight blocks.

You just turned 240 cold addresses into ~35 high-probability inspections your best rep can work in a day and a half, with a second tier of ~60 behind them. That is the entire point: the prediction is what lets you spend your scarce, expensive crew hours on the roofs most likely to have something real on them.

The math on why ranking pays

It is worth putting numbers on this, because the value of prediction is easy to wave at and hard to feel until you see it as a ratio. The scarce resource is not doors — it is productive inspection hours. A rep who can run, say, eight quality roof inspections in a day is the constraint. The question is what fraction of those eight slots land on roofs with something real on them.

Compare two crews working the same 240-address storm.

Crew A — radar-and-instinct. They treat the swath as one blob and knock it in driving order. Their inspection slots land roughly in proportion to the neighborhood mix: a lot of newer roofs, a few aged ones. Say 1 in 5 of the roofs they get onto has documentable damage. Out of 40 inspections over a week, ~8 turn into documented, file-worthy roofs. The other 32 inspections were real labor — ladder up, photos, the homeowner conversation, the write-up — spent on roofs with nothing.

Crew B — ranked. They inspect the top tier first: aged roofs whose exposed planes faced the storm. On those roofs, the hit rate is far higher — say 1 in 2 has documentable damage, because they pre-selected for the exact conditions that produce it. Out of the same 40 inspections, ~20 turn into documented roofs.

Same trucks, same payroll, same week. Crew B walks away with roughly two and a half times the documented roofs, and — just as important — fewer homeowners disappointed by an inspection that found nothing, fewer reps demoralized by clean roof after clean roof, and a cleaner reputation with the adjusters who keep seeing well-targeted, well-documented files from them. The exact ratios are yours to measure; the direction is not in doubt. Prediction concentrates your best hours on your best roofs, and storm work lives or dies on that concentration.

There is a second-order effect that compounds. The single biggest controllable cost in a storm operation is rep churn. A green canvasser who spends a week knocking doors that lead to clean roofs makes no money, gets discouraged, and quits — and you eat the recruiting and training cost again. The same green rep, handed a ranked list of roofs that actually have damage, books inspections, sees jobs close, makes money, and stays. Feeding new hires good doors is one of the highest-ROI things ranking does, and it never shows up on a single inspection's P&L.

Where RoofPredict fits in this prediction

Everything in the workflow above is doable by hand if you have the time, a good read on imagery, and patience to cross-reference storm data address by address. The problem is that the storm window is short — homeowners are most receptive in the days right after, and other crews are moving — and doing this manually across hundreds of addresses is exactly the kind of work that does not happen when the phones are ringing.

This is the gap RoofPredict is built to close. It does the two heavy-lifting signals for you, at the address level, across your whole area: it estimates roof age as a range per house from aerial imagery (the actual roof, not the house's year-built), and it models the storm physics on each roof — hail and wind scored house by house, not a swath polygon draped over the neighborhood. Then it ranks the roofs so the ones where real storm energy met an aged roof rise to the top of your list, and it can enrich a list you already own — your CRM, your old estimates, a mailing list — with those same roof-age and storm signals so you are working your own book, not renting someone else's.

What it is honest about: roof age comes back as a range, not an install date, because no one can read an exact date off imagery. The storm model gives you odds and exposure — which roofs the storm most likely wore out — not proof that a specific shingle is fractured. It does not tell you the damage is functional, it does not tell you it is attributable to one specific storm, and it certainly does not tell you anything about coverage. It tells you where to point the ladder first. You and your crew still do the inspection, still make the functional-versus-cosmetic call on the roof, and still write the estimate. The tool moves the inspection from a guess to a ranked bet, and it keeps you off the new roofs that waste your day. That is the limit of what any pre-inspection signal can honestly claim, and it is a lot.

A fair way to think about it: a hail map sells you weather, and a lead site rents you a homeowner five of your competitors are also calling. Ranking your own streets and your own customer list by roof age and storm exposure is work you own — repeatable, storm or not.

The line you do not cross: predict and document, never adjust

We need to be blunt here because this is where contractors get into real legal trouble, and "everybody does it" is not a defense when your state's department of insurance or attorney general comes calling.

A roofing contractor is allowed to inspect a roof, document its condition, identify and photograph damage, and prepare an accurate estimate to repair the work they would perform. You can state facts about your own scope to anyone, including a carrier's representative, when you are present as the contractor doing the repair. That is your lane and it is a wide one.

What a roofer may not do — without a public adjuster's license, which is a different profession with its own legal duties — is, for a fee, negotiate or adjust the homeowner's claim, interpret the policy or what it covers, tell the homeowner what their payout or deductible will be, promise that a claim will be approved, advertise that the roof will be "free," or otherwise represent the homeowner against their insurer. Courts have taken this seriously: in one Texas case the court held that even a roofer advertising themselves as an insurance claims "specialist" and offering to handle the claim process crossed into unlicensed public adjusting. The specifics vary by state, but the principle is national: adjusting the claim is a licensed activity, and the contractor's estimate is not the same thing as adjusting.

So translate every "qualify" instinct into the safe frame:

• You do not tell a homeowner "your roof qualifies and your claim will be approved." You tell them "based on the age and the storm, your roof is worth a thorough inspection, and if I find damage I will document it and write an honest estimate of the repair."
• You do not say "we'll get your deductible covered" or anything about the deductible at all in a promising way. The deductible is the homeowner's contractual obligation; offering to absorb or erase it is illegal in many states and is fraud-adjacent everywhere.
• You do not interpret coverage. "Whether this is covered is between you and your carrier" is the true and safe answer, every time.
• You do document thoroughly, write an accurate estimate aligned to standard estimating practice, and hand it to the homeowner. The homeowner files the claim. The insurer's adjuster inspects and the insurer decides coverage. You are the contractor who will do the repair, present to substantiate your scope.

Prediction lives entirely on the safe side. Estimating which roofs likely have documentable storm damage is reading physical reality — age and storm energy — to decide where to inspect. It says nothing about anyone's policy. Keep it there.

From prediction to proof: documenting the roofs that hold up

The prediction gets you onto the right roof. Now you have to find out if the roof actually has what you expected, and if it does, document it so cleanly that the file stands on its own. A prediction you cannot back up with evidence on the roof is just a hopeful knock. Here is the inspection-and-documentation discipline that turns a likely roof into a documented one.

Before you climb: the ground and elevation walk

Functional storm damage almost never starts on the shingles, and the soft metals around the house are your fastest read on whether a storm had the energy to matter.

1. Walk the soft metals first. Gutters, downspouts, gutter aprons, fascia wraps, valley metal, vents, flashing, the AC condenser fins, mailbox, and any metal on the elevations. Hail leaves dents in soft aluminum that are hard to argue with and that establish the direction and energy of the storm. If the north-facing gutter is peppered and the south one is clean, you have just confirmed a directional hail event — which both predicts where the roof damage will concentrate and corroborates your storm read.
2. Photograph collateral with scale. Every dent shot wants a reference for size — a coin, a chalk circle, a tape. Date and address the photos. This is the corroboration that ties any roof damage you find to a real impact event.
3. Read window screens, garage doors, and downspouts for impact marks and the splatter/oxidation marks that indicate where stones struck. A garage door full of dimples on one side is a directional storm signature.

If you walk the elevations and find zero soft-metal evidence on a roof you predicted would be hit, that is real information. Either the storm was weaker on this footprint than your model suggested, or the damage is not there. Do not manufacture a story to fit your prediction. The discipline of being willing to walk away from a clean roof is what keeps your approval ratio and your reputation intact.

On the roof: test squares and the functional standard

When you do climb, your job is to determine whether the roof took functional damage and to document it the way a careful inspector would.

• Lay out test squares. The common practice is a 10' x 10' square on each slope (mark the corners with chalk). Within each square, find and circle the hits. Document the hit count per square per slope, because density and distribution by slope are exactly what an adjuster evaluates and what your estimate has to reflect.
• Press and read each hit. A functional hail hit on asphalt typically shows a bruise — a soft spot where the mat is fractured and granules are displaced, often with the granules knocked into the mat. Run your hand over it; a fractured mat feels different from a surface scuff. Distinguish that from blistering, mechanical scuffing, manufacturing inconsistency, and ordinary granule loss, none of which is storm damage.
• Document directionality. Note which slopes carry the hits and how they correlate with your storm read and the soft-metal evidence. A roof where the windward slopes are hit and the soft metals on the same side are dented tells one coherent story. Coherence is credibility.
• For wind: look for creased tabs, torn or missing shingles, unsealed/lifted tabs especially along rakes, ridges, and the field, and any exposed fasteners or substrate. A crease is a fold line where the shingle was lifted and bent back; it is a functional failure because the mat is broken at the fold.
• Photograph everything, with a system. Overall slope shots, the chalked test square, each circled hit close-up with scale, the soft-metal collateral, the directional pattern. Consistent, dated, address-stamped photos are the file.

The functional-versus-cosmetic and attribution traps

Two judgment calls separate a clean file from a weak one, and getting them honest is what protects your name over a season of claims.

Functional vs. cosmetic. Functional damage compromises the roof's ability to shed water or measurably shortens its service life — fractured mat, displaced granules exposing the asphalt to UV, creased or torn shingles. Cosmetic damage only affects appearance. Adjusters live on this distinction and some policies specifically exclude cosmetic damage. If what you are looking at is genuinely cosmetic, say so. Writing up cosmetic marks as functional is how you lose credibility with every adjuster in your market and how a homeowner ends up filing on nothing.

Attribution. The damage has to be plausibly from the storm in question, not last year's storm, not foot traffic, not age-related deterioration, not a defect. Your storm date, your soft-metal directional evidence, and the freshness of the hits (oxidation state of exposed metal, granule displacement that looks recent) all build the attribution case. An old, oxidized, dark bruise reads as an older event; a fresh fracture with bright exposed mat reads as recent. You are documenting the physical facts that support attribution; you are not declaring a legal conclusion.

What the documentation package should contain

When you finish, the homeowner should walk away with a package that stands on its own. A clean one includes:

• A dated, addressed inspection record with the storm date and event referenced.
• Soft-metal and collateral photos showing energy and direction, with scale.
• Test-square photos per slope with hit counts and circled, close-up hits with scale.
• Slope diagram showing damage distribution and orientation.
• An itemized, accurate estimate to repair your scope, aligned to standard estimating practice (Xactimate-style line items, correct quantities and measurements, code-required items like ice-and-water, drip edge, and ridge per the applicable code where they apply).
• A plain-language summary the homeowner can read.

That package is what the homeowner takes to their carrier. You hand it over. They file. The adjuster inspects. The insurer decides. Your job was to be right about the roof and thorough about the evidence — and a clean package earns you the repair when coverage is granted, on the merits.

Edge cases that break the simple model

The storm-energy × roof-age frame is the right default, but a season of inspections will throw cases at you that the simple model handles badly. Knowing them in advance keeps you from both over-knocking and missing real work.

Impact-resistant (Class 4) shingles. Some markets, especially hail-prone ones, have a meaningful share of impact-rated roofs, sometimes installed for an insurance premium discount. These can be ten years old and take a serious storm with little functional damage, because that is the entire point of the product. If you canvass a subdivision built to a hail-resistant standard the same way you would a standard-shingle neighborhood, your hit rate craters. Know your market's building era and product mix.

Tile, metal, slate, and wood. The asphalt age curve does not transfer. Hail damage on tile is about cracking and is highly tile-and-impact-angle dependent; metal shows denting that may be cosmetic or functional depending on the panel and the standard; slate and wood have their own failure modes and service lives measured in decades. The prediction logic — storm energy meeting a vulnerable surface — still holds, but the age thresholds and damage signatures are different. Do not run an asphalt playbook on a tile roof.

Partial re-roofs and mixed-age roofs. A house where one slope was replaced after a prior storm and the rest is original is now two different roofs for prediction and for attribution. The old slopes are vulnerable; the new slope probably is not. And if you find damage, you have to be careful which storm it is attributable to. Flag these for a closer look rather than a confident assumption.

The recently sold house. A home that sold in the last year or two often got a new roof or a roof certification at sale, or conversely a buyer inherited a roof at the end of its life that a seller declined to replace. Sale events scramble the age signal in both directions; treat a recent sale as a flag to verify, not a conclusion.

Sheltered and shaded roofs. Heavy tree canopy both shields a roof from some hail and suppresses the algae streaking you use to read age, so a shaded roof can read younger and be less damaged than an exposed neighbor of the same vintage. Conversely, those same trees drop limbs in wind events, creating impact damage that is real but mechanical rather than hail — document it for what it is.

The storm that was worse than the report says. Official hail and wind measurements are sparse samples. The nearest report might say 1 inch while a cell dropped 1.5 inch stones two streets over with nobody to measure them. Soft-metal evidence on the ground is your correction for this: if the gutters are peppered harder than the reported hail size suggests, believe the metal. The roof saw what it saw, not what the nearest station recorded.

The roof that is just old, no storm. Plenty of roofs are at or past service life with no qualifying storm behind them. These are real replacement jobs — retail or financed, on the merits of age and condition — and they belong in your pipeline. They do not belong in a storm-claim conversation, and pretending an aging roof has storm damage it does not have is how you end up with a denied claim and an angry homeowner. Keep the two pipelines distinct.

What pros get wrong

A few failure modes show up over and over, and most of them come from skipping the prediction or fudging the documentation.

Treating the swath map as gospel. Covered above, but it is the number-one time-waster. Inside the blob, roofs vary enormously. Rank within the corridor; do not knock it flat.

Sorting the list by house age instead of roof age. Year-built is not roof-age. Re-roofs are invisible in most public data. A list sorted by house age sends you to new roofs and skips aging ones. Sort by estimated roof age, ideally as a range, or you are flying half-blind.

Chasing every storm out of FOMO. A 0.75" hail event on a market full of newer roofs is mostly not a job. You do not have to canvass it just because it happened. Spend the day instead on the aged roofs from a prior real storm, or on your age-only pipeline. Discipline about which storms are worth a full canvass is a competitive advantage.

Over-promising at the door. "Your claim's a slam dunk, we'll get this approved, deductible's no problem" — every clause of that is wrong, and the deductible clause may be illegal. It also sets the homeowner up to be furious at you when the carrier says no. Predict and document; never promise an outcome.

Documenting to fit the prediction. Confirmation bias is brutal in this work. You predicted the roof was hit, you climbed up wanting it to be hit, and now you are tempted to read cosmetic marks as functional. Discipline yourself to document what is there. A clean roof you correctly walk away from protects your name; a marginal roof you oversell costs you with adjusters and homeowners for years.

Ignoring the non-storm pipeline. The roofs that are 18+ years old are jobs whether or not a storm hit them. If you only ever work fresh storms, you starve between events and you live and die on weather. The same age data that ranks your storm inspections gives you a steady replacement pipeline in the quiet months. Work both.

Letting the storm window close. Homeowner receptivity decays fast after a storm, and so does the freshness of the evidence (metals oxidize, the memory fades, the next crew shows up). The whole reason to rank before you inspect is speed: get to the best roofs while they are best. A slow manual sort that takes you three days has already cost you the window.

Turning a single storm into a season: the data you keep

The last piece is operational. Every storm you work generates a list, and most contractors throw it away. Don't.

The addresses you inspected and documented — including the ones where the homeowner did not file this time — are a CRM asset. The 14-year-old roof that took a marginal storm and came up just short of worth-filing is a 16-year-old roof after the next storm, and you already have its data, its history, and a relationship. Re-rank your own book after every event by layering the new storm onto the roof ages you already know. That is the difference between a company that restarts cold after every storm and one that compounds.

This is also the cleanest way to grow without buying anyone's leads. Your old estimates and past customers are money already in your book — roofs you have data on, homeowners who know your name. Enriching that list with current roof-age and storm signals tells you which of your own past contacts are now due. There is no shared-lead competition on a homeowner you already know.

A simple cadence to run

1. After every significant storm: define the real corridor, rank the affected addresses by storm-energy × roof-age, route the top tier, inspect, document. Keep every inspection record.
2. Monthly, in any market: re-rank your CRM and old-estimate list by current estimated roof age; the roofs that have aged into the 16+ bucket are your steady, no-storm-needed pipeline.
3. After each new storm: re-score your existing book against the new event. Roofs that were borderline before may now be worth another look.
4. Always: keep the documentation discipline identical whether the roof came from a storm canvass or your aging-roof pipeline. One standard, one clean file, every time.

Run that cadence and the question stops being "which roofs likely qualify" asked in a panic the morning after a storm, and becomes a standing, ranked view of which roofs in your area and your book are most likely worth your ladder — storm or not. You point your crew at the best roofs, you document the ones that hold up, you hand the homeowner a clean package, and you stay firmly on the side of the line where a roofer belongs: inspect, document, estimate. The homeowner files. The insurer decides. You did your job right, and your job was to be right about the roof.

FAQ

Can a roofer tell which roofs qualify for a storm claim before inspecting?

A roofer can't determine that a roof 'qualifies' — coverage is the insurer's call on a specific policy, and the contractor isn't a party to it. What a roofer can do well is predict which roofs likely took real, documentable storm damage worth inspecting, by combining two signals: how much storm energy actually reached that specific roof, and how old (and therefore how vulnerable) the roof is. That prediction tells you where to point the ladder first. The inspection still has to confirm functional damage, and the homeowner still files while the insurer decides.

Why isn't a hail swath map enough to know which roofs were damaged?

A swath map shows where hail of a given size fell, not what happened on any individual roof. Two houses a few hundred feet apart can have completely different outcomes from the same storm because hail direction, roof slope and orientation, exposure, tree cover, and the local size distribution of stones all vary block to block. Wind is even more directional, loading one side of a neighborhood far harder than the rest. To rank houses inside the storm, you want a per-roof read of what the storm did, not a polygon draped over the whole area.

How does roof age change whether a storm causes damage?

Asphalt shingles embrittle with age as they lose volatiles and granules, so the same impact that a 3-year-old roof absorbs elastically can fracture the mat of an 18-year-old roof. Age isn't just a filter for who can afford a job — it changes the physics of whether the storm did anything. A marginal storm that does nothing to newer roofs can produce real functional damage on roofs in the 16+ year range, which is why aged roofs in a storm corridor are the highest-priority inspections.

Why can't I just sort my list by the year the house was built?

Year-built is the house's age, not the roof's age. A 1994 home may be on its third roof, and re-roofs are nearly invisible in public records unless a permit was pulled and digitized. Sorting by year-built sends crews to homes with brand-new roofs (old house, new roof) and skips homes with aging original roofs (newer-looking house, missing data). You want an estimated roof age — ideally expressed as a range read from the roof's condition — not the house's birth date.

What does it mean that a roof's storm damage is 'functional' versus 'cosmetic'?

Functional damage compromises the roof's ability to shed water or measurably shortens its service life — a fractured shingle mat, displaced granules exposing asphalt to UV, creased or torn shingles. Cosmetic damage only affects appearance. Adjusters draw a hard line here, and some policies exclude cosmetic damage outright. Honest documentation calls cosmetic marks cosmetic; writing them up as functional erodes your credibility with adjusters and sets homeowners up to file on nothing.

How do I document storm damage so the file holds up?

Build a coherent, dated, address-stamped package: walk the soft metals first (gutters, vents, AC fins, flashing) and photograph dents with scale to establish storm energy and direction; lay 10x10 test squares per slope, circle and count the hits, and shoot close-ups with scale; press each hit to confirm a fractured mat versus a surface scuff; note which slopes are hit and confirm the pattern matches your storm read; and write an accurate, itemized estimate of the repair aligned to standard estimating practice. Hand the package to the homeowner — they file it with their carrier.

Is it legal for a roofer to help with a homeowner's storm claim?

A roofer may inspect, document damage, and prepare an accurate estimate to repair their own scope, and state facts about that scope. A roofer may not, without a public adjuster's license, negotiate or adjust the claim, interpret policy or coverage, promise approval or a payout, say anything that erases the deductible, advertise a 'free roof,' or represent the homeowner against the insurer — courts have treated even advertising as a claims 'specialist' as unlicensed public adjusting. Stay on the document-and-estimate side; the homeowner files and the insurer decides.

How does RoofPredict help decide which roofs to inspect first?

It supplies the two heavy-lifting signals at the address level across your area: an estimated roof age as a range per house from aerial imagery (the actual roof, not the house's year-built), and a storm model scored house by house rather than a swath polygon. It ranks roofs so the ones where strong storm energy met an aged roof rise to the top, and it can enrich your own CRM or mailing list with the same signals. Honest limits: age is a range, not an install date; the storm model gives odds and exposure, not proof of functional damage; and it says nothing about coverage. It tells you where to point the ladder first — your crew still inspects, judges, and estimates.

Should I canvass every storm that hits my market?

No. A 0.75-inch hail event across a market of newer roofs is mostly not a job — that hail rarely causes functional damage to anything but the most deteriorated roofs. Chasing every storm out of fear of missing out burns crew hours that would pay better on aged roofs from a prior real storm or on your steady non-storm replacement pipeline. Discipline about which storms justify a full canvass — and which roofs inside a real storm corridor are worth a slot — is a competitive advantage.

What should I tell a homeowner at the door about their claim?

Tell them the true, safe thing: based on the roof's age and the storm, it's worth a thorough inspection, and if you find damage you'll document it and write an honest estimate of the repair. Don't promise approval, don't predict the payout, don't say anything about covering or erasing the deductible, and don't interpret their coverage. 'Whether this is covered is between you and your carrier' is the correct answer every time. Over-promising at the door sets the homeowner up to be angry when the carrier says no, and some of those promises are illegal.