When Weather Closes the Office: The Minimum Operating Set

The forecast says the storm arrives Monday night and the office will be closed Tuesday. Most companies treat that as a calendar problem. Customers experience it as a service problem: the phones, the orders, the deadlines do not check the weather.

The businesses that handle closures well made one decision in advance. They know their minimum operating set: the small list of things that keep running, who runs them from wherever they are, and what is explicitly allowed to wait.

Key takeaways

• A closure is a service decision, not a calendar entry.

• The minimum operating set names what keeps running, at what level, and who runs it.

• Everything not on the list gets a communicated pause, not a silent failure.

• Remote fallback only works if it was tested before the storm.

• The decision belongs to leadership, made in calm weather.

Step 1: List what customers would notice first

Start outside-in. If the office closes for two days, what do customers, patients, clients or members notice by lunchtime on day one? The unanswered phone, the unshipped order, the unprocessed payment, the appointment nobody confirmed.

That list, not the org chart, defines what the minimum operating set must cover.

Step 2: Define the minimum level, not the full service

For each item on the list, decide the smallest version that keeps faith: phones forwarded to two working cell numbers, orders processed but shipping notices delayed, urgent requests handled and routine ones queued.

This fictional example shows the set. It is an illustration, not a prescription.

The pause column is what makes the promise honest. Customers forgive a stated delay; they do not forgive silence.

Step 3: Confirm the fallback actually works from a kitchen table

The plan fails on details: the phone forwarding nobody has tested from home, the system that needs the office network, the login that only works from the front desk. Test each fallback once, from outside the office, before the season starts. Setting the restoration order covers the judgment calls when the closure lasts longer than a day.

Step 4: Decide who declares the closure

Someone named decides, by a stated time the night before or the morning of, using a stated rule. Without that, the company holds a slow-motion vote by text message at 6 a.m. while employees guess whether to start the commute.

The declaration includes the message to staff and the message to customers, both drafted in advance.

Step 5: Write it on one page and keep it current

The minimum operating set fits on one page: the list, the levels, the people, the declaration rule, the message templates. It lives with the response plan and gets a five-minute review each fall.

The Maine winter connectivity guide covers keeping people connected when the storm takes the power and the broadband too.

Frequently asked questions

Isn't this just a business continuity plan?

A narrow, practical slice of one. Full continuity planning covers major disruption; the minimum operating set covers the ordinary two-day closure that actually happens every winter. Small scope is what makes it get written.

What if we are already mostly remote?

Then the question shifts to power, connectivity and dependencies: who loses their home office in the storm, which cloud services the fallback depends on, and what customers experience. The outside-in list still applies.

Who should own the minimum operating set?

One operations-minded leader who can say what runs and what waits. The list fails when it is maintained by committee.

How is this different from the incident response plan?

The response plan is for attacks and failures. This is for weather and closures. They share contacts and discipline, but a planned closure is a service decision made in daylight, not an incident.

A Defensible Next Step

Before the first storm watch, write the one page: what keeps running, at what level, who runs it, and what customers will be told. Book a Decision-Clarity Call if you want a working session to draft it.