Leave management software is where your team asks for time off, a manager says yes or no, and the balances and the "who's off" calendar update without anyone touching a spreadsheet. For a UK team of 5 to 50 people, the right one counts each person's own working pattern and bank holidays correctly, routes requests to the right person, and keeps a record you can show later, which since April 2026 is a legal requirement rather than a nice-to-have.
This guide is for owners of small service businesses (agencies, studios, consultancies) who've outgrown the spreadsheet or the "just message me" system. It covers what changed in UK law this year, the checks that separate a good tool from a pretty one, what the main UK options cost today, and a one-week test to run before you commit.
If you're not sure you need software yet, start with the free annual leave tracker layout. It's the same rules in a spreadsheet, and it's enough for a few people on the same hours.
What changed in 2026: leave records you have to keep
Since 6 April 2026, UK employers must keep records of annual leave and holiday pay, and keep that information for at least six years. That's from Acas's summary of the Employment Rights Act 2025. The duty sits in section 35 of the Act, which adds it to the Working Time Regulations and leaves the format to the employer.
Two practical consequences for a small team:
- The common spreadsheet habit of copying this year's tab and overwriting the balances in January destroys exactly what you now need to keep. Six years of leave years is six intact tabs, or a system that keeps the history for you.
- Leave software records the days. What you paid for them usually lives in payroll. Make sure both halves exist and can be put side by side if someone queries a payslip.
The same April changes made paternity leave and unpaid parental leave day-one rights, and statutory sick pay now starts from the first day of illness, according to the same Acas page. If your tool has leave types for these, check that nobody is blocked from booking them because of a length-of-service rule someone set up years ago.
The rules the software has to get right
The law behind leave in the UK is short. The difficulty is applying it to real people with different hours. Per gov.uk's holiday entitlement guidance, almost all workers get 5.6 weeks' paid holiday a year, capped at 28 days, and an employer can choose to count bank holidays inside that allowance. Part-timers on regular hours get the same 5.6 weeks of their own working week: three days a week is 16.8 days. Irregular-hours and part-year workers build up leave from the hours they've already worked.
Carry-over is where most tools and most policies get vague. Per Acas on carrying over holiday, without an agreement that allows it, workers must take their 5.6 weeks in the leave year. There are exceptions you can't opt out of: someone on long-term sick leave can carry over up to 4 weeks and has 18 months to use it; someone who couldn't take holiday because of maternity or other statutory leave must be allowed to carry it over; and if you didn't let someone take their holiday, or didn't tell them they'd lose it, they can carry over up to 4 weeks.
So the questions to ask any leave tool are:
- Does it count a booking against that person's working days, not a generic Monday to Friday?
- Can different people have different public holiday calendars? England and Wales, Scotland and Northern Ireland have different bank holidays, and anyone abroad has their own.
- Can it handle the part-timer who works Tuesday to Thursday, and the starter who joins in June, without you overriding numbers by hand?
- Can it apply a carry-over cap at the start of the leave year, and let you grant an exception (the long-term sick case) with a note saying why?
- If you have irregular-hours staff, does it accrue in hours? Many tools only count days. Ask before you buy, not after.
The annual leave tracker guide works through each of these with a six-person example, if you want to check your own numbers first.
What leave management software must do for a small team
Large HR systems sell on reporting and integrations. At 5 to 50 people the things that matter are more basic, and you can check every one in a trial.
| Need | What good looks like | Why it matters at your size |
|---|---|---|
| Requests in one place | Phone or browser, with half days at either end | Requests in chat, email and the corridor are how clashes happen |
| The right approver | Goes to the person's manager, with a fallback when they're off | The founder shouldn't approve every half day once there's a team lead |
| Clash warnings | Shows who else is off in the same role or on the same project | Two of your three developers off in launch week is a delivery problem, not an HR one |
| Correct balances | Recalculated from the requests, not typed in | A balance you can't explain is the start of every leave dispute |
| Adjustments with a reason | Who changed it, by how much, why | The next person, or you in two years, can see why the number is what it is |
| A calendar people see | A shared view plus a feed into Google, Outlook or Apple | Nobody opens a leave app to plan their week |
| History that lasts | Last year's requests and decisions still there | The 2026 record-keeping duty |
| Leave beyond the allowance | Either blocked, or split into paid and unpaid with the person told | Saves the awkward conversation after the payslip |
| Other leave types | Sick, unpaid, parental, compassionate, TOIL | Not all absence is holiday, and capacity planning needs all of it |
The one most small teams skip is clash warnings. It's the difference between a leave tool and a leave calendar. If you plan client work around who's in, the capacity planning guide explains why the calendar on its own isn't enough: you need leave subtracted from the hours you're promising clients.
If people work overtime for launches and take the time back later, check how the tool handles time off in lieu. Most treat it as a custom leave type with manual top-ups. The TOIL guide has a policy you can copy and the tracking options.
What it costs: UK prices checked today
There are three kinds of tool a small UK team ends up comparing. These prices are from each company's own pricing page on 19 November 2026, excluding VAT.
Dedicated leave apps charge per user per month. Timetastic shows two leave plans, Business at £1.20 and Pro at £2.00 per user a month for UK visitors, plus a Rota & Time Clock plan that adds shifts and timesheets. It's month to month with a 30-day trial and no card. (The page loads live prices by region, so check yours.) Leave Dates starts at £0.75 per user a month across Starter, Essential and Plus plans, with 25% off yearly billing and a 30-day trial. Its page notes that every employee added counts towards the subscription even if they never log in, and that archiving people who've left is on Essential and Plus, not Starter.
HR suites include leave alongside records, documents and more, usually priced by company size. Breathe is £24 a month for up to 10 employees, £44 for 11 to 20, and £99 for 21 to 50, with holiday and absence management in every plan, a 14-day trial, and roughly 15% off for paying yearly on those bands.
All-in-one workspaces include leave as one part of running the business. Suprwork is one of these, covered below.
Here's what that looks like for two team sizes. The leave-app figures are per user at the prices above; Leave Dates is shown at its starting price because its page doesn't list the per-plan rate.
| Monthly cost, ex VAT | 10 people | 25 people |
|---|---|---|
| Leave Dates (from) | £7.50 | £18.75 |
| Timetastic Business | £12.00 | £30.00 |
| Timetastic Pro | £20.00 | £50.00 |
| Breathe (by band) | £24 | £99 |
For leave alone, the dedicated apps are cheap and hard to beat. The number that matters is what else you're paying for per person. A 25-person team on a per-seat project tool, a per-seat chat tool, a timesheet app and a leave app can spend more on the per-head tools around the work than on any one of them. That's the calculation in replacing Slack and ClickUp with one tool.
Which kind of tool fits which team
Pick the dedicated app if leave is the only thing that's broken. Your projects, chat and invoicing all work, people just book holiday by message and balances drift. Timetastic and Leave Dates are both built for UK teams, cheap, and set up in an afternoon. This is the right answer for a lot of small businesses, and we'd say so to anyone asking.
Pick an HR suite if what's really missing is employee records: contracts, documents, absence history and the rest of the HR admin, with leave as one part of it. Breathe's banded price means adding people within a band costs nothing extra, which suits a team that's growing steadily.
Look at an all-in-one workspace if leave is a symptom of a wider problem: you're paying per seat for several tools, you still ask people for status because nobody updates the project tool, and you plan client work in one place while leave lives in another. In that case adding a leave app fixes one spreadsheet and adds one more login.
Where Suprwork fits
Suprwork is one workspace for running a small service business: projects and time, team chat, check-ins, invoicing and the people side, including time off. Plans are a flat monthly price with everyone on the team included (Starter $49, Basic $99, Plus $199, Max $249 on the pricing page), so a new starter or part-timer doesn't change the bill.
What the time-off part does today:
- It reads the leave policy you already wrote and proposes each leave type (allowance, upfront or monthly accrual, carry-over cap, leave-year start), quoting the sentence it came from, and you apply what's right.
- Each request is counted in that person's working days, minus their public holidays, with half days at either end, and the balance is checked before it goes to their manager.
- The request lists who else in the same role or on the same project is off on some of the same days.
- When a request goes past what's left, the days that fit stay on the leave type and the rest can be booked as unpaid leave.
- Each request keeps who decided it and when, and cancellations keep who cancelled. A people lead can record leave that was missed or agreed off the system, marked as recorded by them.
- Balance corrections are logged with the number of days, a note, who made it and when.
- A team calendar, a calendar feed for Google, Outlook or Apple, balances and requests in the phone apps, and who's away next week on the owner's dashboard.
- Approved leave and public holidays come off people's capacity in projects and time, so the forecast date for someone's work accounts for their holiday.
What it doesn't do: public holidays are entered or copied in, not fetched for you; it counts in days and half days, not hours; and it doesn't make payroll deductions or hold holiday pay, so the pay half of your 2026 record stays in payroll. Your written policy can live in Documents.
If all you need is a leave calendar, a dedicated app is cheaper. Suprwork makes sense when leave is one of several things you want in the same place as the work.
A one-week test before you commit
Most UK leave tools give you a two- to four-week trial. Use the first week for this rather than clicking around the demo data.
- Load your three hardest people. The part-timer, the person who joined mid-year, and anyone in Scotland, Northern Ireland or abroad. Work out their correct allowance by hand from the gov.uk rules and compare.
- Book a request that spans a bank holiday. The bank holiday shouldn't come off the balance unless your policy puts bank holidays inside the allowance.
- Book a clash. Two people in the same role, overlapping days. See whether the approver is told before saying yes.
- Go over the balance. What happens: blocked, warned, or split?
- Correct a balance. Is there a reason field, and can you see it later?
- Approve as someone other than the owner. Then check the record shows who approved.
- Look for last year. Ask the vendor how you'd see a 2026 request in 2031, and how you'd get it out if you left.
- Get the calendar into your own calendar. If the feed doesn't work in five minutes, nobody on the team will use it.
Score each one pass or fail. A tool that fails 1 or 2 will produce wrong balances, and no amount of nice design fixes that. A tool that fails 7 leaves you exposed on the record-keeping duty.
Before you switch: write the policy down
Software applies a policy; it can't invent one. Before you load anyone in, write down your leave year, whether bank holidays sit inside or on top of the allowance, how starters and leavers are pro-rated, how much contractual leave carries over, how half days round, who approves what, and how much notice you want. Gov.uk says that if there's nothing in the contract, workers must give notice of at least twice the length of the leave they want, plus one day (three days for one day off), which is a sensible default to write in if you haven't set your own.
Once it's written, the setup in any of these tools takes an hour, and the answer to "how many days do I have left?" stops being a question you get.
Sources
- Acas, Employment Rights Act 2025 (leave records from 6 April 2026; checked 19 November 2026)
- Legislation.gov.uk, Employment Rights Act 2025, section 35
- Gov.uk, Holiday entitlement and Booking time off
- Acas, Carrying over holiday
- Timetastic, Pricing; Leave Dates, Pricing plans; Breathe, HR software prices (all checked 19 November 2026)