Storm Season Playbook: Intake to Invoice Without Chaos

A storm does not create new problems for a roofing company. It compresses months of normal problems into about ten days: the phone rings off the hook, every lead feels urgent, inspections stack up, adjusters run behind, and the paperwork that was "a bit behind" in a normal week becomes the reason jobs stall and checks arrive late. The companies that come out of storm season ahead are not the ones that worked the longest hours — they are the ones whose intake-to-invoice flow held up at ten times the volume. This playbook walks that flow stage by stage. For the claim mechanics themselves — the adjuster meeting, documentation, and supplements — see our guide to working insurance claims without the chaos; this post is about keeping the whole pipeline moving while the surge is on.

Before the storm: get the board ready

The worst time to design your system is the morning after the storm, with forty voicemails waiting. Do the setup while the weather is quiet. Every open job should already sit in one visible stage of your pipeline — Lead, Prospect, Approved, Completed, Invoiced, Closed — with no undecided estimates rotting in a rep's notebook, because a dirty board going into a surge comes out unreadable. Decide in advance who owns intake when the phones light up, who books inspections, and who can answer a homeowner's "what is happening with my claim?" without asking three other people. Storm season does not forgive single points of failure: if the answer to any of those questions is one person's memory, that is the first thing to fix.

Intake: every lead becomes a record the day it arrives

In a normal week, a lead scribbled on a windshield note might survive until Friday. In storm week, it will not. Every inquiry — door knock, call, referral, form fill — becomes a job record the same day, before anyone climbs anything. Capture the same fields every time, while the homeowner is in front of you:

• Homeowner name, phone, and the property address — one record per property, even if the owner calls twice
• What was reported or seen: missing shingles, active leak, interior water, tree damage — in the homeowner's situation, not just "storm damage"
• Insurance status: claim already filed or not, and the carrier and claim number if they have one
• The inspection date and time promised — a specific appointment, not "we'll get out there"
• Where the lead came from, so you know later which storm work actually paid

That discipline is what makes speed possible. The first company to inspect usually writes the estimate, and the first company to answer a status question keeps the job. Neither happens when half the week's leads live in call logs and text threads.

Triage: work the order, not the noise

Not every roof in a surge is equally urgent, and treating them as if they were is how crews burn a week on the loudest callers while a quiet homeowner with water coming through a ceiling waits. Triage openly, on the board: active leaks and interior water first, damage that will get worse with the next rain next, then inspections in the order they were promised. The point of triage is not just fairness — it is that anyone in the company can look at the pipeline and see why a job is where it is. When a homeowner calls for an update, the answer should take ten seconds because the stage and the next step are written on the record, not because the right person happened to be in the office.

Inspections and documentation: build the evidence file once

Storm documentation does double duty: it sells the job to the homeowner and it proves the job to the carrier. Photograph every slope and every elevation, gutters, siding, windows, and any interior leaks — more than feels reasonable, dated and attached to the job record the day of the inspection, not sitting in a camera roll waiting to be sorted. A captioned photo report built from those photos is what you hand the homeowner and what you hand the adjuster. Build that file once, properly, at inspection time. Rebuilding it three weeks later from three people's phones — while a supplement is pending on exactly those photos — is where storm margins quietly leak away. The fields those photos support on the estimate itself are laid out in our roofing estimate template.

Estimates, adjusters, and supplements: track the claim like a job

Get the branded estimate out fast — same day or next day — even while the claim is young; an estimate in the homeowner's hands is what makes your company the one shepherding the claim instead of a competitor. Then track the claim on the job record with the same fields visible at all times: claim number, carrier, adjuster name and phone, date of loss, approval status, and supplement status. Supplements are normal on storm work, not exceptions: code upgrades, decking replacement, and extra flashing show up on job after job. Track each one as its own line — what was requested, when, for how much, and whether it was approved — because at storm volume, "the supplement is being handled" with nobody's name on it means it is not being handled at all.

Approved is not scheduled: run both clocks

A storm job lives on two clocks: the insurance clock — approvals, supplements, depreciation — and the production clock — materials, crew scheduling, and the install itself. The classic storm-season failure is a job that sits in Approved for weeks: the claim moved, the homeowner signed, and production never got scheduled because the handoff lived in a hallway conversation. The Approved stage is the handoff, and it only works if everything production needs is already on the record: the scope, the measurements, the materials, the property details, and the documentation. If sales has to be chased for any of it, the handoff is a rumor. Look at your board every day during a surge and ask one specific question: which approved jobs have no production step attached yet? That list is your real backlog, whatever the approval count says.

Completed to invoiced to closed: finish the paperwork at surge pace

The roof being on is not the job being done. Final walkthrough, completion photos on the record, warranty details written down, and the invoice out — while the crew is already on the next roof. Storm season punishes slow invoicing twice: the pile at the end of the surge is enormous, and details that were obvious in week one are archaeology by week six. The same goes for money already invoiced: what is outstanding, and what is aging, is one of the five numbers a roofing owner should check every Monday in a normal week, and it matters double when a dozen storm jobs are waiting on final checks at once. A job is Closed when it is paid in full — and those closed storm jobs become next season's referral list, so the record is worth finishing properly.

The daily rhythm that keeps the surge honest

You do not need a war room. You need fifteen minutes with the board every morning of the surge, reading the same five piles:

• New leads with no first contact yet — yesterday's intake is today's inspection list, or it is a competitor's
• Inspections booked for today, and who owns each one
• Estimates sent and still undecided — counted, dated, and owned, not a feeling
• Approved jobs with no production step scheduled
• Jobs invoiced but not yet paid, especially anything aging past its terms

Every one of those piles is just a pipeline stage counted honestly. That is the whole playbook, really: one record per job, the same fields every time, both clocks visible, and a daily look at the piles that stall. GableFlow is built around exactly that shape — the six-stage pipeline (Lead → Prospect → Approved → Completed → Invoiced → Closed) with the branded estimate, photo report, documents, claim details, invoice, and payments on the same job record, and team roles (owner, admin, manager, and user) so office, sales, and field all read the same truth during the surge. Because seats are unlimited on the flat $40/month pricing, the extra hands storm season demands can all be on the board without the bill changing — every feature included, with a 7-day free trial. See the full workflow on our features page, and if your current surge is still living in a spreadsheet, our breakdown of roofing CRM vs. spreadsheets: when to switch runs the honest test for whether it will survive the next one.