Absence Management: A Practical Guide for UK Teams

What absence management means day to day

The gap between how leave is described in a policy and how it behaves in practice is where nearly all the friction lives.

On paper: an employee requests time off, a manager approves it, a balance decreases. In practice: the employee is not sure what their balance is, the manager is not sure who else is away, and the balance lives in a spreadsheet that two people edit.

Everything worth saying about absence management follows from closing that gap — making the balance trustworthy, and making coverage visible at the moment someone decides.

A worked example: what the spreadsheet actually costs

A 25-person company runs leave on a shared spreadsheet plus email approvals.

Per request, the real handling time is rarely the 30 seconds people assume. Someone checks their own balance (2 minutes, often wrong), emails their manager (1 minute), the manager checks who else is off by scrolling the sheet (3 minutes), replies (1 minute), and someone updates the master sheet (2 minutes). That is roughly 9 minutes of human attention per request.

At 25 people taking an average of 18 requests-worth of leave events a year — holidays, odd days, appointments — that is 450 requests, or about 67 hours a year. Call it two working weeks spread thinly across the company in two-minute slices, which is the most expensive way to spend it.

The number that matters more is the error rate. Manual balance tracking across a year of edits reliably produces a handful of wrong balances, and those surface at the worst moment: a leaver’s final payslip, where an incorrect accrued balance is a payroll correction and occasionally a dispute.

The honest comparison is not "spreadsheet costs £0". It is 67 hours plus the cost of the two or three balance corrections you will make this year.

The rules that apply

The statutory baseline is 5.6 weeks of paid holiday per leave year, per gov.uk holiday entitlement guidance. For a five-day week that is 28 days, and employers may count the eight UK bank holidays within that figure or grant them separately — but the contract must say which.

Anyone not on a standard five-day week needs their own calculation. Entitlement is defined in weeks, so it multiplies by that person’s working week; it does not scale from 28 by intuition.

Acas is the practical reference for the awkward cases: sickness during booked holiday, leave during notice periods, and irregular hours.

Where the process usually breaks

Four failure points account for most of the pain, and none of them are about the policy document.

The balance nobody trusts. When employees keep their own count because they do not believe the official number, you have two systems and one of them is invisible.

The approval that sits. A request submitted on Monday and decided on Friday is not a policy failure, it is a visibility failure — the approver did not know it was waiting.

The clash discovered late. Two approvals that were individually fine, combined into a week with nobody senior on shift, noticed when the week arrives.

The correction that erases history. Someone edits an approved booking rather than cancelling and rebooking, and the audit trail quietly loses the fact that anything changed.

Each of these is a consequence of where the information lives, not of how strictly the rules are written.

Making it work operationally

Three things separate teams where this runs smoothly from teams where it does not.

The balance is trustworthy. One number, visible to the employee, that already accounts for future bookings — not just days taken.

Coverage is visible at decision time. The approver sees who else is off before deciding, not after.

The record survives people leaving. Approval history that lives in a manager’s inbox disappears when the manager does.

None of those require sophisticated software. They do require the record to live somewhere other than a spreadsheet and an inbox, because a spreadsheet cannot warn anyone and an inbox cannot be queried.

Where LeaveKit fits

LeaveKit is a leave management tool for UK teams of roughly 5 to 50 employees, and it is worth being precise about what it does and does not do.

What it does: month, week, 30-day and day views with department filter, hover detail cards, holiday and birthday markers; date range with half-day start/end and live working-day calculation; and — the part that motivated it — warns at booking time when teammates are already off on the same dates (/api/leave/conflicts). It also handles overtime entry logging at /toil, converts logged hours into toil balance, CSV reporting, an iCal subscription feed, and public holiday calendars for 11 countries with the UK dates checked against gov.uk for 2026 to 2028.

What it does not do, stated plainly because buying decisions are made on the gaps: there is no Slack integration, no two-way Google or Outlook calendar sync (the iCal feed is one-way), no payroll or Xero connector, no public API, and no SSO. The mobile app is built but not yet released. If any of those are requirements today, LeaveKit is not the right tool for you yet.

Commercially, LeaveKit is in early access with a 30-day free trial and no card required. Public pricing is not published yet. You can also open the demo workspace without signing up at all, which is the fastest way to judge whether the wall chart matches how your team actually thinks about coverage.

Frequently asked questions

How much holiday are UK employees legally entitled to?

The statutory minimum is 5.6 weeks of paid holiday per leave year, according to gov.uk holiday entitlement guidance. For someone working five days a week that is 28 days, and employers are permitted to count the eight UK bank holidays within that total rather than in addition to it. Part-time employees get 5.6 weeks of their own working week: three days a week gives 16.8 days. The contract must state whether bank holidays are included.

Can an employer refuse a holiday request?

Yes, an employer can decline a specific request, subject to notice requirements. What an employer cannot do is operate in a way that prevents someone taking their statutory entitlement at all. In practice, a refusal is far easier to defend when it comes with a concrete reason — a stated minimum cover level for that team on those dates — than when it is attributed to unspecified operational requirements. Acas publishes guidance on handling refusals.

What happens to holiday that has not been taken by the end of the leave year?

That depends on your policy and on which part of the entitlement is involved. Of the 5.6 weeks, 1.6 weeks can generally be restricted more tightly, while the four-week portion carries stronger protections — particularly where someone was prevented from taking it through sickness or because they were never given a real opportunity. Set a carry-over cap in policy, and run a balance check in the third quarter rather than in December.

Is LeaveKit free?

LeaveKit is in early access with a 30-day free trial and no card required. There is no permanent free tier and public pricing has not been announced yet. The trial is the full product: wall chart, booking with half-days, conflict warnings, approvals, TOIL logging, CSV reports and public holiday calendars. There is also a demo workspace at /demo that needs no sign-up at all.

Does LeaveKit integrate with Slack or sync with Google Calendar?

No Slack integration exists today, and calendar support is a one-way iCal subscription feed rather than two-way sync — leave appears in Google Calendar or Outlook, but changes made there do not flow back. There is also no payroll connector, no public API and no SSO at present. If any of those are firm requirements, LeaveKit is not the right fit yet, and it is better to know that before a trial than during one.

Try it on a real month

The fastest way to judge any leave tool is to run one real month through it. LeaveKit has a demo workspace that needs no sign-up, and a 30-day trial with no card required.

Open the demo workspace · Start a 30-day trial