How to design a leave policy: accrual, carry forward and notice periods

A leave policy affects everyone in the organisation, every year, and it is surprisingly easy to get wrong. Unclear accrual rules lead to disputed balances. Unlimited carry forward leads to people hoarding leave and taking weeks off at awkward times. Missing notice periods lead to last-minute gaps in the rota. This guide walks through the decisions you need to make and how to turn them into rules that are applied automatically.

Step 1: Choose your leave types

Start by listing the kinds of leave you offer. Common types include:

• Earned or privilege leave, for planned time off.
• Casual leave, for short, unplanned needs.
• Sick leave.
• Parental leave, compassionate leave and other statutory or special types.
• Unpaid leave.

Keep the list as short as you can while still meeting your obligations. Every extra type is something employees need to understand and managers need to apply.

Step 2: Decide the annual entitlement

For each type, decide how many days per year an employee is entitled to. Be clear whether this differs by role, location or length of service, and write those differences down.

Step 3: Decide how leave accrues

Accrual is how the entitlement becomes available over the year. There are two common approaches:

Yearly accrual

The full year's entitlement is available from the start of the year (or from the joining date). It is simple and generous, but someone who leaves early in the year may have taken more leave than they earned.

Monthly accrual

A fraction of the entitlement is added each month, for example one twelfth. It matches leave to time worked, which is fairer for new joiners and leavers, but people have less available at the start of the year.

Many organisations use yearly accrual for sick or casual leave, which people cannot plan, and monthly accrual for earned leave.

Step 4: Set carry-forward rules

Decide what happens to unused leave at the end of the year. Options include losing it, carrying all of it forward, or carrying forward up to a limit. A limit is usually the best balance: it rewards people who could not take all their leave without letting large balances build up year after year.

A carry-forward limit protects both sides: employees keep some unused leave, and the organisation avoids long, unplanned absences built from years of saved days.

Step 5: Add notice periods and maximums

To keep teams covered, many policies require advance notice for planned leave, for example three days' notice for up to two days off, and longer notice for longer periods. You may also want a maximum number of consecutive days for certain types without special approval.

• Notice period: the minimum number of days between applying and the first day of leave.
• Maximum consecutive days: the longest single block of a leave type that can be requested.

Sick leave usually has no notice period, for obvious reasons.

Step 6: Decide eligibility

Some leave types may apply only to certain teams, or only after probation. Decide whether new joiners can take earned leave during probation, and whether any types are restricted to particular groups.

Step 7: Set it up so requests are checked automatically

Rules that live only in a handbook are applied inconsistently. In BeeWorkforce, leave policies are configured under Settings → Leave policies. For each leave type you can set:

1. Yearly or monthly accrual.
2. Carry forward, and its limit.
3. A notice period in days.
4. A maximum number of consecutive days.
5. Which teams the type applies to, and whether it is available during probation.

When an employee applies, requests that break a rule are refused with the reason, so the employee knows what to change, and balances shown to employees reflect accrual and carry forward automatically.

Step 8: Handle the edge cases

Before publishing, think through the awkward cases:

• Someone joins mid-year: how much leave do they get?
• Someone leaves with a negative balance: is it recovered?
• A public holiday falls inside a leave period: does it count as leave?
• Leave is cancelled after approval: is the balance restored?

Write down the answer to each and check that your setup matches.

A sample policy summary

Here is the kind of summary that works well at the top of a leave policy. Adjust the numbers to your own entitlements and obligations:

• Earned leave: 18 days a year, accrued monthly, up to 10 days carried forward, 7 days' notice for more than 2 days off, available after probation.
• Casual leave: 8 days a year, available from the start of the year, not carried forward, maximum 2 consecutive days.
• Sick leave: 8 days a year, available from the start of the year, not carried forward, no notice required.
• Unpaid leave: by approval only, no fixed entitlement.

A summary like this answers most questions on its own. The full policy text can then cover definitions, edge cases and the approval process for anyone who needs the detail.

Step 9: Set up approvals and the team calendar

Decide who approves each type of leave, usually the reporting manager with HR as a fallback, and how quickly requests should be answered. A simple service level, such as a response within two working days, prevents requests from sitting unanswered while people wait to book travel.

Make approved leave visible on a shared team calendar. Managers can then see overlaps before approving, and colleagues can plan around each other's time off without needing to ask. Visibility reduces the number of clashes and last-minute surprises more than any rule about notice periods.

Step 10: Publish and explain

Share the policy with a short summary table: each leave type, the annual entitlement, how it accrues, carry-forward limits and notice periods. Walk new joiners through it in their first week. Most leave disputes come from people not knowing the rules, not from disagreeing with them.