FTO vs PTO: Which Should Your Business Offer?

Almost every article comparing FTO vs PTO frames it as a culture question: do you trust your people, are you a modern employer, is flexibility the future. That framing is comfortable and it is mostly beside the point.

The question is a financial and legal one. Traditional PTO accrues, which means in a large number of states it becomes a debt you owe your employees, payable in cash when they leave. FTO does not accrue, which means that debt does not exist. That single difference is worth more to a small business than every argument about trust and culture combined, and it is also the thing that will bite you hardest if you implement it carelessly, because a flexible policy that is not genuinely flexible gets treated as an accrual policy anyway, and you end up owing the payout without ever having had the benefit.

This guide covers what FTO actually is, how it differs from unlimited PTO (the terms are not synonyms and the sloppiness is expensive), the liability argument that nobody makes properly, the specific way a flexible policy gets reclassified in court, why employees frequently take less time off under FTO, why it does not work for hourly staff, and which model a business with five to fifty people should actually choose. I build the leave tracking and policy management that either model needs into FirstHR. This is general information rather than legal advice, and the payout rules vary sharply by state.

The Short Answer

FTO stands for flexible time off. It is paid time off with no accrual: employees do not earn or bank days, and there is no balance to track. Traditional PTO is accrual-based: employees earn time at a defined rate, the balance is tracked and carried over, and in many states that balance is legally earned wages.

Both are paid. The flexible in flexible time off refers to how the time is allocated, not to whether the employee gets paid, and that is worth saying plainly because the terminology invites the wrong conclusion. An employee on FTO taking a week off receives a normal week's pay.

The consequence of the accrual difference is the whole story. No accrual means no balance, which means generally no payout when someone leaves, which means a liability that simply does not exist on your books. Everything else about this comparison is downstream of that.

What Is FTO?

Flexible time off is a paid leave model in which employees take time off as they need it, subject to manager approval and business needs, rather than drawing down an accrued balance. There is no accrual rate, no bank of days, and no carryover, because there is nothing to carry.

Crucially, FTO is not the same as an absence of structure. Most functional FTO policies retain a great deal of it: an expectation about the typical range of time people take, a stated minimum, a requirement for notice, an approval process, and a manager's ability to say not this week. What FTO removes is the accounting mechanism, not the management of it.

That distinction matters because it is where the terminology gets tangled, and the tangle is not academic.

FTO vs Unlimited PTO vs Traditional Accrual

Three terms, used interchangeably by people who should know better, and the confusion causes real harm. Separating them properly is the single most useful thing this article can do.

Sources genuinely contradict each other on these definitions. Some treat FTO and unlimited PTO as synonyms; others insist FTO usually has soft limits while unlimited does not. Both positions have support, which tells you the market has not settled the language, and it is not going to.

Here is the useful way through. Stop trying to work out whether your policy is FTO or unlimited, because that distinction has no legal weight. Ask instead the question that does: does time accrue, or does it not? That is the line that determines whether you owe a payout, whether you carry a liability, and whether a court will treat your policy as what you say it is. Everything else is branding.

FTO vs PTO, Side by Side

Laid against each other on the dimensions that actually affect an employer, the tradeoff becomes clear quickly.

Read down that table and the pattern is unmistakable. FTO wins decisively on cost and administration, which are exactly the things a business without an HR department cares about most. Traditional PTO wins on clarity and safety, which are the things that matter when something goes wrong.

The two rows worth staring at are payout and under-use, because they point in opposite directions. FTO removes the payout and creates the under-use problem. An employer who adopts FTO for the financial benefit and does nothing about the under-use has traded a liability for a quieter, slower harm: a team that is more tired than it should be, holding a benefit it does not feel able to use.

The Liability Argument for FTO

This is the strongest case for FTO and almost nobody makes it properly, because it requires arithmetic rather than adjectives. Accrued PTO is not a perk sitting in a spreadsheet. In many states it is a debt, payable in cash, at short notice, whenever an employee leaves.

