Spreadsheet vs Leave Software: When to Switch

Disclosure: some software links on this page are affiliate links. If you sign up through one, we may earn a commission at no additional cost to you. We only recommend tools we have set up and used, and commission never affects placement or verdicts. Not legal advice: this page summarises publicly available state agency guidance for general information. Verify with the linked agency or an employment attorney before acting on it.

When the spreadsheet is the right tool

Be honest about this, because most software comparisons are not. A spreadsheet is a perfectly good leave tracker when all of the following hold:

• fewer than about ten people;
• one country, so one public-holiday calendar and one set of rules;
• one policy — the same entitlement and carryover rule for everyone;
• one person maintains it, and approvals are recorded in it, not in chat;
• nobody has ever disputed a balance.

If that is you, the country page for your jurisdiction and a well-built workbook will do. The rest of this guide is about noticing when it stops being you.

The six ways spreadsheets fail

1. No audit trail. A cell that says 12 tells you nothing about how it became 12. When someone leaves and says they had 15, the workbook cannot show who approved what and when — and in every jurisdiction that requires payout at exit, that gap is money.

2. Formula drift. Someone inserts a row, a range stops updating, a carryover formula is copied from last year with last year’s cap. The error is silent until it is expensive.

3. Public holidays by location. The moment you employ someone in a second country — or a second German state, Spanish region or Australian state — the “holidays” column is wrong for somebody. Public holidays are per workplace, not per company.

4. Carryover and expiry logic. Every country’s rule is different: Dutch statutory days expire six months after the year, Swedish days can be saved for five years, Australian leave never expires, and the EU protects leave an employee could not take. A year-end formula that zeroes balances is illegal somewhere in any multi-country team.

5. Concurrent editing and access. Either everyone can see everyone’s sickness (a GDPR problem — sickness is special-category data) or one person is a bottleneck. Version conflicts in shared workbooks quietly overwrite approvals.

6. Liability blindness. Untaken leave is a debt at each person’s current pay rate in most of the world. A spreadsheet can compute it, but nobody looks, so the number is discovered on someone’s last day rather than managed through the year.

The signals that it is time

Switch when the first of these happens, not the third:

• a hire in a second country or region;
• a second policy group (part-timers, a different entitlement for a team, a collective agreement);
• a carryover or expiry rule you have to apply by hand;
• a manager approving leave in chat or email instead of the workbook;
• a disputed balance — even one, even resolved amicably;
• an exit where you had to reconstruct the balance;
• any request from an accountant, auditor or inspector for the history.

What to demand from a tool

Not features — records. Before you look at integrations, check the tool can:

1. Log every request, approval and change with author and timestamp, and export the log.
2. Run one policy per group: entitlement, accrual rhythm, cap, carryover and expiry, each per location.
3. Attach a public-holiday calendar per location, including regional holidays.
4. Show the balance and the liability on any date, not just today.
5. Restrict who sees what — managers see their team, HR sees all, colleagues see only that someone is away.
6. Export everything as CSV so you are never locked in.
7. Handle the leave types you actually have — annual, sick, parental, unpaid, time in lieu — with the right rules for each.

Cost is a weaker filter than it used to be. Several tools are free for small teams; the software comparison lists what each free tier includes and where the minimum charges start.

Migrating without losing the record

1. Pick a cut-over date — the first of a month is easiest.
2. Reconcile the spreadsheet first. Fix known errors now; do not import them.
3. Import people, entitlements and opening balances as of the cut-over date, per policy group.
4. Archive the workbook read-only with the date in the filename. It remains the record for earlier periods.
5. Approve everything in the tool from day one, including requests that arrive by chat — redirect them.
6. After the first month, run the liability report and compare it with what the spreadsheet would have said. The difference is usually your first finding.

The honest summary

Spreadsheets are not the problem; the moment you keep using one past its limits is. The limits are small — a second location, a second policy, a first dispute — and the cost of crossing them is paid at the worst possible time: when someone leaves and the balance has to be a number, not a reconstruction.

Related guides

Sources

• Regulation (EU) 2016/679 (GDPR), Articles 5 and 32 — data minimisation, integrity and security
• Working Time Regulations 1998 (UK), regulation 9 — records
• Leave Atlas — Best leave management software compared

General information, not legal advice. Rules change and national implementations differ — confirm against the current text or a local employment lawyer before acting. See our methodology.