Leave of Absence UK: A Practical Guide for Employers

A Manchester operations manager starts the week with two sickness absence cases, three annual leave requests and a bereavement notification. Each request has a different eligibility test, evidence requirement, pay consequence and approval route. The manager still needs to keep the operation staffed, while HR must produce records that explain what happened and why.

That's the practical reality behind leave of absence UK administration. Leave isn't a single form or calendar entry. It's a controlled process linking employee wellbeing, statutory rights, payroll, workforce planning and evidence. The employers that manage it well give managers clear rules, capture decisions consistently and keep one reliable record from request to return.

Why Leave of Absence Matters More Than Ever in the UK

Sickness absence remains a large-scale workforce issue. The Office for National Statistics sickness absence figures for 2025 put the UK sickness absence rate at 2.0%, unchanged from 2024. An estimated 148.8 million working days were lost because of sickness or injury, averaging 4.4 days per worker.

The recent history matters. The rate reached 2.6% in 2022, when 185.6 million working days were lost, the highest level since 2004, before easing through 2023 and 2024. The 2025 rate remains only slightly above the pre-coronavirus 2019 level, so employers are operating with a higher baseline than the long-run pre-pandemic norm.

Leave is a management control, not an inbox task

The compliance pressure is moving towards evidence. From 6 April 2026, statutory sick pay changes affect the first full day of sickness, the lower earnings limit and the way payroll assesses eligibility. The UK Government guidance on statutory sick pay changes says SSP will be payable from the first full day, with the lower earnings limit removed. The weekly rate will be the lower of £123.25 or 80% of average weekly earnings.

Annual leave creates a separate audit problem. CIPD guidance on holiday records and annual leave obligations highlights the requirement from 6 April 2026 for employers to keep records that are “adequate to show” compliance with annual leave and holiday pay duties under the Employment Rights Act 2025.

That means a defensible process must show the request, the decision, the entitlement calculation, relevant evidence, pay treatment and the employee's return. Wellbeing support also belongs in the operating model. Employers reviewing their approach to burnout and absence may find workplace wellness from reVIBE Mental Health useful when building earlier support around leave decisions.

The Main Types of Leave UK Employers Must Manage

A reliable leave framework starts by classifying each request correctly. Statutory leave comes from legislation and cannot be treated as a discretionary benefit. Contractual or discretionary leave may be enhanced by the employer, but the policy must state the conditions clearly and apply them consistently.

Annual leave is governed by the Working Time Regulations. Most workers are entitled to 5.6 weeks or 28 days of statutory annual leave, as explained in CIPD guidance on UK holiday entitlement. Employers must also manage sickness absence and SSP, including self-certification, fit notes, occupational sick pay and return-to-work arrangements.

Parental categories require particular care. Maternity, paternity, adoption, parental leave, Shared Parental Leave and parental bereavement leave each have different eligibility, notice and pay rules. The Government review of parental leave and pay evidence records that mothers' maternity leave lasts nearly 44 weeks on average in total, including about 40 weeks after birth. Average maternity leave rose from 32 weeks in 2006 to 39 weeks in 2008. Shared Parental Leave is used at much lower levels, with average leave among all SPL parents just over 16 weeks, while the same evidence includes measures of 10 weeks for men and 14 weeks for women.

Other statutory categories include carer's leave, time off for dependants, jury service, public duties and reservist duties. Parental bereavement arrangements also require employers to check the applicable UK jurisdiction, particularly where employees work across England, Wales, Scotland, Northern Ireland, Jersey or the Isle of Man.

Common discretionary categories include compassionate leave, study leave, sabbaticals and religious observance. Pregnancy-related appointments and time off for trade union duties can create additional operational requirements.

Eligibility, Notice and Documentation Essentials

Managers shouldn't decide leave eligibility from memory. HR should maintain a simple rules matrix showing the qualifying conditions, notice route, evidence and pay treatment for every category.

