Use-It-or-Lose-It PTO: How to Design a Policy That Holds Up

A use-it-or-lose-it clause is a policy design choice in most of the country — and a wage violation in California and Colorado the moment earned vacation disappears at year-end.

That is the line most multi-state handbooks miss. Operators copy a single PTO policy from a Texas or Florida template, apply it to remote employees in California or Colorado, and only discover the problem when someone leaves with a forfeited balance and a wage claim. The fix is not another 50-state survey. The fix is a design pattern: what you cap, what you carry, what you pay at separation, and how you write the handbook so the strictest work location does not break the whole system.

This guide is for employers building or rewriting vacation / PTO policy — not for readers who need the full state map. For the map, use vacation and PTO payout laws by state and the vacation payout calculator. For a one-minute design checklist, see how to design a PTO carryover policy. Source detail lives in the vacation payout research.

Quick reference

• No federal use-it-or-lose-it rule. The FLSA does not require vacation or regulate forfeiture. State law and your written policy control.
• Forfeiture banned for earned vacation in California and Colorado. California Labor Code §227.3 and Suastez treat vested vacation as wages that cannot be forfeited; Colorado's Wage Claim Act plus Nieto v. Clark's Market (2021) make use-it-or-lose-it unenforceable.
• Accrual caps are not the same as forfeiture. Stopping further earning past a maximum balance is generally allowed in CA and CO; wiping already-earned hours is not.
• Payout at separation is a separate design lever. Six jurisdictions require vacation payout regardless of policy (CA, CO, MA, NE, MT, ME for 11+ Maine employees). Elsewhere, clear written rules usually control.
• Combined "PTO" banks are a design risk. Discretionary-use banks can be treated as vacation for payout — including time you intended as sick leave.
• Multi-state default: either a per-state library or a California-baseline policy (no forfeiture of earned vacation, accrual cap optional, payout at final rate on separation, vacation separate from sick).

What "Use-It-or-Lose-It" Actually Is

A use-it-or-lose-it rule says: if you do not take the time by a deadline (usually year-end), the unused balance is gone.

Employers use it to:

• Limit large balances walking out the door
• Encourage people to take time off
• Keep accrual liability off the books

Those business goals are real. The legal question is whether the balance you are about to zero was already earned. In California and Colorado, earned vacation is wages. Once it vests under your accrual schedule, a year-end wipe is not a clever scheduling nudge — it is unpaid wages.

Related designs people confuse with use-it-or-lose-it:

Design	What it does	Typical legal posture
Use-it-or-lose-it / forfeiture	Deletes already-earned hours after a deadline	Illegal for vacation in CA and CO; often allowed elsewhere if clear and consistent
Accrual cap (max bank)	Stops new accrual when balance hits a ceiling	Generally allowed in CA and CO if it stops earning, not forfeits vested time
Carryover limit with cash-out	Caps hours that roll; pays cash for the excess	Often safer than pure forfeiture where payout is mandatory
Use-it-or-cash-it	Requires use or payout by a date	Aligns with mandatory-payout jurisdictions
Probation blackout	No accrual or no use in the first N days	Design carefully; "earn then forfeit" patterns re-create the same risk

The design win is to pick caps and carryover, not silent forfeiture, whenever any employee works in a ban state.

The Two Anchor Rules (California and Colorado)

You do not need a lawyer's memo to understand the operational difference.

California — vacation vests as it is earned

California Labor Code §227.3 requires vested vacation to be paid as wages at the final rate when employment ends, and it forbids policy language that forfeits vested vacation on termination. The California Supreme Court in Suastez v. Plastic Dress-Up Co. held that vacation pay vests as it is earned and may not be forfeited.

Operational translation for policy writers:

• If your policy says employees earn 1.25 days per month, those days are theirs as they accrue.
• You may stop further accrual at a reasonable cap (for example, 1.5× annual grant) so the bank does not grow forever.
• You may not say "unused days disappear every December 31" for California vacation.
• Sick leave under California's paid sick leave law is generally not paid out at separation — which is why combining vacation and sick into one discretionary bank is expensive.

Late final pay that includes an unpaid vacation balance can also trigger Labor Code §203 waiting-time penalties (daily wage continuation up to 30 days). Design payout timing into the offboarding checklist, not only the handbook.

Colorado — Nieto closed the forfeiture loophole

Colorado treats earned vacation as wages under the Wage Claim Act. In Nieto v. Clark's Market, Inc. (2021), the Colorado Supreme Court held that contractual use-it-or-lose-it and related forfeiture clauses for earned vacation are unenforceable. CDLE guidance (INFO #3E) operationalizes the holding: pay earned vacation on separation; caps on accrual remain available; use-it-or-lose-it does not.

If your corporate handbook still has pre-2021 "forfeit if you quit without notice" language, treat Colorado employees as if that clause is void for earned vacation.

Design Patterns That Survive Multi-State Reality

Pattern A — California-baseline single policy (best default for remote-heavy companies)

One handbook for everyone:

1. Vacation accrues on a written schedule.
2. Optional accrual cap stops further earning at a set balance.
3. No forfeiture of earned vacation at year-end or on separation.
4. Payout at separation at the final rate of pay.
5. Sick leave is a separate bank with its own accrual and no vacation-style payout promise.
6. Carryover is unlimited up to the cap (or a stated rollover that never zeros earned time).

Pros: One policy; satisfies CA/CO and the mandatory-payout jurisdictions; simple admin.
Cons: Higher balance liability than pure forfeiture states allow; you "over-comply" in Texas/Florida-style states.

