PTO Policy Template Example for Growing Teams

A PTO policy fails long before someone disputes a vacation balance. It fails when the rules live in a founder's head, a spreadsheet only one person understands, and a Slack thread that says, "I think we allow that." A clear PTO policy template example gives growing teams one source of truth before leave requests become payroll corrections, coverage gaps, or awkward exceptions.

The goal is not to write a 12-page handbook nobody reads. It is to define what employees earn, when they can use it, what happens at year-end, and who approves time away. Put those rules in writing, configure them in your leave system, and stop handling every request as a special case.

What a PTO policy needs to settle

Paid time off sounds simple until the details arrive. Does PTO accrue each pay period or appear as a full annual balance on January 1? Can unused hours roll over? What happens when a new hire leaves after taking more time than they earned? Are sick days included in the PTO bank, or tracked separately because a state or local law requires it?

Your answer depends on where your team works, how predictable staffing needs are, and the level of flexibility you want to offer. A five-person agency with fixed client deadlines may need clearer advance-notice rules than a distributed software team. A company with employees across multiple states may need separate sick leave rules even if its main PTO policy is company-wide.

The non-negotiable part is clarity. Employees should be able to see their balance, request leave, and understand the outcome without asking HR to interpret a spreadsheet.

PTO policy template example

Use the following as a starting point, not a legal document to copy without review. Confirm state and local requirements, particularly rules on paid sick leave, payout of accrued vacation at separation, carryover, and front-loading leave.

Purpose and eligibility

> Purpose: [Company Name] provides paid time off so employees can rest, manage personal needs, and take planned time away from work. > > Eligibility: Regular full-time employees are eligible for PTO beginning on their first day of employment. Part-time, temporary, and contract workers are eligible only where required by applicable law or stated in their agreement.

This language makes eligibility direct. If you use different rules for part-time employees, state the threshold clearly, such as employees scheduled to work 20 or more hours per week. Do not leave managers to decide case by case.

Accrual and availability

> Accrual: Eligible employees accrue [80] hours of PTO per calendar year, earned at a rate of [3.08] hours per biweekly pay period. PTO accrual begins on the employee's start date. > > Use of PTO: Employees may use accrued PTO after [30] days of employment. PTO may be used in increments of [one hour/four hours/one full day]. > > Accrual cap: Employees may accrue up to [120] hours. Once an employee reaches this cap, further accrual pauses until their balance falls below the cap.

Accrual is easier to administer than granting a full annual bank upfront, especially for new teams with turnover or uneven start dates. It also prevents an employee from taking a year's worth of time in January and leaving in February. That said, front-loading an annual balance can be more generous and easier for employees to understand. If you choose it, define whether unearned PTO can be recovered from final pay, where legal.

Request and approval process

> Planned leave: Employees should submit PTO requests at least [two weeks] before planned absences of [three or more consecutive workdays]. Requests for shorter absences should be submitted as soon as practical. > > Unplanned leave: Employees must notify their manager as soon as possible on the first day of an unplanned absence, following the team's call-out procedure. > > Approval: Managers approve requests based on business coverage, project deadlines, and fairness across the team. Approval is not automatic until recorded in the company's leave management system.

Avoid rules that imply a manager can deny leave indefinitely. Coverage matters, but so does consistency. If two people request the same high-demand period, state how you decide: first approved request, rotation, or manager review based on business need. A visible request history is far more defensible than informal chat approvals.

Carryover, payout, and separation

> Carryover: Employees may carry over up to [40] unused PTO hours into the next calendar year. Any balance above this limit expires on [date], except where prohibited by law. > > Payout at separation: Unused accrued PTO will be paid out upon separation only where required by applicable law or by a written employment agreement. > > Negative balances: Employees may not use more PTO than they have accrued unless written approval is provided by [HR/Operations]. Any approved negative balance will be handled in accordance with applicable law at separation.

This is the section that creates the most legal risk. Some jurisdictions treat earned vacation as wages and restrict use-it-or-lose-it policies or require payout at termination. Sick leave can follow a different set of rules. Do not use one broad sentence to cover every type of leave if your workforce spans multiple states.

Holidays, sick leave, and protected leave

> Company holidays do not reduce an employee's PTO balance. Statutory sick leave, family and medical leave, jury duty, military leave, and other protected absences are administered according to applicable law and may be tracked separately from PTO.

This keeps your general PTO policy from accidentally overriding rights that cannot be waived. It also prevents a common reporting problem: calling all absences "PTO" when payroll, compliance records, and leave balances need different categories.

Turn the policy into an operating rule

A written policy is only useful if it matches how work actually happens. Start with the few settings that control most disputes: leave types, annual allowance or accrual rate, carryover cap, approval path, minimum request increment, and visibility of balances.

For a small team, one approval step is usually enough. The employee submits the request, the manager checks coverage, and the approved absence appears on the shared calendar. Add a second approver only when there is a real need, such as a finance review for long absences or an owner approving a department lead's leave. Extra approval layers do not create control. They create delays and side-channel requests.

Keep employee records, leave balances, and approvals in the same system where possible. HourSquare, for example, lets teams configure leave policies and manage requests without rebuilding the process across spreadsheets, email, and chat. The operational win is simple: the balance shown to the employee should be the same balance your payroll and operations team rely on.

Decide the trade-offs before publishing

There is no single best PTO design. More carryover gives employees flexibility, but it can create a large outstanding liability and encourage people to postpone rest. A lower cap limits that liability, but may feel punitive if employees cannot realistically take time away during busy periods.

Likewise, unlimited PTO can work in high-trust environments with strong manager habits. It can also produce less time off when employees are unsure what is acceptable. If you use unlimited PTO, define a minimum encouraged amount, a request process, and coverage expectations. "Take what you need" is not a policy by itself.

Be especially careful with a combined PTO bank. Combining vacation and sick time reduces administration, but may conflict with local paid sick leave requirements. Separate categories can add configuration work, yet they make compliance reporting and employee protections easier to manage.

Publish it without creating confusion

Before launch, test the policy against three realistic scenarios: a new hire requesting time before fully accruing it, an employee reaching the carryover cap, and a manager needing to handle an unexpected absence. If the answer requires someone to improvise, the rule is incomplete.

Then share the policy in the employee handbook and the leave system, explain what changes for current balances, and give managers a short briefing on consistent approvals. Do not bury the policy in a document folder and assume the process is done. Employees need to know where to request time, where to view balances, and who can answer an exception question.

A good PTO policy should feel almost invisible. People request time, managers plan coverage, balances stay accurate, and payroll is not chasing corrections. That is the standard: fewer interpretations, fewer spreadsheets, and more confidence that time away is handled fairly.