PTO & Leave Tracking: The Complete Guide

PTO tracking sounds simple: people get days off, they use them, you record it. In practice, it's a compliance minefield — accrual calculations, carry-over rules, state-specific sick leave mandates, FMLA tracking, and the cascade effect of absences on team capacity.

Most companies manage PTO in spreadsheets until they hit 20-30 employees. Then the spreadsheet breaks — accrual errors compound, nobody's sure who has how many days left, and the year-end "use it or lose it" rush creates scheduling chaos.

Here's how to build a PTO and leave tracking system that actually works — from accrual policies through team capacity planning.

Types of Leave You Need to Track

Paid Time Off (PTO)

The umbrella category. Can be:

• Separate banks: Vacation, sick, personal (each with its own rules)
• Combined PTO: One pool for all time off (simpler to administer, harder to ensure sick time protection)
• Unlimited PTO: No specific balance, but you still need to track usage for patterns, compliance, and capacity

Sick Leave (State-Mandated)

As of 2026, most states have mandatory paid sick leave laws:

• Accrual rates vary (1 hour per 30-40 hours worked is common)
• Usage caps differ by state
• Carry-over rules are state-specific
• You must track this separately even if you offer combined PTO (for compliance reporting)

FMLA and Protected Leave

The Family and Medical Leave Act provides 12 weeks unpaid leave for qualifying events. You must track:

• FMLA eligibility (1,250 hours worked in previous 12 months — you need time data for this)
• Leave usage against the 12-week allowance
• Intermittent FMLA (partial days taken for ongoing medical needs)
• Return-to-work documentation

Other Leave Types

• Bereavement (company policy)
• Jury duty (legally required time off)
• Military leave (USERRA protected)
• Parental leave (company policy + state law)
• Sabbatical (typically at milestone tenure)

Each type has different accrual rules, approval workflows, and legal protections. Your tracking system needs to handle them all.

Accrual Methods Explained

Method 1: Annual Lump Sum

• All PTO available on January 1 (or hire anniversary)
• Simple to understand, simple to administer
• Risk: New hires who leave early have used more than "earned"
• Solution: Proration or negative balance policies

Method 2: Per-Pay-Period Accrual

• PTO accumulates each pay period (e.g., 6.67 hours/biweekly = 20 days/year)
• More complex but aligns with hours worked
• Required for sick leave in many states
• Needs system calculation each pay period

Method 3: Hours-Worked Accrual

• PTO earned per hour worked (e.g., 1 hour PTO per 30 hours worked)
• Required for part-time and variable-hour employees in many states
• Most complex to calculate manually
• Time tracking data feeds directly into accrual calculations

Method 4: Tenure-Based

• More PTO at tenure milestones (2 weeks year 1-3, 3 weeks year 4-7, 4 weeks year 8+)
• Popular for retention incentive
• System needs to know hire date and auto-adjust allocations

Key insight: Your time tracking system and PTO system must talk to each other. Hours worked determines accrual. Accrual determines available balance. Balance determines approval.

Building Your PTO Policy (Checklist)

For each leave type, define:

• Accrual method — Lump sum, per-period, or hours-worked
• Accrual rate — How much is earned and how often
• Maximum accrual cap — Can balance grow indefinitely?
• Carry-over limit — How many days transfer to next year?
• Waiting period — When can new hires start using PTO?
• Minimum increment — Can employees take 1 hour? Half day? Full day only?
• Advance notice required — How much lead time for requesting time off?
• Blackout dates — Any periods where PTO can't be taken?
• Approval authority — Who approves? Is there an escalation path?
• Payout on termination — Is accrued PTO paid out?

Team Capacity Planning

PTO tracking isn't just about individual balances — it's about ensuring adequate team coverage at all times.

The Coverage Problem

If 3 of your 8 team members are on vacation the same week, you have 37% reduced capacity. For client-facing teams, this can mean missed deadlines, dropped balls, or overworked remaining team members.

PTO Calendar Visibility

Everyone on the team should see who's off when (without seeing balances or leave types — privacy matters):

• Shared team calendar showing approved absences
• View of upcoming coverage gaps
• Integration with project timelines (alert if a key person is absent during a deadline)

Coverage Rules

Define minimum staffing:

