Time-off blocks tell the schedule when a tech is unavailable. Vacations, sick days, holidays, and training all get tracked the same way — start date, end date, kind, paid or unpaid.
Recording a block
- 1Go to /portal/time-off → 'Record time off'
Pick the tech, start date, end date, kind, and paid/unpaid.
- 2Add notes if useful
'Cancun trip' or 'broke arm in pickup game' — internal-only context.
- 3Save
The block now renders on /portal/schedule as a gray band so dispatchers see at a glance who's out.
What happens when you book during a block
Plyrium shows a warning ('Mike is off Tuesday — book anyway?') but does NOT hard-block scheduling. Emergencies happen; sometimes you really do need a tech to come in on their day off. The block is a flag, not a fence.
Paid vs unpaid
Pure bookkeeping — drives the future 'PTO used this year' rollup but doesn't affect scheduling. Most shops mark vacation + holiday + sick as paid; training is usually paid; 'other' covers things like jury duty or unpaid leave.
On Jan 1, take 5 minutes and record every federal holiday for every tech. You'll thank yourself in November when you're not manually un-scheduling Thanksgiving.