Time off and PTO

Time off lives on the Team page. It does two jobs at once: HR bookkeeping (balances, approvals) and operations (what happens to the routes).

Balances and accrual

Each person's available PTO is simple arithmetic: what they have accrued, plus any manual adjustment you have made, minus what they have used, plus any carryover you allow. Accrual works either way you run it:

• Monthly accrual: a person earning 96 hours a year accrues 8 per month, and their balance grows through the year.
• Full-year grant: the whole allowance appears at the start of the year.

Manual adjustments cover the real world: a signing bonus of extra days, a correction, a use-it-or-lose-it zero-out. Every adjustment is logged with who did it.

Requests and approvals

Techs request time off in the app; owners and managers approve or decline. Half days are supported, and a PTO day converts to paid hours using your configured hours-per-day.

What approval does to the schedule

Approving leave is an operational event, not just a calendar note:

• The tech's routes inside the leave window are removed automatically.
• The pools from those routes are re-planned: absorbed onto adjacent days or other techs where the schedule math allows.
• Anything that could not be absorbed is surfaced for manual placement, so glance at the affected week's routes after approving; the calendar's day view makes redistributing the leftovers a two-minute drag session.

This is why approving Friday-for-next-week beats approving Sunday night: the re-planning has more open days to work with.

Ripple into pay

Approved PTO hours flow into that week's timesheet as paid, non-overtime hours. They count toward the paycheck but never toward the overtime threshold, so a tech taking Monday off and working four ten-hour days shows 48 paid hours and zero overtime, which is the legally-normal treatment. Details in Timesheets, overtime, and pay.