A strong PTO policy is the foundation of fair, consistent time-off management. Without one, HR answers the same questions every week, managers apply different rules, and employees lose trust in their leave balances.

Creating a PTO policy does not require a legal team or a 40-page handbook. It requires clarity — on who gets PTO, how much, how it is earned, and how requests are approved.

In this guide, you will learn how to create a PTO policy step by step — from choosing a policy type to writing the rules, communicating them to staff, and configuring them in your HR system.

Not sure what PTO means in the first place? Start with our guide on what is PTO — then use the steps below to build your policy.

Why You Need a Written PTO Policy

A verbal or informal PTO approach breaks down quickly as teams grow. A written policy gives everyone the same reference point:

• HR configures the system once and enforces rules consistently
• Managers approve requests against documented standards — not personal preference
• Employees know exactly what they are entitled to and how to request time off
• Finance understands carryover, payout, and payroll implications

Without a written policy, disputes over balances, notice periods, and carryover become HR’s daily workload instead of rare exceptions.

Step 1: Choose Your PTO Policy Type

Before writing rules, decide how PTO will be structured. The four most common models are:

Your choice affects every other section of the policy — accrual rates, carryover limits, and how balances display in software. Decide this first before writing detailed rules.

Step 2: Define PTO Eligibility and Entitlements

State clearly who receives PTO and how much:

• Which employee groups are eligible (full-time, part-time, contractors excluded?)
• When PTO starts — from day one, after a probation period, or after 90 days?
• How many PTO days per year (or hours, if hourly)?
• Do entitlements increase with tenure? If yes, define the tiers
• How are part-time employees calculated — pro-rated by hours or FTE?

Example entitlement clause:
“Full-time employees receive 20 PTO days per calendar year, pro-rated for mid-year hires. After three years of continuous service, the allowance increases to 25 days.”

Step 3: Set Accrual and Grant Rules

How employees receive PTO must be explicit:

Accrued PTO

• Accrual frequency — per pay period, monthly, or per hours worked
• Accrual rate — e.g. 1.67 days per month (20 days ÷ 12)
• Maximum accrual cap — can balances exceed the annual allowance?
• Waiting period — do new hires accrue from day one or after probation?

Front-Loaded PTO

• Grant date — January 1, hire anniversary, or fiscal year start
• Pro-rating rules for mid-year hires
• Whether unused days expire at year-end or carry over

Unlimited PTO

• Minimum expected usage — encourage employees to take adequate rest
• Manager approval standards — team coverage, project deadlines
• Documentation requirements — notice period, blackout periods

For accrual formulas and worked examples, see how to calculate PTO accrual — covered later in this series.

Step 4: Write Carryover and Expiry Rules

Unused PTO is one of the most disputed topics in HR. Your policy must answer:

• Can unused PTO carry over to the next year?
• If yes, what is the maximum carryover limit?
• Do carried-over days expire after a set period?
• What happens to unused PTO when an employee leaves — paid out or forfeited?

Example carryover clause:
“Employees may carry forward up to 5 unused PTO days into the next calendar year. Carried-over days must be used by March 31 or they expire. Upon termination, unused PTO is paid out at the employee’s current daily rate.”

PTO rollover and carryover rules in detail — covered later in this series.

Step 5: Define the Request and Approval Process

Every employee should know exactly how to request PTO:

• How to submit — through HR software only (no email exceptions)
• Notice period — e.g. two weeks for planned vacation, same-day for sick leave
• Who approves — direct manager, manager plus HR, or department head
• Approval timeframe — e.g. managers respond within 48 hours
• Half-day and partial-day rules — minimum increment (0.5 day, 1 hour)
• Blackout periods — any restricted dates (if applicable)

Managers should approve with team visibility — not blind yes/no over email. A team wallchart prevents scheduling conflicts before they reach HR.

Step 6: Clarify PTO vs Sick Leave

If you use a combined PTO bank, state that sick days come from the same pool. If sick leave is separate, define:

