The Skeleton-Crew Runbook: Half the Team, Same Promises

The stretch between Christmas and New Year's Day runs on whoever drew the short straw: one engineer, one support rep, an executive checking email between leftovers. The customers, meanwhile, were promised the same service as any other week.

A skeleton crew is not a problem. An unbriefed skeleton crew is. The runbook that makes the week work fits on one page, and someone has to write it before the out-of-office messages start.

Key takeaways

• A skeleton crew works when everyone knows what the crew can and cannot promise.

• The runbook names the crew, the coverage, the escalation path and the explicit pauses.

• Escalation during a thin week needs names and phone numbers, not a mailbox.

• Tell customers what the week looks like before they find out the hard way.

• The debrief in January is where next year's runbook gets better.

Step 1: Name the crew and their actual hours

Write down who is working which days, and when they are genuinely reachable versus nominally around. The gap between those two is where thin-week incidents go to grow.

Half the value of the runbook is forcing the honest version of this list in advance, instead of discovering it ticket by ticket.

Step 2: Set the service level the crew can keep

A skeleton crew cannot run the full menu. Decide the week's real service level: urgent issues answered same day, routine ones queued for January, maintenance and releases paused entirely.

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

The pause column is the part customers need to hear before the week starts.

Step 3: Write the escalation path with names on it

Thin weeks break when the one person on duty hits something over their head and the escalation is an alias nobody reads. The runbook names two humans, in order, with phone numbers, for the things that cannot wait: the outage, the security alert, the angry top customer.

The holiday call tree test is how you verify those numbers before the week, and the incident communication matrix covers who hears what if the thin week turns into a real one.

Step 4: Tell customers the shape of the week

A short note in mid-December does the work: our team is light between the holidays, urgent issues get us fastest this way, everything else gets a thoughtful answer in January. Customers plan around honesty. What they punish is discovering the pause by silence.

Step 5: Debrief in January while it is fresh

Fifteen minutes in the first week back: what broke, what held, which pauses nobody noticed and which caused pain. Next year's runbook starts from those notes instead of from memory, and the skeleton week gets quieter every year.

Frequently asked questions

Does a small company really need a runbook for this?

The smaller the company, the thinner the week, and the more the week depends on one or two people knowing the plan. The runbook is one page precisely because the crew is small.

What if something serious happens in the thin week?

Then the incident plan and its call tree take over, and the runbook's job was to make sure the right people could be reached. Thin staffing is a reason the escalation path matters more, not less.

Should the skeleton week apply to security monitoring?

Monitoring and alerting continue; what pauses is change. The thin week is when you want the fewest moving parts, which is why releases and maintenance belong on the pause list.

Who writes the runbook?

Whoever runs operations day to day, reviewed by one executive. Thirty minutes of writing, one read-through with the crew, done.

A Defensible Next Step

Before the out-of-office messages go up, write the one page: the crew, the real service level, the two escalation names, the customer note. Book a Decision-Clarity Call if you want help pressure-testing the week.