A startup PTO policy that works when the founder is away

Write the first-hire terms before making the offer¶

An early engineer should not have to infer the vacation policy from the founder's weekend Slack activity. Put the benefit in writing with the offer materials: how time is earned, who approves dates, and what happens when the founder is fundraising or traveling. Keep production coverage separate from permission to take leave.

The first hire also exposes dependencies that the founders have been carrying informally. Someone needs to own the pager, the support inbox or the enterprise customer's renewal while that employee is away. Name that person before approving the dates instead of requiring the employee to stay reachable.

Use the same written terms for subsequent offers unless you deliberately approve an exception. A private promise made during recruiting should become a recorded policy assignment, not a surprise the operations lead discovers when reconciling balances later.

Formalize PTO tracking for startups as ownership changes¶

Use the stages below as prompts for handing off decisions, not compliance thresholds. The trigger is a change in how the company works: the founder stops seeing every request, team leads gain approval responsibility, or an operations owner inherits several offer-letter arrangements. Add structure before those gaps cause conflicting decisions.

At the earliest stage, a shared understanding is fragile because the founder is the memory. At the next stage, team leads need the same definition of an approved absence. By the time operations owns the records, that person needs recorded policy terms and balances, not a search through recruiting DMs.

Choose accrued PTO until backups make unlimited workable¶

For a seed-stage company without dependable coverage, start with accrued PTO. A visible balance gives the first hires a concrete entitlement and gives the founder a clear record. Unlimited leave becomes a workable choice when employees can actually disconnect and managers review time taken, rather than relying on the word “flexible.”

An unlimited policy does not solve a sole engineer's pager dependency. Nor should it become a hidden fixed allowance enforced through denials. Read How unlimited PTO actually works for the operating rules, and Accrual vs. bank vs. unlimited PTO before selecting the structure for your offers.

Give the first hire a clause with testable earning rules¶

Choose benefit terms that the employee and whoever runs payroll can calculate independently. This illustrative clause uses 15 days per year for an employee working eight-hour days, earned across 26 biweekly accrual events. Replace the bracketed terms and have the full policy reviewed for the employee's work location.

Copy-ready first-hire clause

Vacation earning begins on your employment start date. Your annual vacation allowance is [120 hours, equivalent to 15 eight-hour days], earned in equal amounts across [26 biweekly accrual events]. Your policy schedule states the credit dates and treatment of any partial first period. [Founder or team lead] approves planned vacation; [named authorized backup] handles decisions when that person is unavailable.

Before planned leave, the manager confirms ownership of production on-call duties and customer commitments. Approved vacation does not require routine monitoring of company messages. Sick, emergency and protected leave follow [separate policy and contact]. Carryover and separation terms are recorded in [attached policy schedule].

Check the first hire's balance with an exact example¶

The sample allowance is 120 hours divided by 26, or approximately 4.615385 hours per accrual event. After 13 complete events, the employee has earned exactly 60 hours: 7.5 eight-hour days. If they have used five days, or 40 hours, they have 20 hours remaining: 2.5 days.

This example has no pending requests, carryover or adjustments. Keep full precision while calculating and round the displayed figure at the end. Rounding each credit too early can make the annual total drift from the promise in the offer.

The Department of Labor states that the FLSA does not require vacation pay. Review the company's commitments and applicable rules before adopting or changing these terms.

Hand off production access before approving a launch-week absence¶

Put the on-call replacement on the rota and confirm they can use the relevant systems. A founder who says “I'll cover” but cannot deploy or reach the customer escalation channel has not closed the gap. Run the handoff while the employee is still available to answer questions.

For a product launch, identify the decisions that genuinely require the absent specialist. Move those decisions earlier, delegate them or reschedule that part of the launch. Avoid letting every sprint, release and investor deadline become a new reason nobody can book vacation.

Give the approval backup authority to make a decision while the founder is traveling. The backup must know the launch plan and existing approvals; forwarding requests into an unattended inbox only moves the bottleneck.

Run startup requests in Slack or Teams with Cabana¶

Use PTO tracking in Slack to replace founder DMs with recorded requests, balances and approvals from messages. PTO tracking in Microsoft Teams gives startups using Teams requests, balances, who's out and manager decisions inside Teams.

Cabana supports accrued and unlimited policies. With unlimited leave, track days taken rather than a remaining bank; the suggested annual usage figure is a nudge, not an enforced minimum. Managers still own the usage conversation and the production handoff.

Configure the approval chain and an eligible coverage contact before the founder's next trip. Keep the written terms from the Free PTO policy generator alongside the records in PTO tracking software for small teams, so the next operations hire inherits an actual system.