Paid Time Off (PTO) Policy Template | Vacation & Sick Leave Rules

A paid time off policy is an employer-adopted set of rules governing compensated leave: how much an employee gets, how it accrues, how it is requested and approved, and how any remaining balance is handled at termination. Most modern policies consolidate what used to be separate vacation and sick-day programs into one PTO bank, giving employees flexibility over why they take a day off while giving the employer a single, simpler number to track. Some companies keep sick leave separate, usually because a state or city paid-sick-leave statute forces them to track sick hours under specific rules that a blended bank cannot satisfy.

People often confuse a PTO policy with a leave law, and the distinction matters. A leave law, such as the Family and Medical Leave Act, is a statutory entitlement you cannot waive or shrink. A PTO policy is a benefit you design, and outside the handful of states with mandatory sick leave, you choose almost every term. The catch is that once you put a number in writing and an employee earns those hours, most states treat the accrued balance as a form of earned wages. You cannot quietly delete time an employee has already banked. That single principle drives nearly every drafting decision in this document, from accrual caps to the carryover rules covered in our employee handbook and HR policy templates.

PTO sits in an unusual legal space: it is one of the few employment benefits Washington leaves almost entirely to employers and states. The Fair Labor Standards Act (FLSA) governs minimum wage, overtime, and recordkeeping, but it contains no requirement to provide paid vacation, paid holidays, or paid sick days. The federal Family and Medical Leave Act (FMLA) guarantees up to twelve weeks of leave for qualifying medical and family reasons, yet that leave is unpaid and job-protected only, not a PTO entitlement. The U.S. Department of Labor states the position plainly in its official guidance on sick leave and FLSA-covered time off, confirming there is no federal mandate for paid leave of any kind.

Because the federal floor is so low, the real rules come from the states, and they diverge sharply. A growing list of states and cities now mandate paid sick leave with their own accrual formulas, usage triggers, and carryover minimums, while no state mandates paid vacation at all. The decisive issue for most employers is PTO payout at separation. Several states, including California, treat accrued vacation as earned wages that must be paid in the final check, and they prohibit any policy that forces employees to forfeit banked time. California Labor Code §227.3 is the textbook authority: use-it-or-lose-it vacation policies are unenforceable there, though a reasonable accrual cap is allowed. Other states honor a clearly written forfeiture clause, which means the same handbook language can be perfectly legal in one state and an automatic penalty in another.

Two formal requirements run through almost every jurisdiction. First, the policy should be written, dated, and acknowledged by the employee, because an unwritten promise is the hardest thing to defend in a wage dispute. Second, the policy must match what you actually do; a written rule you ignore is often read against you. Final-paycheck deadlines are the most penalized mistake, since many states impose daily wage penalties for late payment of owed PTO even when the termination itself was lawful. These compliance pressure points are the same ones we flag in our US employee termination letter template.

The most common trigger is your first handful of employees, the moment informal "take a day when you need it" arrangements stop scaling. Once two managers interpret the same unwritten rule differently, you have inconsistency that looks like favoritism, and favoritism is how discrimination claims begin. A written policy turns a judgment call into a documented standard. The second trigger is multi-state hiring. The day you employ someone in California, New York, or any city with a sick-leave ordinance, a generic national policy that ignores payout and accrual rules quietly puts you out of compliance, and the penalties accrue per employee.

You also need this document when you are building or revising an employee handbook, because the PTO section is one of the few that carries direct financial liability if drafted loosely. Companies issuing formal offer letters lean on it too, since a candidate who is promised "three weeks of vacation" needs the mechanics spelled out somewhere, and the offer should point to the policy rather than create a separate, conflicting promise. Our offer letter template for US employers is built to reference a PTO policy cleanly instead of inventing terms.

One edge case is worth flagging. If you are moving from a traditional accrual model to an unlimited or "flexible" PTO structure, the transition itself can create liability: in payout states, employees may be entitled to cash out the vacation they accrued under the old plan before the new one takes effect. Another quiet trap is the exempt employee under the FLSA. Docking a salaried exempt worker's pay for a partial-day absence can destroy the exemption, so your PTO policy has to coordinate carefully with how partial days are charged against the bank.

