Manager handovers: preserve review responsibilities during role changes

Define the decision behind the record

Prepare an indexed list of authoritative records instead of copying everything into a new document. Define which responsibilities transfer and which remain elsewhere. Give the incoming manager a way to record questions and acceptance without falsely closing underlying issues.

Transfer recurring duties as well as individual open actions

Define the outgoing role’s sites, review responsibilities, recurring obligations and current open decisions. Identify authoritative records and the access needed to review them. A list of urgent tasks alone can miss regular duties that become visible only after the previous manager leaves.

Record receiving owners, next review points, restrictions and unresolved questions. Confirm that the incoming manager can retrieve the evidence and applicable instructions. Keep acknowledgement separate from completion of the duties and actions transferred.

Test a pending corrective action and a recurring review due after the role change. The record should identify who now owns each item and preserve the earlier history. Verify relevant access changes without assuming that a role announcement automatically transferred permissions, knowledge and accountability.

Build a usable record

Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.

• Role and site scope
• Pending decisions and reviews
• Authoritative record links
• Incoming owner and acceptance
• Unresolved questions and next step

Test the review, not just the form

Revisit the handover after the role change. Confirm that outstanding items remain visible to their new owners and that previous decisions retain their author and context. Avoid interpreting a completed handover as proof that every linked action is finished.