Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management |
| Access | Admin |
Changing one person's shift after publication. Small in the system, and not at all small for the person.
Change it
- Open the schedule and find the shift.
- Edit the times, or the activities within it.
- Save.
- Check coverage did not open a gap.
- Tell the person.
Telling them is part of the task
The system knowing is not the same as the person knowing. Somebody who does not see the change works the shift they remember, and that is a gap nobody planned for.
Message them directly rather than relying on the schedule being checked.
Watch what the change opens
Moving somebody off an hour leaves that hour short unless somebody else covers it. The edit is easy; the consequence is a gap at a peak.
Look at coverage after every change, not just at the person.
Ask before you move somebody
Where the change is for convenience rather than necessity, ask. A published schedule is a commitment people have arranged their lives around, and treating it as provisional undoes the value of publishing early.
Prefer a swap
Where somebody wants a change, a shift trade between two agents solves it without a manager rearranging anybody. It also leaves both people willing rather than one accommodated.
Note why
A schedule full of unexplained edits is impossible to review later, and adherence figures for that week make no sense to anybody reading them afterwards.
Count them
If you are editing many shifts every week, the schedule is not matching reality. That is a forecasting or availability problem, and fixing it saves more than the edits do.
Comments
0 comments
Article is closed for comments.