How to write a simple PTO policy

PTO policy for early startups only works when teammates can find the rules without asking three times. Spell out paid time off (PTO) the first time the acronym appears in your handbook so new hires are not guessing. Write allotment or accrual, how to request time, blackout dates if any, approval owners, and what happens to unused days. Keep it to one page. Long handbooks nobody opens create side deals.

PTO policy for early startups begins with the leave type

Separate ordinary paid time off from legally distinct leave so you do not blur categories.

DOL's vacation leave topic page says the FLSA "does not require payment for time not worked, such as vacations, sick leave or federal or other holidays," and that those benefits are matters of agreement between employer and employee (DOL Vacation Leave). DOL's sick leave topic page confirms there are currently no federal legal requirements for paid sick leave, while FMLA may require unpaid leave when its coverage rules are met (DOL Sick Leave). Several states (and some cities) still require paid sick leave under their own statutes. Some states also treat accrued vacation as wages that must be paid out when employment ends, even when federal law does not. Those payout and sick-leave rules vary by state, so start from DOL's State Labor Laws hub and your state labor office rather than assuming a national template. As of November 2026 those DOL pages still carry that federal baseline. This post is not legal advice; check with employment counsel before you publish allotment, sick-time, and payout clauses.

Choose allotment or accrual and write the number

Whatever you pick, write:

1. Number of days or hours, or the unlimited norm
2. When the year resets
3. Whether unused days carry, pay out, or expire
4. Probation rules for new joiners
5. Part-time or contractor treatment (or "not eligible")

Example allotment line: "Full-time teammates receive 15 PTO days each calendar year, front-loaded on January 1, unused days expire December 31, no payout on exit unless required by law." Replace the numbers with yours; keep the sentence shape.

Store the live policy in Notes and link it from Employee management so the people record and the rules sit together.

Request and approval path

Ambiguity here causes calendar chaos.

Put requests in writing even on a three-person team. Slack thumbs-up evaporates. Track balances in Sheets until you use a dedicated tool.

Mark out-of-office on the shared calendar the same day you approve so customers and teammates see it.

Blackouts, notice, and stacking rules

Write only the rules you will enforce.

Do not invent a blackout after someone already booked a trip. Publish blackouts at quarter start.

Who is out and how work moves

A policy without coverage is a calendar fiction.

Keep coverage names on Task boards for the active week so work does not wait in private chats.

Recording balances without drama

Publish opening balances when the policy goes live so handshake deals die on paper.

Update the sheet the day time is taken, not at month end. Stale balances cause fights. People should see their own row or get a monthly snapshot.

Sick time versus PTO in practice

Keep ordinary vacation requests out of the sick bucket unless your written rule says otherwise. Mixing them makes planning impossible and can conflict with state or city paid-sick rules. When someone is out sick, require only the notice counsel approves. Do not demand medical detail in a group channel. On exit, do not invent a national payout rule: some states treat accrued vacation as wages that must be paid out, and that varies by state, so follow counsel and the State Labor Laws hub linked above.

Protected leave such as FMLA, when it applies, is not a PTO favor. Keep PTO math separate so you do not spend down protected leave as vacation by accident.

Holidays and shutdowns

Publish the holiday list for the year by your start date. If you run a year-end shutdown, say whether those days come from the PTO bank or are company-paid closures. Surprise shutdowns that consume PTO destroy trust.

Fairness checks each quarter

Once a quarter, glance at who has taken near-zero time. High performers who never step away are a burnout risk. Also glance at who always gets blackout exceptions; fix the list or the approval calibration.

Rollout in one week

Day 1: draft the one-pager and get a quick counsel pass on local sick-time triggers.

Day 2: fill balances for current people; correct any handshake deals.

Day 3: walk the team through request and approval; answer questions live.

Day 4: publish the note link in the company home doc.

Day 5: approve one real request end-to-end to prove the path.

PTO policy for early startups fails when founders keep secret exceptions. If you grant an exception, write whether it is one-time and update the page if it becomes the new rule.

What to leave out of version one

Version one is allotment or accrual, request path, approval owner, carry/expire, and coverage. Everything else can wait.

Revisit yearly or when you enter a new jurisdiction. Laws change; your one-pager should show a last-reviewed date.

When someone leaves, follow your written rule on unused days and any jurisdiction payout requirements. Do not negotiate a quiet special case that contradicts the page. Exceptions become precedent overnight.

If unlimited PTO is your model, still require coverage plans and minimum notice. Unlimited without norms usually means high performers take less time, not more. Publish an expected annual range as culture guidance without turning it into a hidden quota.

Leadership should take visible PTO too. A policy nobody in leadership uses trains the company to treat rest as optional theater.

Document examples of approved and declined requests (with names removed) so approvers calibrate. Two paragraphs beat a training deck. Refresh those examples when the company changes stage.

If a customer-facing rotation makes same-week PTO hard, say so in the coverage table rather than denying requests ad hoc. Predictable constraints feel fairer than surprise nos.

Keep the last-reviewed date at the top of the one-pager. When counsel or a new jurisdiction rule forces a change, bump the date the same day. Readers trust a dated page more than a wiki without a timestamp.

PTO policy for early startups is an operations artifact first. Clarity on the calendar beats eloquence in the handbook.

Accrual math should be boring and visible. If people earn 1.25 days per month toward fifteen a year, show the monthly earn rate in the sheet. Hidden formulas create disputes that feel personal.

Remote-first teams should state the time zone used for "business days" in notice rules. A Friday request in California is already Monday in Singapore; say which clock you mean.

When balances go negative because of an emergency, write the recovery plan (earn-back versus payroll deduction where lawful). Silence turns a crisis into a lingering trust wound.

Carryover caps, if you allow unused days into the next year, need a hard ceiling and a use-by date. Example: carry up to five days, which expire March 31. Without a ceiling, banks grow until finance panics.

Out-of-office messages should name a backup and a return date. A vague "away" autoresponder trains customers to escalate to the founder.

Blackout lists belong beside the holiday list, not in a founder's head. If a launch window slips, update the blackout note the same day rather than denying requests after the fact.

Approve time the same way every time. If founders skip the form, everyone else will too, and the sheet will lie.

Floating holidays, if you offer them, need a request deadline and a forfeit date. Example: choose two floating days by March 1 or lose them. Without a deadline, floating days become invisible debt.

Comp time for weekend launches should either be banned or written with an expiry. Unwritten "take a day later" promises are how resentment accumulates.

For interns or fixed-term contractors, say whether PTO applies at all. "Not eligible; follow the contractor agreement" is clearer than silence.

Shift swaps are not PTO. If two people trade on-call weekends, log that on the coverage plan, not as a balance change, unless your written rule says otherwise.

Bereavement and jury duty belong in separate short clauses or a pointer to counsel templates. Do not fold them into the vacation bank without a written reason.