Roofing - Storm handoff - 6 min read
Roofing Storm Inquiry Handoff: Keep Every Request Clear
Twelve requests in two hours after the hail. A practical post-storm intake workflow: preserve what the homeowner said, name an owner, make the next action clear - without claiming damage you have not seen.
The afternoon the phones melt down
The hail came through Tuesday night. By Wednesday at 9 a.m., the office has ten forms, four voicemails, texts on two personal phones, and messages from the Google profile and the Facebook page - all before the crews have rolled.
Every one of those homeowners is comparing roofers right now. And in the rush, the thing that gets lost is not the job - it is the thread. Who said what, who owns the callback, and what was promised to whom.
The immediate risk after a storm is not that the office cannot judge every job from a screen. It is that a request loses its homeowner context before anyone agrees on what happens next.
A post-storm board does not diagnose roofs
A useful post-storm board does not pretend to diagnose a roof or route the crews. It gives every request one visible record: what the homeowner asked for, in their own words, who owns the follow-up, what happened last, and the next action the office agreed to.
Nobody needs a hail map on the wall. They need to know that Mrs. Callahan's tarp request did not fall behind the voicemail stack.
Capture enough context for a real handoff
The first contact is not an inspection. Keep the intake short enough that a homeowner can finish it from a porch, but specific enough that the next person does not start from an empty note. Use the same core fields whether the request began by phone, a web form, a Google Business Profile link, or a Facebook message - after a storm, they all land in the same day.
Copy this post-storm roofing intake card into the office queue
These fields create a real record without asking a homeowner to diagnose their roof from the driveway. Record their words - do not turn a report into a conclusion about damage or coverage.
| Ask or capture | Why the office needs it | Record or next action |
|---|---|---|
| What happened, in the homeowner's own words? | Preserves the report without turning it into a roof diagnosis. | Save the exact wording and the requested service. |
| What is the property ZIP? | Location and coverage: is it on the routes you actually run? | Record the ZIP; handle an out-of-area request deliberately instead of losing it in the pile. |
| Water coming in now, or tarp needed? | Separates an active report from a future inspection request without deciding the roof's condition. | Record the report; give the request a named owner for the next contact. |
| Repair, inspection, or possible replacement? | Gives the next person basic scope before the conversation continues. | Write the requested service; the inspection still determines the actual condition. |
| Best callback number and time? | Makes the next action concrete instead of a vague "call them back." | Assign a named owner and write the callback or review action. |
Keep the homeowner's report separate from the inspection decision
"Water is coming through the ceiling since last night" and "I am thinking about a new roof next spring" are two different reports. Both deserve an accurate record. Neither is a roof diagnosis, an insurance coverage decision, or a promise that an inspection will find damage.
The person taking the request writes the words, not a verdict. The owner of the request then contacts the homeowner, follows the company's safety process, and decides whether an inspection or another step makes sense.
Give each request one owner, then hand it to your follow-up routine
A shared inbox is not a handoff. If a request just says "call customer" with no name beside it, the office cannot tell whether the call happened, who owns it, or what happens when the homeowner does not answer.
Give every request a named owner and one written next action: "Maya: call after 4 p.m." or "Luis: confirm coverage, then update the homeowner."
After that, a storm request is handled like any other lead. Ownership, last action, next action, outcome - the same discipline whether or not there was a storm, so we will not repeat it here. Our roofing follow-up process for small teams covers the routine step by step.
Use public storm information carefully
The National Weather Service notes that storm reports remain preliminary until they are certified in Storm Data. Read the National Weather Service storm-report guidance before treating a public report as more than area-and-date context.
A public report adds area-and-date context to an office record. It does not establish that a particular property was damaged - the inspection determines the condition of a specific roof. A hail report two ZIPs over says nothing about Mrs. Callahan's roof.
That distinction matters in the office as much as in homeowner communication. Keep the report factual, never turn it into a coverage promise, and let the inspection do its job.
What a post-storm intake board should not decide
A quick intake is not a roof diagnosis, a coverage decision, a dispatch instruction, or a promise that a homeowner has a claim. It never replaces an inspection, the company's safety procedure, or clear emergency instruction when someone is in immediate danger - if there is water coming through a ceiling onto a live electrical panel, that is a 911 call, not a follow-up record.
The board's job is narrower and honest: keep every request owned while the day gets crowded.
Start with the request path you already own
Before adding another lead source, test the request path you already pay for. Submit a request through the link on your website, Google Business Profile, ads, or QR code. Then check whether the homeowner context arrives intact, whether someone owns it, and whether the next action is visible to the office.
Kaldwick gives a roofing team one visible place to keep the request context, ownership, and next action clear when the office gets busy. It does not replace an inspection or decide the job for your team.
Frequently asked questions
What should a roofing office capture after a storm?
The homeowner's own description, the property ZIP, the requested service, callback details, a named owner, and a written next action. Keep those facts separate from any inspection conclusion or coverage decision.
Does a hail report mean a roof was damaged?
No. A public hail report gives area-and-date context - not proof that a specific property was damaged. The inspection confirms the actual condition of the roof.
What makes a storm request handoff clear?
The record shows what the homeowner asked for, who owns it now, what happened last, and what the office agreed happens next. A shared inbox alone does not make those things clear.
Can a spreadsheet handle post-storm roofing requests?
For a small team, yes - if it preserves the request context and someone keeps ownership, last action, next action, and outcome current. The tool matters less than not letting a request become an unowned note.