Most leave disputes come from three unwritten rules: carry-over, refusal, and what happens on leaving. A short annual leave policy that answers them.
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.
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.
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.
In many jurisdictions yes, with sufficient notice — often twice the length of the leave being imposed. It is used for shutdowns and for staff who have accumulated too much. Put the notice rule in the policy rather than inventing it at the time.
For the statutory minimum, usually not except on termination. For contractual days above the minimum you have more freedom, but paying leave off routinely tends to produce people who never rest and eventually leave.
A small fixed number with a deadline, typically expiring in the first quarter, works better than either none or unlimited. Zero carry-over produces December leave chaos, and unlimited produces a growing liability on the balance sheet nobody notices until it is large.
A social media schedule fails for one of two reasons: it was built for a team twice your size, or it was never written down at all. The realistic version is smaller than the advice suggests and survives longer.
Staff scheduling looks like a puzzle about coverage. It is really a negotiation between demand, fairness and notice — and the schedule that ignores the last two gets solved every week by people quitting.
Absence management is the practice of recording who is away, spotting patterns early, and handling the awkward cases consistently. Most of it is admin; the part that matters is the conversation after a return.