Twenty-four thousand dollars sitting on the books of a twelve-person business is not a rounding error. It is a real obligation that grows as people accumulate balances, that you may have to settle without warning, and that you probably have not budgeted for. FTO makes it disappear entirely, because there is no balance to owe.

The second, quieter benefit is administrative. Accrual policies require you to compute accrual rates, enforce caps, handle carryover under whatever your state permits, and calculate the payout correctly at separation, and getting any of it wrong in a payout state is a wage claim. FTO reduces all of that to a single question: do I approve this request. For a founder doing HR on top of their actual job, that is not a small saving.

But the liability only disappears if the policy is real, and that is where employers get badly caught.

The Payout Trap

In a significant number of states, accrued vacation is treated as earned wages: it vests as the employee works, it cannot be forfeited, and it must be paid out in cash when they leave. There is no federal requirement to pay out unused time off, since the Fair Labor Standards Act does not require payment for time not worked, but a state can and many do.

California is the clearest and strictest example. Per the California Department of Industrial Relations, there is no requirement to provide vacation at all, but once an employer establishes a policy, accrued vacation is a form of wages that vests as it is earned and must be paid at the final rate of pay on separation. Use-it-or-lose-it policies are therefore prohibited there. That is the rule FTO is designed to sidestep, and the logic is sound: if nothing accrues, nothing vests, and there is nothing to pay.

The relevant law is unusually specific about this. California's Labor Code section 227.3 requires that vested vacation be paid as wages at the final rate on termination, and provides that an employment contract or policy cannot provide for forfeiture of vested vacation. The question, for an FTO policy, is simply whether anything vested. And that question has been litigated.

How an FTO Policy Gets Reclassified

In 2020, a California Court of Appeal issued the state's first published opinion on the legality of unlimited paid time off policies, in McPherson v. EF Intercultural Foundation. It is the single most instructive thing an employer considering FTO can read about, and I have not seen a competitor guide on this topic explain it properly.

The facts are the lesson. Three salaried employees were subject to what the employer described as an unlimited vacation policy. They sued for unpaid vacation wages at separation, arguing that the policy was not unlimited in practice. The employer's defense was the obvious one: nothing accrued, so nothing vested, so nothing was owed.

The court disagreed, on the specific facts. The policy had never been put in writing. It had been communicated informally, in side conversations with supervisors. The employees were never actually told they had unlimited vacation. And in practice, the employer expected people to take somewhere in the range of two to six weeks, which is an implied cap. The court found that the policy was not unlimited, it was undefined, and that section 227.3 applied to it anyway. The plaintiffs were awarded payout for twenty days of vacation per year, which was, tellingly, more than they had actually been taking.

The court was careful to say it was not holding that all unlimited policies trigger a payout obligation, and it explicitly declined to decide whether a genuinely unlimited policy creates vested vacation. It is a fact-specific decision, not a ban. But it hands employers a usable checklist, and ignoring it is unwise.

The through-line is that a real FTO policy is a more deliberate document than an accrual policy, not a less deliberate one. Employers adopt FTO thinking it is the simple option, write nothing down because there is nothing to track, and thereby create precisely the informality that gets the policy recharacterized. The paperwork you saved on accrual you must spend on definition. The state-by-state variation in these rules is covered in the PTO laws by state guide.

The Honest Pros and Cons

Stated plainly, with the tradeoffs on the table.

The first item in the cons list is the one that gets waved away and it should not be. It is not a minor drawback. It is a structural feature of the model, and if you adopt FTO without addressing it you will have paid for a benefit that makes your team more tired rather than less.

The Problem Nobody Warns You About

Here is the counterintuitive finding that makes FTO fail: employees frequently take less time off under a flexible policy than under an accrual policy. Not more. Less.

