Leave Clashes: When Everyone Wants the Same Week Off

It is the first Monday back in January. Three of your five developers submit leave requests within hours of each other, all for the same week in late July - the first week of the school summer holidays. They all have young children. They all have flights booked. And you cannot run the sprint without at least two of them.

This is one of the most dreaded scenarios in people management, especially in small businesses where every person's absence is felt. Handle it badly and you create resentment that lasts for months. Handle it well and you build a culture of fairness that makes future conflicts easier to resolve. This guide covers the legal framework, the most common allocation methods, and practical strategies for preventing mutiny while keeping the business running.

What the Law Says

UK employment law gives employers significant discretion to manage when annual leave is taken. Under the Working Time Regulations 1998:

Employees must give notice at least twice the length of the leave they want to take. So for one week off, they should give at least two weeks' notice.
Employers can refuse a leave request on business grounds, provided they give counter-notice at least as long as the requested leave. So to refuse a one-week request, you must give at least one week's notice of the refusal.
Employers can direct when leave is taken (for example, requiring a factory shutdown week) with appropriate notice.
The employer must ensure that every employee can take their full statutory entitlement (5.6 weeks) during the leave year. You cannot keep refusing requests until there are not enough days left in the year for the employee to take their holiday.

The key legal principle is that while employees have a right to their leave entitlement, they do not have an absolute right to take it on any specific date. The employer can legitimately say: "You can have your 28 days, but not all during the same week as your two colleagues."

Discrimination Warning

Be careful that your leave allocation decisions do not indirectly discriminate against protected groups. For example, always giving school-holiday priority to parents over non-parents could constitute indirect discrimination on grounds of age, sex, or marital status. Similarly, always prioritising senior staff over junior staff may disproportionately affect younger employees. Whatever system you use, it must be applied consistently and justified on legitimate business grounds.

The Allocation Methods

There is no single "correct" way to allocate contested leave slots, but there are several established approaches, each with trade-offs. The best choice depends on your company culture, team size, and the nature of the work.

1. First Come, First Served

The simplest and most transparent method. Whoever submits their request first gets the slot. If the team's maximum concurrent absence limit is two, the first two requests are approved and the third is declined.

Pros: Clear, objective, easy to administer, and impossible to accuse of favouritism. Encourages early planning.

Cons: Rewards people who can plan early and penalises those whose circumstances make early planning difficult (for example, parents who do not know their children's school holiday dates until late, or employees waiting on family members' schedules). Over time, the same organised individuals may dominate the popular slots, creating structural unfairness.

Best for: Teams where popular leave periods are not consistently contested by the same people.

2. Rotation System

Contested peak periods (school half-terms, summer holidays, Christmas) are allocated on a rotating basis. If Alice got the first week of the summer holidays last year, Bob gets priority this year, and Carol gets it next year. The rotation is tracked and published, so everyone knows their "turn" in advance.

Pros: Maximally fair over time. Removes the stress of competitive booking. Eliminates favouritism. Makes long-term family planning possible.

