📋 HR Policy Document Generator

PTO Policy — Series A SaaS, 38 employees, Multi-State

An employee PTO policy is the company's formal commitment on time off — both what employees get and how they take it — written to balance the legal requirements of every state where employees work, the operational needs of the business, and the cultural values the company explicitly chooses. Based on our work with 200+ Series A-to-B SaaS companies, the policies that work for 3+ years without major revision share three traits: they have clear minimums AND maximums, they distinguish exempt from non-exempt treatment explicitly, and they include an escape-valve clause for the rare edge case.

Plain-Language Summary (at the top, for employees)

> You get 20 paid days per year of flexible time off. It covers vacation, personal days, and mental-health days. Sick days are separate and handled differently (see Section 4). We expect everyone to take at least 15 of the 20 days per year — because rest is part of the job, and we've seen what happens when people don't take time off. You can take up to 2 consecutive weeks without special approval; longer absences need 30 days advance notice and coordination with your team. Your manager approves time off, and the default answer is yes. If you get declined twice for the same request, escalate to People Ops.

The Policy

1. Purpose and Scope

This policy governs paid time off (PTO) for all employees of [Company Name]. It covers flexible time off, sick leave, and the procedures for requesting and approving time away from work. It applies to all exempt and non-exempt employees; specific differences in application are noted in each section.

2. Definitions

• Flexible Time Off (FTO): 20 paid days per calendar year, covering vacation, personal days, mental health days, and non-medical personal matters.
• Sick Leave: Separate from FTO. Accrual and use governed by state-specific law (see Section 4).
• Consecutive Absence: Any continuous absence longer than 5 business days.
• Extended Absence: Any continuous absence longer than 10 business days (2 weeks).
• Blackout Period: A business-critical window during which FTO may be declined with cause.

3. The Policy

3.1 Each full-time employee receives 20 days of FTO per calendar year, prorated for mid-year hires.

3.2 — Minimum Expectation: The company expects each employee to use at least 15 days of their FTO per calendar year. Managers are responsible for noticing when a direct report is not on track to meet this minimum by September 30 and for initiating a conversation. FTO is not 'banked' — unused days beyond the 20-day annual allocation do not roll over (but see 3.7 for parental-leave stacking).

3.3 — Consecutive Absence Up to 2 Weeks (10 business days): Any FTO request of up to 10 consecutive business days may be submitted with 2 weeks' notice and approved at manager discretion. The default answer is yes.

3.4 — Extended Absence (more than 10 consecutive business days): Any request for more than 2 consecutive weeks requires 30 days' advance notice and explicit coordination with the employee's team. These requests require dual approval (direct manager + next level up) and coverage planning documented before departure.

3.5 — Blackout Periods: The company may designate up to 2 weeks per year as blackout periods during which FTO may be declined with cause (e.g., board meeting week, product launch week). Blackout periods must be announced at least 60 days in advance.

3.6 — Sick Leave (separate from FTO):

• California employees: 40 hours per year, accrued per CA Labor Code §245
• New York employees: 40 hours per year, accrued per NY Labor Law §196-b (companies 5-99 employees)
• Washington employees: 1 hour per 40 hours worked, accrued per RCW 49.46.210
• Illinois employees: 40 hours per year, accrued per Paid Leave for All Workers Act
• Texas employees: No state mandate; company provides 40 hours per year of paid sick leave as a matter of policy

Sick leave is to be used for the employee's or family member's illness. No documentation required for absences of 3 days or fewer; documentation may be requested for longer absences per applicable state law.

3.7 — Interaction with Parental Leave: FTO and parental leave are separate. Employees may stack FTO onto parental leave to extend paid time. See the Parental Leave Policy for specifics.

3.8 — Compensation for Unused FTO at Termination (California): California law treats accrued-and-unused FTO as earned wages. California employees leaving the company will be compensated for unused FTO at their current base rate. (This does not apply to employees in other states covered by this policy.)

