Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management or Workforce Engagement Management |
| Access | Admin |
Copying a shift pattern to another person or another week. How most schedule building happens.
Duplicate it
- In Workforce Management, click Schedule in the navigation bar and select Schedule.
- Find the agent whose shift you want, right-click a task in that shift and choose Copy shift.
- Hover over the agent you are copying to and click the Paste shift icon next to their name.
- Check time off and availability in the target period.
Two things happen quietly. Pasting onto somebody who already has a shift replaces it, including the start time; to keep their own start time, click their shift and choose Paste shift over instead. And where the person is not assigned to all the workstreams in the copied shift, those workstreams are swapped for ones they are assigned to.
Copy the week, then adjust
Most weeks resemble the last one. Copying and correcting is far faster than generating from nothing, and it keeps patterns consistent for the people working them.
Check time off in the target period
The step people skip. Copying a week onto a week where somebody has approved leave schedules them anyway, and the conflict is not always flagged.
Look at approved absence before pasting, every time.
Watch holidays
Copying a normal week onto a week with a public holiday staffs a day nobody is working. Same class of error, same check.
Copying between people
Useful when somebody joins a team and should work the same pattern as their colleagues. Confirm their contracted hours match, because a pattern copied onto somebody part-time is wrong in a way that looks fine.
Consistency is a feature
People prefer a predictable pattern to an optimised one that changes weekly. Duplicating supports that, and it is one of the few places where the easy path is also the humane one.
Review coverage after
A copied week was built against a different forecast. Check it against this period's demand rather than assuming last week's answer still fits.
Comments
0 comments
Article is closed for comments.