The mechanism is straightforward once you see it. With an accrual balance, an employee has a number. They can see fifteen days sitting there, they know it is theirs, they know it was earned, and taking it feels like using something they own. Under FTO there is no number. There is only a social question: how much is too much? And in the absence of an answer, most people guess conservatively, because nobody wants to be the person who took five weeks when their colleagues took two.

The people most affected are precisely the ones you least want to burn out: the conscientious, the newer, the more junior, and anyone unsure of their standing. The confident senior person takes their time. The anxious high performer takes less than they used to and does not tell you.

The minimum also helps with the legal question, which is a happy coincidence rather than a design accident. A policy that actively pushes people to take substantial time is a policy that is visibly not operating as a de facto use-it-or-lose-it scheme, which is exactly the characterization you are trying to avoid.

FTO Does Not Work for Hourly Staff

This rules FTO out at a large share of small businesses and it deserves to be stated bluntly rather than buried. FTO assumes an employee whose work is measured by output rather than hours, and who is paid a fixed salary regardless of exactly how many hours they put in. That describes salaried exempt staff. It does not describe an hourly employee.

For an hourly worker, pay is a direct function of hours worked. Time off is not a matter of whether the work gets done; it is a matter of whether they are paid. A flexible policy that says take time as you need it, without a defined paid allowance, is either meaningless or a pay cut, and the employee will read it correctly as one of the two.

Coverage compounds it. Shift-based work depends on someone being physically present at a specific time, and an undefined absence policy does not survive contact with a rota. Hourly and shift teams need a defined allowance, planned in advance, precisely so that coverage can be planned around it.

The hybrid is worth taking seriously and is frequently the correct design. It is not a compromise or an admission of failure; it is matching the policy to the nature of the work. Just be careful to write both policies properly and to be able to explain, without embarrassment, why the two groups are treated differently, because your hourly staff will notice and they will ask.

Which Model Fits a Small Business

Here is the section for the business with five to fifty people and nobody doing HR full time, and my answer may not be the one the rest of the internet gives.

My honest view, and it is a minority one among HR blogs: for most small businesses, a well-run accrual policy is the safer answer. FTO is not simpler, despite appearances. It is a policy that trades administrative work for cultural work and legal precision, and cultural work is the thing a stretched founder has least of. The liability saving is real and it is not free.

FTO is the right call when three conditions all hold: your team is predominantly salaried, your culture demonstrably supports people taking real time off, and you are willing to write the policy carefully and enforce a minimum. If any one of those is missing, accrual is better. The broader mechanics of accrual policies, carryover, and payout are covered in the PTO vs vacation guide.

How to Transition From PTO to FTO

If you already run an accrual policy and want to move to FTO, there is one thing you must handle before anything else, and getting it wrong is a wage claim.

Your employees have accrued balances. In a state that treats accrued vacation as earned wages, you cannot simply zero them out. That time is already earned and it belongs to them; switching your policy does not retroactively unearn it. You have two legitimate options: pay the accrued balances out at the point of transition, or preserve them as a frozen legacy balance that employees can draw down or be paid on separation, while no further time accrues under the new policy.

The fourth step matters more than it looks. An employee on accrual who leaves gets a check. The same employee on FTO gets nothing, and they will work that out. An employer who presents FTO as costless generosity, when it visibly removes something the employee had, spends credibility that would have been better kept.

Writing an FTO Policy That Holds Up

Because FTO removes the accounting mechanism, the written policy is doing all of the work. Here is what it has to contain.

The seventh step catches people. Adopting FTO does not exempt you from a statutory paid sick leave requirement, and an FTO policy that swallows sick leave without independently satisfying the mandate is a compliance problem regardless of how generous the policy feels. Check your state and your city.

The eighth is the whole lesson of the case law in one line. The employer who lost did so substantially because their policy was informal and unwritten. Writing it down is the cheapest legal protection available to you, and there is no excuse for skipping it. If you want the deeper treatment of the fully uncapped version of this model, the unlimited PTO guide covers it.

Frequently Asked Questions