• "At least 75% of the team must be available any given week"
• "No more than 2 of 5 engineers out simultaneously"
• "Client-facing roles require 2-week advance notice"

Build these into your approval workflow. When someone requests PTO, the system checks: "If approved, does this violate any coverage rules?" If yes, flag it — don't auto-deny, but make the manager aware.

Holiday Season Strategy

November-December creates a PTO bottleneck in most companies. People who "saved" their days try to use them all before year-end. Solutions:

• Allow carry-over (eliminates the "use it or lose it" rush)
• Encourage PTO throughout the year (track quarterly usage)
• Set team-level caps for holiday weeks
• Communicate blackout dates early (Q1 for year-end blackouts)

Compliance Considerations

State Sick Leave Laws

A quick overview of the patchwork (check current law for specifics):

• California: 5 paid sick days/year (40 hours), earned at 1h per 30h worked
• New York: Up to 56 hours, employer-size-dependent
• Colorado: 1h per 30h worked, no annual cap
• Massachusetts: Up to 40 hours/year
• Many others: Each with unique rules

Multi-state employers: You likely need different sick leave policies per state. Your tracking system must apply the correct rules based on employee work location.

"Use It or Lose It" vs Carry-Over

• Some states prohibit "use it or lose it" policies (California, Montana)
• Some allow caps but not forfeiture (earn up to X, can't accrue past cap)
• Most states have no restriction on PTO forfeiture policies

Know your state(s). A blanket "no carry-over" policy may violate law in certain jurisdictions.

PTO Payout on Termination

• Some states require payout of all accrued PTO (California, Illinois, Massachusetts)
• Others allow it only if policy promises it
• "Unlimited PTO" loophole: No accrual = nothing to pay out (legal in most states, but ethically questionable)

Your tracking system must maintain accurate balance data for separation calculations.

Integration with Time Tracking

PTO and time tracking are two sides of the same coin. Integration provides:

Automatic Balance Deduction

When an employee logs PTO in the time system, their balance decreases automatically. No manual adjustment, no spreadsheet reconciliation.

Accrual from Hours Worked

For hourly employees and hours-based accrual, the time tracking system feeds actual hours worked into the accrual calculation. Accurate time records = accurate PTO balances.

Overtime and PTO Interaction

In many jurisdictions, PTO hours don't count toward overtime calculations:

• Employee works 36 hours + 8 hours PTO = 44 total hours on timesheet
• But overtime is only calculated on hours actually worked (36)
• This distinction matters for payroll accuracy

Capacity Planning

Combining time tracking (who's working on what) with PTO (who's going to be off) gives you true capacity planning:

• "Next sprint, we have 320 available team hours instead of 400 (two people on PTO)"
• "Client Alpha's deadline conflicts with Sarah's vacation — we need to adjust"

Technology Requirements

Your PTO/leave tracking system should:

Feature	Why
Multiple leave types	Different accrual rules per type
Policy engine	Configure accrual, cap, carry-over rules
Multi-state compliance	Different rules per work location
Self-service requests	Employee requests, manager approves
Team calendar view	See who's off without showing private details
Coverage rules	Auto-flag when minimum staffing violated
Balance visibility	Employees see their real-time balance
Time tracking integration	PTO deducted from balances automatically
Year-end automation	Auto-apply carry-over/forfeiture rules
Audit trail	Every change logged for compliance

Getting Started

1. Audit current state. Where are your PTO balances tracked today? How accurate are they? What's your current error rate?

2. Map your policies. Document every leave type, its rules, and which states they apply to. This is your configuration blueprint.

3. Choose integrated tooling. PTO tracking that doesn't connect to your time tracking and payroll systems creates reconciliation work. Integration is essential.

4. Migrate balances carefully. When switching systems, verify every employee's balance. Errors in the starting balance compound forever.

5. Communicate to employees. Self-service balance checking and request submission improves satisfaction and reduces HR inbox volume by 50%+.

A Human Time includes integrated PTO and leave management: configurable accrual policies, self-service requests with approval workflows, team coverage calendars, and automatic balance tracking that syncs with time worked. One system for time on the job and time away from it.

PTO isn't just an employee benefit — it's a capacity management tool, a compliance obligation, and (when tracked well) a burnout prevention system. Track it as carefully as you track the hours worked.