Absence Management Software: How to Choose in 2026

What absence management software actually needs to do

Most evaluations start with a feature list, which is why most evaluations end with a tool nobody uses.

The useful starting point is the workflow: an employee wants two days off, a manager decides, and someone needs to know whether the team is still covered. Everything else is secondary to those three moments.

Judge candidates on how many clicks and how much context each moment takes. Can the employee see their true remaining balance without asking anyone? Does the manager see who else is off on those dates at the point of deciding, or do they have to go and look? When the answer is no, the tool has moved the admin rather than removed it — and moved admin is the most common outcome of a leave software purchase.

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 requirements that matter for UK teams

UK bank holidays, handled properly. Not just a list, but correct treatment when someone part-time does not work the day the holiday falls on. Ask specifically about this — it is where cheap implementations break.

Pro-rata and irregular patterns. If any of your team work compressed hours, term-time, or shifts, ask the vendor to calculate one of your real employees during the trial. Do not accept a demo of a five-day-a-week example.

Half-days, and preferably hours. Half-days cover most needs; hours cover everyone.

An export you can hand to payroll. A CSV is enough. A dashboard you cannot export is a dashboard you will re-key.

Approval history that survives staff turnover. When the approving manager leaves, the record has to remain.

Deliberately not on this list: integrations. They are usually the first thing asked about and the last thing used. Buy the workflow first.

Running a trial that tells you something

A 30-day trial spent clicking around a demo workspace tells you nothing, because demo data has no conflicts in it.

Run it against a real month instead. Load your actual team, your actual allowances, and let real requests flow through it in parallel with whatever you use now. One month is enough to hit at least one awkward case: a clash, a part-timer, a cancellation after approval, or a sickness conversion.

Then judge on three things. Did managers approve faster than by email? Did any balance come out wrong? And did anyone have to ask a human a question the tool should have answered?

That last one is the real test of adoption. Every question that reaches a person is a question the interface failed to answer, and those questions do not decrease after go-live — they multiply.

Getting the team to actually use it

The most common failure of a leave software purchase is not that the tool was wrong. It is that half the company kept using the old habit alongside it, so neither record was complete.

Three things prevent that. Set a hard cutover date and stop accepting requests by any other route from that date — a soft transition produces a permanent parallel system. Make sure managers can decide from their phone, because the approval delay is almost always a manager who will not open a laptop for a two-day request. And load the leave already booked for the rest of the year before you launch, so nobody’s first experience of the new tool is discovering their August holiday has vanished.

The signal that it worked is the absence of questions. If people stop asking HR what their balance is, the tool has replaced the habit. If they still ask, the balance is not visible enough or not trusted, and both are fixable.

Pricing, and what to check before signing

Dedicated leave tools generally sit at a low per-user monthly rate; full HR suites cost several times more because leave is one module among many. Vendors change pricing frequently, so any figure in an article — including this one — is a prompt to check the vendor’s own page, not a quote.

Four questions to ask before signing:

Is there a minimum user count? A five-user minimum makes a three-person team pay for five.

Is the price per active user or per record? These diverge quickly if you have seasonal staff.

What happens to your data if you leave? You want an export, in a format that opens.

Is VAT included in the quoted figure? Frequently it is not.

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

What should I test during a leave software trial?

Run it against a real month rather than demo data, because demo data contains no conflicts. Load your actual team and allowances, then check four things: whether a part-time employee’s entitlement calculates correctly, what happens when two people request the same week, whether a booking can be corrected after approval, and whether the payroll export opens cleanly. One real month will surface at least one awkward case; a week of clicking around will not.

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.

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