For most of the year a restoration shop knows its own size. There is a crew, and you know it by name. You know who drives what, who is certified for which work, who is steady in a flooded basement in the small hours of the morning. The company is a known quantity, and the insurance program underneath it is built around that known quantity.
Then a named storm makes landfall, and inside a week the business is somebody else. The phone does not stop. Work arrives faster than the crew you have can touch it, so you do the only thing the moment allows: you get bigger. You bring on hands. You put more trucks on the road. You send a crew to a catastrophe several states over because that is where the work is. The shop that ran lean all year is, briefly, a much larger company.
That growth is the business. Nobody in restoration apologizes for surging — the surge is where the year is made. But the thing worth saying out loud, because it is the thing that gets lost in the rush, is that the exposure grows in lockstep with the crew, and it grows along the same lines the crew does. A bigger payroll. More drivers. More outside help whose paperwork nobody had time to check. The shop that swells for a season swells its risk with it, and the difference between a good storm season and a bad claim is almost never the quality of the work. It is whether the record kept up.
The season that swells the business
Surge work has a shape every restoration owner knows. It is quiet, and then it is not, and the not-quiet part does not build gradually — it lands. A single weather event can turn a full week of work into a full month of it overnight, and the only way to meet that is capacity you did not have the week before.
So the honest picture of a restoration company is not one size. It is two: the size it is most of the year, and the size it becomes for a few weeks when the weather hands it more than it can hold. The insurance program has to understand both, because a program built only around the calm months is describing a company that briefly stops existing every time a storm makes the news.
None of this is a problem to be solved. It is a feature of the trade to be planned for. The shops that handle it well are not the ones that avoid surging — they are the ones that surge without losing track of what they became while they did it.
The crew you did not have last month
The fastest way to get bigger is to add people, and storm season is when restoration shops add them fastest. Some are seasonal hands you have used before. Some are new. Some are borrowed from another shop, or brought in by a subcontractor you barely know.
Every one of them is payroll, and payroll is the number a great deal of the program is measured against. A workforce that swells for the season and shrinks afterward is not a problem in itself — it is a normal fact about how the business runs. It becomes a problem only when it is a surprise, when the insurer’s picture of the company is the quiet-months version and the audit finds the storm-months reality. The fix is not to hide the surge. It is to treat it as the known thing it is and to keep the payroll records clean enough that the audit is a formality.
The coverage consequence of scaling a crew — how the injuries of those new hands are actually answered for — belongs to the workers-compensation page, and this post does not re-teach it. What belongs here is the staffing truth underneath it: every person you add is a person the program now has to account for, and the moment to get that right is while you are adding them, not at audit.
The crew working a loss several states away
The other way restoration companies grow during a catastrophe is by traveling to it. The work is where the storm was, and the storm was not always at home. So a crew loads up and drives to a loss several states away, and now the company is operating somewhere it does not usually operate.
That crew carries every exposure the local crew does, plus everything that comes from distance. The rules that govern an injured worker can turn on where the work is actually performed, not simply where your business is based — which is a coverage question the workers-compensation page addresses, not this one. And the vehicles are logging long unfamiliar miles in the conditions a storm leaves behind, which is the whole reason a surge is also a road-risk event.
Real-World Scenario: A shop sends a borrowed crew and a run of trucks to a coastal county after a hurricane, a long way from home. The work goes well. Weeks later, after everyone is back and the season has quieted, a question arrives about an injury one of the traveling hands says happened on that job — and the shop discovers it cannot cleanly say who that person was working for, because in the rush he had been treated as a subcontractor’s helper by the field lead and as a direct hire by the office. Nobody did anything malicious. The work was good and the loss was real. But the company grew faster than its own records, and the gap that opened up was not in the drying or the demolition. It was in the paperwork that was supposed to describe who was standing on that site.
That scenario has no bad actor in it, which is exactly why it is the one to plan for. The exposure was not created by poor work. It was created by growing faster than the file that is supposed to describe the company.
Employee or subcontractor, decided in a hurry
The scenario above turns on the single most consequential staffing question in a surge: is this person your employee, or an independent subcontractor? It is a real distinction with real weight — it drives who answers for their injuries, their taxes, and their coverage — and it does not turn on what you call the arrangement or what a hastily signed page says. It turns on how the relationship actually works.
The trouble with a surge is that it is the worst possible moment to decide this, and it is exactly when shops end up deciding it by accident. A helper shows up with a subcontractor, works alongside your crew, takes direction from your field lead, and is paid — and now the question of what he was is genuinely unclear, which is the same as saying it will be answered by someone else, later, in a way you did not choose.
The way out is to make the decision before the season, not during it. This is a question for your accountant and your attorney: how you bring people on, what documents exist before they lift anything, and where the line sits between a sub who is genuinely independent and a worker who is yours in everything but name. Settle it in the calm months, so that when the storm lands you are executing a plan instead of improvising a classification job by job.
The certificate that has to keep up
When the outside help is genuinely a subcontractor, one piece of paper does most of the work of keeping the exposure where it belongs: the certificate of insurance. It is the evidence that the sub actually carries the coverage they say they carry, so that their injuries and their damage answer to their own program rather than rolling back onto yours.
In a surge, the certificate is the first discipline to slip and the most expensive one to skip. The sub is standing in front of you, the work is waiting, and asking for a document feels like friction the moment cannot afford. But the friction is the point. No certificate on file, no work — no exception for the storm, no exception for the sub you have used before, no exception for the crew a friend vouched for. The few minutes it takes to collect one is the cheapest insurance in the whole operation, and the cost of not collecting it only appears later, when something has gone wrong on that sub’s watch and there is nothing in the file to stand behind it.
The same rule extends to the trucks. A surge puts more vehicles and more drivers on worse roads than any other stretch of the year, and the exposure that creates is real; the way the coverage responds to it lives on the commercial auto page rather than here. The staffing point is narrower and it is this: every driver you add during a surge is a driver the program now carries, and knowing who was behind the wheel of which vehicle is part of keeping up with what the company became.
When the crew goes home
The season ends the way it started — fast. The extra hands move on, the borrowed trucks go back, the traveling crews come home, and the company returns to the size it knows. It is tempting to treat that as the end of the exposure, and it is not.
A claim does not respect the calendar. An injury, a dispute, a damaged property can surface long after the last piece of drying equipment has been picked up, and when it does, the only thing that answers it is the record you kept while everyone was still on site. Who was on payroll and who was a subcontractor. Which certificates were collected and from whom. Who drove what. Where the traveling crews actually worked. Assembled in the moment, those facts cost almost nothing. Reconstructed from memory a season later, they are close to worthless — and they are precisely the facts a late claim will ask about.
So the discipline that matters is not visible during the surge, when everything is motion. It is visible afterward, in whether the company can still describe the larger thing it briefly was. That capacity is what separates the shops that grow into their storm seasons from the ones that get hurt by them.
<rect x="26" y="58" width="150" height="86" rx="9" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="101" y="92" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Off-season shop</text>
<text x="101" y="114" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">A crew you know</text>
<text x="101" y="130" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">by name</text>
<text x="350" y="94" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">a named storm lands</text>
<path d="M 182 108 L 516 108" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#surge-arrow)"/>
<rect x="524" y="52" width="150" height="98" rx="9" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="599" y="86" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Surge company</text>
<text x="599" y="108" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">A larger business,</text>
<text x="599" y="124" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">built in a week,</text>
<text x="599" y="140" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">gone by fall</text>
<rect x="40" y="168" width="620" height="46" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="350" y="196" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">More hands on payroll — the base the program is measured against</text>
<rect x="40" y="222" width="620" height="46" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="350" y="250" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">More drivers on unfamiliar roads in what the storm left behind</text>
<rect x="40" y="276" width="620" height="46" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="350" y="304" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">More outside help arriving faster than the certificate file</text>
<rect x="60" y="342" width="580" height="66" rx="10" fill="#C7683F" stroke="#12703F"/>
<text x="350" y="372" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="14" font-weight="600" fill="#1A1A1A">The crew and the exposure scale at the same speed,</text>
<text x="350" y="394" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="14" font-weight="600" fill="#1A1A1A">along the same lines — so the paperwork has to keep up</text>
<text x="350" y="436" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">The crew goes home when the season ends. The exposure does not.</text>
The one habit that carries a restoration company through a hard season is not a bigger crew or a faster response. It is the boring discipline of letting the file grow as fast as the business does — classifying people before the storm rather than during it, collecting a certificate before the work rather than after, and writing down who was where while they were still there.
If you want the program underneath your restoration business read against how large you actually get when the weather turns — the surge payroll, the traveling crews, the trucks, the subs — ask us for a quote.