Why does unlimited PTO often result in employees taking less time off, not more?

The missing anchor: nothing to use, nothing to lose

With an accrued plan, every employee has a number. It grows each pay period, it shows up on a pay stub or in a balance tool, and it eventually caps or expires. That number acts as a nudge. When someone sees 96 hours sitting there in October, they book a week in December because the alternative is losing it or hitting the cap. Unlimited PTO removes the number and, with it, the nudge. There is no balance to protect and no visible signal that says you have earned this. Related: Why does tracking employee PTO in a spreadsheet eventually break down for teams?

Without an anchor, people default to what they see around them. If the founder takes four days a year and the senior engineer takes six, that becomes the real policy, whatever the handbook says. Newer employees in particular tend to underuse because they have no reference point and would rather be safe than seen as taking advantage. The policy is technically unlimited but socially capped at whatever the most visible people take.

Keep reading: Why does tracking employee PTO in a spreadsheet eventually break down for teams?, How do PTO accruals actually work and how should a small business set them up?, How can managers approve time-off requests fairly without leaving the team short?. See how LeaveLedgr helps you employee pto and leave balance tracking.

How the accounting change shapes behavior

One reason companies adopt unlimited PTO is the balance sheet. Accrued vacation is a liability that has to be tracked and, in some states, paid out when someone leaves. An unlimited policy typically eliminates that accrual, which is a legitimate simplification for a small business. It also means there is usually nothing to pay out at separation, which is a real cost saving that employees do not always notice at hiring time. Related: How do PTO accruals actually work and how should a small business set them up?

The honest tradeoff is that the company no longer has a financial reason to encourage usage. Under an accrued plan, a large unused balance is a growing liability, so finance and managers have an incentive to push people to take their days. Under unlimited, unused time costs nothing. Nobody is watching the number because there is no number, and the people who would benefit most from a nudge are the ones least likely to ask for one.

Manager behavior matters more than the handbook

Under an accrued plan, approving time off is mostly arithmetic: does the person have the hours, and is the team covered? Under unlimited, every request becomes a judgment call about whether this amount is reasonable. Managers who have never been given a benchmark tend to become quietly conservative, and employees can feel that hesitation even when a request is approved. Over time, the effort of negotiating each request discourages people from asking. Related: How can managers approve time-off requests fairly without leaving the team short?

The fix is to give managers a concrete expectation. State a target number of days everyone is expected to take, and ask managers to check in with anyone who is well below it by midyear. Leaders should take visible vacations and say so. When a manager books two full weeks and hands off work cleanly, that does more for the policy than any paragraph in the handbook.

What to track even when the policy is unlimited

Unlimited does not mean untracked. You still need to know who is out, when, and for how long, both for coverage planning and to spot people who have not taken a real break in a year. Recording every approved absence in one place, even without a balance attached, gives you a usage report per person and per team. That report is the early warning system for burnout and for the uneven usage that unlimited policies tend to hide. Related: What are the real benefits of giving your whole team a shared leave calendar?

A few practices make unlimited work in practice: publish a suggested range rather than leaving it open, run a simple quarterly review of days taken by person, treat the first week or two of usage as a default expectation rather than a request, and keep a shared calendar so absences feel normal rather than exceptional. If you use a tool like LeaveLedgr, you can set the policy type to unlimited and still log every request, which keeps the calendar and usage history intact without inventing a fake balance.