Skip to main content

How To Use Roof Age And Hail History To Rank Door-Knocking Routes

RoofPredict Team, Roofing Data & Growth Research··32 min readCanvassing & Territory
On this page

Rank door-knocking routes by combining two signals the rest of your competition ignores: how old each roof actually is, and whether real hail of a damaging size has hit that specific block. A storm-area polygon tells you where it rained. Roof age plus verified hail history tells you which doors are worth a respectful inspection offer and which ones are a waste of a canvasser's afternoon. Score each home on weather context, age confidence, prior relationship, route density, and safe access, then knock the high-scoring streets first.

The short version: pull the hail event for the date and area from NOAA's Storm Events Database, note the reported hail size in inches, layer in roof-age confidence from permit records or your own CRM, and rank streets by a simple point system. A 17-year-old asphalt roof on a block that took 1.5-inch hail is a far stronger route than a 4-year-old roof under a storm that dropped pea-sized hail two counties over. Knock the first one. Skip or deprioritize the second.

What this is not: it is not a way to decide that any specific roof is damaged, and it is not a script for promising insurance money. Age and hail history rank outreach priority. They do not prove damage, certify remaining roof life, or determine coverage. The insurer decides coverage after an adjuster looks at the actual roof. A canvasser's job is to earn a safe, documented inspection, not to litigate a claim at the door. Crews that blur that line get homeowners burned and get companies fined.

Here's the operating model a 15-year veteran would actually run, including a scoring scorecard you can copy, the weather and age data sources that hold up, the field scripts that work without overpromising, and the legal boundaries that keep you out of a public-adjusting lawsuit.

Why a storm map alone produces bad routes

The most common mistake in storm response is treating a hail swath as a route list. A canvassing manager screenshots a radar-derived hail map, draws a polygon around the red, and tells the crew to knock everything inside it. That feels like speed. It is actually noise.

Radar-derived hail maps estimate hail in the atmosphere, not on the ground. Maximum estimated size of hail (MESH) and similar products are useful for triage, but they overstate and understate ground-truth all the time. Hail shafts are narrow and patchy. One street can get hammered while the next street over gets nothing. So a polygon route sends reps to hundreds of doors where nothing damaging fell, and the homeowners there know it. You train an entire neighborhood to distrust your knock.

The second problem is roof age. Inside any storm polygon you have brand-new roofs, mid-life roofs, and roofs that were already failing before the storm. A 3-year-old architectural shingle roof that took 1-inch hail probably shrugged it off. A 22-year-old three-tab roof that took the same hail may have lost protective granules it could not spare. Same storm, completely different conversation. If you knock them with the same script, you sound like everyone else and you waste your best reps on doors that go nowhere.

The fix is to stop ranking by geography and start ranking by per-home signal. The two strongest signals you can get before anyone climbs a ladder are verified hail history (was there damaging-size hail on this block, on a known date) and roof age confidence (how old is this roof, and how sure are you). Everything in this playbook builds on layering those two together, then filtering for relationship, density, safety, and the local rules on whether you can even knock.

The two signals that actually rank routes

Roof age: why it leads, and what "old enough" means

Roof age is the cleanest pre-inspection signal you have, because it correlates with how much margin a roof has left. The widely cited service life for an asphalt shingle roof runs roughly 15 to 30 years depending on product, install quality, ventilation, and climate exposure, and NRCA's homeowner guidance frames a roof in the 15-to-20-year band as a sensible candidate for a professional inspection. A roof near or past that band has thinner reserves. When hail strips granules or fractures the mat, an older roof has less life to give up before leaks start.

That is why age leads your ranking. But age is a range, not a verdict. A well-ventilated, properly installed 18-year-old roof in a mild climate can outlast a baking, poorly vented 12-year-old roof. Age raises a question. It never closes one. The honest framing at the door is, "Our records suggest this roof may be on the older side, and the area had hail recently, so it may be a sensible time to document its condition" -- not "your roof is shot."

The practical job is to attach an age confidence level to every address, because guessing roof age from the curb is unreliable. Sun-faded shingles, a re-roof over an old layer, and a cheap recent install can all fool the eye. Rank your age sources by how much you trust them:

Age source Confidence Notes
Building permit / re-roof permit record High Local building departments archive roofing permits as public records, searchable by address; many are online. The gold standard.
Your own CRM (prior install, estimate, or inspection) High If you put the roof on or quoted it, you know the year. This is your unfair advantage.
Homeowner-provided records (closing docs, prior invoice) Medium-high Reliable when produced, but you only get them after a conversation.
Property tax / assessor improvement notes Medium Sometimes flags major improvements or a roof replacement year. Spotty coverage.
Real-estate listing history (prior "new roof" mention) Low-medium A listing from years back may state a roof age; treat as a lead, not proof.
Curb estimate from the street Low "Looks old" is a hypothesis, not a record. Mark confidence low and verify.

