Time Off Management

You've scheduled your lead designer on a critical project starting Monday. Friday afternoon, you discover she booked vacation two weeks ago — in a system nobody checked. The project kicks off without her, the client notices, and your team scrambles to cover.

This happens more than anyone likes to admit. The root problem isn't forgetfulness. It's that absences live in one system and scheduling decisions happen in another.

Where Absences Need to Live

Time off management only works when it's embedded in the same tool where you plan work. If a project manager has to cross-reference an HR portal before making allocations, they won't — not consistently, not under deadline pressure. The absence data has to be right there on the timeline, impossible to miss.

WrkSched treats time off as a first-class scheduling object. When someone's on vacation or out sick, their availability updates instantly. If they already had allocations during that period, those allocations get automatically split around the absence. No manual cleanup, no forgotten overlaps.

The Approval Question

Smaller teams (under 10 people) often do fine with automatic approval — everyone's visible, conflicts surface in standups. Larger teams typically need admin approval so managers can check capacity before greenlighting a two-week holiday during a sprint deadline.

WrkSched supports both modes. Either way, the calendar reflects reality the moment a request is confirmed, and email notifications keep everyone in the loop.

Four categories cover most scenarios: vacation, sick leave, personal days, and a catch-all "other" for things like jury duty or conference travel. Each one shows on the calendar with a distinct visual pattern, so you can tell at a glance whether someone's sick versus on holiday — useful context when you're deciding whether to rebalance workloads or just wait it out.