Half your team books the same Friday off. Again. Here's how to prevent overlapping holidays without becoming the bad guy.
Most clashes aren't caused by bad employees — they're caused by poor systems and unclear policies.
No visibility
Employees can't see who else is already off before they request leave.
Manual processes
Managers approve in email without checking the team calendar first.
No maximum limits
No policy defining how many people can be off simultaneously.
School holidays
Everyone with children competes for the same 13 weeks per year.
Last-minute requests
Late bookings when the calendar is already tight.
No escalation path
No fair process for resolving competing requests.
Practical steps you can implement this week — no expensive software required (though it helps).
The single biggest fix: let employees see team availability before they submit a request. When people can see that 3 colleagues are already off that week, most will choose different dates without needing a manager to intervene.
Define the maximum number of people who can be off simultaneously per team or department. This gives managers a clear, objective reason to decline requests — it's not personal, it's policy.
The longer the notice period, the fewer clashes you'll face. When everyone books well in advance, it's easier to manage capacity. Late requests should only be approved if no conflict exists.
School holidays, Christmas, and bank holiday weekends create predictable bottlenecks. A first-come-first-served approach alone isn't fair for these periods — parents and carers will always lose.
The best leave management tools automatically flag when approving a request would breach your team's maximum absence limit. This catches clashes before they happen — without relying on a manager's memory.
A policy only works if everyone knows it exists. Include your leave clash rules in your employee handbook, discuss them in onboarding, and reference them when declining requests.
Adapt this template for your employee handbook.
Annual Leave — Concurrent Absence Policy
Maximum concurrent absences: No more than [X] employees per team may be on annual leave at the same time. Managers will assess each request against existing bookings before approving.
Notice periods:Employees must submit annual leave requests at least [X] working days before the requested start date. For requests of 5+ days, a minimum of [X] weeks' notice is required.
Conflicting requests: Where two or more requests overlap and cannot all be accommodated, priority will be given based on: (1) order of submission (first-come-first-served), (2) whether the employee was refused for the same period previously, (3) any special circumstances.
Peak periods: During school holidays and Christmas, a rotation system will apply to ensure all team members get fair access. The rotation schedule will be published at the start of each calendar year.
Refusal process: If a request is declined, the manager will explain the reason in writing and suggest alternative dates where possible. Employees may appeal to [HR / senior manager] if they believe the refusal is unreasonable.
The right tool does 80% of the work. Here's what Offly does to prevent clashes.
Team availability at approval time
When a manager opens a leave request, they see exactly who else is already off that week. No cross-referencing needed.
Slack/Teams status sync
Everyone can see who's on leave from their Slack sidebar. No need to check a separate calendar.
Shared team calendar
Employees see team availability before they even submit a request — so they self-resolve most clashes.
Notifications for managers
Instant push notifications for new requests. No requests sit in an email inbox for days.
Calendar feed exports
Subscribe to team leave calendars in Google Calendar or Outlook for always-current visibility.
Offly shows who's off before anyone books. Prevent clashes, not just manage them. Free for up to 5 users.