Role change handovers
Role changes, without the access piling up.
When someone moves role or team, Handover Pro hands their old work to the right people and reviews the SharePoint access they no longer need, with an overlap so nothing breaks while they settle in.
What goes wrong
The same problems, every time.
Access piles up
Each move adds permissions and rarely takes any away, until people can open far more than their job needs.
The old team is left guessing
Decisions, approvals and regular reports still point at someone who has moved on.
Nobody sets an end date
A quick "keep it for now" becomes permanent, because nobody comes back to remove it.
Access reviews are hard to evidence
Auditors ask how access was reviewed when people moved, and the answer is an email thread.
The interview
Questions written for this kind of handover.
Alongside a question for every gap the map finds, Handover Pro asks questions like these. The person answers in their own words, and every answer can be cited in the document.
- Which of your current access will you still need in the new role?
- Which decisions or approvals are you responsible for in this role, and who should make them now?
- Who are the main contacts for this role, inside and outside the organisation?
- Which regular tasks, reports or meetings come with this role?
- Which meetings do you chair?
Step by step
The same eight stages, tuned for this handover.
-
1
Map
Coordinator
-
2
Gaps
Coordinator
-
3
Interview
Person handing over
-
4
Document
Coordinator
-
5
Sign-off
Person handing over
-
6
Access plan
Coordinator and approver
-
7
Acceptance
People taking over
-
8
Seal
Coordinator
An overlap that actually ends.
They keep read access to their own handover and its sealed package. Access kept alongside the new owner can have an overlap end date; on that day the handover is flagged, and End the overlap removes it after checking the new owner still has what they need.
Evidence for access reviews
Each handover records who had which access, what was decided for each item and by whom, and when the changes were made and checked. That is the evidence ISO/IEC 27001:2022 control 5.18 and NIST SP 800-53 PS-5 ask for when people move.
Other kinds of handover