PTO Policy Template and Planning Checklist

A clear paid-time-off policy tells employees what time is available, how to request it, who approves it, and how balances are handled. The policy must also be practical for HR and managers to administer consistently.

This template is an operating outline, not legal advice. Requirements differ by jurisdiction and leave type. The US Department of Labor explains that federal law does not require vacation pay, while agreements and state rules may apply; review its vacation leave overview and obtain qualified advice before adopting a policy.

1. Purpose and scope

State why the policy exists and who it covers.

Template:

This policy explains how eligible employees request, receive approval for, and track paid time off. It applies to [eligible employee groups and locations] from [effective date]. Separate statutory, protected, sick, parental, or other leave policies may apply.

Do not combine legally distinct leave categories merely to simplify the document without location-specific review.

2. Eligibility

Define:

• Employee groups covered
• Waiting period, if any
• Full-time, part-time, temporary, or other treatment
• Location-specific variants
• What happens when eligibility changes

Use structured employee attributes to assign policies. Avoid maintaining eligibility through an informal list that drifts from the employee record.

3. How PTO is provided

Document whether time is:

• Granted at the start of a period
• Accrued over time
• Based on service, working schedule, or another approved rule
• Capped at a maximum balance
• Adjusted for changes in eligibility

Include examples reviewed for the actual policy. Do not leave critical rules hidden only in undocumented system configuration.

4. Requests and notice

Template:

Employees submit planned PTO through [system] with the requested dates and any information required by the policy. Where practicable, requests should be submitted [notice period]. Unexpected absence follows [separate reporting process].

Clarify:

• Minimum request unit
• Notice expectations
• How partial days work
• How employees change or cancel a request
• Which absences follow a different process

5. Approval process

State who approves, what they consider, and how decisions are recorded.

Template:

The assigned manager reviews requests using team coverage, existing approved leave, operational requirements, and consistent policy application. A request is approved only when its status is recorded as approved in [system].

Define a fallback approver and escalation path. Avoid subjective criteria that have not been reviewed for fairness and consistency.

6. Carryover, expiry, and negative balances

Address each explicitly:

• Whether unused time carries forward
• Any carryover limit
• Whether balances expire and when
• Whether negative balances are permitted
• How corrections are handled
• Treatment when employment ends

These sections need jurisdiction-specific review. Do not copy another company’s wording without confirming it fits the company’s locations and obligations.

7. Holidays and working schedules

Explain how company holidays, weekends, part-time schedules, and non-standard workweeks interact with a request. The system and written policy should calculate or describe the same outcome.

8. Communication and records

Employees should know where to find:

• The current policy version
• Their balance
• Submitted and approved requests
• The team calendar where appropriate
• The correction and escalation path

Managers need separate guidance for timely, consistent approvals.

Policy launch checklist

• [ ] Locations and employee groups identified
• [ ] Legal and payroll review completed
• [ ] Eligibility and balance rules approved
• [ ] Request and approval owners documented
• [ ] Carryover and termination treatment confirmed
• [ ] Examples match system configuration
• [ ] Opening balances reconciled
• [ ] Employees and managers informed
• [ ] Effective date and version recorded
• [ ] Review date assigned

After approval, configure the policy in a dependable time-off management system and use the time-off software buyer's guide to plan a controlled cut-over.