NOAA’s August outlook put this Atlantic season at 75% likely to come in below average: seven to thirteen named storms, two to six hurricanes, zero to two majors. Colorado State’s update landed in the same neighborhood: nine, four, one, with a 16% chance of a major hurricane making U.S. landfall.
Through early August the basin had produced two named storms and no hurricanes. By the middle of the month, forecasters were tracking systems again.
If you run restoration work, a below-average forecast is the most dangerous number to plan around, and it’s worth being precise about why.
What the forecast does and doesn’t say
NOAA prints the caveat in the outlook itself: the forecast is for total seasonal activity, not landfall risk. Those are separate questions, and only one of them affects your phone.
A nine-storm season where everything recurves into open water produces almost no work. A four-storm season where one of them parks over a metro area produces a year’s revenue in six weeks. The seasonal count tells you very little about which one you’re getting.
And the calendar hasn’t changed regardless of the forecast. Mid-August through mid-October is the peak of the season every single year, active or quiet. That window is now.
So the practical read is not “it’ll be a light year.” It’s: the same work, compressed into a narrower window, with less warning.
That’s a harder operating problem than a busy season, not an easier one. A steady flow of jobs you can staff up for. A spike you can’t.
Where restoration days actually leak
Programs that route work tend to score three things: contact time, arrival time, and cycle time. Those scores affect standing, and standing affects referral volume.
They get discussed as production metrics, a measure of how fast crews work. Two of the three barely touch production at all.
Contact time is whether somebody saw the assignment and called the homeowner. That’s intake and routing. If it comes in at 7pm and the person who monitors that inbox is at dinner, you lose hours to a notification problem, not a labor problem.
Arrival time is whether the person who called had a truck free and knew it. That’s a scheduling question. When you’re running twelve active files and a surge hits, the constraint stops being trucks and becomes knowing which truck is where.
Cycle time is the whole file, start to finish, and it’s the one that hurts.
Here’s what surprises people who actually break their cycle time into segments: the days rarely leak during mitigation. Mitigation is urgent, everybody knows it’s urgent, equipment is on the floor, somebody is checking readings daily. It runs about as fast as it can run.
The days leak in the handoff from mitigation to rebuild.
The handoff is the critical path
Mitigation wraps. Equipment comes out. The file needs to become a construction project. Scope written, estimate approved, subs lined up, materials ordered, a start date set.
And for three or four days, sometimes longer, it belongs to nobody.
The mitigation lead thinks they’re done, because operationally they are. The rebuild PM hasn’t picked it up yet, because it hasn’t formally landed on their list, because the trigger for it landing is usually a conversation that hasn’t happened. The file sits in a state that looks finished from one side and hasn’t started from the other.
Nobody is doing anything wrong. There’s just a seam in the process, and work falls into seams.
Multiply that across the twenty files sitting in the same seam during a surge and you have a cycle-time number that looks like a production problem and isn’t. Your crews are fast. Your handoff isn’t owned.
Anyone who’s worked through critical path method on a construction schedule will recognize the shape of this immediately. It’s a merge point with no owner, the single most common place a schedule quietly loses a week. We walked through how to find those points on a normal remodel here, and the logic is identical on a restoration file. The dry-out isn’t your bottleneck. The transfer is.
Four things to fix before October
Give the handoff a name and a date. Not a status. Not a folder. A person who owns it and a day it’s due. The single highest-leverage change available to most restoration shops is treating mitigation-complete-to-rebuild-scoped as an assigned task with a deadline, the same as any other line on a schedule, instead of an event that’s supposed to happen on its own.
Assign by person, not by role. “The rebuild team will pick it up” is how files sit. During a surge, a queue with no name attached is a queue that grows. This is a small change that shows up directly in cycle time.
Pre-stage your sub commitments now, not in October. During a surge your subs are getting calls from every outfit in the region. Conversations you have in late August about capacity, rates, and who gets first call are conversations you cannot have when forty jobs land at once. This is the readiness work that actually pays, and it’s cheap right now precisely because the season has been quiet.
Decide the homeowner communication rhythm before you need it. In a surge, client updates are the first thing to get dropped, and they’re the thing that generates the most inbound calls when they stop, which eats the exact hours you don’t have. A homeowner who can see where their job stands doesn’t call to ask. A homeowner who can’t will call twice.
That last one is the compounding problem. Every status call you field during a surge is fifteen minutes not spent scheduling the next file, which extends the next file’s cycle time, which generates more status calls. It’s a loop, and it runs in the wrong direction at the worst possible time.
The compressed-surge math
Say a normal month is fifteen files and a surge month is forty-five.
Your production capacity might handle that with overtime and some sub help. That’s the part everyone plans for. Crews, equipment, drying chambers.
What triples that nobody plans for: intake decisions, assignment decisions, scope approvals, sub confirmations, material orders, homeowner updates, and handoffs. All of it lands on the same two or three people, in the same week, on top of everything else.
That’s the actual failure point in a surge, and it fails quietly. Nothing breaks. Files just sit two days longer at every step, and two days at four steps is eight days on your cycle time. Repeat across forty-five files and your program metrics move, during exactly the period the program is paying the most attention.
None of that is fixed with more trucks.
What being ready actually means
Not “can we handle the volume.” It’s:
When forty jobs land in nine days, does file number twenty-three get assigned to somebody with a name and a date? Or does it sit in a text message until someone remembers it on Thursday?
That question has a yes-or-no answer, and you already know yours. Most shops that have been through a real surge know exactly which files fell through and roughly why, and the reason is almost never that somebody didn’t care.
It’s that during a surge, the systems that work at fifteen files a month, a whiteboard, a group text, one person holding the whole picture in their head, stop working at forty-five. They don’t degrade gracefully. They work, then they don’t, and the transition happens in about four days.
This is the same failure mode that shows up in ordinary construction work when a shop grows past the point its systems were built for, and it carries the same price tag. We’ve written about what those lost days actually cost once you price them out, and on restoration work the number is worse, because cycle time isn’t just margin. It’s your standing, and standing is next season’s volume.
What Relay does about this
The seam is the problem, so the fix is making the handoff a real, owned line of work instead of an event everyone assumes will happen. In Relay, the mitigation-to-rebuild transfer is an activity with a person’s name and a date on it, not a status somebody has to notice. Punch items get assigned by email, so a sub who isn’t in your account still gets routed the work. And the client portal gives the homeowner a live view of where their job stands, which is the cheapest way to stop the status calls that eat the hours you need during a surge.
Use the quiet part
The forecast being below average isn’t a reason to relax. It’s the last window you get to fix the seam before it’s tested.
Sit down with your last five completed files. Pull the actual date stamps: assignment, first contact, arrival, mitigation complete, scope approved, rebuild start, completion. Find the two longest gaps.
It will almost certainly be the mitigation-to-rebuild handoff, and one other spot you weren’t expecting.
That’s your list. Fix those two before the middle of September, and a compressed surge is a good month instead of a bad quarter.
Relay assigns work to a person with a date, cascades the downstream effect when something moves, and gives the homeowner a live view so they stop calling to ask. Try it free for 30 days on the Complete plan at relayconstruct.com. Card up front, $199.99/month when the trial converts.