For many SMBs, over-complying is cheaper than dual handbooks plus a wage claim.

Pattern B — Accrual cap + unlimited rollover of vested time

Employees keep what they earned; they stop earning more until they use time down.

Example: annual grant 15 days; cap 22.5 days. At the cap, the meter pauses. Nothing disappears.

This is the cleanest translation of the CA/CO line for operators who want to control liability without year-end drama.

Pattern C — Carryover limit with mandatory cash-out of the excess

"Up to 40 hours roll; anything above is paid out in the first paycheck of January."

You still need to confirm cash-out is lawful and correctly taxed in each state, but you are not forfeiting wages — you are paying them. That is the opposite of use-it-or-lose-it.

Pattern D — Per-state policy library (only if you have the ops muscle)

Maintain:

• Strict set (CA, CO, plus any location you choose to treat as strict): no forfeiture, payout on separation, separate sick.
• Policy-driven set: clear written forfeiture or carryover rules, communicated at hire, applied consistently.
• No-statute set: same as policy-driven, with even more weight on the written document.

Work location — not HQ — picks the row. Remote employees in mandatory-payout or ban-forfeiture states never inherit a Texas zero-payout default. See the multi-state section of vacation payout laws by state.

Pattern E — What not to do

• One combined "PTO" bucket for vacation + sick in CA, CO, MA, NE, MT, or ME (11+)
• HQ-state forfeiture applied to California or Colorado residents
• Silent handbooks in follows-policy states (silence often defaults to "wages owed")
• Year-end mass zeroing without checking who works where
• Paying vacation at the old accrual rate instead of the final rate in California

Separation Payout: Design It With Carryover, Not After

Carryover rules and final-pay rules fail as a pair when you design them separately.

Design choice	Separation consequence
No forfeiture + payout on separation	Balance is a known liability; offboarding is arithmetic
Forfeiture in a ban state	Wage claim + possible penalties
Forfeiture in a follows-policy state with a clear handbook	Often enforceable if consistent
Forfeiture with a silent handbook	Employee argues the default is payout — and often wins
Combined PTO bank in a mandatory-payout state	Entire discretionary bank can become wages

Wire the vacation payout calculator into offboarding for anyone with a balance over a few days. For accrual math while employed, use the PTO accrual calculator.

Multi-State Handbook Drafting Checklist

Use this when you rewrite the policy this quarter:

1. List work locations (state + remote flag) for every employee who accrues vacation/PTO.
2. Mark ban-forfeiture locations (at minimum CA and CO).
3. Mark mandatory-payout locations (CA, CO, MA, NE, MT, ME 11+).
4. Choose Pattern A or D — single strict baseline vs library.
5. Write the accrual schedule in days or hours per pay period (not vague "generous PTO").
6. Write the cap as a maximum balance, not as a year-end delete.
7. Write carryover so earned time never silently vanishes in ban states.
8. Separate sick leave types in the system and the handbook.
9. State final-pay timing (same-day / 72-hour rules where they apply — especially CA and MA).
10. Get acknowledgments at hire and when the policy changes.
11. Audit last year-end: anyone in CA/CO who lost hours? Credit them back before the next claim arrives.
12. Train managers that "use your days or lose them" is not a motivational slogan in ban states.

Scenarios Policy Designers Recognize

The Series B company with 40 remote engineers. HQ in Austin, people in Oakland and Denver. The Texas-style use-it-or-lose-it clause is the bug. Pattern A (California-baseline) is usually cheaper than litigating two states.

The 80-person manufacturer with one CA sales rep. You can run Pattern D: forfeiture allowed for plant staff where lawful; no-forfeiture + payout for the California rep. The trap is applying plant rules to the rep "for consistency."

The hospitality group that loves one PTO bank. In Nebraska, California, and other mandatory-payout jurisdictions, that simplicity can convert intended sick time into payable wages at separation. Split the banks; keep the scheduling culture.

The PE-backed rollup mid-integration. Three acquired handbooks, three year-end forfeiture dates, one shared HRIS. Freeze year-end zeroing until location mapping is done. Credit back any CA/CO forfeitures already taken.

What to Do This Week

• Export a census: employee, work state, vacation/PTO balance, sick balance (if separate).
• Search the handbook for "forfeit," "use it or lose it," "does not carry over," and "lost if not used."
• If any CA or CO employee is subject to those phrases for vacation, stop the next scheduled forfeiture and plan a credit.
• Decide Pattern A vs D in writing (even a one-page ops note).
• Split combined PTO going forward if you have people in mandatory-payout states — do not claw back existing balances.
• Put separation payout steps on the offboarding checklist with final-rate math.

When to Get Counsel

Escalate when:

• Multiple CA/CO employees already lost vested vacation under a corporate clause
• You are unwinding a combined PTO bank with multi-year balances in a payout state
• A layoff will hit employees across ban-forfeiture and mandatory-payout states in the same week
• You want a forfeiture policy in a follows-policy state and need state-specific language

This article is policy-design education, not advice on a specific wage claim.

FAQ

Bottom Line

Design PTO around vesting, not wishful year-end resets. In California and Colorado, earned vacation cannot be forfeited; accrual caps and separation payouts are the tools that still control liability. Everywhere else, clear writing beats silence. Separate sick from vacation, map work locations before you copy an HQ template, and treat carryover, caps, and final pay as one system — not three disconnected handbook paragraphs.

For state-by-state payout rules, open vacation and PTO payout laws by state. For the short checklist, read how to design a PTO carryover policy.