How to Track Unlimited PTO

Unlimited paid time off removes the allowance. It does not remove approval, coverage, notice, or the company's interest in whether people are resting. What disappears is a number, not a process.

That is worth stating plainly, because the commonest failure of an unlimited policy is treating the absence of a balance as the absence of a system. Requests still have to be agreed. Somebody still needs to know that half the support team is away next Thursday. And somebody still has to notice when a person has taken four days in eleven months.

Coverage

The question a manager asks is never how many days somebody has left. It is who is here next week. That question is identical under an unlimited policy and it gets harder rather than easier, because the informal signal of a shrinking balance is gone. A shared view of who is off, with a threshold that flags the days when too many people are away at once, is the entire operational requirement.

Fairness

Without a stated allowance, the amount of leave people take is set by confidence, by team culture and by what they see their manager do. That is how unlimited policies produce wide, quiet gaps between people doing the same job. You cannot see that gap without counting days taken.

The record

Absence still needs a record, for sickness, for pay questions, and for anything that later becomes a dispute. Unlimited removes the balance, not the need to know when somebody was not at work.

• Days taken per person, per year. The single most useful number, and the only one that exposes the fairness problem.
• The spread across the team. One person on 30 days and another on 6 is a conversation about workload, not about entitlement.
• Clustering. Whether time off lands where the company can absorb it, and which weeks nobody could cover.
• Time since the last real break. Somebody who has not taken five consecutive days in a year is worth checking on, whatever their total says.

None of those are performance metrics and none belong in a review. They are inputs to a manager's judgement, and the moment they become a score people will manage the score instead of taking the rest.

The predicted failure of unlimited policies is people taking too much time. The failure companies actually report is the opposite. Without a stated number, people often take less, because nothing tells them what normal looks like and nobody wants to be the person who took the most.

The mechanism is simple. An allowance is permission. Twenty days in a policy document says the company expects you to take twenty days. Unlimited says nothing at all, so people substitute the most cautious signal available, which is usually whatever their manager does.

The fix most companies land on is a minimum. Write down the number of days everybody is expected to take, make it real by asking managers to check at the halfway point of the year, and leave the ceiling open. A minimum restores the permission the allowance used to carry, and it costs the company nothing it was not already offering.

Managers taking visible leave is the other half of it. A policy that says take what you need, run by a manager who took four days last year, means take four days.

Two more lines belong beside the minimum: how much notice a request needs, and who agrees it. Unlimited removes the allowance, and if it also removes the process then nobody knows whether a week in June has been agreed or merely announced. That ambiguity is what makes people stop asking.

The mechanics are the same as any other leave tracking, minus the arithmetic. Record every absence with a person, a range and a type. Count working days rather than calendar days, so a week off is five and public holidays inside a range cost nothing. Keep sickness as its own type, which matters more under an unlimited policy rather than less, because otherwise sickness and holiday are indistinguishable in the record. The distinction is covered in the PTO, vacation and sick leave guide.

This site's tracker supports an unlimited policy directly. Set the method to unlimited and the balance stops claiming a number it cannot know, while days taken, the year view and the clash warnings all keep working. Open the tracker and set the method once.

If part of your team is on unlimited and part is not, that is normal, and it is a per person setting rather than a company wide one. The other methods are compared in the accrual methods guide.

• Do not rank people by days taken, or publish a leaderboard in either direction.
• Do not put days taken into a performance review. It converts rest into a metric, and the metric wins.
• Do not switch to unlimited purely to clear accrued balances. Where accrued time has to be paid out on termination, converting a balance away has legal consequences that vary by jurisdiction, so take advice first.
• Do not leave approval undefined. Take what you need, with nobody to ask, means the cautious take nothing.