How to Write a PTO Policy
A leave policy has about ten questions to answer. If it runs longer than two pages, it is answering questions nobody asked.
Last reviewed 17 Aug 2026
Before you start
A leave policy exists so the same question gets the same answer regardless of who asks and who is asked. That is the whole job. It is not a statement of values, and every paragraph not answering a question somebody will actually ask makes the ones that do harder to find.
Write it for the person reading at nine in the evening because they want to book a holiday and are not sure whether they have the days. That reader wants short sections in the order they think in.
Who it covers
Open with scope. Which employment types the policy applies to, whether part time staff are included and on what basis, whether contractors are covered, and when eligibility begins.
Probation deserves a sentence of its own: whether leave accrues during it, whether it can be taken during it, and what happens to any balance if somebody leaves inside it. Leaving this out is how one manager ends up saying yes and another no in the same month.
How much time, and how it is earned
State the full year allowance and the leave year it applies to. If your leave year is not January to December, give the dates. Then state the method: a grant at the start of the year, an accrual per month or per pay period, or unlimited. One sentence each, and the accrual methods guide has the comparison if you have not chosen yet.
Say what happens for somebody joining partway through the year, in the same section. Name the rule rather than only the outcome: complete months remaining, or accrual from the first eligible month, and how the result is rounded. The proration guide covers the options and the arithmetic. Whichever you choose, the policy is where it stops being a habit and becomes a rule.
Say whether public holidays sit on top of the allowance or inside it. This is the single most misunderstood line in most policies, and one sentence removes the ambiguity for good.
What happens to unused time
Whether unused days carry into the new year, how many, and whether carried days have a deadline. If nothing carries, say so plainly and name who can grant an exception, because the exception will happen. If there is a cap, give the number rather than a principle. The carryover guide covers the shapes and the legal caution that goes with them.
How to request, and who approves
The mechanical section, and the one people reread. Where requests go. How much notice is expected, usually scaled to the length of the request. Who approves. How long an answer takes. What happens when two people ask for the same week, which is the genuinely contentious part and the reason to write it down before it happens rather than after.
Say on what grounds a request can be refused: cover, a delivery, a peak period. A policy implying leave is always approved sets up a worse conversation than one saying cover comes first and naming the busy weeks.
Blackout and peak periods
If there are weeks when leave cannot be taken, or can only be taken by a limited number of people, name them. A retailer in December, a finance team at year end, a support desk through a launch.
Two rules keep this fair. Publish the dates well before people plan holidays, and state how many people may be away rather than refusing everybody by default. A number is easier to argue with than a blanket, which is precisely why it produces fewer arguments.
Sickness and the other categories
Say whether sickness comes out of the same allowance or has its own, what notification is expected on the first day, and at what point a medical note is required. Keep the tone plain and keep medical detail out of the record entirely. The distinction between the categories is set out in the PTO, vacation and sick leave guide.
Then list the other categories you offer, a line or two each: bereavement, jury service, parental leave, unpaid leave. Where a category is discretionary, say who decides.
Leaving
What happens to a balance on the final payslip. Whether unused days are paid out and at what rate, and what happens to an overdrawn balance. This paragraph is the one most likely to be governed by law rather than preference, so confirm the position for each jurisdiction before writing it, and revisit it whenever you start employing people somewhere new.
The skeleton
- Scope and eligibility.
- Allowance, leave year and accrual method.
- Proration for joiners and leavers.
- Public holidays, and whether they sit inside or outside the allowance.
- Carryover, any cap and any deadline.
- Requesting, notice and approval.
- Blackout or peak periods.
- Sickness.
- Other leave categories.
- What happens on leaving, plus who owns the policy and when it was last reviewed.
Ten headings, one or two short paragraphs under each. If a section needs a full page, the rule underneath it is probably too complicated to be applied consistently anyway.
Keeping it usable
Put a review date and an owner on the last line. Leave policies rot quietly: a company starts employing somebody in another country, a leave year changes, a statutory minimum moves, and the document goes on saying something nobody has believed for two years.
Then make the policy and the tracking agree. A policy saying five days carry over, sitting beside a spreadsheet that carries ten, means the document is not the rule. Whatever tool you use, configure the allowance, the method, the cap and the leave year to match the words. The tracker on this site holds all four as settings, with per person overrides for the cases the policy allows.