Leave Plan Template: Plan Your Team's Time Off (Free Example)
A leave plan maps out who is off and when, before conflicts happen. A free template, a filled-in example, the five steps to build yours and the notice and carry-over rules to respect — valid for any year.
Every year, the same script: half the company wants the same two weeks in summer, someone discovers in November they still have ten days to burn, and the "leave plan" lives scattered across an email thread. This guide brings order: a leave plan template ready to copy, a filled-in example, the five steps to build yours, and the legal rules to respect. Deliberately not tied to any specific year — the structure and the rules work for this year, next year, and the one after that.
A leave plan is the document where a company schedules who is off and when, ahead of time: it gathers everyone's balances and preferences, checks them against each team's minimum coverage, and fixes the approved periods in writing. Few countries mandate the document itself — but almost all mandate planning leave and giving notice, and a written plan is the simplest proof that you did.
What a leave plan should contain
A useful template is not a decorative calendar: it is a table that answers three questions at a glance — how much each person has left, who asked for what, and who keeps the team running. The essential fields:
| Field | Why it matters |
|---|---|
| Employee and team | Leave is planned per team, not alphabetically: conflicts happen inside a department. |
| Remaining balance | Days accrued minus days already taken — including any carry-over from last year and its expiry date. |
| Requested period | Start and end dates of every request, half days included. |
| Status | Requested, approved or declined — with the decision date, which doubles as proof of notice. |
| Minimum coverage | How many people in each team must stay operational every week: the constraint that settles conflicts. |
| Notes | Reasons for a refusal, agreements made, later changes — all documented. |
A filled-in example
Here is what the plan of a small restaurant team looks like during summer planning. Two requests in Front of house overlapped: one was moved by applying the rotation rule, and the note remembers it for next year.
| Employee | Team | Balance | Requested period | Status | Notes |
|---|---|---|---|---|---|
| Anna Bianchi | Front of house | 18 days | 3–21 August | Approved | Long break: requested before the deadline |
| Luca Ferri | Front of house | 14 days | 10–21 August → 24 Aug–4 Sep | Approved | Moved for minimum coverage; goes first next year |
| Marta Colombo | Kitchen | 21 days | 3–14 August | Approved | — |
| Davide Russo | Kitchen | 9 days | 17–28 August | Approved | Low balance: 5 carry-over days expiring soon |
| Elena Greco | Admin | 22 days | 24 Aug–11 Sep | Pending | Waiting on supplier shutdown dates |
The free template to copy
No need to build the sheet from scratch: our free Google Sheets template already has twelve monthly tabs, colour codes for vacation, sickness and other absences, and balances that update themselves through formulas. Copy it with File → Make a copy (or download it as Excel) and it works for any year — just refresh the dates in the holidays tab. The step-by-step guide to using it is in the companion article on the PTO tracker in Google Sheets.
How to build it: the 5 steps
1. Verify the starting balances
Before collecting requests, get the numbers straight: leave carried over from last year (with its expiry date), accrual for the current year, and any extra balances your contracts grant. A plan built on wrong balances only produces arguments in December.
2. Collect preferences 4–6 weeks ahead
Ask for preferences in writing, with a clear deadline and — above all — the tie-breaking criteria announced up front. A template message:
Subject: summer leave planning
By Friday [date], please add your preferences for [period] to [form/sheet]. If requests overlap we will apply, in order: rotation versus last year, documented family constraints, order of submission. The final plan will be published by [date].
3. Cross-check requests against minimum coverage
Move the requests into the template and look at weeks, not names: wherever a team drops below its minimum coverage, there is a conflict to resolve. The usual danger zones — the central weeks of summer and the days between Christmas and New Year — deserve a dedicated control row.
4. Settle conflicts with objective criteria
Year-on-year rotation, seniority, documented family constraints: any criterion works, as long as it was announced at step 2 and is applied verifiably. This year's arbitrary decision is next year's grievance.
5. Publish in writing and record every change
Share the final plan with proper notice, keep the requests and approvals, and document every later change with its date and reason. If a last-minute cancellation is ever disputed, that record is your defence.
The rules to respect
The plan is free in form, but the substance is regulated almost everywhere:
- European Union — the Working Time Directive guarantees at least 4 weeks of paid annual leave, which cannot be replaced by pay except when employment ends. Member states add their own carry-over deadlines and notice rules — Italy, France and Spain each regulate who fixes the dates and how much notice is due.
- United Kingdom — statutory entitlement is 5.6 weeks (28 days for a five-day week, bank holidays can count toward it). Notice rules cut both ways: an employer refusing or imposing leave must give notice at least as long as the rules in the statutory scheme require.
- United States — no federal minimum: PTO is set by company policy and state law. Carry-over is where plans get legal: some states, California first, prohibit use-it-or-lose-it policies, so the plan must track accrued balances honestly.
- Everywhere — collective agreements and employment contracts can only improve on the legal floor. Write the rule that binds you into the plan itself: notice period, carry-over deadline, blackout periods.
When the spreadsheet stops scaling
Up to 10–15 people, the template holds. Then the symptoms start: multiple versions of the file that disagree, balances updated by hand, requests arriving in chat and never copied over, and the coverage rule checked by eye. Bueggio HR does exactly the leave plan's job, by itself: a shared team calendar, balances that update on every approval, requests and decisions tracked, a cap on concurrent absences per team, and date locks for the critical weeks. The four methods compared — software, spreadsheet, email, paper — are in our guide on how to track vacation time.
Frequently asked questions
What is a leave plan?
A leave plan is the document where a company maps out who is off and when, before the absences happen: for each person it records the remaining balance, the periods requested and the approval status, checked against each team's minimum coverage. It can be a spreadsheet, a PDF on the noticeboard or software — what matters is that it is written down, shared and kept current.
Can an employer decide when employees take their leave?
In most countries, yes — within limits. Employers can generally set or refuse dates for business reasons, but must respect notice rules (for example, UK employers must give notice of at least twice the length of the leave they are cancelling or imposing) and any collective agreement. The safest pattern everywhere: publish the criteria first, decide in writing, keep the records.
How far in advance should a leave plan be built?
Collect preferences four to six weeks before each peak season, and publish the plan early enough for people to book travel. Many collective agreements and national laws set specific notice periods — one to two months is a safe default for summer and year-end planning.
What happens to unused leave at the end of the year?
It depends on the country. The EU requires at least four weeks of paid leave and limits paying it out instead of taking it; carry-over deadlines vary by member state. In the US there is no federal minimum and carry-over is set by policy and state law — California, for example, bans use-it-or-lose-it policies. Write the rule that applies to you into the plan, per person.
How do you handle two requests for the same dates?
With objective criteria announced before requests are collected: year-on-year rotation on the most popular weeks, seniority, documented family constraints. Whoever gives way this year goes first next year — and the written plan is what makes that promise credible.
Sources
Legal references: Directive 2003/88/EC, art. 7 (four-week EU minimum, no pay in lieu during employment) and gov.uk on UK holiday entitlement. For national specifics, this article exists in Italian, French and Spanish editions with each country's own rules; your collective agreement or company policy governs the details.