When Two People Want the Same Week Off

A manager opens two requests. Both are for the same week in August. The team is four people and at least two need to be around. Both requesters have the balance. Both have a reason. Neither request is unreasonable.

There is no clever answer here — one of them is getting a no. The question is whether that no arrives as a policy or as a judgment call, because those two things feel completely different to the person receiving them, even when the outcome is identical.

The Rule Has to Exist Before the Conflict

Most teams do have a rule. It is just undocumented, applied inconsistently, and known only to the manager. When the conflict arrives, the manager reaches for whichever version feels defensible in the moment — first come first served, or seniority, or who took the last good slot, or who asked more politely.

Each of those is a legitimate tiebreaker. Choosing among them after seeing the two names is the problem. That is what makes an approval feel personal, and it is what generates the "she always gets the summer weeks" conversation that quietly poisons a team.

Write the rule down. Publish it where people book. It does not need to be elaborate, and it will not make anyone happy about being declined — but it converts a verdict into an outcome, which is a much easier thing to accept.

Pick One Primary Rule

First come, first served is the most common and the easiest to defend, because it is fully observable: whoever submitted first wins, and everyone can see their own timestamp. Its weakness is that it rewards planning ahead in a way that compounds — the same organised people win every year — and it punishes anyone whose plans depend on someone else's schedule.

Rotation fixes the compounding. If Priya had the last week of August last year, she is behind Marcus this year. It requires you to keep a record, which is trivial if your leave history is in one place and painful if it is in email.

Business criticality is the honest one for teams where the work genuinely differs: whoever is holding the release, the client, or the on-call rotation stays. It is defensible right up until it always lands on the same person, at which point you have a staffing problem disguised as a leave problem.

Most teams end up with first-come-first-served as the primary rule, rotation as the tiebreaker for genuinely contested peak weeks, and business criticality as a stated override that is used rarely and explained when it is.

Define Coverage as a Number

"We need enough people around" is not a rule; it is a feeling. "At least two of the four of us, and at least one who can handle a production incident" is a rule. It can be checked before approving instead of argued about afterwards.

The exercise is worth doing per team rather than per company, because the shape differs. A support rota has a hard floor. A research team may genuinely be able to go to zero for a week in August. A team of one has no coverage rule at all, only a handover plan.

Once the number is written down, the approval decision mostly makes itself, and the manager stops being the person who says no and becomes the person who reports what the constraint is.

Blackout Periods, Used Sparingly

Some organisations have weeks where leave genuinely cannot happen: a retail peak, a fiscal close, a planned migration weekend. Naming those periods in advance is fairer than declining requests one at a time, because it lets people plan around them a year out rather than discovering the constraint when they have already booked flights.

Two rules of thumb keep blackouts from breeding. Publish them at the start of the leave year, not when someone asks. And keep them genuinely rare — a calendar with six blackout periods is not a coverage policy, it is a company that has decided its people cannot take leave, and it will show up in retention long before it shows up in a survey.

Make the Conflict Visible Before It Is Submitted

The best version of this problem is the one that never reaches the manager. If an employee can see, while they are choosing dates, that two teammates are already off that week, a good number of conflicts resolve themselves — people shift by a few days, or split a week, or simply pick the adjacent one.

That is the entire argument for a shared team calendar sitting next to the booking form rather than in a separate system nobody opens. It turns a hidden constraint into an obvious one at the exact moment it is actionable. Our own staff holiday planner view exists for this reason: the request form and the team's booked leave are the same screen, so who is already off is not something you have to go and find out.

There is a privacy consideration worth being deliberate about. Some organisations show leave type on the shared calendar, which means everyone can see who is on sick leave or parental leave. Most should not. Showing that someone is unavailable is a coverage fact; showing why is personal, and the distinction is worth configuring rather than defaulting.

Say No Properly

When you do decline, three things make it land better, and none of them are about tone.

Cite the rule, not the person. "Coverage floor is two and Marcus booked on the 3rd" is a fact. "I need you here that week" is a preference, even when it is true.

Offer the adjacent option in the same message. Declining without a counter-proposal makes the employee do the work of restarting. Declining with "the week before is completely clear" usually ends the conversation there.

Do it quickly. A request that sits for two weeks and then gets declined is worse than one declined the same day, because the employee has been planning in the meantime. If your approval queue routinely runs long, that is the actual problem — the tiebreaker rule is a distraction from it.

The Underlying Point

Overlapping requests are not a sign that anything has gone wrong. They are what happens when a team of finite size wants time off during the finite number of weeks that are pleasant to take it. You cannot design them away.

What you can do is make the constraint visible, the rule public, and the answer fast. Do those three and the same August conflict that used to generate a week of quiet resentment becomes a two-minute conversation about moving a booking. The decision does not change. The experience of it does.