Plan requirement
| Subscription | Any plan |
| Also required | Workforce Management or Workforce Engagement Management |
| Access | Admin |
Moving many people between teams at once, which is what you need after a reorganisation. Their location does not move with them, and that is the catch.
Do it
- Open the Team members page in Workforce Management. It shows each person's role, teams and assigned workstreams, and you can search, export and refresh the list from there.
- Select the people to move.
- Add them to the new team, or remove them from the old one. Those are two separate actions, and since people can belong to several teams, adding without removing leaves them in both.
- Check their location and their workstreams are still correct. Both are edited from the same page, individually or in bulk, and workstream membership is what decides which shifts they can be given.
- Regenerate any affected schedule.
Check the location
Moving somebody between teams does not necessarily change their location, and a person on the wrong location gets the wrong hours and the wrong time zone.
This is the check people skip after a reorganisation.
Published schedules do not follow
A schedule already published still reflects the old membership. Moving people does not rebuild it, so either regenerate it or accept that the current period is planned on the old structure.
Time off travels with the person
Approved absence stays approved. Check it appears in the new team's schedule, because an approved day off that is not visible to the new lead is the one that gets scheduled over.
Do it before generating
Membership first, then the schedule. Doing it the other way round means building a plan for a team that is about to change.
Tell the leads
Both of them. The old lead loses visibility of somebody they may still be counting on, and the new one gains somebody whose pattern they do not know yet.
Verify with one person
Ask somebody who moved to open their schedule. Reading the membership list confirms what you configured; their screen confirms what happened.
Comments
0 comments
Article is closed for comments.