For canvassing at scale, the highest-leverage move is mining records you already have. Permit data and your old CRM let you assign defensible age confidence to thousands of homes without setting foot outside. This is exactly where a planning tool earns its keep: contractors who use platforms like RoofPredict get an estimated roof-age range per house across a target area, so the team can sort brand-new roofs out of the route before knocking them. Treat that range as a planning input, the same as a permit lookup -- it points you at the right doors; it does not diagnose the roof.

Hail history: verify the hit, and verify the size

The second signal is whether damaging-size hail actually fell on the block. Two numbers matter: the date and the reported size in inches. Size is the part most canvassing operations skip, and it is the part that separates a real storm route from a rain route.

Research and field practice both point to a rough damage threshold around one inch in diameter for typical asphalt shingles, with heavier laminated/architectural shingles often needing closer to 1.25 inches before clear, claimable damage shows up. Below roughly an inch, you can still get accelerated granule loss and shortened service life, especially with high hail density or long duration, but clean impact bruising that an adjuster will recognize usually wants quarter-size (one inch) hail or larger. Aged shingles take damage at smaller sizes than fresh ones, which is exactly why age and hail size belong on the same scorecard.

So when you build a route, find the storm and read its magnitude. The authoritative ground-truth record is NOAA's Storm Events Database, maintained by the National Centers for Environmental Information. You search by state and county and date, choose the hail event type, and the record lists hail magnitude in inches plus a narrative. For fresh, same-week awareness, the Storm Prediction Center's storm reports give preliminary hail and wind reports, though SPC itself directs you to NCEI for the official, quality-controlled record. The National Weather Service's severe storm education -- for example the NWS severe thunderstorm outreach material -- explains the size and gust terminology so your notes use the right words.

A few discipline points that keep hail history honest:

  • Record the source and the lookup date. "NCEI Storm Events, Tarrant County, hail 1.50 in, event date 4/12/2026, looked up 4/15/2026." That note survives scrutiny. A radar screenshot does not.
  • Label preliminary data as preliminary. SPC reports and paid radar tools are operational estimates. Don't present them to a homeowner as proven fact.
  • Never say the record proves this roof is damaged. Storm Events confirms hail of a size occurred in an area on a date. It says nothing about one specific roof. Only a safe inspection does.

Wind matters too. The same databases log severe wind gusts, and wind drives creased shingles, lifted tabs, and ridge-cap loss. If a date shows damaging wind but little hail, that is still a legitimate inspection reason for older roofs -- just frame it as wind, not hail. A storm-planning tool that models wind and hail impact per individual roof rather than per polygon, the way RoofPredict does, sharpens this further by estimating which roofs likely took the worst of a given storm's physics. It still ranks outreach. It does not replace the ladder.

Why the same hail hits two roofs differently

Two houses on the same block can take identical hail and end up with completely different damage, and understanding why makes your routing smarter. Hail comes in at an angle set by the wind, so the windward slopes -- usually the same compass face across a neighborhood -- absorb the brunt while leeward slopes get far less. A storm tracking out of the southwest tends to beat up south and west faces. That is one reason per-home physics beats a flat polygon: the slope orientation, roof pitch, and even tree cover change the dose each roof actually received.

Material matters as much as orientation. A 25-year-old three-tab roof has thinner, more brittle shingles with granules already shedding; the same impact that merely dents a fresh laminated shingle can fracture the mat on an aged three-tab and expose the asphalt to UV. Soft metals on the roof -- gutters, vents, valley metal, the furnace cap, downspouts -- often show the clearest evidence of hail size, because dents in soft metal are unambiguous in a way shingle bruising is not. When a canvasser reports "the downspouts and the AC fins are dimpled three streets over," that is a stronger ground-truth signal than any radar pixel, and it should bump nearby older-roof addresses up the route.

Hail density and duration also count. A two-minute burst of marginal hail does less than ten minutes of the same size driven hard by wind. The NCEI narrative sometimes captures this ("hail covered the ground," "accumulated to two inches"), which is gold for routing because it implies sustained impact. Read the narrative, not only the magnitude number.

A route-ranking scorecard you can copy

Give every address a score so routes come from evidence, not from a rep's gut or a map screenshot. Here is a point model that has held up in the field. It deliberately rewards verified data and penalizes guessing and unsafe access.