• Sick leave allowance and accrual (if different from PTO)
• Whether medical documentation is required and after how many days
• Whether sick leave carries over or expires separately

Ambiguity here causes the most employee confusion. One sentence of clarity saves dozens of HR emails per month.

Step 7: Address Legal and Compliance Considerations

PTO laws vary by country, state, and city. While this guide is not legal advice, HR teams should verify:

• Minimum paid leave requirements in each location where employees work
• Sick leave mandates that may require separate tracking
• Payout obligations for unused PTO upon termination
• Use-it-or-lose-it rules — some jurisdictions prohibit forfeiture
• Record-keeping requirements for leave requests and approvals

Consult local employment law or legal counsel for location-specific rules before finalising your policy.

Step 8: Communicate the Policy to Employees

A policy nobody reads is a policy nobody follows. Launch communication should include:

1. Employee handbook update — full policy text in an accessible location
2. Manager briefing — how to approve, wallchart usage, common edge cases
3. Employee announcement — summary email with link to full policy and self-service portal
4. FAQ document — answers to the top 10 questions employees will ask
5. Opening balances — communicate each employee’s starting PTO balance on launch day

Re-send the policy summary annually and whenever rules change. Employees forget — reminders prevent disputes.

Step 9: Configure the Policy in Your HR System

Once the policy is written, configure it in your PTO management software — not the other way around. Software should enforce your rules automatically:

• Create leave types matching your policy (PTO, sick, unpaid, custom)
• Set accrual rates, grant dates, and carryover limits
• Configure approval chains and notice period rules
• Import employee data and verify opening balances
• Enable the team wallchart for manager visibility

Platforms like TimeOffLedger support accrued, front-loaded, unlimited, and separate-pool policies — so HR configures once and the system applies rules consistently for every employee.

PTO Policy Template Checklist

Use this checklist to confirm your policy document covers everything:

• ☐ Policy type defined (accrued, front-loaded, unlimited, or separate pools)
• ☐ Eligibility criteria stated (full-time, part-time, probation rules)
• ☐ Annual entitlement and tenure tiers documented
• ☐ Accrual or grant method explained with examples
• ☐ Carryover limit and expiry date defined
• ☐ Termination payout rules stated
• ☐ Request process and notice period documented
• ☐ Approval chain and response timeframe defined
• ☐ Half-day and partial-day rules included
• ☐ PTO vs sick leave clarified
• ☐ Blackout periods listed (if any)
• ☐ Legal compliance verified for each location

Score 10 or more: your policy is ready to publish. Below 8: fill the gaps before configuring software.

Review full leave and PTO management features to understand what your system should support before you configure policies.

Common PTO Policy Mistakes to Avoid

Mistake 1: Copying another company’s policy without adapting it
Every organisation has different entitlements, locations, and laws. Use templates as a starting point — not a final document.

Mistake 2: Unlimited PTO with no manager guidelines
Without standards, unlimited PTO leads to either abuse or employees taking less time off than they need.

Mistake 3: Silent carryover rules
Employees assume unused days roll over forever. State the limit and expiry date explicitly.

Mistake 4: Allowing email PTO requests alongside software
Mixed channels recreate spreadsheet chaos. Route every request through the system from day one.

Mistake 5: Launching software before the policy is written
Configure tools to match policy — not policy to match whatever the software defaults to.

Related Guides in This Series

This article is part of our PTO Management content series:

1. Complete Guide to PTO Management — full overview (start here)
2. What Is PTO? — definition, types, and examples
3. How to Calculate PTO Accrual — formulas and examples
4. PTO Rollover and Carryover Rules — what HR needs to know

Final Thoughts

Creating a PTO policy is one of the highest-impact tasks HR can complete. A clear, written policy eliminates daily confusion, gives managers a consistent framework, and gives employees the transparency they expect.

Start with your policy type, document every rule, communicate it clearly, and configure your software to enforce it automatically. The time invested upfront saves months of disputes later.

Start your free 30-day trial of TimeOffLedger — no credit card required — and configure your PTO policy in a live system.