Parental leave normally requires one year of continuous service, while carer's leave is a day-one right. Time off for dependants covers a reasonable amount of time to deal with an emergency, not an open-ended absence. The employee should notify the employer as soon as reasonably practicable and explain the reason and expected duration.

Notice varies by leave type. Maternity and Shared Parental Leave require advance planning and formal notices, while sickness absence may be reported at short notice under the organisation's absence procedure. Jury service is supported by the official summons. Employers should avoid imposing an invented notice standard where legislation or the contract provides a different route.

Ask for relevant evidence, not unnecessary medical detail

Evidence should prove the entitlement or explain the operational event. Typical examples include:

• Sickness absence: Employees can usually self-certify for the first 7 calendar days. A fit note is generally required from day 8 for longer sickness absence.
• Maternity: A MAT B1 certificate or relevant birth evidence can support maternity administration.
• Jury service: The jury summons confirms the obligation and dates.
• Parental leave: Formal notices and declarations may be needed for the statutory scheme.
• Carer's leave: The employee's request should identify the intended leave dates and confirm the statutory basis.

An employer shouldn't demand a diagnosis for a short sickness absence that falls within the self-certification period. Medical information must be limited, protected and accessible only to people who need it for a legitimate HR, payroll or management purpose.

Leave records should show entitlement, dates, approvals, evidence and pay outcomes. The Working Time Regulations create record-keeping duties, while tribunal claims have strict limitation rules and may require an employee to bring a claim within the applicable early conciliation and tribunal time limits. Store the evidence from the first request, not after a dispute has started.

Sample Leave of Absence Policy UK Employers Can Adapt

A workable policy should read like an operating instruction. Start with scope, identifying employees covered, the manager responsible for first review and the HR team responsible for statutory validation. Then separate annual leave, sickness absence, maternity, paternity, adoption, parental leave, bereavement, jury service, public duties and discretionary arrangements.

Each category needs five practical statements:

1. Eligibility: State who qualifies and whether service is required.
2. Notice: Explain the normal notice route and the exception for emergencies or sickness.
3. Evidence: List what the organisation can request, such as a fit note, MAT B1 or jury summons.
4. Pay: Distinguish SSP, statutory family-related pay, contractual sick pay and unpaid leave.
5. Return: Set out contact expectations, return-to-work discussions, adjustments and phased returns.

The policy should refer to the Employment Rights Act 1996 and the Working Time Regulations 1998. It should also state that SSP arrangements will be updated for the changes taking effect on 6 April 2026, including first-day payment, removal of the lower earnings limit and the revised weekly rate described in the Government employer guidance for SSP. That source is already relevant to payroll configuration, so HR should avoid maintaining a second contradictory summary.

Make the policy usable in the real workforce

Shift workers and part-time employees need examples that reflect their working pattern. Explain how entitlement is expressed for their schedule, how managers handle overlapping requests and how public holidays interact with contracted working days. State how carry-over works after family leave or long-term sickness, and explain the holiday pay treatment applied by payroll.

Unauthorised absence should trigger a fair investigation, not an automatic disciplinary outcome. The policy must distinguish misconduct from illness, caring emergencies and protected leave. Keep the approved policy, employee acknowledgement and version history in a controlled HR document centre so HR can identify which wording applied when a decision was made.

How to Run a Smooth Leave Request and Approval Process

A defensible process has a fixed sequence. It gives employees a clear route, gives managers enough information to plan cover and gives HR an audit trail that explains the final decision.

1. Employee submission: The employee uses a self-service form, portal or designated email route. The request captures leave type, dates, expected return, supporting evidence and any adjustment or contact needs.
2. Manager review: The manager checks team cover, operational constraints and any existing approved leave. The manager shouldn't decide statutory eligibility alone where pay or legal status is involved.
3. HR validation: HR checks qualifying service, entitlement, evidence, holiday balance and payroll impact. At this point the organisation identifies a family leave category, SSP issue or potential reasonable adjustment.
4. Decision and notification: The approver confirms approval or refusal in writing. A refusal should give a genuine operational reason and explain any alternative dates or next step.
5. Record and payroll synchronisation: The final decision updates the leave calendar, employee record, payroll input and reporting dataset. The return-to-work conversation then records actual attendance, adjustments and follow-up actions.