Score factor Points What earns points What does not
Hail/wind context 0-25 NCEI Storm Events record, SPC report, or NWS warning tied to date and area, with hail size noted A radar screenshot, or claiming the record proves damage
Hail size relevance 0-15 Reported hail at or above ~1 in (more for laminated shingles), or damaging wind Sub-threshold hail treated as a storm route
Roof age confidence 0-20 Permit record, prior CRM file, estimated age range, or homeowner document A curbside "looks old" guess alone
Prior relationship 0-15 Past customer, open warranty, maintenance plan, or homeowner who asked Cold contact with no history
Route density 0-10 Several high-scoring homes in a compact, safe loop Long drives between weak signals
Safe ground access -15 to 0 Clear ground approach, no obvious hazard Active weather, power-line hazard, no-access, aggressive-dog notes
Compliance hold hold Local solicitation rules, HOA, no-knock registry, emergency order all checked Ignoring local rules to move faster

A simple routing rule on the total:

  • 75-85: priority route. Manager-reviewed, knock first, best reps.
  • 55-74: warm route. Knock after the priority streets, or open with a call/mailer/prior-customer touch first where lawful.
  • 35-54: research/monitor. Verify roof age or storm context before sending a crew. Don't burn a route on it yet.
  • Below 35: no storm route. Age or weather alone is too weak. Use general maintenance outreach only if compliant, or leave it.
  • Any compliance or safety hold: pause. A high score never overrides a hold. Clear the hold first.

The score does not say a roof is damaged. It says the door is worth a respectful, factual inspection offer. Keeping that distinction explicit protects your insurance boundaries, your brand, and your homeowners.

Worked calibration examples

Run a handful of real addresses through the model before the whole team uses it, and sanity-check the outputs.

Example A -- prior customer, old roof, real hail. Say a contractor pulls a past customer whose file shows a 2009 install, on a block where NCEI logs 1.75-inch hail three days ago.

  • Hail context: 23 (official record, date and area match)
  • Hail size: 15 (1.75 in, well over threshold)
  • Age confidence: 20 (install year in the CRM, roof ~17 years old)
  • Relationship: 15 (prior customer)
  • Density: 8 (several similar homes nearby)
  • Safe access: 0 deduction
  • Compliance: clear

Total: 81 -- priority route. Open as a service follow-up: "We installed your roof back in 2009 and the area just took some sizable hail, so we wanted to offer a documented look."

Example B -- old roof, weak storm, no relationship. Consider a 20-year-old roof where the nearest hail report is pea-size two counties away and there's no prior contact.

  • Hail context: 5
  • Hail size: 2 (sub-threshold)
  • Age confidence: 14 (permit record)
  • Relationship: 0
  • Density: 6
  • Safe access: 0 deduction
  • Compliance: clear

Total: 27 -- no storm route. The roof may genuinely be near end of life, but this is a maintenance conversation, not storm response. Don't knock it with a hail script.

Example C -- strong hail, unknown age, compliance unclear. Suppose a block took confirmed 2-inch hail, but you have no age data and the municipality may require a solicitation permit you haven't pulled.

  • Hail context: 24
  • Hail size: 15
  • Age confidence: 0
  • Relationship: 0
  • Density: 9
  • Safe access: 0 deduction
  • Compliance: hold

The raw points look strong, but the number is irrelevant until the permit question clears and you've researched ages. Next step is compliance review and age lookup -- not a crew on the street.

These examples teach the team the model's real purpose: lower noise, prevent weak outreach, and keep the company off ground its evidence cannot defend.

Building the route in layers

Don't start from a polygon and send everyone inside it. Build the route in deliberate layers so the highest-scoring, safest, most lawful doors rise to the top.

  1. Set the storm window. Pick the date range you're working and record why -- a homeowner call, a prior-customer request, an SPC preliminary report, or a confirmed NCEI event. Save the source link and the lookup date. Label preliminary data as preliminary.

  2. Draw a serviceable area, not the whole swath. Outline only what you can actually inspect, schedule, and service this week. A route bigger than your capacity creates slow response, rushed scripts, and dropped follow-up. If you can't service a neighborhood properly this week, don't knock it today.

  3. Layer in roof-age confidence. Attach permit records, CRM history, estimated age ranges, or homeowner documents to each address, and mark low-confidence guesses as low. Sort obviously new roofs out of the route. They drag down conversion and make you look like you didn't do your homework.

  4. Separate relationships from cold contacts. Prior customers, warranty contacts, and maintenance-plan members get a service-follow-up lane with a warmer script. Cold doors get a stricter script and tighter compliance review. Never run them on the same generic pitch.

  5. Apply safety and compliance holds. Pull out active-weather zones, unsafe travel areas, no-access properties, known hazards, and any address where local solicitation rules, an HOA, or a no-knock registry create uncertainty. A strong score does not override a hold.

  6. Assign a rep and a follow-up owner to every address. No address goes live without someone owning the next step. A route list with no follow-up discipline produces duplicate knocks, missed callbacks, and loose promises you can't keep.

