The Complete Guide to Annual Leave Tracking for Small Businesses

Annual leave tracking for small businesses doesn't need to be complicated. With two or three people on the team, a shared calendar works. By ten or twenty employees, it breaks down: overlapping requests, part-time entitlements, days carried over from last year, public holidays, and the inevitable dispute about who booked Christmas first.

This complete guide to annual leave tracking covers what small businesses actually need: calculating entitlements, choosing a system that works, and handling the edge cases that catch most businesses by surprise.

Legal entitlements

Your starting point is the legal minimum. Annual leave entitlements vary by jurisdiction, but most countries guarantee a minimum number of paid holiday days per year:

• 28 days (including public holidays) in the UK for full-time workers
• Varies by state in the United States (no federal mandate for private-sector workers under the FLSA)
• 20 days across much of the European Union
• 20 days in Australia for full-time workers
• 4 weeks in New Zealand

These are minimums. Many businesses offer more. Know the legal requirement for your jurisdiction and ensure your policy meets or exceeds it. If you're unsure, check with ACAS (in the UK) or your local employment standards body.

Part-time workers and pro-rata entitlements

A part-time worker is entitled to a pro-rata share of the full-time entitlement. A worker doing three days per week gets three-fifths of the full-time allowance.

The math is straightforward:

Part-time entitlement = Full-time entitlement × (Part-time hours ÷ Full-time hours)

Example: Full-time entitlement is 28 days. A worker does 24 hours per week out of a standard 40-hour week:

28 × (24 ÷ 40) = 16.8 days

You can round this up to 17 (and probably should, to stay generous). Never round down below the statutory minimum.

Accrual during the year

Leave typically accrues as time passes. A worker starting mid-year doesn't get the full annual allowance on day one — they earn a proportional amount based on time remaining in the leave year.

Accrued entitlement = Annual entitlement × (Months worked ÷ 12)

Some businesses front-load the full year's entitlement in January. This is simpler to administer but creates risk: if a worker leaves in March after taking three weeks, they've taken more than they've earned. Your contract should clarify whether you can recover this.

Building your leave policy

A clear policy prevents disputes. It should cover:

Define your leave year

When does annual leave reset? January to December is most common. Some businesses use April to March (aligned with the tax year). Others tie it to each worker's start date (messier to administer, but fairer — each person's entitlement anniversary is their hiring anniversary).

Pick one and write it down. Your team should know when their entitlement resets.

How workers request leave

Specify the process. Through a task management system? Email? Verbally to their manager? And how far in advance? One week for a single day, one month for a longer block — the earlier, the easier coverage planning becomes.

Approval criteria

What determines yes or no? Common factors:

• Will the team have adequate coverage?
• Are the dates blackout periods (year-end crunch, peak season)?
• Has another team member already booked those dates?
• First come, first served (or something else)?

Be transparent. Workers who understand the decision-making process feel less like they're being arbitrarily denied. If you're refusing a request, explain why.

Carry-over

Can unused leave roll into next year? If yes, how much? A cap of five days with a "use by March 31" deadline is common. Unlimited carry-over creates a financial liability (accrued leave is owed if they leave) and operational disruption (when they finally take it).

Public holidays

Clarify: are public holidays included in the annual entitlement, or on top? In the UK, 28 days includes public holidays. In other jurisdictions, they're separate. Your policy should be explicit.

Tracking leave effectively

You have three main options, each with trade-offs.

Spreadsheets

A shared Google Sheet with workers as rows and months as columns. Works for small teams (under five people) but degrades quickly:

• No approval workflow (requests happen verbally or via email)
• No automatic calculation of remaining entitlement
• No visibility into team coverage or clashes
• Risk of conflicting edits
• Difficult to audit if there's a dispute

By the time you hit ten employees, a spreadsheet is less a system and more a record of chaos.

Shared calendars

Google Calendar or Outlook provide a visual overview: who's off when, coverage at a glance. Useful for planning but missing the machinery underneath:

• No entitlement tracking
• No approval workflow
• No balance calculations
• Tempting to double-book because there's no validation

A calendar is a window into leave, not a management system.

Dedicated leave or timesheet software

Purpose-built tools handle the complete workflow: requests, approvals, entitlement calculations, balance tracking, and reporting. Many timesheet systems include leave management as an integrated module — which makes sense. Leave and working time are two parts of the same story.

