Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management |
| Access | Agent |
Where absence is requested, approved and seen. Handling it promptly is what makes the published schedule real.
What it holds
- Requests waiting for a decision.
- Approved absence, which the scheduler works around.
- Balances, where you track them.
- A calendar view of who is away when.
Approve before generating
The schedule can only work around absence it knows about. Approving afterwards means removing people from a schedule you have already built, which produces gaps you fix by hand.
Requests first, then generate. That order saves most of the manual work.
Answer quickly, even when the answer is no
A request sitting for three weeks blocks somebody's plans. It also makes people ask in the corridor instead, and then the schedule does not know.
The calendar view is for spotting collisions
Four people asking for the same week is visible here and invisible in a list of requests. That is the check to make before approving the third one.
Not everything is holiday
Training, appointments, parental leave, sickness. Distinct reasons make the schedule accurate and the shrinkage figure meaningful, and they are how you find out that training is a larger commitment than anybody assumed.
It is employee data
Absence reasons can be sensitive. Who can see this page deserves the same thought as any other personal data, and it should not be everybody with a login.
Agents should see their own
Their requests, their balance, their approved days. Withholding it produces chasing, which costs a lead more time than showing it would.
Comments
0 comments
Article is closed for comments.