Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management or Workforce Engagement 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.
- Click the task and edit it. Type into the time fields, or use Duration to change its length. Dragging an edge works too, but it moves in 15 minute steps, so anything ending at ten past has to be typed.
- To take an activity out, drag its edge over the one before or after it until it is covered.
- Save, then Publish.
- 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.
Publishing does send them a push notification, so this is not silent. It is still a notification among all their others, on a phone that may be in a drawer. Message them directly rather than relying on it.
An activity has to fit inside the shift
Adding an activity that runs past the end of the shift is refused. Where the task genuinely belongs outside it, such as a required meeting, the way through is the option Add task even if user has no shift scheduled for this time on the bulk Add task screen.
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.
If the edit was wrong
The revert icon returns the schedule to the last published version, for up to 90 days at once. That undoes the record and not the conversation: somebody already told about the change still believes it.
Note why, on the task itself
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.
You do not have to keep that reasoning somewhere else. A task takes a note, one per task, and it shows the agent a white corner they can hover over to read it. That puts the explanation where both of you will look for it.
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.