Getting Your Office Ready for Storm Season Before It Starts

Almost nothing about a busy season gets decided during one. By the time the weather has turned, a roofing company is running whatever arrangements it already had, and the only real question is whether those arrangements were chosen deliberately in a quiet month or accumulated by accident over several loud ones.

The office does not scale the way the crews do

A company that wins more work than usual can put more people on roofs. That is a solved problem: it costs money, it is unpleasant, and it works.

The office half has no equivalent move. There is no version of the administrative work that can be doubled in a fortnight, because most of it is not a task that can be handed to a stranger — it is a set of small judgements that live in whoever has been making them. More work arriving does not create more of that person.

So the two halves of the company respond to the same event on completely different timescales. Production adjusts in days. The office adjusts in months, or it does not adjust, and the difference between those two outcomes was settled long before the busy period began.

Severe weather is a matter of record, not of recollection

It is worth knowing that the events themselves are documented. NOAA’s National Centers for Environmental Information maintains a public record of severe weather events, entered event by event, with a documented publication lag and a version history — so an event has an official description that is not anybody’s memory of it.

That is genuinely useful when a company is reconstructing a period afterwards, or when two people remember a week differently. It is also a reminder of the shape of the thing: severe weather does not arrive as a general increase in business. It arrives as discrete events, in particular places, on particular days, and the administrative consequences land in a lump a few days behind each one.

Planning for a general increase produces vague preparation. Planning for a lump that arrives without notice produces specific preparation, and specific preparation is the only kind that survives contact.

The number that gets quoted, and why it is not in this guide

Somebody will tell you that a busy season is worth a particular multiple of an ordinary one, or that a company should expect a given rise in call volume after a significant weather event. Those figures circulate confidently and they are not sourced to anything.

No public dataset records them. Nobody publishes call volumes by trade, and the revenue effect of a weather event on a roofing company depends on the company’s size, its area, its existing pipeline and how many competitors arrived at the same moment. The figures in circulation are recollections of particular companies in particular years, repeated until they acquired the texture of a statistic. They are usually quoted by somebody selling readiness.

So there is no figure here. What can be said honestly is directional and considerably more useful: the administrative load rises faster than the production load, it rises first at the point of contact, and it stays elevated for longer than the work does, because the paperwork outlives the roof by weeks.

Decide the answering arrangement while it is boring

The phone is where a busy period is won or lost, and it is the first thing to break because demand for it rises before anything else does.

Most companies have an arrangement that is not really an arrangement: calls divert to whoever is nearest a phone, which in practice means the owner, including at seven in the evening and on a Saturday. That works at ordinary volume and it stops working precisely when the calls start mattering most.

Choosing something different is not difficult, but it takes a few weeks to settle, and those weeks have to happen while nothing is going on. Whether the answer is a rota, a service, or a properly configured set of hours with somebody covering the edges, the decision is cheap in a quiet month and unavailable in a busy one.

Write down what a call has to capture

The second thing worth having in advance is a fixed shape for what an incoming enquiry produces.

Experienced people ask good questions. That is not the problem. The problem is that what they heard stays with them — in their memory, or in a note on a phone — and a company under pressure needs it somewhere a second person can act on without a conversation. A short, fixed intake shape is not a script for the person answering; it is a guarantee about what exists afterwards.

A company that discovered this the hard way had a genuinely good office manager who took every call herself and knew every job. When a run of bad weather put four days of work into one, she was still answering well, but three people were now waiting on things only she could tell them, and she spent the week being interrupted for information rather than collecting any more of it. Nothing about her performance had declined. The company had simply run out of the one thing it had never written down. Getting the enquiry into a shared record the first time is what removes that ceiling, and it has to be habitual before the ceiling is reached.

Agree what you will turn away

A company with no stated limit does not end up taking everything. It ends up taking whatever happens to arrive at a moment when somebody has capacity, which is a worse filter than any rule anybody would have written.

The useful limits are about shape rather than quantity: how far out, what kinds of work, and whether a job depends on one particular person being available. Those questions are answerable while calm. They are not answerable at speed with somebody on the phone.

Writing them down does something a conversation does not. It lets a person who is not the owner say no on the company’s behalf, which is the whole point — a limit only one person can apply is not a limit, it is another thing that routes through the owner.

Fix the parts of the record that are already awkward

Whatever is mildly annoying about the office in a slow month becomes structural in a busy one. A file naming habit nobody quite follows, a place where two people record the same thing differently, a step that only works because somebody remembers to do it — these are tolerable at ordinary volume because there is slack to absorb them.

Volume removes the slack. Nothing new breaks; the existing awkwardness simply stops being survivable. So the honest preparation exercise is not imagining a crisis. It is listing the things that are currently irritating and fixing two of them, because those are the things that will fail.

This is also the argument for doing the unglamorous document and filing work before it is urgent. Nobody has ever done it during a busy period.

Tell the crews how the office is going to work

The preparation that gets skipped most often is the internal half: telling everybody who is not in the office what the office is going to do.

It sounds like a courtesy and it is not. During a busy stretch the people on roofs are the ones generating the administrative work — a change on site, a material shortfall, a customer question answered in a driveway. If they do not know where that information is supposed to go, it goes wherever it went last time, which is usually a message to whoever they get on with best. Half the office overload in a busy month is not volume at all; it is the same fact arriving three times through three channels and having to be reconciled.

A short conversation before the season fixes most of it. Where does a change get recorded. Who does a crew tell when a job will not finish today. What does somebody do with a question they cannot answer standing in front of a customer. None of that is difficult, and all of it is unteachable once the schedule is already moving every hour.

What to actually do this month

None of the above requires a project. It requires four decisions made while nothing is wrong: what happens to a call outside hours, what an enquiry has to produce, what the company will not take on, and which two existing irritations get fixed.

A company that has made those four decisions meets a busy season with the same people and the same software and comes out of it in a completely different condition to one that has not. Where the work eventually goes — kept in-house, spread across the team, or run by a desk outside the company — matters far less than whether it was decided in advance. The rest of this cluster is about what happens once the work has already arrived; this is the part that is still cheap.