Leave management is the process of tracking, approving, and recording employee absences. Setting it up properly means creating a policy, choosing a system, configuring the rules, and getting your team to actually use it. The difference between a system that works and one that gathers dust is the quality of the setup — getting the configuration right upfront saves months of remediation later. This guide covers the complete setup process, from policy creation to team adoption.
This guide walks you through how to set up leave management from scratch, whether you are replacing a spreadsheet or building the function for the first time.
Key Takeaways
- Leave management setup has five phases: policy, system, configuration, training, and review.
- The policy comes first — the system enforces what the policy defines.
- Configuration must match your policy exactly — accrual rates, leave types, approval workflows, and carry-over rules.
- Training for both managers and employees is essential — a system nobody uses correctly is worse than no system.
- Review quarterly in the first year — you will find configuration gaps that need fixing.
Phase 1: Create the policy
Before choosing or configuring any system, define the policy. The system is only as good as the rules it enforces.
Leave types to define
- Annual leave — entitlement, leave year period, bank holiday inclusion, carry-over rules
- Sick leave — SSP process, contractual enhancements, fit note requirements, return-to-work interviews
- Parental leave — maternity, paternity, adoption, shared parental
- Other leave — compassionate, study, unpaid, jury service, time off for dependants
For each leave type, specify
- Entitlement — days, weeks, or hours per year
- Accrual method — monthly, from start date, or 12.07% for irregular hours
- Carry-over rules — what carries over and any deadlines
- Notice requirements — minimum notice for planned leave
- Approval process — who approves and what criteria apply
- Pay rules — full pay, SSP, or other rates during the absence
Document the policy
Write it down. The policy should be:
- Accessible to all employees (handbook, intranet, or employee portal)
- Referenced in the employment contract
- Reviewed annually
Phase 2: Choose a system
Criteria for selection
- Leave types — does the system support all your absence types?
- Accrual rules — can it handle monthly accrual, pro-rata, and irregular-hours accrual?
- Approval workflows — multi-level, single-level, auto-approve?
- Team calendar — can everyone see who is off?
- Integration — does it connect to your payroll system?
- Mobile access — can employees request and approve from their phone?
- Reporting — does it generate absence reports, Bradford Factor scores, and cost analysis?
- Multi-country — does it handle different leave laws and bank holidays?
System options
- Spreadsheets — only for teams under 10 people, and only temporarily.
- Shared calendars — visual but unstructured; no calculations or reporting.
- Dedicated software — the only practical option for teams of 10 or more.
Phase 3: Configure the system
Once you have a system, configure it to match your policy:
Leave types
- Create each leave type as a separate entry.
- Set the entitlement, accrual method, and carry-over rules for each.
- Mark statutory vs contractual leave separately.
Approval workflows
- Single-level — direct manager approves all requests.
- Multi-level — manager approves, then HR or department head for extended leave.
- Auto-approve — for certain leave types where no approval is needed (e.g., time off in lieu).
Carry-over rules
- Set the maximum carry-over days per leave type.
- Set the deadline for using carried-over leave.
- Configure whether the system auto-resets balances at the start of the leave year.
Bank holidays
- Import the correct bank holidays for each country and region where you have employees.
- Decide whether bank holidays are included in or in addition to the annual leave entitlement.
Notifications
- Configure email or Slack notifications for new requests, approvals, and declines.
- Set reminder notifications for pending requests.
- Send calendar invites for approved leave.
Phase 4: Train your team
Manager training
- How to approve and decline requests using the system
- How to read the team calendar and check capacity
- How to conduct return-to-work interviews
- How to use the reporting tools
Employee training
- How to submit a leave request
- How to check their leave balance
- How to see team availability
- How to report an unplanned absence
HR training
- How to configure leave types and rules
- How to run reports and audit absence data
- How to handle escalations and appeals
Phase 5: Review and refine
First 30 days
- Monitor adoption — are managers and employees actually using the system?
- Check for configuration errors — are accruals calculating correctly?
- Gather feedback — what is confusing, what is missing?
First 90 days
- Review the first full cycle of leave requests and approvals.
- Identify any policy gaps the system exposed.
- Adjust configuration based on real usage patterns.
Quarterly
- Run an absence report by department.
- Check the Bradford Factor for any emerging patterns.
- Review the cost of absence against the previous period.
Annually
- Update the policy for any legal changes.
- Review the system configuration against the updated policy.
- Check bank holidays for the coming year.
Common leave management setup mistakes
1. Configuring the system before writing the policy
The policy defines the rules. The system enforces them. Configure the system to match the policy, not the other way around.
2. Choosing a system based on price alone
The cheapest system that does not handle your leave types, accrual rules, or approval workflows is more expensive than a properly featured system at a higher price.
3. Skipping training
A system without training is a policy without enforcement. Invest the time to train every manager and employee.
4. Not updating bank holidays annually
Bank holidays change. If your system does not have the correct dates, leave calculations will be wrong.
5. Ignoring the review phase
The first configuration is never perfect. Build in a review cycle and adjust based on real usage.
Putting it into practice
Five checks cover most leave management setup efforts:
- Write the policy before touching the system — define every leave type with entitlements, accrual rules, and approval criteria.
- Choose a system that handles your specific leave types, accrual rules, and multi-country requirements.
- Configure the system to match the policy exactly — test with a small group before rolling out.
- Train managers and employees on how to use the system — do not assume they will figure it out.
- Review quarterly in the first year — configuration gaps will emerge and need fixing.
A leave management system that is properly configured to match your policy, adopted by your team, and reviewed regularly turns absence management from a headache into a process that runs itself.
Frequently Asked Questions
What is the first step in setting up leave management?
Write the leave policy. Define every leave type, entitlement, accrual rule, and approval process before choosing or configuring a system.
What system do I need for leave management?
For teams of 10 or more, dedicated leave management software is the only practical option. For smaller teams, a well-structured spreadsheet can work temporarily.
How long does it take to set up leave management?
Typically 2–4 weeks for a small to mid-size business: 1 week for policy creation, 1 week for system selection and configuration, and 1–2 weeks for training and rollout.
How do I get my team to use the new system?
Train them. Make it easier than the old way. Set a go-live date and stop accepting requests through old channels. Lead by example — managers should use it first.
How often should I review the leave management setup?
Quarterly in the first year, then annually. Legal changes, bank holidays, and organisational changes all require policy and system updates.
This article is general information, not legal advice.
Last updated: 26 July 2026.