Summary
Approving leave and then forgetting to update the roster is one of the most common scheduling mistakes. It leads to understaffed shifts, confused employees, and wasted time fixing problems that should have been caught automatically. NestedClock now handles this for you.
The Problem
In most systems, leave management and roster management are separate. You approve Sarah's annual leave for next Thursday, then you (or someone else) builds the roster and accidentally schedules Sarah for that same day. Nobody notices until Sarah doesn't show up.
The fix used to be: "just remember to check leave before rostering." That doesn't scale.
How It Works Now
When you approve a leave request, three things happen automatically:
- Unavailability records are created — for every day covered by the leave, the system marks the staff member as unavailable with a "via Leave" tag
- Conflicting shifts are removed — any existing roster shifts for that staff member on those dates are automatically deleted
- Future shift creation is blocked — if you try to roster someone on a day they have approved leave, the system returns a clear error message
What You See
In the Roster
The week view shows leave indicators on days where staff have approved leave. When you hover or try to add a shift, you'll see which staff members are unavailable and why.
In Availability
Leave-based unavailability records appear with a distinctive "via Leave" tag. These records cannot be manually deleted — they're managed by the leave system. A reminder banner explains this.
When Creating Shifts
If you try to add a shift for someone who's on leave (through the UI or the AI Agent), you'll get a clear error. The AI Agent checks availability before even proposing a shift.
What Happens on Rejection or Cancellation
- The unavailability records are automatically cleaned up
- The staff member becomes available for rostering again
- Previously deleted shifts are not restored — you'll need to re-add them if needed (this is intentional, as the roster may have changed)
Manual Unavailability
The same conflict resolution applies to manual unavailability. If you mark someone as unavailable for a day (not through leave, just directly), any existing shifts on that day are automatically removed.
AI Agent Integration
The Agentic AI checks both leave and manual unavailability before proposing a shift. If you say "Add Sarah to Monday," and Sarah has approved leave on Monday, the Agent will tell you immediately — no wasted step.
Why This Matters
- No more double-booking — the system prevents it at every entry point
- No manual cleanup — approving leave automatically updates the roster
- Clear visibility — leave indicators in the roster view, "via Leave" tags in availability
- Works with AI — the Agent respects leave just like the manual UI does
Leave-Roster Integration is available on Starter plans and above. It works automatically — there's nothing to configure.