What a good leave policy looks like for a small team
Most leave policy guides are written for companies with HR departments, legal review, and a compliance team sitting somewhere down the hall. If you are running ops for a 15-person company, that guidance is not just unhelpful — it actively gets in the way.
A good leave policy for a small team does not need to be a 20-page document. It needs to answer the four questions your employees and managers will actually ask: how much leave do I get, how do I request it, who approves it, and what happens to unused days at the end of the year. Everything else is noise.
Accrual vs. unlimited PTO: what actually works
Unlimited PTO sounds appealing. In practice, it often backfires at small companies. Without a reference point, employees tend to take less time off — not more — because they do not know what is normal or acceptable. Managers end up making ad hoc decisions. No one tracks anything. The policy that was supposed to reduce admin creates more of it.
Accrual-based PTO is simpler to operate for most small teams. Employees know exactly what they have. Managers can see balances clearly. Approvals are grounded in real numbers. The most common setup for companies with under 50 employees is 15–20 days per year, accrued monthly, with a defined carryover cap.
Unlimited PTO can work well when your team is small, senior, and has a strong culture of actually taking time off. It requires clear norms and a manager who actively encourages leave. If you are not confident both conditions are true, start with accrual.
Approval chains: keep them short
For most small teams, a one-step approval process is the right call. The employee submits a leave request. Their direct manager approves or rejects it. Done.
The mistake small companies make is mirroring enterprise approval chains — requiring HR sign-off, finance notification, and a department head override — before they have any reason to. This adds friction, slows down approvals, and creates a process no one trusts.
What you do need to document: who approves leave when the primary approver is away. If your ops lead is on holiday, who handles the queue? Spell this out. The absence of a backup creates the kind of problem that surfaces at the worst possible time.
Carryover rules: pick one and communicate it clearly
There is no universally correct carryover policy. The three most common approaches for small teams are:
No carryover. Days expire at year-end. Simple to administer. Can create a rush of leave requests in November and December if employees feel pressure to use days before they lose them.
Capped carryover. Employees can carry a fixed number of days into the next year — often five to ten. Balances stay manageable. Employees have some flexibility. This is the most common approach for growing teams.
Full carryover. All unused days roll forward. Works in some cultures, but can lead to large accumulated balances that become a liability as the company grows.
Whatever you choose, write it down and tell people about it at the start of the year. The carryover rule that causes problems is not the one that is too generous or too strict — it is the one employees did not know existed until they tried to use their leave.
What to put in writing vs. what can stay informal
At ten employees, you can probably run a lot of this on trust and Slack. At thirty, you cannot. The inflection point arrives faster than most founders expect.
Put these in writing from the start:
- How much leave employees are entitled to, and how it accrues
- The process for submitting a leave request
- Who approves leave and who the backup approver is
- Carryover rules and the date they apply
- What happens to unused leave when someone leaves the company
You do not need a policy document for every edge case. What you need is a short, clear reference that a new employee can read in five minutes and come away knowing the basics. If it takes longer than that, it is too long.
Common mistakes small teams make
Copying an enterprise template. Most policy templates online are written for companies with 500 employees and a dedicated HR function. They include clauses, approval structures, and legal language that do not apply to a 20-person team. Strip it back to what you actually need.
Leaving balances in a spreadsheet. A shared spreadsheet works until someone makes an error, forgets to update it, or leaves the company. Balances become unreliable. Employees stop trusting the numbers. Managers start making calls without full information.
Not telling employees how to request leave. The process seems obvious until someone new joins and asks how to book a week off in July. Document the steps, even if they are simple.
Waiting too long to formalise anything. The best time to set up a clear leave policy is before you need it. Once leave disputes or confusion arrive, fixing the process under pressure is harder than getting it right upfront.
The goal is clarity, not compliance
A good leave policy for a small team does one thing well: it makes expectations clear. Employees know what they are entitled to. Managers know how to approve it. Ops knows how to track it. No one has to ask the same question twice.
If your current leave setup requires anyone to chase an answer — whether that is a balance, an approval, or a policy detail — that is the problem to solve. Not with a heavier process, but with a clearer one.
Teamper handles policy configuration, leave requests, and balance tracking for small teams who want clear employee operations without the overhead of full HR software. Start a free trial.