Minimum Vacation Policies: Making People Take Time Off
A floor works where a ceiling does not. How minimum vacation policies work, what number to set, and the enforcement question that decides whether yours is real.
Most time-off policies are ceilings: here is the maximum you may take. For a growing number of companies the actual problem is the opposite — people take too little, burn out, and leave, while the policy sits there permitting time nobody uses.
A minimum vacation policy inverts the constraint. It states the least you are expected to take.
Why a floor is needed
Under a fixed allowance, the number itself is the prompt: fifteen days exist, so people work toward using fifteen days. Remove or inflate the allowance and the anchor disappears, replaced by whatever colleagues appear to take — which trends downward, because the person taking the least is the most visible signal of what is expected.
This is the well-documented failure of unlimited PTO: average time taken often goes down after adoption. A minimum is the correction.
It also helps under generous fixed allowances. A company offering 25 days where the norm is to take 12 has a benefit that costs it nothing and delivers nothing.
The person to worry about
Setting the number
| Minimum | Works for | Notes |
|---|---|---|
| 10 days | Very small teams, tight coverage | Barely above what people take anyway |
| 15 days | Most small businesses | Meaningful without straining cover |
| 20 days | Companies with unlimited PTO | The common pairing |
| 25 days | European norms, well-staffed teams | Needs real coverage planning |
Two rules:
Exclude public holidays. A "minimum 20 days" that counts ten public holidays is a minimum of ten days, and describing it otherwise is the kind of thing employees work out and resent.
Set it slightly above your current average. If people currently take 14 days, a minimum of 15 is achievable and moves the bottom of the distribution. A minimum of 25 is aspirational, unachievable without changing staffing, and will be ignored — which then teaches everyone that policy numbers are decorative.
The enforcement question
This is the whole design problem, and there are three honest answers.
Expectation only. The policy states the minimum; nobody checks. Costs nothing, changes nothing. The people who need it are exactly the people who will not act on an unenforced expectation.
Manager-accountable. The manager is responsible for their team hitting the minimum, and it is reviewed quarterly. This is the version that works. It moves the burden from the person least able to act on it to the person with the authority to arrange cover.
Individually enforced. Scheduled time off assigned to anyone below pace by a certain date. Effective and heavy-handed; appropriate in high-burnout environments, resented in most others.
Manager-accountable is the recommendation. The measurement is simple: at the end of each quarter, has each person taken roughly a quarter of the minimum? Anyone materially behind gets a conversation, not a scolding — the usual answer is that they do not believe their work can be covered, which is a real problem the manager can actually solve.
The policy language
Add to your existing PTO policy:
Minimum time off
We expect everyone to take at least [15] working days of time off each year, in addition to public holidays. This is a floor, not a target.
Managers are responsible for their team reaching it. We review progress quarterly. If you are behind, your manager will help you plan time off — including arranging cover, which is their job rather than yours.
If you are consistently unable to take time off because of workload, that is a resourcing problem we need to fix, not a personal failing.
The last sentence is the one that makes it credible. Without it, a minimum reads as another target to fail at, and the person most affected already feels they have too much to do.
Coverage is the real constraint
Nearly every failure to take time off traces back to one belief: the work will not get done, or it will be waiting for me when I return. No policy sentence fixes that. What fixes it:
Cross-training. If exactly one person can do a thing, that person cannot take a real holiday. Mapping single points of failure — see the capability table in holiday coverage scheduling — usually reveals two or three of these, and each one is a training task with a clear payoff.
Genuine handover, and no contact. A holiday interrupted by three "quick questions" is not rest, and everyone watching learns what taking time off actually means here.
Not punishing the absence with a backlog. If a week off means two weeks of catching up, the arithmetic does not favor going. Redistribute the work; do not stack it.
Getting employees to take PTO and preventing burnout on small teams go further into this.
What to measure
Only one thing really matters: days taken per person, sorted ascending.
Not the average — the average hides the problem, because one person taking 25 days masks another taking four. Look at the bottom three names every quarter. That is the entire practice.
Two supporting numbers if you want them:
- Share of the team on pace at each quarter end
- Longest single break taken, because five separate days is not the same restorative unit as one continuous week, and people who never take a full week are often the ones closest to burning out
Combining a floor with a ceiling
A minimum does not replace an allowance. The two work together:
- Fixed allowance + minimum: "You get 20 days. We expect you to take at least 15." Clear, bounded, and it addresses under-use without removing the cap.
- Unlimited + minimum: the standard pairing, and unlimited PTO without a floor is the configuration most likely to reduce time taken. The unlimited PTO policy template includes one.
Seeing the bottom of the list
The quarterly review only happens if it is easy. Reconstructing days-taken-per-person from a request log means filtering and summing by hand, which is exactly the sort of task that gets skipped in a busy quarter — and skipping it is how someone reaches December on four days.
SimplyPTO shows days taken per person alongside remaining balance, so the check is a single glance rather than an exercise. Start free for up to 10 people.
Frequently asked questions
What is a minimum vacation policy?
A policy stating the least amount of time off employees are expected to take each year, rather than the most they are allowed. It is usually paired with unlimited or generous PTO, where the problem is people taking too little rather than too much.
What is a good minimum vacation requirement?
Fifteen to twenty working days a year is the common range, excluding public holidays. Below about ten days a minimum stops being meaningful; above twenty-five it becomes hard for small teams to cover without deliberate planning.
Can you force an employee to take vacation?
Employers can generally require employees to use accrued vacation at specified times, subject to notice expectations and state rules. In practice a minimum works better as an expectation that managers are accountable for than as something enforced against individuals.
Do minimum vacation policies work?
They work when someone is accountable for the number and it is reviewed during the year. A minimum that is announced and never measured changes nothing, because the people who take too little are precisely the ones who will not act on a suggestion.
Should a minimum vacation policy apply to founders and managers?
Especially to them. The amount of time leaders visibly take sets the real norm regardless of policy, so a minimum that leadership does not observe will be understood as decorative.