• The accrual and grant method sets how employees earn time, whether by hours worked, by pay period, or as a lump-sum annual grant. The clause states the rate precisely (for example, accrual per forty hours worked) and ties it to length of service tiers, so a five-year employee and a new hire have unambiguous balances rather than a number nobody can reconstruct.
• The carryover and cap provision controls how much unused time rolls into the next year. It is drafted with a state toggle in mind: a forfeiture or use-it-or-lose-it rule where the state permits one, and a reasonable accrual cap where forfeiture is banned, so the same template stays lawful whether the employee sits in Texas or California.
• The request and approval procedure spells out notice periods, blackout dates, and how competing requests are resolved. This is the clause that protects you from the "I assumed it was approved" dispute, because it puts the approval mechanics in writing and requires manager sign-off in a documented form.
• The separation payout clause is the highest-stakes provision. It states whether accrued, unused PTO is paid on termination and aligns that answer with the governing state, because the wrong default here is the fastest route to statutory wage penalties.
• The sick-leave coordination clause addresses how the policy interacts with any mandatory state or local paid-sick-leave law, either by carving sick hours out of the general bank or by confirming the blended bank meets the statutory minimum. The non-compete and non-solicitation agreement in our employment library uses the same state-toggle architecture for jurisdictions that treat a clause differently.

California is the most demanding jurisdiction. Accrued vacation is earned wages under Labor Code §227.3, so use-it-or-lose-it forfeiture is void, unused PTO must be paid in the final check, and that final check is due immediately on involuntary termination. A reasonable accrual cap is permitted, but the policy must stop short of confiscating time already banked. California also layers a statewide paid-sick-leave mandate on top, so a blended bank has to satisfy the sick-leave accrual and usage floor independently.

New York does not require paid vacation, but it enforces written PTO policies strictly and its statewide Paid Sick Leave law sets accrual at one hour per thirty hours worked, with the annual amount scaled to employer size. If your policy promises a vacation payout on separation, the New York Department of Labor will hold you to that written language, which is why ambiguous drafting is more dangerous here than silence.

Texas sits at the opposite end. There is no state requirement to provide or pay out PTO, and a clearly written forfeiture clause is generally enforceable. That freedom is a trap for the unwary: because Texas relies entirely on the written policy, a sloppy or contradictory document is the only thing a court has to read, and it will read it against the drafter. Precision, not generosity, is what protects a Texas employer.

Florida mirrors Texas in having no state PTO mandate and no payout requirement, leaving everything to the policy and the employment contract. The absence of a statute does not reduce your exposure; it concentrates all of it in your handbook language. Across all four states, the lesson is identical: the policy is only as strong as its weakest, vaguest sentence, a point we develop in our at-will employment contract for US employers.

You start by selecting the state where your employees primarily work, because that single choice drives the payout and forfeiture logic for the rest of the document. From there the template asks whether you want a blended PTO bank or separate vacation and sick leave, and it adjusts the sick-leave language to match any mandatory state or local minimum. You then set your accrual model, choosing between an hourly accrual rate, a per-pay-period amount, or an annual lump-sum grant, and you enter the service tiers if you reward longevity with more time.

Next you define the carryover rules, where the form steers you toward a lawful default for your chosen state: a forfeiture clause where it is allowed, a reasonable cap where forfeiture is not. You specify the request and approval procedure, including notice periods and any blackout dates, then confirm how accrued time is treated at separation. The final step is the acknowledgment block, where the employee signs and dates receipt of the policy, which is the piece most homemade policies forget and the piece that matters most in a dispute. The completed policy exports in Word and PDF so you can paste it into a handbook or store the signed copy, and it pairs naturally with the documents in our US employment forms and contracts library.

The most expensive error is copying a national or out-of-state policy without checking the payout rule. A use-it-or-lose-it clause that works in Texas is automatically void in California, and the employer who forfeits banked vacation there walks straight into wage penalties. Close behind is the vague accrual rate: a policy that says "employees earn vacation over time" gives payroll nothing to calculate and gives a departing employee room to argue for the higher number. Employers also routinely forget the acknowledgment signature, then discover during a dispute that they cannot prove the worker ever saw the rules. A policy nobody signed is the easiest one to attack.

Two operational mistakes recur in practice. The first is inconsistent enforcement, where managers grant time to favored employees and deny it to others under the same written rule, which converts a neutral policy into evidence of discrimination. The second is the exempt-employee docking trap: charging a salaried exempt worker's pay, rather than their PTO bank, for a partial-day absence can void the FLSA exemption and trigger overtime liability for the whole class. Finally, many employers let the written policy and actual practice drift apart, approving leave the policy forbids or ignoring caps the policy sets. A policy you do not follow is worse than no policy, because it documents that you knew the rule and broke it.