Reduce Burnout — Root Causes and Practical Fixes | LeaveKit

Why this keeps happening

Recurring leave problems are almost never caused by individual carelessness. They are caused by decisions made without the information that would have prevented them.

An approver deciding a request in isolation cannot see the other three requests sitting in other managers’ queues for the same week. An employee booking time off cannot see that the only other person who knows the billing system is already away. Both act reasonably, and the outcome is still bad.

So the diagnostic question is not "who got this wrong". It is "what did the person deciding not have in front of them".

A worked example: separating sickness from annual leave

An employee is signed off sick for three weeks in June, and two of those weeks had already been booked and approved as annual leave.

Under UK rules, they are entitled to reclaim those two weeks as annual leave rather than lose them — sickness during booked holiday converts back, provided they follow the notification process in your policy. That is the position reflected in Acas guidance on holiday and sickness.

So the sequence is: the two weeks return to their annual leave balance, and the whole three-week period is recorded as sickness absence, subject to your Statutory Sick Pay rules and any company sick pay scheme.

The practical trap is the audit trail. If your system recorded those two weeks as "holiday — approved" and someone simply edits the record to "sick", you have lost the fact that a conversion happened, when it was requested and who authorised it. Six months later, in a capability or pay dispute, that missing history is the problem — not the two weeks themselves.

Record the conversion as an event, not an edit. At minimum: original booking, date of sickness notification, date of conversion, and who approved it.

Fixing it structurally

Three changes fix most of it, in descending order of effect.

Show conflicts at the point of decision. Not in a weekly report, not in a calendar someone has to open — in the request itself. This is the difference between a policy people have to remember and a system that makes the right thing easy.

Define minimum cover per team, explicitly, as a number. "Use judgement" is not a threshold; four people is a threshold.

Make the queue visible. Approvals that sit for a week are usually approvals nobody knew were waiting.

The order matters. Stricter policy without better visibility just produces more escalations.

Diagnosing your own version of it

Before changing anything, establish which of the four common shapes you actually have, because the fixes differ.

A visibility problem: decisions are made without knowing what else is pending. Symptom — clashes that everyone agrees should have been obvious.

A threshold problem: nobody has defined what "enough cover" means, so every decision is a judgement call and different managers judge differently. Symptom — inconsistent outcomes for similar requests.

A queue problem: requests wait because approvers do not know they are there. Symptom — long gaps between submission and decision, with no disagreement about the outcome.

A record problem: the balance or the history is unreliable. Symptom — disputes about what someone had, or an inability to say who approved something.

Run a month of your own requests against those four descriptions. The distribution tells you where to spend effort, and it is usually concentrated in one.

The conversation when you have to say no

Sometimes cover genuinely does not allow it, and the request has to be declined. How that is handled determines whether the policy is seen as fair or arbitrary.

Give the actual reason, with the number. "We need four on the support desk that week and approving this leaves three" is a reason someone can evaluate. "Operational requirements" is not, and it reads as a decision made about the person rather than the rota.

Offer the alternative in the same message. If the Tuesday works but the Wednesday does not, say so.

And check whether the same person is repeatedly the one declined. Peak weeks concentrate on the same people — parents in school holidays, for example — and a first-come-first-served rule quietly becomes a rule about who checks their email fastest.

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 do I stop two people booking the same week off?

Make the clash visible at the moment of decision rather than afterwards. Define a minimum cover number per team as an explicit figure, then ensure the person booking and the person approving both see who else is already off on those dates. LeaveKit does this check at booking time. Without that, two managers approving separately will each make a defensible decision and the combination will still leave you short.

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

Reduce Burnout — Root Causes and Practical Fixes