This sequence keeps route selection calm and explainable. A manager can say exactly why one street is active and another is on hold, without hand-waving.

The roof-age-plus-hail ranking matrix

The safest mental model keeps "storm context" and "roof condition" in separate columns and only combines them for priority, never for a damage claim.

Route scenario Priority Why Required limit
Old roof, prior customer, confirmed damaging hail nearby High Strong fit: known relationship, age margin thin, real weather Don't promise damage or coverage
Old roof, confirmed hail, no relationship Medium-high Age and weather both present; cold script and stricter compliance Offer inspection, not a verdict
Old roof, no reliable hail record Medium Age may justify maintenance/inspection outreach Don't frame it as storm response
New roof, strong damaging hail Medium Weather may justify a check, especially for prior customers Don't imply age makes it safe or unsafe
Unknown age, strong damaging hail Medium-low Needs age research before a door route Don't rank on weather alone
Old roof, sub-threshold hail, no relationship Low Age alone isn't a storm route Maintenance outreach only, if compliant
Any safety or access concern Hold Field work may be unsafe Safety review first
Solicitation/legal uncertainty Hold Door route may break local rules Local review first

Manufacturer guidance backs the principle that age is one factor among several. GAF's homeowner roof-damage education treats age alongside visible condition, repair history, and professional inspection -- never as the lone deciding factor. In a route list, age should raise a question ("is this roof worth a professional look after this storm?"), not script a claim ("your roof is damaged").

Hail-resistant roofs change the math

A factor that's reshaping storm routes: impact-resistant (IR) shingles. More homes now carry Class 3 or Class 4 rated products, and they behave differently under hail. If a block was re-roofed recently with a strong IR product, even a real hailstorm may not have produced claimable damage -- and knocking those homes with a standard storm pitch makes you look uninformed.

This is where independent testing helps you calibrate. The Insurance Institute for Business & Home Safety (IBHS) publishes a hail impact-resistant shingle performance rating, and its 2025 edition evaluated a record 24 products -- roughly 95% of IR shingles sold annually. Notably, most earned a "Good" rating and none earned "Excellent," and for the first time IBHS paired the familiar Excellent/Good/Marginal/Poor scale with a 0-to-10 numerical score measuring dents, tears, and granule loss. The 2025 FORTIFIED standard now requires steep-slope asphalt roofs to use a "Good" or "Excellent"-rated product to qualify for the hail supplement, aimed at withstanding hail up to two inches.

Two takeaways for routing:

  • A recent IR re-roof should lower a home's storm-route priority unless the hail was large (think two inches or more) or the wind was severe. The roof was built to take it.
  • "Impact resistant" is not "impact proof." Even IR shingles take granule loss and cosmetic damage, and no product rated "Excellent" yet exists. A two-inch-hail event is still an inspection reason on any roof. Use judgment, and let the inspection -- not the label -- decide.

Knowing which homes likely carry IR roofs, and how old they are, is exactly the kind of detail that keeps a crew from wasting a morning. It's another reason age-range and per-home storm modeling beat a flat polygon.

Regional and climate variation

A scorecard that works in north Texas needs different weights than one in the upper Midwest or the Gulf Coast, because the storm physics and the housing stock differ. Tune the model to your market instead of copying someone else's.

Region Dominant storm signal Routing adjustment
Southern Plains / Hail Alley (TX, OK, KS, CO Front Range) Frequent large hail, repeat events per season Weight hail size heavily; many roofs are young because they were recently re-roofed -- lean hard on age confidence to skip them
Upper Midwest (MN, IA, NE, the Dakotas) Large hail plus straight-line wind (derechos) Score wind events alongside hail; freeze-thaw aging means a "15-year" roof may be functionally older
Southeast / Gulf (FL, LA, MS, AL) Wind and tropical events more than classic hail; heat and humidity age roofs fast Weight wind and roof age over hail; watch Florida's roofing-solicitation statute closely
Mountain West / high elevation Intense but localized hail, big sun/UV exposure Per-home orientation and elevation matter; UV shortens shingle life, so age band shifts earlier
Pacific Northwest / mild coastal Hail rare; moss, algae, and moisture drive aging Hail routing barely applies; this is maintenance and age territory, not storm response

Climate changes what "old" means. A roof bakes faster in Phoenix than in Seattle, so a 14-year-old roof in a high-UV, high-heat market may have less margin than an 18-year-old roof in a mild one. Hard freeze-thaw cycling in northern markets stresses shingles and flashing every winter. When you tune your age-confidence weighting, account for the fact that calendar age and effective age drift apart by climate. A roof-age range that already reflects regional aging is more useful than a flat "installed in year X" stamp -- it tells you how much life the roof has likely spent, rather than only how many birthdays it has had.

