Five Signs Your Team Has Outgrown the Holiday Spreadsheet (and How to Tidy It Now)

A holiday spreadsheet usually stops working when your small business adds a second site or takes on staff in another part of the UK. One sheet then has to hold two sets of bank holidays, entitlements and carryover rules, and nobody can quite trust the balances. Below are five signs you have reached that point, and a checklist to tidy your holiday records today, whatever tool you use next.

Why the holiday spreadsheet starts to crack when you add a second site

The holiday spreadsheet cracks because it was built for one set of rules, and a new site brings another. The new office may follow different bank holidays, or staff there may be on contracts with different holiday entitlement or carryover terms. The single sheet now has to hold both, and it has no way of knowing which rule applies to whom.

In most small businesses, annual leave is looked after by an office manager, ops lead or founder alongside everything else. Leave lives in a spreadsheet, a trail of email threads and a pile of paper forms, and those three drift apart. Nobody planned it that way; it is just what happens when a busy person keeps three records in step by hand.

The cost shows up in four places:

Mistakes in holiday entitlement, often a day or two per person, found only when someone checks.
Disputes, when staff challenge what they are owed and you cannot show how the figure was reached.
Payroll corrections, made after the fact in the next pay run.
Compliance exposure, because rules applied inconsistently are hard to defend.

Check your own set-up against the five signs below.

Sign 1: Each site has its own bank holidays and one tab can't keep them straight

Bank holidays are not the same across the UK. Scotland and Northern Ireland each have bank holidays that England and Wales do not, and the reverse is also true. A holiday spreadsheet that serves staff in more than one nation has to apply the right calendar to each person.

In practice, one shared tab means someone has to remember which staff get which days. A formula copied down from an England-based row quietly applies the wrong calendar to someone in Glasgow or Belfast. Nothing flags the error.

The knock-on effect is balances that are off by a day or two per person. Because the mistake is silent, it usually comes to light only when an employee challenges their figure, by which point you have to reconstruct the year to put it right.

Sign 2: Holiday entitlement and carryover are applied from memory, not from rules

When holiday entitlement and carryover rules differ between sites or contracts, a spreadsheet holds them in someone's head or in a comment cell. The sheet stores numbers; it does not store the reasoning behind them.

The year-end scramble is the giveaway. Working out what each person can carry over becomes a manual exercise, and it is done slightly differently each year depending on who does it and how much time they have. Other entitlements are just as easy to get wrong in a sheet; our guide to calculating maternity leave accurately shows how many moving parts one type of leave can have.

Inconsistency, rather than a single error, is where the real risk sits. If two people in the same situation are treated differently, that is what turns a query into a dispute and a dispute into a compliance problem.

Sign 3: The spreadsheet, the emails and the paper forms no longer agree

Version clashes are the clearest sign that the holiday spreadsheet has stopped being the record. A holiday request is approved by email but never typed into the sheet. A paper form says one thing and the spreadsheet says another. Two copies of the file are saved on different drives.

This pattern is common well beyond the UK. Mellorca describes a small maintenance business where request, approval, balance and cover were handled separately by different people, which led to wrong balances, payroll errors and coverage gaps.

Balances nobody trusts are worse than no balances at all. Once staff stop believing the figure, they ask you instead, and the office manager is interrupted again and again with "how many days have I got left?" and "can I carry holiday over?" Each question is small; together they eat into the rest of the job.

Sign 4: Payroll gets corrected after the fact

If month-end leave figures for payroll have to be pieced together by hand from the sheet, the inbox and the forms, the record is not doing its job.

The pattern tends to repeat: annual leave is underpaid or overpaid, it is fixed in the next pay run, and an awkward conversation follows. Each correction also leaves another adjustment for someone to explain later.

Put plainly: if you routinely adjust payroll for annual leave after the event, you have outgrown the holiday spreadsheet.

Sign 5: You say yes to time off without seeing who else is off

A spreadsheet records leave, but it cannot warn you about a coverage gap at the moment you approve a holiday request. You only discover the overlap when you look at the week ahead, or when the day arrives.

The cost of overlapping leave is being short-staffed on client days and letting down the patients, clients or service users who rely on you. For a small team, two people off at once can be a third of the people on shift.

Redstone HR's own non-profit example shows what checking first looks like. A food bank needs to keep distribution running while staff take holiday. Managers check the team calendar and coverage warnings before approving, so key distribution days are not left short over the holiday season. There is more on how charities keep key programmes staffed over the holidays.

A bonus sign: when the person who built the spreadsheet leaves, the history and the logic behind it often go with them. If nobody else could explain how last year's carryover was worked out, the knowledge lives in a person, not a record.

Why a tidier spreadsheet won't fix it

A tidier spreadsheet moves the work around rather than removing it. More tabs, more colour coding and more reconciliation simply shift the same hours of checking, chasing and correcting onto someone who already has a full job.

