Unlimited PTO

Managing time off by the day creates an odd piece of arithmetic inside a company. The remaining balance starts to feel like personal property, and not spending it starts to feel like a loss. Resting when rest is needed and burning down a number get tangled together.

Every December the same notice goes around: use your remaining days before the year closes. People scramble to book dates. The work does not shrink to match, so they check messages during the break and clear two days' worth of backlog on return. The calendar records vacation. Nobody rested.

The opposite problem sat right next to it. A cap makes the number underneath it look like a guaranteed right, and nobody can explain why the number is fifteen rather than twelve or twenty. Somebody who is ill and wants two more days checks the balance and decides from there. How much rest a person needs and how much they are allotted were never the same quantity, and the number was papering over the difference.

Unlimited PTO deletes the number. In place of a ceiling it offers a standard — take what your team can absorb — and hands the judgment over. It also removes the company's obligation to pay out unused days, which is a real accounting effect. When that is the actual motive for adopting it, people generally work it out, and from there the policy earns cynicism instead of trust.

Within the same time-off family, a sabbatical hands long-tenured employees a defined stretch of leave; this policy defines no length and transfers the decision instead.

Remove the cap and write everything else down more clearly. Statutory leave stays exactly where it was, with no ceiling above it, alongside rules for notice, records, a minimum, and handover.

1. It sits on top of statutory leave. A company cannot delete the legal minimum, so unlimited does not mean the statutory entitlement disappears — it means no ceiling above it. Whatever labor law requires in days granted and unused-day payouts still applies.
2. Set the notice rules. How far ahead a request goes in, at what length a manager's agreement becomes necessary, and how many people from one team may be away at once. With the cap gone, these rules are what actually help somebody decide. Two people from a four-person team away in the same week is the case worth writing down, because it is the one that turns a policy into resentment.
3. Keep records anyway. It is tempting to think there is nothing to count once the limit is gone, but without usage data there is no way to find the people taking too little. The thing worth monitoring here is under-use, not over-use. A quarterly list of days taken per person, read by one manager, is enough instrumentation.
4. Set a floor. More companies now write something like fifteen days minimum. Removing the ceiling without adding a floor removes the reference point entirely, and average usage tends to fall as a result.
5. Attach a handover condition. Anything over two weeks needs a named backup, for instance. Where one person is the only one who knows an area, that person cannot use the policy no matter what it says.
6. Managers go first. How many days team leads actually take in the first quarter after launch decides whether this works. People read that number, not the announcement.

Four places where the policy surfaces in practice.

1. Job postings — one of the standard lines in a benefits list. Candidates who have seen it before ask not about the policy but about last year's average usage, and a company that cannot answer makes the line work against it.
2. Onboarding documents — the first thing new hires are unsure about. Without a written answer on when a first vacation may be taken and how probation affects it, nobody goes first, and a new hire's first three months set the pattern for the rest of their time there.
3. Departure settlements — the payout for unused statutory leave still exists. Telling a leaver there is nothing to settle because the policy is unlimited is how this turns into a dispute.
4. Separation from reviews — a written principle that days taken do not feed into performance evaluation. Without that sentence, people factor in the possibility that a long break looks bad later.

Companies running this alongside remote work end up writing one more rule. When the boundary of the working day is already soft, removing the cap on time off makes answering messages on a day off the default.

"We say unlimited, and last year's average was nine days. That's a culture problem, not a policy problem."

Deleting the number did not finish the job.

"Over two weeks, just name a backup. We're not counting days."

The cap has been replaced by a handover condition.

"Statutory leave doesn't go away. There's just no ceiling above it."

Correcting the scope of the policy.

Pagedeck adopted this right after its Series A. Grace posted the announcement, and the first quarter's average came to seven days — two fewer than the same period the previous year under a conventional allowance. People had lost the reference point and were watching each other.

Mia went looking for the cause and found the four team leads had taken two, three, zero and four days respectively in that quarter. Grace changed two things: fifteen days went in as a floor, and the leads were asked to each take a full consecutive week. Theo took two weeks and ran the backup-naming procedure for the first time, and that record became the example everyone else worked from.

The most common reading is that unlimited means people can take as much as they like, which is what the name says. In practice, removing the ceiling removes the reference point too, and people substitute their colleagues' usage for a remaining balance. Nobody wants to be the first to take a lot, the average drifts down, and the company ends up resting less than it did before — while believing it offers one of the more generous policies in the market. Which is why companies that run this well write a floor instead of a ceiling and review usage every quarter.

The other misreading is that the policy abolishes statutory leave, since "no limit" sounds like the concept of counted days has gone. A company cannot remove the legal minimum by policy, and the obligation to pay out unused statutory days survives too. Unlimited PTO is a layer on top of that, and a company that never writes the relationship down ends up at a final settlement with two parties holding two different calculations.