Everyone Wants the Same Week Off: A Fair Rule for Holiday Time-Off Requests

Sometime in the next few weeks, the first request will arrive. Someone wants the last week of December off — family is flying in, or they're flying out, or they simply want the week everyone else wants. On a small team, that first request is easy to approve. So is the second. The third is where it gets hard, because now approving it means the business is closed for a week nobody decided to close, and denying it means telling someone their plans matter less than a colleague's.

Most small companies settle this the same way every year: by accident. Whoever asked first gets it, or whoever asked the owner directly, or whoever has been around longest, or whoever complains most effectively. None of these is a rule. Each of them feels like favoritism to the person who loses. The fix is to decide the rule before the requests arrive, and to make it visible enough that people can plan around it.

Start from coverage, not from requests

The first question isn't who wants what. It's what the business needs during the holiday weeks. Does anyone need to be reachable for customers? Is there payroll to run, inventory to receive, a system that needs someone watching it? For each week, write down the minimum coverage: which roles, how many people, and whether “covered” means working normal hours or being reachable if something breaks.

Sometimes the honest answer is that the business can close, or nearly close, for a week. If so, decide that early and announce it — a planned shutdown is a gift; an accidental one is a risk. If the answer is that someone has to be there, you now know how many slots of time off actually exist, which is the number every fair rule has to work within.

Pick the rule, and write it down

There are a handful of workable rules, each with a real trade-off:

• First come, first served. Simple and easy to explain, but it rewards whoever plans earliest and it tends to hand the same people the same weeks year after year.
• Seniority. Predictable, and it rewards tenure — but on a small team it can mean newer people never get the popular weeks, which is its own retention problem.
• Rotation. Whoever had the popular week last year goes to the back of the line this year. It's the rule most people experience as fair over time, and it only needs one thing to work: a record of who got what.

Many teams combine them: a request window, then rotation as the tiebreak when requests collide. Whatever you pick, put it in writing in the time-off policy, and apply it the same way to everyone — including the people who are easiest to say yes to.

Open a request window

First-come-first-served has a hidden flaw: it turns the process into a race, and the race is won by whoever happens to hear about it first. A request window removes the race. Announce a date by which holiday requests are due, collect them all, decide them together against the coverage plan, and tell everyone the outcome on a date you've also announced. Requests that arrive after the window are handled from whatever's left.

Deciding everything at once also lets you see the collisions whole. Two people want the same week? Maybe one of them would be just as happy with the week after, if asked. You can only have that conversation if you're looking at all the requests together rather than approving them one at a time as they land.

Check the obligations before you decide

Two checks belong in every holiday decision. First, “the holidays” aren't the same days for everyone. People observe different religious holidays at different times of year, and federal law requires employers covered by Title VII to reasonably accommodate religious observance unless it would cause undue hardship — a standard the Supreme Court strengthened in Groff v. DeJoy. A rule that quietly treats one holiday season as the only one that counts can create a problem you didn't intend.

Second, check your own policy and your state's rules on paid time off — accrual, carryover, and what happens to unused time differ by state and by policy. If people are rushing to use time before it expires, that's a policy design issue to fix on your compliance calendar, not something to sort out one request at a time in December.

Say no in a way people can accept

Some requests will be denied. The difference between a denial people accept and one they resent is almost entirely in how it's explained. Say it in person or at least directly, not by letting a request sit unanswered. Name the rule that decided it. Offer what's available — the adjacent week, a shorter stretch, first place in line next year under the rotation. And if someone is working through a holiday so others can be off, acknowledge it concretely; people remember whether that was noticed.

A denied request is also a useful signal. If the same person keeps losing out, or someone mentions they're “never able to take time off,” that belongs in your next stay interview. Time off is one of the quieter reasons people start looking elsewhere.

Keep the record for next year

Rotation only works if someone remembers who got the popular weeks. Write it down: for each holiday period, who was off, who covered, and any promises made about next year. It takes a few minutes, and it turns next fall's decisions from a negotiation into a lookup.

The bottom line

Holiday time off feels personal because it is. That's exactly why it needs a rule rather than a series of judgment calls. Start from the coverage the business actually needs. Choose a rule — ideally a request window with rotation as the tiebreak — and write it down. Decide requests together, check accommodation and policy obligations, and explain every no with the rule that decided it and what's available instead. Then keep the record, so next year starts from fairness instead of memory.

— Tom