Apply the same decision logic to difficult requests

Overlapping annual leave requests are manageable when the policy sets the method in advance. Use an announced cut-off, assess operational cover against objective criteria and record why one request was accepted while another was refused. School holiday peaks need capacity planning, not informal first-come assumptions that managers apply inconsistently.

Short-notice sickness should follow a different route. The employee reports the absence through the agreed channel, the manager records the expected duration and HR validates pay and evidence when required. Managers should focus on fitness for work and support, rather than asking intrusive questions about diagnosis.

Fairness test: If another manager reviewed the same facts, would the written record show why the outcome was reasonable?

A platform can route approvals through Microsoft Teams or email, but automation shouldn't remove judgement. HRManagement365 can be configured within a Microsoft environment to centralise leave requests, approvals, balances, absence records and reporting. It's based on Dynamics 365, Power Platform and Dataverse, with customer-specific workflows, integrations and applications added where the standard process doesn't fit.

Annual Leave Record-Keeping and SSP Changes for 2026

The 2026 compliance issue isn't just calculating entitlement. It's proving what the employer calculated, what the employee took, what carried over and how holiday pay was handled. CIPD identifies the requirement from 6 April 2026 for records that are “adequate to show” compliance with annual leave and holiday pay obligations under the Employment Rights Act 2025. Employers using spreadsheets and shared inboxes should treat this as a control weakness.

A usable record should connect the employee's contract, working pattern, entitlement, accrual, requests, approvals, cancellations, carry-over, payment and termination calculation. Irregular-hours and part-year workers need particular attention because entitlement and holiday pay depend on the applicable rules and the employee's actual working pattern.

Prepare payroll and HR together

From 6 April 2026, SSP is payable from the first full day of sickness, the lower earnings limit is removed and the weekly rate becomes the lower of £123.25 or 80% of average weekly earnings, according to Business.gov.uk's employer guidance. Eligibility checks will focus on qualifying days and average weekly earnings over the previous 8 weeks, rather than a minimum earnings threshold.

That change affects low-paid employees, payroll exclusions, waiting-day logic and any occupational sick pay scheme that offsets SSP. HR and payroll should test the rule against real employee scenarios, update policy wording and confirm that the absence record feeds the correct payroll period.

Long-term sickness can also affect holiday accrual and carry-over. Don't rely on a manager's calendar or a payroll note to resolve it. A controlled system should flag missing evidence, apply configured entitlement rules, calculate pro-rated entitlement on termination and retain the decision history.

For organisations reviewing the wider workforce data flow, time and attendance systems can help connect working patterns, absence events and payroll inputs. The objective is one traceable record, not another isolated tool.

How HR Software Simplifies Leave Management

Spreadsheet sprawl creates predictable failure points. One file contains annual leave balances, another records sickness, a shared inbox holds approvals and payroll maintains a separate SSP calculation. When an employee changes hours, transfers team or returns from family leave, someone has to reconcile the versions manually.

An integrated HR platform gives the employee one profile containing contract data, working pattern, entitlement, carried-over days, absence events and relevant payroll inputs. That profile can sit in Microsoft Dataverse, while Power Automate routes requests and reminders, Power Apps supports custom forms and Power BI presents management reporting.

Automate the routine, keep judgement with people

A sensible configuration can:

• Route requests: Send an annual leave request to the correct line manager, then escalate overdue approvals.
• Calculate balances: Apply configured UK entitlement rules, including the statutory 5.6-week minimum where relevant.
• Control over-booking: Flag conflicts with team cover, blackout periods or insufficient balance before approval.
• Capture evidence: Attach fit notes, family leave notices, summonses and approval commentary to the employee record.
• Synchronise payroll inputs: Pass approved absence and SSP information to the relevant payroll or finance process.
• Report patterns: Give HR and leaders visibility of absence, leave usage, returns and unresolved exceptions.

The configuration must be explicit. Microsoft Teams, Outlook, Microsoft 365, Dynamics 365 Business Central, Finance & Operations and Power BI may form part of the surrounding Microsoft estate, but the organisation still needs to define the rules, ownership and integration points. Copilot can assist with suitable administrative tasks where configured and governed correctly, but it shouldn't make unsupervised decisions about statutory entitlement or sensitive health information.

See how leave of absence management software can support a defined workflow. HRManagement365 can extend Hubdrive and Microsoft technology through implementation, configuration, integrations, custom approval flows and HR applications for customer-specific employee lifecycle processes.

Common Mistakes and Practical Next Steps

Most leave failures aren't caused by obscure law. They happen because an ordinary request enters the wrong process, a manager makes an undocumented exception or payroll receives incomplete information.

• Treating statutory leave as discretionary: Map each request to its legal category before discussing operational convenience.
• Miscalculating part-time entitlement: Base the calculation on the employee's working pattern and apply the relevant rules for irregular hours and part-year workers.
• Losing carry-over after family or sickness leave: Configure a review trigger when an employee starts or ends protected or long-term absence.
• Applying outdated SSP logic: Update payroll and HR workflows for the 6 April 2026 changes, including first-day payment, the removed lower earnings limit and the revised rate.
• Keeping weak evidence: Store the request, decision, supporting document and pay outcome together, with controlled access to health information.
• Leaving refusal decisions unexplained: Record the operational reason, alternatives considered and any review route.
• Ignoring reasonable adjustments: Train managers to consider temporary or longer-term adjustments where health or disability may affect work.

Run four checks this quarter:

1. Confirm that the written policy covers statutory, contractual and discretionary leave.
2. Standardise request, evidence, approval and return-to-work templates.
3. Move leave records from disconnected spreadsheets into one controlled HR platform.
4. Run a dry-month audit before the next peak absence period, checking balances, approvals, evidence, payroll updates and reporting.

The aim is simple: every leave decision should be understandable to the employee, usable by the manager and defensible to HR, payroll or an auditor.

HRManagement365, powered by Hubdrive and Microsoft, can help UK and EU organisations connect leave requests, approvals, absence records, employee data, workflows and reporting across the HR lifecycle. Speak to the HRManagement365 team about implementation, custom workflows, Power Platform integrations and a practical leave management process, then visit HR Management 365 or phone +44 1522 508096 today.

Chris Pickles Director | Dynamics 365, Power Platform & HR Solutions Architect

I help HR leaders get off the admin hamster wheel with a Dynamics-based HR Management solution built on Hubdrive. HRManagement365 gives organisations a flexible HR platform within the Microsoft ecosystem that can be easily customised around the way they already work — rather than forcing teams into rigid, one-size-fits-all processes. It can be tailored to your HR workflows, integrated with Microsoft Dynamics 365 Business Central (BC) and Finance & Operations (F&O), and extended with Microsoft Power Platform to automate processes and connect HR more closely with the wider business. For employees, the experience stays familiar. They can interact with HR processes through the Microsoft tools they already know and use every day, including Teams, Outlook, Word and Power BI, helping drive adoption without introducing another unfamiliar system. The goal is simple: less manual admin, better-connected processes and an HR solution that fits your organisation. If you’re using Microsoft Dynamics and want HR to work as part of the same ecosystem, ask me about HRManagement365.

See Full Bio

Digital Transformation Microsoft Power Platform Power Apps Power Automate Power BI Dynamics 365 HR / HR Systems Business Process Automation Hubdrive HR