Housing stock matters too. A subdivision built in one tight window tends to have roofs of similar original age, which is why a single big hail year can re-roof a whole neighborhood at once. Three years later, that neighborhood is your worst storm route, not your best, because nearly every roof is new. Knowing the build-out year of a subdivision -- and which blocks already got re-roofed after the last big event -- keeps you from canvassing a sea of three-year-old roofs.

Weather source workflow

Write a short, defensible weather note before any route goes live. Keep the sources and their limits straight.

Source Use it for Don't use it for
NCEI Storm Events Database Official hail/wind events by date, county, type, magnitude (inches), and narrative Proving a specific roof is damaged
SPC storm reports Fresh, same-week preliminary hail/wind awareness Final damage or claim proof; it's preliminary
NWS severe storm education Correct hail-size and wind terminology for your notes Diagnosing roofs
Paid radar / hail-swath tools Operational enrichment and per-home estimates if approved internally Public claims before checking against the official record

A good route note reads: "Weather context reviewed: NCEI Storm Events confirms 1.50-in hail, [county], event date [date], looked up [date]; SPC preliminary report consistent. This is route-priority context only. Property-specific condition requires a safe inspection with homeowner permission."

A bad note reads: "NOAA says your roof got hit." That's an overclaim, and it starts the homeowner conversation on a lie.

Field scripts that earn the inspection

A route can be direct without being aggressive, and the script is where most companies destroy or build trust. The goal at the door is one thing: earn permission for a safe, documented inspection. Not a signature. Not a claim. An inspection.

Use language like this:

"We're checking in with homeowners near the recent storm. We can't tell from the street whether your roof has damage, but if you'd like, we can schedule a safe inspection and document its condition for you."

For an older roof on a confirmed-hail block:

"Our records suggest this roof may be on the older side, and the area had hail recently. That doesn't mean you have damage -- it means this may be a sensible time to document the roof's condition, on your schedule."

For a prior customer:

"We installed [or inspected] your roof back in [year], and the area just took some hail, so we're following up. We can review the file, the roof's age, and any visible concerns before recommending a next step."

And a copy-ready door framework your reps can internalize:

STORM-ROUTE DOOR SCRIPT (offer an inspection, never a verdict)

1. Identify: "Hi, I'm [name] with [company], local roofer."
2. Reason: "The area took hail on [date] -- we're offering documented
   roof inspections to homeowners nearby."
3. Honest limit: "I can't tell from the ground if your roof is
   damaged. That's what a safe inspection is for."
4. The ask: "Would you like us to schedule a free, no-pressure
   inspection and give you a written report with photos?"
5. On insurance: "If we find a concern, the report and photos are
   yours to share with your insurer. Your insurer decides coverage."
6. Close to next step: book the inspection, or leave a card. No
   contract at the door. No claim talk. No deductible talk.

Lines to ban from every script -- they create legal, insurance, and brand risk, and they're often illegal:

  • "Your roof qualifies."
  • "Insurance will replace it" / "we'll get your claim approved."
  • "The storm map says your roof is damaged."
  • "Everyone on this street is getting approved."
  • "We'll handle / fight / negotiate / maximize your claim."
  • "We'll cover [or eat] your deductible."
  • "Sign today or you lose your chance."

The next two sections explain exactly why the last few of those can end a business.

The insurance boundary that gets roofers fined

This is the part canvassing managers cannot afford to wing. A roofer documents conditions and provides an estimate. The insurer decides coverage. The moment a roofer crosses into negotiating, adjusting, or settling a claim on the homeowner's behalf without a public-adjuster license, the company is exposed -- and courts are enforcing it.

In 2024 the Texas Supreme Court decided Texas Department of Insurance v. Stonewater Roofing. The roofer had advertised itself as having extensive experience settling insurance claims and signed contracts authorizing it to negotiate with insurers on customers' behalf. The court held that public-adjuster licensing laws regulate that representative capacity -- acting on behalf of an insured to negotiate or effect a claim settlement -- not protected speech, and that a roofer can't sidestep the license by branding itself an "insurance specialist." The full opinion is public via Justia. The plain lesson: a roofer who isn't a licensed public adjuster must not act as one.

So train the boundary into your scripts. Say this:

  • "We'll document the roof's condition with photos and measurements."
  • "The report and photos are yours to share with your insurer."
  • "Your insurer decides what's covered."
  • "You're welcome to contact your insurer or review your policy."