When your timesheet system tracks both, you get a unified view: days worked, days off, remaining entitlement, absence patterns. You're not stitching data from three different places.

Timesheets and leave: the connection

Annual leave and timesheets answer the same underlying question: for any period, how many days did this worker work, and how many days were they absent?

This connection matters for:

Payroll accuracy. Leave days may pay differently from working days (especially if someone has variable hours or shift premiums). Payroll needs to distinguish the two.

Working time calculations. When checking if a worker has exceeded weekly or annual hour limits, leave days must be excluded. Two weeks of leave means fewer available working days, which affects overtime and utilisation. See our guides on minimum wage compliance with time records and overtime calculations for more detail.

Absence patterns. Combine timesheet data with leave records and you see absence trends — workers with frequent short-notice requests, teams with consistently high absence, seasonal spikes (school holidays, Christmas, summer). These patterns inform staffing and scheduling decisions.

Forecasting. Historical leave data helps you predict when absences will spike and plan staffing levels accordingly.

Frequently Asked Questions

Q: Can I require workers to carry over unused leave rather than paying it out?

A: Not in the UK. UK law entitles workers to use their leave. Paying out carried-over days is fine and common, but you can't force someone to carry leave into the next year (though you can offer a carry-over cap with a deadline). Check local law in your jurisdiction — the rules vary.

Q: What if a worker leaves before using all their leave?

A: They're owed payment for accrued but unused leave. This is a liability on your accounts. Conversely, if they've taken more than they've earned (e.g., they started in November, took three weeks in December, then left), your contract should clarify whether you can deduct the excess. Accurate leave records make this straightforward.

Q: How do I handle leave for shift workers or those on non-standard schedules?

A: Pro-rata entitlement still applies. A shift worker doing 30 hours per week gets 30 ÷ 40 of the full-time entitlement. Public holidays can be trickier: if they're scheduled to work a bank holiday, they might be entitled to a substitute day off, enhanced pay, or both. Track this explicitly. Our guide on shift scheduling covers this in more detail.

Q: Can I enforce a minimum notice period for leave requests?

A: Yes. A standard notice period (one week for a single day, one month for a week or more) is reasonable and widely accepted. Make it part of your policy and enforce it consistently. Workers who need emergency leave should go through their manager, with a clear process for handling last-minute requests.

Q: What's the difference between leave tracking and timesheet software?

A: A dedicated timesheet system tracks hours worked; leave management tools track paid time off. Many platforms offer both. The distinction matters if you only need leave (just use a calendar or spreadsheet) versus if you need to see working hours alongside leave to answer questions like "did this worker exceed 48 hours per week?" Our guide to timesheet vs time tracking software explores this in more detail.

Q: How do I enforce a carry-over deadline?

A: Write it into your policy and communicate it clearly. If the deadline is March 31 for carried-over days, remind workers in January and February. Track usage and flag anyone who hasn't used their carry-over by the deadline. A reasonable business might offer a one-off extension, but enforcing the deadline consistently prevents long-term accumulation.

Q: Can I refuse leave requests during busy periods?

A: Yes, if you have a legitimate business reason (insufficient coverage, peak season, project deadline). Your approval criteria should define these blackout periods or busy seasons upfront. This is less arbitrary and easier to defend.

Common mistakes to avoid

Operating on honour. "Take leave as needed; we'll trust you've not exceeded your entitlement." This works until it doesn't. A worker who believes they have days remaining disputes your records. Without documentation, there's no resolution.

Inconsistent approval. If one worker's request is approved while another's is denied without clear reasoning, resentment follows. Apply your criteria consistently and explain refusals.

Ignoring carry-over deadlines. If your policy allows carry-over with a deadline, enforce it. Workers who pile up leave are a liability and an operational bottleneck.

Forgetting leavers. Accrued but unused leave is owed at their final pay. Track it accurately.

Making it work

Annual leave tracking is unglamorous but foundational. The investment is modest — a clear policy, a reliable tracking method, a consistent approval process — and the return is significant: fewer disputes, better coverage planning, accurate payroll, and a team that feels treated fairly.

Start with a policy. Choose a tool that fits your size and budget. Communicate the rules clearly. Track everything. The leave dispute you prevent with accurate records is one you never need to escalate.