UK employers can refuse a holiday request when too many people want the same time off, provided they have a good business reason and give counter-notice at least equal in length to the leave requested. The fairest approach is to publish departmental capacity limits, decide your tie-break method in advance (first-come-first-served, rotation, or hybrid), and apply it consistently to everyone. Watch for indirect discrimination on religion or caring responsibilities.
What actually counts as a clash
A holiday clash is any situation where granting one or more pending requests would leave your team or department below the staffing level you need to operate. That is broader than two people wanting the exact same day. In practice the four common patterns are:
- Direct overlap - two or more people want the same dates, or overlapping dates, where you can only spare one
- Capacity breach - any combination of approved and pending leave that would push the team below its minimum cover for those days
- Skills clash - one duty-rota slot, on-call rota, or role only certain people can cover, and they all want the same period
- Seasonal pressure - Christmas, school holidays, Eid, Diwali, Easter half-term, the August bank holiday week - when most of the team competes for the same dates and the maths simply does not add up
The right way to handle each of these starts with the same thing: a written rule everyone knows about before the clash happens. The rest of this guide explains how to write it.
The legal rules: notice, refusal, cancellation
The framework comes from regulation 15 of the Working Time Regulations 1998, supplemented by the worker's contract and any "relevant agreement". Three rules matter most for clashes:
In plain English: if a worker asks for one week off, they need to give you at least 10 calendar days' notice. If you want to say no, you must give counter-notice at least 7 calendar days before the start of the leave - all in calendar days, not working days. ACAS confirms the same rule in its guidance on asking for and taking holiday, and GOV.UK summarises it on the booking time off page.
| Length of leave requested | Worker must give at least | Employer must refuse by |
|---|---|---|
| 1 day | 2 calendar days | 1 calendar day before start |
| 3 days | 6 calendar days | 3 calendar days before start |
| 1 week (5 working days) | 10 calendar days | 5 calendar days before start |
| 2 weeks (10 working days) | 20 calendar days | 10 calendar days before start |
The statutory floor. You can refuse a request, but you cannot refuse so often that the worker is unable to take their full 5.6 weeks of statutory holiday in the leave year. This is the part of the law that catches employers out: if you refuse three Christmas requests in a row from the same person and they end the year with unused leave, you are exposed to a claim that you denied them their statutory entitlement, even if each individual refusal looked reasonable in isolation.
For more on the carry-over consequences when leave goes untaken, see our guide to annual leave carry forward rules.
Setting capacity limits before clashes happen
The single most useful thing you can do is decide, in advance, how many people from each team or department can be off at any one time. If everyone knows the limit, most clashes never reach you - the system or the manager simply tells the second requester that the slots are full.
How to set a defensible capacity limit:
Five fair methods for choosing between competing requests
When two or more requests arrive that would breach capacity, you need a tie-break rule. The five most common methods all have a place - the right one depends on the size of the team, the predictability of the business, and how much advance notice your staff can realistically give.
1. First-come-first-served
The default in most UK businesses, and the easiest to defend if applied consistently. The first request that arrives gets the slot; later requests are refused or offered alternative dates. It rewards organisation and gives staff a clear incentive to plan early. The downside is that it disadvantages anyone who cannot plan as far ahead - parents tied to school holiday announcements, employees waiting for partners' shifts, those whose religious calendar depends on the lunar year, and new starters who joined after others had already booked.
2. Rotation by year
Used most often for Christmas, New Year and the August bank holiday week. Whoever was off last year is at the back of the queue this year; whoever worked through is at the front. Keep a simple log so the rotation is visible and verifiable. This works well for predictable peak periods where everyone wants the same dates and you cannot grant them all - it converts a yearly fight into a yearly fairness mechanism.
3. Batch deadline plus structured allocation
Best for high-pressure peaks like Christmas. Set a single submission deadline (say, 30 September for that year's Christmas). Treat all requests received before the deadline as a batch, then apply your tie-break rule (rotation, business need, or a points system). Requests received after the deadline drop to first-come-first-served. This stops the unfair race-to-submit and gives parents and shift workers a fair shot.
4. Departmental swap
Two people in the same role and team agree to swap days, or one volunteers to cover the other and bank a day. The employer's job is to facilitate, not impose. Swaps work well when team relationships are strong and the workload is genuinely transferable - they fail when one person feels pressured into giving up their preferred dates.
5. Manager judgement against published criteria
The manager picks, but only against criteria published in advance: things like "longest-serving employee gets priority for one peak period per year", "previously approved leave that was later cancelled gets first refusal", or "leave needed for a major personal event over routine leave". This is the most flexible method but the most exposed to challenge. If you use it, document the reason for every decision and review at year end to check the same people are not consistently winning or losing out.
The discrimination traps to avoid
Most holiday refusals are lawful. The ones that go wrong tend to fail in the same handful of ways - and the law that catches them is usually the Equality Act 2010, not the Working Time Regulations. The risk is indirect discrimination: a rule that applies to everyone but disadvantages a particular group, and cannot be justified as a proportionate way of meeting a legitimate aim.
Religion or belief
The Equality and Human Rights Commission and ACAS both warn that refusing leave for a religious festival can be indirect religion or belief discrimination unless the refusal is objectively justified. Christian festivals are largely covered by the bank holiday calendar; major non-Christian festivals - Eid, Diwali, Yom Kippur, Vesak, Vaisakhi - are not, so the staff observing them rely on annual leave. A blanket "no leave during peak weeks" rule can disproportionately affect them.
The fix is not to grant every religious request automatically, but to document the alternatives you considered before refusing: flexible working, a swap with a colleague, partial leave, or unpaid leave on top of the booked annual leave. ACAS guidance on managing religion in the workplace and the EHRC publication "Religion or belief: how do I handle employee requests?" both stress documenting your reasoning.
Sex and caring responsibilities
Refusals during school holidays are an indirect sex discrimination risk because women still take on the majority of caring responsibilities for children, so a rule that consistently denies school-holiday leave hits women harder. The same logic applies to other caring patterns. The defence is the same: show the business reason, show you considered alternatives, and check the pattern of refusals over time does not consistently fall on the same group.
Disability and reasonable adjustments
If an employee needs leave at a particular time for treatment, recovery, or to attend medical appointments connected to a disability, refusing routinely can engage the duty to make reasonable adjustments. This often manifests not as a one-off refusal but as a pattern.
Part-time workers and the comparator trap
Treat part-time workers no less favourably than comparable full-timers under the Part-time Workers (Prevention of Less Favourable Treatment) Regulations 2000. If full-timers can take three weeks consecutively in summer but a part-timer is told they cannot, that needs a business reason that does not boil down to "they work fewer days".
How to refuse a request properly
If you do need to refuse, the process is what matters. Most successful tribunal challenges to a refusal are not about whether the employer had a reason; they are about whether the employer applied the rules consistently and gave the right notice.
Sample holiday clash policy clause
Use this as a starting point for your staff handbook or leave policy. Adapt the limits to your team size and seasonal pattern.
1. Capacity limits. So that we can maintain cover, no more than [X] members of a team may be on annual leave at the same time during the standard year, and no more than [Y] during peak periods (defined below). The current capacity limits are set out in [Annex A / the leave management system].
2. Notice. All annual leave must be requested at least [the statutory minimum / four weeks / your figure] in advance, in writing or via the leave management system. We will respond as soon as reasonably practicable, and in any event within the statutory deadline.
3. Peak periods and Christmas. Requests for leave during [Christmas / school summer holidays / any other peak] must be submitted by [date] each year. All requests received by that date will be treated as a single batch. Where requests exceed capacity, we will allocate by [rotation / first-come-first-served within the batch / other rule]. Requests received after the deadline will be considered on a first-come-first-served basis subject to remaining capacity.
4. Religious observance. We recognise that staff may wish to take leave for religious festivals not covered by UK bank holidays. We will give such requests the same fair consideration as any other request, and where capacity does not permit approval, we will explore alternative arrangements (swaps, flexible working, partial leave, or additional unpaid leave) before refusing.
5. Refusal. Where a request is refused, we will give a written reason and offer alternative dates where reasonably possible. If a request is refused, the worker may resubmit for different dates without prejudice.
6. Cancellation of approved leave. We will only cancel approved leave in exceptional circumstances and in accordance with the statutory notice period. Where cancellation results in a financial loss to the worker (for example pre-paid travel), we will consider reasonable compensation.
If you are creating or refreshing the wider policy, our guide to writing a UK leave policy covers all the other clauses you will need - statutory minimums, accrual rules, and the seven essential sections.