Start planning summer cover by February or March: set a capacity limit (maximum people off at once per team), decide your request method (first-come-first-served or a batch deadline), and communicate both before requests start arriving. You can refuse a request for a genuine business reason, but you cannot refuse so often that a worker cannot take their full 5.6 weeks' statutory entitlement within the leave year.
Why summer leave is harder to manage
For most UK small businesses, the summer months concentrate annual leave demand into a short window. Several forces arrive at the same time:
- School holidays · parents of school-age children need leave during the six-week summer holidays and, in many cases, during May and October half-terms as well. These dates are largely fixed and predictable.
- Peak request volumes · even employees without children tend to favour July and August. A team of eight may produce more holiday requests in those two months than in the rest of the year combined.
- Thin backup cover · small businesses often have one person per role or per skill. There is less redundancy than in a large organisation, so a single absence can genuinely affect operations.
- Bank holidays adding pressure · the May bank holidays and the late August bank holiday in England and Wales (and Northern Ireland) cluster at the edges of the school-holiday window, reducing available working weeks further.
- A real discrimination risk · consistently refusing leave during school holidays can amount to indirect sex discrimination under the Equality Act 2010. Handling this lawfully requires a consistent, documented approach.
None of these pressures is unusual or unfixable. They become a problem when there is no plan, no policy and no conversation with the team before the requests arrive. The rest of this guide sets out how to build that plan.
Setting your capacity limit
The single most important decision in summer leave planning is also the simplest: how many people can be off at the same time in each team? Getting this number written down and communicated before requests arrive makes almost everything else easier.
A few worked examples to illustrate how to approach it:
To work out your defensible limit for each team or department:
Book Time Off lets you set a maximum number of people who can be off at once in each department. When an employee submits a request that would breach the limit, it is flagged before anyone approves it, so the manager never has to count how many people are already off on those dates. The wallchart shows existing approved leave for any week at a glance.
→ Start free trialChoosing your summer request method
Once you know your capacity limit, you need a rule for what happens when more requests arrive than you can grant. There are four main approaches:
First-come-first-served
The most common method: the first request that arrives within the capacity limit is granted; later requests for the same dates are refused or offered alternatives. It is straightforward and easy to defend if applied consistently. The drawback for summer is that it heavily rewards people who can plan furthest ahead. Parents whose children's school only announces term dates in February are at a disadvantage compared with employees who book in January.
Batch deadline
Set a single submission deadline for all summer requests (say, 31 March for all leave from 1 July to 31 August). Every request received by the deadline is treated as a simultaneous batch, rather than a race to submit. Where requests exceed capacity, you then apply your tie-break rule (rotation from last year, longest-serving employee priority, or a random draw). Requests received after the deadline revert to first-come-first-served for whatever capacity remains. This is the fairest approach for summer and reduces the frantic early-morning email race.
Rotation
For teams where everyone wants the same two weeks (the last week of school term, for instance), a rotation by year is clean and easy to explain. Whoever had the prime week last year goes to the back of the queue this year. Keep a log so the rotation is visible. The weakness is that it requires a record going back several years and does not handle new starters easily.
Hybrid
Many businesses run a batch deadline for their two or three peak weeks (the weeks immediately after school breaks up and before it returns) and revert to first-come-first-served for the rest of the summer. This reduces the planning burden without abandoning the fairness benefits of batch allocation for the most contested dates.
The legal rules you cannot ignore
The framework for taking and refusing leave comes from regulation 15 of the Working Time Regulations 1998. The three rules that matter most for summer planning are:
| Rule | Who gives notice | Minimum notice required |
|---|---|---|
| Worker requests leave | Employee | At least twice the leave length (calendar days) |
| Employer refuses leave | Employer (counter-notice) | At least equal to the leave length (calendar days) |
| Employer requires leave on set dates (e.g. shutdown) | Employer | At least twice the leave length (calendar days) |
In practice: a one-week holiday request (five working days) requires the employee to give at least 10 calendar days' notice. If you want to refuse it, you must give counter-notice at least five calendar days before the leave was due to start. ACAS and GOV.UK both confirm this framework on their guidance pages linked in the sources below.
Many employers extend the notice requirement contractually. Setting a four-week or six-week minimum notice period for any leave over five days is entirely lawful, gives you more planning time, and is standard in industries such as hospitality, retail and healthcare. If you set a longer notice period, put it in writing and apply it to everyone.
The statutory floor you must protect. You can refuse individual requests, but the Working Time Regulations are explicit: you cannot refuse so often that a worker is unable to take their full 5.6 weeks statutory holiday (28 days for a five-day-a-week worker) within the leave year. If you have refused several summer requests and a worker is approaching year-end with a significant unused balance, you must grant leave in sufficient time for them to use it. Failing to do so exposes you to an Employment Tribunal claim for unlawful refusal of statutory leave. For more on what happens to untaken leave, see the guide to annual leave carry forward rules.
School holidays, fairness and the discrimination risk
Summer leave refusals create two specific legal risks that do not apply as sharply at other times of year. Both stem from the Equality Act 2010.
Indirect sex discrimination and caring responsibilities
The school summer holidays are a fixed, unavoidable constraint for employees with children. Employees who need leave during those weeks are disproportionately likely to be women, because women still carry the majority of childcare responsibilities in the UK. A policy that consistently refuses school-holiday requests, or a first-come-first-served system that systematically disadvantages people who cannot plan months ahead because of unpredictable school announcements, can amount to indirect sex discrimination under section 19 of the Equality Act 2010.
This does not mean you must grant every school-holiday request. It means that when you refuse one, you need to be able to show:
- A genuine business reason for the refusal (cover cannot be maintained at that level)
- That you considered alternatives before saying no (swaps, flexible working, adjusted hours, split leave)
- That the same rule applies consistently to everyone, not just parents
- That the pattern of refusals over the year is not consistently falling on the same group
Religion or belief
Some employees may observe religious festivals that fall in the summer months. Refusing leave for a religious festival can be indirect religion or belief discrimination under the Equality Act 2010 unless the refusal is a proportionate means of achieving a legitimate business aim. Document your reasoning and explore alternatives before declining.
When requests arrive via Book Time Off, they are timestamped in the order they land, so first-come-first-served is objective rather than based on a manager's memory or an inbox that sorts by sender. Every request and decision is logged, and the wallchart shows the whole team's approved leave for any summer week at a glance before an approval decision is made.
→ Start free trialCommunicating the plan before requests arrive
The point of a summer cover plan is that it prevents contested situations from arising, not that it resolves them once they do. That only works if the plan is communicated to the whole team before the first summer request lands.
What to communicate, and when:
- By the end of February: the capacity limit for summer (maximum people off at once, with any seasonal tightening for peak weeks); the request method (first-come-first-served, batch deadline, or hybrid); and the date the request window opens.
- At the start of the request window: a reminder of the rules, the deadline if there is one, and how to submit a request.
- When requests are processed: decisions communicated promptly, with a written reason for any refusal and an offer of alternative dates.
For small businesses without a formal HR function, a short email in January or February, followed by a five-minute mention at a team meeting, is usually enough. The important thing is that it happens consistently every year so that "this is how we always do summer leave" becomes established common knowledge rather than a new surprise each June.
Your summer planning timeline
Working backwards from a July start of the school holidays, here is a practical timeline:
When an employee requests summer leave in Book Time Off, their approver gets an email and can approve or decline in one click without opening the app. The remaining balance updates, the booking appears on the shared calendar and wallchart, and everyone is notified. The record of every request, decision and outstanding balance is always there when you need it, without any filing.
→ Start free trialWhat to do when cover falls short
Even with good planning, some summers produce a cover shortfall: the person you were relying on calls in sick, or a cluster of requests you did not anticipate arrives late. The options, roughly in order from least to most disruptive:
- Cross-cover from another team or department · works well if the tasks are transferable and the receiving team has capacity. Requires advance cross-training, not a last-minute conversation.
- Ask for a volunteer to shift dates · sometimes a team member is flexible. Asking is different from requiring, and a voluntary swap preserves goodwill better than a compelled change.
- Bring in temporary or agency staff · an option for roles that can be filled by someone without long institutional knowledge. Budget this in your summer planning rather than reaching for it in an emergency.
- Adjust how the business operates · reduced opening hours, a slower service level, or closed-for-certain-tasks days during peak weeks. Some small businesses build this into their summer model deliberately.
- Cancel or postpone approved leave as a last resort · regulation 15 allows this with the right notice (at least equal in length to the leave being cancelled), but it should genuinely be a last resort. Cancelling leave the worker has already booked travel for causes real financial harm and damages trust. ACAS recommends considering compensation for any proven financial loss.
Sample summer leave policy clause
The following clause can be adapted for a staff handbook, company leave policy, or standalone summer leave note. Customise the numbers and dates to match your business. For the wider leave policy framework (statutory minimums, carry-forward, accrual rules), see our guide to writing a UK leave policy.
1. Summer request window. Annual leave requests for the period 1 July to 31 August must be submitted by [31 March / your chosen date]. Requests received by this deadline will be considered as a single batch. Requests received after this deadline will be processed on a first-come-first-served basis subject to remaining capacity.
2. Capacity limits. During the summer period, a maximum of [X] members of each team may be on annual leave at the same time. For the weeks commencing [peak dates, e.g. 28 July and 4 August], the limit is [Y]. These limits are set to ensure [minimum function] remains covered.
3. Tie-break rule. Where requests received within the deadline exceed capacity, preference will be given by [rotation based on the previous year / seniority / a draw among equally-placed requests]. The tie-break rule applies consistently to all team members. Requests declined by the tie-break will be offered the next available slots.
4. Refusal and alternatives. Where a summer request cannot be granted, the manager will give a written reason and offer alternative dates. We will consider requests for flexible working arrangements, swapped days with a colleague, or split leave as alternatives to outright refusal.
5. Ensuring entitlement is taken. Every team member must be able to take their full statutory annual leave entitlement within the leave year. Where summer refusals mean a significant balance remains in September, managers will work with each team member to schedule the remaining leave before the year-end.
Sources
Primary sources cited in this guide
| legislation.gov.uk | Working Time Regulations 1998, regulation 15 (notice for taking and refusing leave) |
| GOV.UK | Holiday entitlement: overview and statutory minimum |
| GOV.UK | Holiday entitlement: booking time off |
| ACAS | Asking for and taking holiday |
| ACAS | Checking holiday entitlement |
| legislation.gov.uk | Equality Act 2010, section 19 (indirect discrimination) |
| legislation.gov.uk | Equality Act 2010 (full text) |
| nidirect | Taking your holidays (Northern Ireland) |