Cons: Requires tracking and consistency over multiple years. Can feel rigid and inflexible. Does not account for changes in personal circumstances (a new parent's needs are different from a five-year veteran of the school-holiday wars). May not work well if team composition changes frequently.

Best for: Stable teams with recurring peak-period conflicts, especially where employees have school-age children.

3. Team Discussion and Negotiation

Bring the affected team members together and let them work it out among themselves. Often, what looks like an irreconcilable clash resolves when people talk: Alice discovers she could shift her holiday by one week, Bob realises he could do the first half of the week and work from home for the second, and Carol is actually flexible on dates but did not say so because nobody asked.

Pros: Often produces creative solutions that top-down allocation misses. Builds team cohesion and mutual respect. Employees feel heard and involved.

Cons: Can create pressure on less assertive team members to give in. Risks becoming a popularity contest. May not resolve if all parties are genuinely inflexible. Requires a skilled manager to facilitate rather than dictate.

Best for: Small, close-knit teams with good working relationships and a collaborative culture.

4. Business-Needs Priority

The manager assesses which employees can be absent with the least impact on current business needs and approves accordingly. If one developer is mid-sprint on a critical feature and another has no blocking work, the latter gets priority regardless of who submitted first.

Pros: Ensures business continuity. Makes operational sense. Can be combined with other methods as a tiebreaker.

Cons: Open to accusations of subjectivity and favouritism. May consistently penalise the most senior or skilled employees (because they are always "too important" to be away). Can breed resentment if the same people are always told their work is too critical.

Best for: As a secondary consideration alongside another primary method, not as the sole criterion.

5. Hybrid Approach

Most well-run teams end up with a combination: first-come-first-served as the default, a rotation for the two or three most contested peak periods, team discussion as a first attempt to resolve conflicts, and business-needs assessment as a final tiebreaker. Document the approach in your leave policy so everyone understands the rules before a clash occurs.

Practical Strategies for Prevention

The best leave clash is the one that never happens. These strategies reduce the frequency and severity of conflicts.

1. Open a "Priority Booking Window" in January

At the start of each leave year, open a two-week window where employees can submit requests for the year's peak periods: school holidays, bank holiday weekends, Christmas, and any other predictable hotspots. All requests submitted during this window are treated equally (not first-come-first-served) and allocated using your chosen method. This prevents the January race and gives everyone a fair shot.

2. Set a Maximum Concurrent Absence Rule

Define how many people in each team or department can be absent simultaneously. For a team of five developers, you might set the maximum at two. Publish this number so that employees know the constraint when planning. A visible team calendar - not a hidden spreadsheet on the manager's laptop - lets everyone see at a glance which weeks are already at capacity.

3. Share the Calendar

Make approved leave visible to the whole team. When employees can see that two colleagues have already booked the first week of August, they are more likely to choose a different week voluntarily. This self-regulation reduces the number of clashes that reach the manager at all. A dedicated leave tracker makes this effortless compared to a shared spreadsheet that nobody remembers to check.

4. Offer Flexibility on Work Patterns

Sometimes a clash dissolves when you offer creative alternatives. Could one developer work from home for part of the contested week instead of taking full leave? Could another shift their hours earlier in the day so they are available for standups but can leave early for childcare? Could a compressed working week (four long days, one day off) give someone the flexibility they need without a full week's absence? These options will not suit every situation, but they expand the set of possible solutions.

5. Plan Sprints Around Leave Patterns

If you know that school holidays will always cause staffing pressure, plan your development cycles accordingly. Do not schedule a major release for the first week of the summer holidays. Front-load critical work before known absence periods. Adjust sprint commitments when the team is operating at reduced capacity. Treating leave as a known variable in your planning - rather than an unwelcome surprise - reduces the business impact and the pressure to deny requests.

6. Cross-Train for Coverage

Single points of failure turn every leave request into a crisis. If only one person can deploy to production, maintain the database, or deal with a particular client, their absence always feels "impossible." Cross-training - ensuring that at least two people can perform every critical function - makes leave approval easier because the business genuinely can cope without any one individual for a week.

A Worked Example

Scenario: You have a team of five developers. Your maximum concurrent absence rule is two. Three developers - Alice, Bob, and Carol - all want the week of 20–24 July (first week of school summer holidays). All three have school-age children.

Step 1: Check the rotation. Last year, Alice and Carol had priority for this week. Bob was declined and took the second week instead. This year, Bob has rotation priority.

Step 2: Team discussion. You bring all three together. Bob confirms he needs the 20–24 July specifically (flights booked). Alice says she could shift to 27–31 July if needed. Carol says she needs the 20th (a specific family event) but could work from home on 21–24 July.

Step 3: Creative resolution. Bob takes the full week of 20–24 July (rotation priority). Carol takes Monday 20 July as leave and works from home Tuesday–Friday. Alice shifts to 27–31 July. All three get meaningful time off, and the team has at least three developers in every day of the contested period.

Step 4: Document and update. Record the resolution and update the rotation tracker so that next year, Alice and Carol have priority for the first week.

What Not to Do

Do Not Ignore the Problem

Hoping that people will sort it out themselves without any framework leads to the most assertive person winning every time and quieter colleagues harbouring silent resentment. Provide a clear, documented process and use it consistently.

Do Not Always Give Priority to Parents

Employees without children have just as much right to take holiday during popular periods. Consistently prioritising parents - while understandable from a practical standpoint - can create a two-tier system that violates the Equality Act 2010 (indirect discrimination on grounds of age or sex) and breeds resentment among childless staff. The rotation or first-come-first-served methods avoid this problem by being neutral to personal circumstances.

Do Not Always Give Priority to Seniority

"I've been here longer, so I get first pick" sounds reasonable until you realise it means junior employees never get their preferred dates. This drives retention problems among the very people you should be investing in. If seniority is a factor, it should be one factor among several, not the sole determinant.

Do Not Approve Everyone and Hope for the Best

Approving all three requests to avoid conflict and then discovering on the Monday that you cannot run the team is worse than having an honest conversation upfront. If you set a maximum concurrent absence rule, enforce it. Your team will respect consistent boundaries more than they resent an honest "no."

Do Not Make Decisions Behind Closed Doors

If you decline a request, explain why. "The team's maximum absence limit for that week has already been reached, and Bob has rotation priority this year" is a clear, defensible explanation. "I've decided it doesn't work" invites speculation about favouritism and undermines trust.

Building a Leave Policy That Prevents Mutiny

The best way to handle leave clashes is to have a documented leave policy that covers the rules before any conflict arises. A good policy includes:

The notice period for leave requests (statutory minimum is twice the length of leave).
The maximum number of concurrent absences per team or department.
The allocation method for contested periods (first-come-first-served, rotation, or hybrid).
A priority booking window at the start of the leave year for peak periods.
How declined requests will be communicated, including the reason and any alternative dates offered.
The appeals process if someone disagrees with a decision.
A commitment to non-discrimination in leave allocation decisions.

Distribute this policy to all employees and reference it in your employment contracts or staff handbook. When a clash occurs, you are applying a known, agreed process rather than making an ad-hoc decision - which is both legally safer and far less likely to cause resentment.

The Bottom Line

Leave clashes are inevitable, especially in small teams where every absence matters. The goal is not to eliminate them but to manage them fairly, transparently, and consistently. A documented policy, a visible team calendar, a rotation system for peak periods, and a willingness to explore creative solutions will resolve 90% of conflicts before they become grievances. The remaining 10% require an honest conversation, a clear explanation of the decision, and a genuine commitment to giving the declined employee priority next time.

Tracking all of this in a spreadsheet is possible but painful - and the spreadsheet will not alert you when three people book the same week or when someone has not taken any leave in four months. A purpose-built leave management tool gives you visibility, enforces your concurrent absence rules automatically, and shows the team calendar in real time so that employees can self-select available weeks before conflicts arise.

Track Your Team's Leave the Easy Way

Managing Leave Clashes: When Everyone Wants the Same Week Off