Annual leave policy: the rules that stop arguments in December

An annual leave policy exists to answer the handful of questions that otherwise get decided differently each time by whoever is asked. How much notice, who approves, what happens to days not taken, and what the leave year is. Companies rarely argue about the entitlement itself, because that is set by law and by contract. They argue about carry-over in January, about two people wanting the same week in July, and about the final payslip of someone who left owing days.

What an annual leave policy has to state

• The leave year — calendar, anniversary of joining, or a fixed company year — because everything else counts from it.
• The entitlement, including how public holidays are treated and whether they are inside or outside the figure.
• How entitlement accrues for part-year joiners and leavers, expressed as a rule rather than as a calculation someone does by hand.
• Notice required to request leave, and the maximum consecutive period without special approval.
• Who approves, and who approves when that person is themselves away.
• Carry-over: how many days, how long they survive, and whether approval is needed.
• What happens on termination — payment for untaken days, and deduction for days taken in advance where the contract permits it.

The rules people actually fight about

• Clashing requests. Say how they are settled — first come, rotation, or business need — before two people ask for the same fortnight.
• Refusal. A request can usually be refused for genuine business reasons, but the policy should say so and require a reason to be given.
• Cancelled leave. If you can require someone to cancel booked leave, say what compensation applies; discovering this in the moment is corrosive.
• Sickness during leave. Many jurisdictions let the employee reclaim those days as sick leave with evidence — state the evidence you need.
• Untaken statutory minimum, which in much of Europe cannot be paid off instead of taken except on termination.

The policy sits on top of statutory minimums that differ by country and sometimes by contract. Nothing here is legal advice — the rule to follow is the one that applies where the employee works. Where your policy is more generous than the statutory floor, say clearly which part is contractual and which is discretionary, or the generous part becomes permanent by custom.

Keeping the balances honest

1. One record of balances that both the employee and the manager can see; two versions guarantee a dispute.
2. Book the leave when it is approved, not when it is taken, so forward visibility is real.
3. Show remaining entitlement alongside the request, because most over-booking is arithmetic rather than intent.
4. Run a carry-over review two months before the leave year ends, when something can still be done about it.
5. Reconcile against payroll at year end and on every leaver, since that is where the errors surface expensively.

The practical question a hybrid pattern raises is where people sit when they come in. Desk booking answers it by making workspaces reservable, so attendance and capacity are agreed before the commute rather than discovered on arrival.

Cover has to be visible to the outside world too. An out of office message names the dates, the person covering and what to do if it is urgent, which is what stops work stalling silently for a fortnight.

Where the leave lives

Ettex Calendar is where approved leave becomes visible to the people it affects — the team sees the coverage gap, not only the HR system — and where clashes are noticed while they can still be resolved. Balances belong next to it rather than in a private spreadsheet. The written policy itself belongs in the employee handbook with your other written rules, so that the answer to "can I carry these over" is readable without asking. Ettex does not run payroll and does not calculate statutory entitlement for your jurisdiction.