Some things a spreadsheet structurally cannot do:

apply each location's bank holidays, entitlements and carryover rules automatically;
check cover at the moment you approve time off;
score absence consistently, for example using the Bradford Factor;
keep a reliable history of who changed what, and when.

The other extreme is not the answer for most small businesses either. Hiring dedicated HR, or buying a full HR suite priced per user, is often more than a 1–50 person team needs, and per-user costs rise with every hire. If you are weighing up the options in between, see these alternatives to tracking leave in Excel.

Checklist: how to tidy your holiday records now, whatever you use next

This checklist is worth doing even if you keep the holiday spreadsheet for another year. It also makes any future move far quicker, because clean records are what you will import.

List every site or region and write down the bank holidays each one follows for the current and next leave year.
Write each location's holiday entitlement and carryover rule in one place, in plain words, not just as formulas.
Agree opening balances with each employee and record the date you agreed them.
Choose one source of truth. Every holiday request and approval goes there; email or paper is only how requests arrive.
Record who approved each request and when.
Keep a change log, so the history survives if the person who maintains the sheet leaves.
Before approving, check who else is off on key days, and write down which days count as key for each team.
Produce one monthly leave figure per person for payroll from that single record, not from three sources.
Note every rule that varies by site. This list becomes your requirements: these are the things a future system must be able to set per location.

What to look for when you move on from the holiday spreadsheet

The right replacement removes the signs above, rather than just storing the same data somewhere new. Look for:

Rules set once per location. Bank holidays, entitlements and carryover applied automatically, so opening a new site does not multiply the admin.
A view of who is out, with a warning before you approve, not after.
Balances that update automatically, which staff can check and ask questions about themselves, so you only handle genuine exceptions.
Exports ready for payroll, so month-end is not a reconstruction job.
Pricing that does not rise every time you hire.

Whatever tool you choose, you remain responsible for compliance. Software can be configured to match the rules, but it does not take that responsibility away. For a feature-by-feature view, read the side-by-side comparison of spreadsheets and dedicated leave tracking.

How Redstone HR approaches this

Redstone HR is one way to run leave from a single record. Admins configure leave policies, bank holidays and carryover rules per location, and balances update automatically. Managers see the team calendar and coverage warnings before approving a holiday request.

Employees check their own balances and ask the AI policy assistant questions about the policy, so fewer of those questions land on your desk. Scheduled reports and payroll-ready exports come in CSV, Excel or PDF.

Pricing is a flat monthly fee per company by headcount band, not per user. The Growth plan covers 16–50 employees and up to 5 locations at $99 a month in total; Scale ($199 a month, 51–150 employees) adds unlimited locations and multi-jurisdiction rules. Typical setup time is about 15 minutes.

Redstone HR is a web app used in any desktop or mobile browser; there is no native iOS or Android app today. You can read more about who Redstone HR is built for.

FAQ: common questions about holiday spreadsheets

Is a holiday spreadsheet good enough for a small business? Often yes, while you have one site, one set of bank holidays and one carryover rule. Once two or more of the five signs above apply, the spreadsheet is costing more time than it saves.

How many staff before a holiday spreadsheet stops working? There is no fixed number. Extra sites, different bank holidays and differing carryover rules matter more than headcount.

Can one spreadsheet handle bank holidays for staff in different UK nations? It can, but only through manual upkeep, such as separate calendars per person or region, which is easy to get wrong without anyone noticing.

What should I fix first in my holiday records? Agree opening balances with each employee and pick one source of truth for every holiday request and approval. Everything else on the checklist builds on those two steps.

Your next step

Work through the tidy-up checklist above for each of your sites, and keep the list of rules that vary by location. Then read the side-by-side comparison of holiday spreadsheets and dedicated leave tracking to see which of your five signs a system would remove, or compare leave management options more broadly.

Frequently asked questions

Is a holiday spreadsheet good enough for a small business?

A holiday spreadsheet is often fine while you have one site, one set of bank holidays and one carryover rule. Once bank holidays differ between sites, balances stop agreeing or payroll needs correcting after the fact, the spreadsheet is costing more time than it saves.

How many staff before a holiday spreadsheet stops working?

There is no fixed headcount at which a holiday spreadsheet stops working. Extra sites, different bank holidays and differing carryover rules are better signs of the tipping point than the number of staff.

Can one spreadsheet handle bank holidays for staff in England, Scotland and Northern Ireland?

One spreadsheet can hold bank holidays for staff in different UK nations, but only through manual upkeep such as separate calendars per region. That upkeep is easy to get wrong, and a copied formula can apply the wrong calendar without anyone noticing.

What should I fix first in my holiday records?

Start by agreeing opening balances with each employee and choosing one source of truth for every holiday request and approval. The rest of the tidy-up, such as change logs and monthly payroll figures, builds on those two steps.