Never say this:

  • "We handle / manage / fight / negotiate / maximize / settle your claim."
  • "We'll get your claim approved" or "recover every dollar."
  • "We're insurance-claim specialists" (used promotionally).
  • Anything that promises an approval, a coverage outcome, or a payment amount.

And the deductible line is its own trap. Offering to waive, absorb, rebate, or "eat" a homeowner's deductible is insurance fraud in many states. The deductible is the homeowner's to pay, full stop. A rep who offers to cover it isn't closing a deal -- they're creating criminal exposure for the company. Make that an instant-termination rule.

Warning reps away from these phrases isn't legal hedging; it's protection. The safe boundary -- document the facts, hand them to the homeowner, let the insurer decide -- is also the boundary that keeps your company in business.

Consumer-protection rules and homeowner trust

Homeowners are warned about post-storm contractors constantly, and your outreach has to survive those warnings. The Federal Trade Commission's guidance on avoiding scams after weather emergencies tells consumers to watch for pressure, vague contracts, demands for large upfront payment, and high-pressure door sales. The National Association of Insurance Commissioners similarly urges homeowners to read the fine print and not sign away insurance benefits to a contractor.

Design your door operation to pass those tests by default:

  • No contract signed at the door on a cold knock. Offer the inspection; let the homeowner decide later.
  • No large upfront payment demands.
  • Clear, plain-language paperwork the homeowner can read and keep.
  • Honor cooling-off / right-to-cancel rules where they apply.
  • Respect "no soliciting" signs and any local no-knock registry.

Which brings up the rule that varies the most: whether you can legally knock at all.

Solicitation law varies wildly -- check before you knock

Door-to-door rules are intensely local, and some are aimed squarely at roofers. Florida's 2021 SB 76, for instance, restricted how roofing contractors could make unsolicited contact about claims, with significant penalties attached, and later litigation reshaped parts of it. Many municipalities require a solicitor's permit from the city or county clerk for door sales above a small dollar threshold. A posted "No Soliciting" or "No Trespassing" sign legally bars the knock regardless of any permit. And a growing number of towns maintain no-knock registries that put an address off-limits for a set period.

None of this is optional, and the rules change between the city and the unincorporated county next door. Before a route goes live, confirm:

  • Permit/registration: Does the jurisdiction require a solicitor's permit or contractor registration for door-to-door work? Is yours current?
  • State roofing-solicitation statute: Some states restrict unsolicited contact specifically about insurance claims.
  • No-knock registry / no-soliciting signs: Pull the local registry and instruct reps to skip posted homes, always.
  • Hours and cooling-off rules: Honor lawful canvassing hours and right-to-cancel periods.
  • HOA rules: Some communities ban solicitation outright.

When any of this is unclear, hold the route until someone qualified clears it. Moving fast through a permit question is exactly how a strong storm season turns into a fine and a news story.

Daily route review and follow-up discipline

Post-storm routes change by the hour. Run a short review at the start and end of every field day.

Morning review

  • Confirm weather is safe for outreach; pull streets under active warnings.
  • Re-check that no local emergency order, permit status, or registry changed overnight.
  • Review the approved script -- especially the insurance and deductible boundaries.
  • Assign route owners and follow-up windows.
  • Confirm no rep is expected to climb a roof from a door route.
  • Confirm a manager contact for any homeowner insurance questions.

End-of-day review

  • Mark every door: contacted, no-answer, interested, not interested, inspection requested, do-not-contact.
  • Record homeowner permission before any inspection is scheduled.
  • Separate inspection requests from coverage/claim questions.
  • Add safety, access, and route notes.
  • Remove addresses that should not be contacted again.
  • Flag any rep language that drifted toward damage or coverage promises, and coach it same-day.

Follow-up discipline is where most door operations leak money. A homeowner who said "maybe next week" is worth more than a fresh cold door, and they vanish without a tracked next step. The best routes aren't the ones with the most doors -- they're the ones with the tightest match between source context, homeowner need, safe capacity, and honest follow-up.

Safety boundaries: a knock is not an inspection

Door knocking is outreach, not roof inspection. A rep at the door should not be climbing roofs, entering attics, or making damage findings unless your safety program, training, authorization, and the site conditions all support it. OSHA's fall-protection guidance identifies the hazards that make ad-hoc roof access dangerous: ladders, unprotected edges, steep or wet surfaces, damaged decking, tools, and power lines. Storm-damaged roofs are more hazardous, not less.

Bake safety into the route:

  • No outreach during active severe weather, lightning, high wind, or dangerous heat.
  • No rep climbs a roof from a door route. Inspections are scheduled with trained crews and fall protection.
  • No attic access without lighting, PPE, and a safety check.
  • Never pressure a homeowner to take roof photos from an unsafe position.
  • Record safety and access holds in the route list, and honor them over any score.

