

When you are building a startup, leave management probably ranks somewhere below "product-market fit" and "not running out of money" on your priority list. That is understandable. But getting it wrong from the start creates legal risk, payroll headaches, and resentful employees — all things that slow you down when you need speed most. Here is the minimum you need to get right and how to scale it as you grow.
From the day you hire your first employee, you are bound by the Working Time Regulations 1998. The key requirements:
Founders beware: The 28-day minimum applies to workers, not just employees. If you have contractors who are legally "workers" (common in startups), they are entitled to paid leave too. Misclassification is one of the most expensive mistakes a startup can make.
Even a two-person startup should have a basic leave policy. Without one, every leave request becomes a negotiation. Write down your rules — even a single page is enough — and include them in employment contracts or your staff handbook.
"We are only five people, I just remember who is off." This works until it does not — usually around the time someone accuses you of approving their colleague's leave but not theirs, or an employee leaves and you owe them untaken holiday pay.
Startups often hire people on varied contracts: 3 days a week, compressed hours, term-time only. Each requires a different pro-rata calculation, and getting it wrong means either overpaying or underpaying leave — both of which are problems.
When someone is off sick repeatedly, many startup founders either ignore it (too awkward) or overreact (too heavy-handed). A simple sick leave policy with clear triggers (e.g. a return-to-work conversation after every absence) gives you a fair, consistent framework.
When an employee hands in their notice, you must calculate and pay any accrued but untaken leave. If you have not been tracking balances, this calculation becomes guesswork — and guesswork invites disputes.
A Google Sheet can genuinely work for a team of 2–5 people. Beyond that, the cracks appear fast:
| Team size | Approach | Why |
|---|---|---|
| 1–5 | Spreadsheet + written policy | Low volume; founder can manage manually |
| 6–15 | Dedicated leave management tool | Multiple leave types, part-timers, coverage planning needed |
| 15+ | Leave management tool with integrations | Payroll sync, reporting, audit trail, manager self-service essential |
The tipping point for most startups is around 8–10 employees. At that point, the founder or office manager is spending several hours per month on leave admin, errors creep in, and the lack of a team calendar causes scheduling conflicts.
Not all tools are built for startups. Here is what matters most when you are small and growing:
Your first leave policy does not need to be complex. Start with the basics and add layers as you grow:
Startup culture can inadvertently discourage people from taking leave. When everyone is working hard and the mission feels urgent, booking two weeks in the Algarve can feel like letting the team down. This is a cultural problem that founders must actively counter:
LeaveManager was designed from the ground up for growing UK teams. Here is why startups choose it:
Try LeaveManager free for 14 days — built for UK startups, from your first hire to your fiftieth.