Time off and conflicts

Time off is the exception layer on top of the staff schedule: it always wins over patterns and week edits, and Randvu warns you when a draft collides with it.

Adding time off

On the schedule page, open Time off in the toolbar. Pick the staff member — or Everyone (closure) to close the whole salon — a type, the date range, and an optional note that's visible to staff.

Three types are available:

• Vacation — planned leave.
• Sick — for advance-known sick days; for today, the Sick today button on the schedule is faster (it publishes instantly).
• Salon closure — applies to everyone and blocks bookings for those days.

The precedence ladder

When layers disagree, the higher one wins:

1. Salon closed days & holidays — override everything.
2. Approved time off — overrides patterns and week edits.
3. This-week-only edits — override the pattern for that week.
4. The weekly pattern — the default that repeats.

That's why adding a vacation doesn't require cleaning up shifts: existing shifts on those days are simply overridden by the leave.

Staff requests

Time-off requests submitted by staff show up with a Pending chip — approve or decline them from the Time off modal or the Needs attention panel. Approved entries start overriding the schedule immediately.

When drafts and leave collide

Drafting a shift on top of approved leave doesn't silently win — it creates a blocking conflict: "{Name} drafted over approved leave." The week can't be published until you resolve it by reverting the draft, removing the shift, or editing the leave. In the grid, affected cells are flagged Leave conflict.

Other conflicts surface in the same Needs attention panel with their severity:

• Blocks — must fix before publishing (drafts over leave, bookings with no shift to land on).
• At risk — coverage below demand, solo cover, missing skill coverage.
• Compliance — overtime above your cap, missing legally required breaks.
• Request — pending staff time-off requests.

Where to go next

• Staff schedule and coverage — the draft-and-publish model this sits on.
• Staff permissions explained — who can edit schedules and approve requests.