A route with strong weather context but unsafe access gets held. A high lead score never outranks a fall hazard.

Running the whole thing as a repeatable system

The difference between a company that wins storm seasons and one that scrambles is whether route ranking is a system or a spreadsheet fire drill. Every address should carry a record that explains, at a glance, why it's prioritized: address and route zone, roof-age source and confidence, the NCEI/SPC weather source link and hail size, the storm date, prior-customer status, last inspection or repair note, safety/access flags, compliance status, rep assignment, outreach status, and follow-up date.

The route view should justify itself. "Score 81: prior customer, ~17-year-old roof, 1.75-in hail confirmed by NCEI, compact loop, no holds" is a defensible route. "Hot lead from hail map" is not. This is the operational gap a planning tool fills. Because RoofPredict pairs an estimated roof-age range with per-home wind and hail modeling, it lets a manager pre-sort an entire storm area into the lanes below, and it doubles as the recordkeeping layer that keeps an audit trail of why each door was knocked. It does not inspect roofs, diagnose damage, certify remaining life, or decide coverage -- it ranks where a safe inspection offer is most likely to be worth everyone's time.

Route lane Best use Risk control
Prior-customer follow-up Service-minded outreach after a confirmed storm Use file history; warranty boundaries; no coverage promises
Age + hail priority Older roofs on confirmed damaging-hail blocks Source note required; offer inspection, not verdict
Requested inspection Homeowners who asked for a look Confirm permission, safety, and scope
Research / monitor Strong hail but unknown age, or weak signals Verify before sending a crew
Maintenance Older roofs without storm context Sell as maintenance, never as storm damage
Hold Legal, safety, source, or access uncertainty Manager clears it before outreach

A mining play that's easy to overlook: your old CRM. Past estimates that never closed and customers whose roofs have aged into the inspection band are some of the warmest doors you'll ever knock, especially when a confirmed storm crosses their block. Re-engaging that list with a service-framed touch -- "we quoted your roof in 2019, the area just took hail, want a documented look?" -- outperforms cold canvassing on almost every metric, and it's fully compliant because you have a prior relationship.

Measuring whether your ranking is working

A ranking model is only worth running if you check whether it predicts the right doors. Track a few numbers per route lane so you can tune the scorecard instead of trusting it blindly. None of these require fancy software -- a tidy CRM column does the job.

  • Inspection-set rate per 100 doors. How many homeowners agreed to a documented inspection. This is your truest measure of route quality, because it reflects whether the door was worth knocking at all.
  • Inspection-to-actionable rate. Of the roofs you inspected, how many showed a real condition worth documenting. If a lane sets lots of inspections but almost none are actionable, your hail-size or age weighting is too loose.
  • New-roof skip accuracy. Track how often a crew arrives and finds a roof far newer than expected. High miss rates mean your age data is stale -- refresh permits and CRM.
  • Compliance incidents. Any no-knock-registry hit, sign violation, or homeowner complaint about pressure. The target is zero, and any incident triggers a script and route review.
  • Cost per set inspection by lane. Prior-customer and age-plus-hail lanes should beat cold polygon canvassing here by a wide margin. If they don't, you're not sorting hard enough.

Review these weekly during storm season. If the 75-plus priority lane isn't clearly out-converting the 55-to-74 lane, your point weights are off -- usually because hail size or age confidence isn't doing enough work in the formula. Adjust the points, re-run a few calibration addresses, and retest. A scorecard you never check drifts back into guesswork within a season.

Keep the audit trail with the numbers. When a route over-performs, you want to know why so you can repeat it, and when a route draws a complaint you want a record of exactly what context justified the knock. "Score 81, NCEI-confirmed 1.75-in hail, prior customer, permit-verified 2009 roof, registry checked" is a record that protects the company. A vague "hail map looked hot" is the kind of note that reads badly if anyone ever asks.

Common mistakes that sink storm routes

  • Treating the polygon as the route. Radar swaths overstate ground hail and ignore roof age entirely. Rank per home.
  • Ignoring hail size. Pea-size hail two counties over is not a storm route. Read the magnitude in inches.
  • Guessing roof age from the curb. "Looks old" misroutes crews. Use permits, CRM, and age ranges.
  • Knocking brand-new and IR roofs with a storm pitch. It wastes reps and makes you look uninformed.
  • Promising damage, coverage, or approval at the door. Illegal-adjacent, brand-damaging, and it starts the relationship on a lie.
  • Offering to cover the deductible. Fraud in many states. Instant-termination rule.
  • Skipping the local permit/registry check. One fine erases a season's margin.
  • Sending reps to climb roofs from a door route. Outreach is not inspection. Schedule it safely.
  • No follow-up owner. "Maybe next week" homeowners are your warmest leads and they evaporate without a tracked next step.

