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

Door knocking after hail should start with route priority, not a claim that every roof in the area is damaged. A useful route list combines roof age, storm-date context, prior customer status, route density, safety/access limits, and review status. The purpose is to decide where an inspection offer may be useful, not to decide damage, coverage, replacement, or claim outcome from a spreadsheet.

Use weather records as context. NOAA's Storm Events Database can support storm-date, area, event-type, and narrative context. The Storm Prediction Center's storm reports can support near-term operational awareness, but SPC itself points users to NCDC/NCEI for official severe weather reports. NWS severe thunderstorm education explains why hail size and wind-gust context matter. None of those sources proves that one house has roof damage.

Use roof age as a triage signal. GAF's roof guidance treats age as one factor alongside visible condition, repair history, and professional inspection. A 17-year-old asphalt shingle roof in a hail-affected area may deserve a higher inspection-priority score than a 3-year-old roof with no prior relationship, but age does not prove damage, remaining life, warranty status, or insurance eligibility.

RoofPredict can organize the route list: roof age, storm context, source links, prior customer notes, route density, safety notes, rep assignment, inspection status, and follow-up. It should not be treated as a weather authority, inspector, insurer, adjuster, public adjuster, attorney, safety authority, or solicitation-compliance tool.

Route Priority Scorecard

Use a scorecard so sales managers do not route crews only from a hail map screenshot or a rep's instinct.

A simple route rule works well:

• 70-85: manager-reviewed priority route.
• 50-69: call, mail, text where lawful, or prior-customer follow-up before door route.
• 30-49: keep in monitoring list; do not send a full route without more evidence.
• Below 30: no door-knock route unless a homeowner requests help or new source information appears.
• Any compliance hold: pause until a qualified person clears the outreach path.

The score does not say the roof is damaged. It says the route may be worth a respectful inspection offer. That distinction matters for insurance boundaries, consumer trust, and internal accountability.

Score Calibration Examples

Managers should calibrate the score before a full team uses it. Run a few sample properties through the model and check whether the result matches common sense.

Example 1: prior customer, known older roof, strong hail context.

• Weather context: 23 points because NOAA/SPC/NWS sources show relevant area context.
• Roof age confidence: 18 points because the install year is in the customer file.
• Prior relationship: 15 points.
• Property fit: 12 points because the home has prior repair history.
• Route density: 8 points.
• Safety/access: 0 point deduction.
• Compliance: clear.

Result: 76. This route should be manager-reviewed and active. The rep script should still say "we can schedule a safe inspection if you want one," not "your roof is damaged."

Example 2: older roof, weak weather context, no relationship.

• Weather context: 5 points.
• Roof age confidence: 15 points.
• Prior relationship: 0 points.
• Property fit: 8 points.
• Route density: 6 points.
• Safety/access: 0 point deduction.
• Compliance: clear.

Result: 34. This is not a storm door route. It may belong in maintenance education or long-term follow-up, but the hail-history signal is too weak for storm-response outreach.

Example 3: strong hail context, unknown roof age, compliance uncertainty.

• Weather context: 24 points.
• Roof age confidence: 0 points.
• Prior relationship: 0 points.
• Property fit: 5 points.
• Route density: 9 points.
• Safety/access: 0 point deduction.
• Compliance: hold.

Result: hold. The numeric score does not matter until the compliance question is cleared. The right next step is source review, local outreach review, or soft non-door follow-up where permitted.

These examples teach the team that route ranking is a decision filter. It should lower noise, prevent weak outreach, and protect the company from statements the evidence does not support.

Route Build Sequence

Build the route in layers. Do not start with a map polygon and send everyone inside it to the field.

1. Define the storm review window.

Choose the date range being reviewed and record why. The source might be a homeowner call, a prior customer request, an SPC preliminary report, a NOAA Storm Events record, or an internal storm alert. Save the source link and lookup date. If the signal is preliminary, label it preliminary.

1. Mark the serviceable area.

Draw only the area the company can reasonably inspect, schedule, and service. A route that is too large can create slow response, rushed scripts, and weak follow-up. If the team cannot handle a neighborhood this week, it should not send reps there today.

1. Add roof-age confidence.

Use known install date, past customer record, permit record, roof report, homeowner-provided document, or previous inspection note. If the source is weak, mark confidence low. "Looks old from the street" is not a reliable age source.

1. Add relationship status.

Prior customers, maintenance-plan customers, open warranty contacts, and homeowners who requested information should be separated from cold outreach. A prior customer route can be framed as service follow-up. A cold route needs stricter script, compliance, and consumer-protection review.

1. Apply safety and compliance holds.

Remove active storm areas, unsafe travel zones, no-access properties, known aggressive dog notes, steep roof expectations, and legal or solicitation uncertainty. A strong score does not override a hold.

1. Assign reps and follow-up owner.

Every address needs an owner and next step. A route list without follow-up discipline produces duplicate knocks, missed callbacks, and loose promises.

This sequence keeps route selection calm. It also gives a manager a way to explain why one street is active and another street is on hold without relying on guesswork.

Roof Age + Hail History Ranking Matrix

The safest ranking matrix separates "storm context" from "roof condition."

GAF's roof damage page supports using roof age, prior inspection reports, and visible signs as inspection context. GAF's repair-versus-replace article also frames age as one factor, not the final answer. In a route list, age should raise a question: "Is this roof worth a professional look after the storm?" It should not create a script that says, "Your roof is damaged."

Weather Source Workflow

Build a weather-context note before a route goes live.

The route note should sound like this: "Weather context reviewed: SPC preliminary hail reports and NOAA/NWS context around the service area and date. This is route-priority context only. Property-specific condition requires safe inspection and homeowner permission."