3.9 — Non-Exempt Employees: For non-exempt employees, FTO usage follows the same allocation (20 days/year) but is recorded in hours (160 hours/year) for wage-and-hour compliance. Non-exempt employees must submit timesheets for all FTO usage.

4. Procedures

4.1 FTO is requested in the company HRIS (currently [Tool]) at least 2 weeks in advance for standard requests, 30 days in advance for extended absences.

4.2 Managers respond to requests within 3 business days. Extended-absence requests within 5 business days.

4.3 If an employee is declined twice for FTO in a calendar year, they may escalate to People Ops for review.

5. Exceptions and Escape Valves

5.1 — The Escape Valve Clause: The company recognizes that life events (family crises, health emergencies, significant personal matters) may require time off that does not fit the standard FTO framework. In such cases, the employee should contact their manager AND People Ops. The company will make a good-faith effort to accommodate these situations, which may include additional paid or unpaid leave, modified schedules, or other arrangements.

5.2 This policy does not replace legally protected leave (FMLA, ADA accommodation, pregnancy disability, military leave, jury duty, bereavement). Those policies take precedence.

5.3 Nothing in this policy creates a contract of continued employment.

6. Review and Amendment

This policy will be reviewed annually by People Ops and the CEO. Material changes will be communicated to all employees at least 30 days before effect.

---

The 2 Implicit Cultural Choices

Choice #1: Minimum expectation of 15 days used. This policy signals that taking time off is a responsibility, not a privilege. It sacrifices the 'unlimited and self-regulating' ideal that some companies aim for. The alternative posture would have been 'unlimited PTO with no minimum' — which research and our own experience across 200+ companies shows leads to LOWER average PTO usage, not higher. You're choosing 'explicit expectation' over 'cultural ideal.'

Choice #2: 2-week max without special approval. This explicitly signals that the team is a dependency graph — no single person can unilaterally take 5 weeks without coordination. It sacrifices the 'treat people as fully autonomous adults' posture in favor of 'team reliability.' The alternative would have been no cap — which creates the scenario you already experienced (5 consecutive weeks straining the team). You're choosing 'team-first default' with an explicit escape valve for real life events.

The Escape Valve

Section 5.1 is the escape valve. It explicitly acknowledges that the policy can't anticipate every life event and commits the company to good-faith accommodation of edge cases. This single clause prevents the vast majority of PTO disputes, because most disputes are about 'something happened that the policy didn't cover' — and you've explicitly said you'll handle those case-by-case in partnership with People Ops. Without this clause, edge cases become adversarial. With it, they become collaborative.

State-Law Considerations for Legal Review

What to Send to the Lawyer

> Hi [Lawyer] — please review the attached draft PTO policy for [Company]. Specific questions: (1) Is the 15-day-minimum-expectation language enforceable under wage-and-hour law in any of our states? We intend it as cultural norm, not contractual obligation — flag any language that could be read otherwise. (2) Is our California §3.8 treatment of FTO-as-wages at termination correctly scoped to only CA employees, or does it inadvertently apply to all? (3) Are we missing any state-specific sick leave requirements for our 5 states? Thanks.

The two questions most likely to come back from the lawyer: 'can you change "expectation" language in 3.2 to avoid creating a de facto mandate?' and 'please add language preserving employer discretion in the escape valve clause.'

How to Roll This Out

• Announce it in a company-wide meeting, not a Slack message. PTO policy changes always trigger questions; make sure questions are answered live, not in a thread.
• Give managers a 1-page manager guide separately. They will be the ones approving/declining requests; they need to understand the 'default answer is yes' posture and the minimum-15-day nudge.
• Announce the blackout periods for the year upfront. Nothing triggers a PTO complaint faster than a surprise blackout during someone's planned vacation.

Key Takeaways

• Minimum-expectation beats unlimited for preventing the under-use failure mode. Research is clear on this.
• 2-week soft cap with 30-day notice for more balances individual autonomy with team reliability.
• Every policy has a Section 5 escape valve. Without it, edge cases become disputes.
• State-law compliance is non-negotiable. California treatment of accrued FTO as wages at termination is the most commonly missed provision; don't skip 3.8.