Get the ranking right and the rest of the operation calms down. Your best reps spend their hours on doors that are old enough, hit hard enough, and lawful enough to be worth a knock -- and every homeowner conversation starts with a fact you can defend instead of a promise you can't.

Sources checked: June 18, 2026.

More from the canvassing series

FAQ

How do I find the hail size for a specific neighborhood and date?

Use NOAA's Storm Events Database, maintained by the National Centers for Environmental Information. Search by state, then county, then your date range, and select the hail event type. The record lists hail magnitude in inches plus a narrative of what was reported. For fresh, same-week awareness, the Storm Prediction Center's storm reports show preliminary hail and wind reports, but treat those as preliminary and confirm against the official NCEI record before relying on them for routing.

What hail size actually damages an asphalt roof?

Clear, claimable impact damage on typical asphalt shingles generally starts around one inch in diameter, roughly quarter size, and heavier laminated or architectural shingles often need closer to 1.25 inches before damage shows. Below an inch you can still see accelerated granule loss and shortened service life, especially with high hail density or long storm duration. Aged shingles take damage at smaller sizes than fresh ones, which is why roof age and hail size belong together when you rank routes.

Should older roofs always rank highest on a door-knocking route?

No. Roof age is the strongest single pre-inspection signal because it tracks how much margin a roof has left, but it is not a verdict on its own. An old roof with no relevant hail history is a maintenance conversation, not storm response. Age earns its highest priority when it combines with confirmed damaging-size hail, a prior customer relationship, a compact safe route, and clear local solicitation rules. Age raises a question; it never proves damage.

How accurate is roof age estimated from records versus the curb?

Records beat eyeballs. Building or re-roof permits are archived as public records and are the most reliable age source, followed by your own CRM if you installed or quoted the roof. Assessor improvement notes and old real-estate listings help but are spotty. A curbside guess is unreliable because sun fading, re-roofs over old layers, and cheap recent installs all fool the eye. Treat curb estimates as low-confidence hypotheses and verify before you commit a crew to the route.

Can a roofer talk about insurance at the door?

Keep it narrow and factual. A rep can say the homeowner may contact their insurer or review their policy, and that any inspection report and photos are the homeowner's to share. A rep must never interpret coverage, promise approval, claim to handle or negotiate the claim, or offer to cover a deductible. The 2024 Texas Stonewater decision confirmed roofers cannot act as unlicensed public adjusters, and covering a deductible is insurance fraud in many states.

Do hail-resistant shingles change how I rank routes?

Yes. Class 3 and Class 4 impact-resistant shingles are built to take hail, so a home recently re-roofed with a strong IR product should usually rank lower unless the hail was large (around two inches) or the wind was severe. But impact resistant is not impact proof. IBHS's 2025 ratings tested 24 products and none earned an Excellent rating, and even good IR shingles take granule loss. A two-inch-hail event is still an inspection reason on any roof.

It depends entirely on your jurisdiction, and some rules target roofers specifically. Many cities require a solicitor's permit; a posted no-soliciting sign legally bars the knock regardless of any permit; many towns maintain no-knock registries; and some states restrict unsolicited contact about insurance claims, as Florida's 2021 SB 76 did. Rules differ between a city and the county next to it. Confirm permit, registry, sign, and HOA rules before any route goes live, and hold the route if anything is unclear.

What is the difference between ranking a route and proving roof damage?

Ranking decides where a respectful inspection offer is most likely worth your team's time, using roof age, hail size and date, relationship, density, safety, and compliance. It never decides that a specific roof is damaged. Storm databases confirm hail of a size occurred in an area on a date; they say nothing about one roof. Only a safe, in-person inspection determines condition, and only the insurer determines coverage. Keeping those separate protects your homeowners and your company.

How can I use my old CRM to find better storm leads?

Mine past estimates that never closed and prior customers whose roofs have aged into the 15-to-20-year inspection band, then cross-reference them against confirmed storm blocks. These are some of the warmest doors you can knock, and re-engaging them is fully compliant because you already have a relationship. A service-framed touch such as, we quoted your roof in 2019 and the area just took hail, would you like a documented look, consistently outperforms cold canvassing while keeping outreach honest.

The Roofline by RoofPredict

Stay Ahead of Roofing Market Changes

Join The Roofline by RoofPredict for weekly roofing intelligence: material price signals, storm demand, insurance and regulatory updates, sales tactics, and local contractor opportunities.

By signing up, you agree to receive The Roofline by RoofPredict. Unsubscribe anytime.

Related Articles