Avoid this: "NOAA says your roof was hit." That is an overclaim and creates trust problems before the conversation starts.

NWS severe thunderstorm education, such as the NWS Birmingham severe thunderstorm page, can help managers explain why hail size and wind gusts are included in source notes. Use that as terminology and triage context only. A route score still needs property records and a safe inspection path.

Door-Knock Route QA Checklist

Before a team canvasses, the manager should run a route QA pass.

The Federal Trade Commission's weather-emergency scam guidance is written for consumers, but it is useful for contractors because it shows what homeowners are being warned about: pressure, unclear contracts, payment risk, and off-premises sales concerns. NAIC's post-storm guidance also warns consumers about contractor fraud and says adjuster and policy review matter. Contractors should design outreach that can survive those warnings.

Ethical Outreach Language

A route can be direct without being aggressive.

Use language like:

We are checking in with homeowners near the recent storm path. We cannot tell from the street whether your roof has damage, but we can schedule a safe inspection if you want a documented review.

Or:

Our records show this roof may be older and the area had hail reports nearby. That does not mean you have damage. It means this may be a sensible time to document condition if you want us to take a look.

For prior customers:

We worked on your roof previously and are following up after the recent hail reports in the area. We can review the file, roof age, and any visible concerns before recommending next steps.

Avoid:

• "Your roof qualifies."
• "Insurance will replace it."
• "The storm map says your roof was damaged."
• "Everyone on this street is getting approved."
• "Sign today or you lose your chance."
• "We can handle everything with your insurance."

Those lines may create legal, insurance, consumer-protection, and brand risk. They also make the route list less useful because the conversation starts with a promise the facts may not support.

Rep Assignment Rules

Route quality depends on who handles the conversation. Assign reps based on the sensitivity of the route.

The rep should know what the route score means. It does not mean "close hard." It means "this homeowner may have a reason to want information." The rep's job is to offer a clean next step: safe inspection, documentation review, prior file check, or no action.

Daily Route Review

Post-storm routes change quickly. Run a short review at the beginning and end of each field day.

Morning review:

• Confirm weather is safe for outreach.
• Remove streets under active warnings or unsafe travel conditions.
• Check whether any local emergency, licensing, or solicitation restriction changed.
• Review the approved script.
• Assign route owners and follow-up windows.
• Confirm that no rep is expected to climb roofs during door outreach.
• Confirm manager contact for homeowner questions about insurance boundaries.

End-of-day review:

• Mark contacted, no answer, interested, not interested, requested inspection, and do-not-contact statuses.
• Record homeowner permission before scheduling inspections.
• Separate inspection requests from claim or coverage questions.
• Add safety notes, access limits, and route issues.
• Remove addresses that should not be contacted again.
• Flag any rep language that drifted into coverage or damage promises.

This review turns door knocking into an accountable operation. It also gives the office better data for the next day. The best routes are not the ones with the most doors. They are the ones with the best match between source context, homeowner need, safe capacity, and honest follow-up.

Safety And Inspection Boundaries

Door knocking is not roof inspection. It is outreach. A rep at the door should not be expected to climb a roof, enter an attic, or make a damage finding unless the company safety program, authorization, training, and site conditions support it.

OSHA's roof inspection and tarping guidance identifies hazards tied to ladders, raised work surfaces, steep or slippery roofs, damaged roofs, tools, power lines, and fall hazards. Route planning should include safety filters:

• Do not route during active severe weather, lightning, high winds, or unsafe heat.
• Do not expect reps to climb roofs from a door route.
• Do not schedule roof access without trained personnel and safety controls.
• Do not enter attics without access, lighting, PPE, and safety review.
• Do not pressure homeowners to provide roof photos from unsafe positions.
• Record safety/access holds in the route list.

If a route has strong weather context but unsafe access conditions, hold it. A high lead score does not override safety.

How RoofPredict Fits The Route Workflow

RoofPredict can turn route ranking into a repeatable process instead of a spreadsheet scramble. A manager can store:

• Property address and route zone.
• Roof age source and confidence.
• NOAA, SPC, or NWS source links.
• Storm date and event type.
• Prior customer status.
• Last inspection or repair note.
• Safety/access notes.
• Outreach status.
• Rep assignment.
• Inspection request status.
• Photo packet status.
• Follow-up date.

The route view should show why a home is being prioritized. "Score 78: prior customer, 14-year-old roof, official hail context nearby, compact route, no safety hold" is useful. "Hot lead from hail map" is not.

RoofPredict also helps managers separate route types:

This structure gives reps better conversations and gives managers a clean audit trail.

Example Route Board

A useful route board might look like this:

This board prevents the common mistake of treating the whole storm area as one route. It also keeps the team from confusing "high route score" with "approved claim." The score only controls outreach priority.

Source Limits

FAQ

Can hail history rank door-knocking routes?

Yes, as a route-priority signal. Hail history can tell you where an inspection offer may be relevant. It cannot prove a specific roof is damaged.

Should older roofs always rank higher?

No. Roof age is one factor. It becomes more useful when combined with weather context, prior customer records, visible concerns, and safe inspection opportunity.

Can reps mention insurance?

Keep it narrow. Reps can say the homeowner may choose to contact their insurer or review their policy. They should not interpret coverage, promise approval, waive deductibles, or act as a public adjuster unless legally authorized and reviewed.

What if a route has a strong hail signal but no reliable roof age?

Put it in a research or monitoring lane. Add roof-age research, prior customer matching, and source review before prioritizing a door route.

What if local door-knocking rules are unclear?

Hold the route. Check local solicitation, emergency, licensing, HOA, and company policy requirements before sending reps.