How to Build a Holiday Coverage Schedule (December Without Chaos)

December goes wrong in a predictable way. Requests arrive in late November, three people want the same week, one has already booked flights, and whatever you decide is going to look like a judgment about who you like most.

All of that is avoidable, and the fix is almost entirely about timing.

The timeline

The single highest-leverage change most small businesses can make is moving the decision from December to October. A decline in October is an inconvenience. The same decline in late November, after flights are booked, is a grievance — and quite often a resignation risk.

Step 1: work out minimum coverage

Not a headcount — a capability count. For each working day in the period, ask what actually has to happen and who can do it.

This table does two things. It tells you the real constraint — usually one or two named people rather than a general shortage — and it gives you a reason you can say out loud. "We need someone who can process refunds and only two of you can" is a fact. "We need enough cover" is an opinion.

It also exposes the single-point-of-failure problem. If Dana is the only person who can run invoicing on 31 December, the coverage plan has revealed a cross-training task, not just a scheduling constraint.

Step 2: pick the tie-breaker before requests open

For the December period specifically, rotating priority is the fairest and the easiest to defend, because the underlying resource — Christmas week — is scarce every single year. First-come-first-served applied to a permanently scarce resource just means the same person wins every year, and everyone notices by year three.

Keep the rotation written down somewhere durable. "You had it last year" is only persuasive if you can show it.

Step 3: publish everything in August

One message, containing:

• The company holiday calendar for the period
• Which days need coverage and roughly how many people
• The tie-breaker rule
• When requests open and close
• When decisions will be communicated

Publishing the rule before anyone requests is what makes the outcome feel like a process rather than a verdict. The identical decision announced in December, without a prior rule, reads as arbitrary.

Step 4: resolve clashes in one pass

When requests close, do the whole period at once rather than approving in arrival order.

1. Lay out the requests against the coverage table
2. Approve everything that does not breach minimum coverage
3. For each remaining conflict, apply the published rule
4. Tell everyone at the same time, including the reasoning

That third step is where the rule earns its keep. You are not deciding; you are applying something you published two months ago.

For anyone declined, follow the pattern in how to deny a time-off request: a checkable reason, an alternative, and priority next time. Then actually record the priority.

Step 5: make the on-duty days worth having

Whoever covers the quiet week is doing you a favor. Some ways to acknowledge it that cost little:

• A day in lieu, taken in January or February when nobody wants time off anyway
• Genuinely light duties — cover means cover, not a chance to catch up on projects
• Clear boundaries on the on-call day: what actually warrants a call, and what waits
• Rotating the unpopular days within the covering group rather than one person absorbing all of them

For non-exempt staff, check whether premium pay applies under your policy or state rules. For exempt staff there is usually no obligation, which makes the day in lieu the practical currency.

The half-week problem

Public holidays that fall midweek generate awkward two-day gaps that nobody wants to work and everybody wants to bridge. Two workable approaches:

Close entirely and account for it. If the business genuinely stops between Christmas and New Year, say so in the company holiday calendar and decide whether those days come out of the allowance. Most companies that close give the days rather than deducting them; deducting a day for an office nobody could attend is a reliable morale cost.

Stay open with a skeleton and accept that it is the least productive week of the year. Fine, provided you have set expectations about what actually gets done.

What does not work is leaving it undeclared. Ambiguity means half the team assumes it is closed and books nothing, the other half assumes it is open and requests leave, and both are annoyed.

Common mistakes

• Opening requests in November. Everything downstream gets harder.
• Approving in arrival order without looking at the whole period, then discovering the last two requests are the ones you cannot cover.
• Coverage as a headcount rather than a capability, so you end up with three people who cannot do the one thing that matters.
• No written rotation record, so last year's fairness is unprovable this year.
• Not declaring the closure position, leaving people to guess.
• Ignoring the balance crunch. December is also when unused balances expire. If carryover is capped and half the team is sitting on a week of unused leave, coverage and carryover collide. Check balances in October, not December — see PTO rollover and carryover.

Seeing the whole period at once

The mechanical part of this — laying every request against every day and spotting where coverage fails — is exactly the part that is painful in a spreadsheet, because a request log tells you dates but not overlaps, and you end up counting rows by hand.

SimplyPTO shows the whole team on one calendar with overlap warnings before you approve, so the October pass takes minutes rather than an afternoon. Start free for up to 10 people, or read overlapping time-off requests for handling clashes the rest of the year.