Write a Replacement Handoff Plan Before the Seat Empties

Name the critical work and the owner

List the work that cannot wait for a replacement to learn slowly: customer commitments, payment or payroll inputs, security tasks, reporting deadlines, and relationships with key vendors. For each item, name the current owner, the backup, the consequence of a missed cycle, and the minimum service level during the transition.

Rank the list by impact and frequency. A daily task with a hard deadline needs a different plan from a monthly report. The ranking tells you what to document first and what can be paused or deferred with an owner decision.

Keep the list short enough to act on. A register with forty critical items is a sign that nothing has been prioritized.

Map access and account recovery

Build an account inventory with the system, the account name, the role, the owner, the recovery method, and the last access review. Include shared mailboxes, distribution lists, vendor portals, and any local tool that holds business data. Do not record passwords in the inventory; record where the credential is stored and who can retrieve it.

Test the recovery path for the accounts the replacement will need. If multi-factor authentication is tied to a personal phone number, change it before the handoff. A replacement who cannot sign in on day one is a plan failure, not a training issue.

Record the date each credential was rotated or transferred. A transfer that is announced but not completed leaves the old person able to sign in.

Inventory open items with next actions

Create a handoff register with the item, the current state, the next action, the due date, the evidence link, and the named owner after the transition. Include escalations, pending customer requests, unfinished reports, and decisions waiting on someone else.

Do not summarize an open item as in progress. That phrase hides whether the next action is with the team, the customer, or a system owner. A specific next action lets the replacement act without reconstructing the history.

Record the date of the walkthrough and the version of the SOP. A routine that changes every week needs a review date, not a one time recording.

Record the undocumented routines

Ask the outgoing person to walk through the tasks that are not in the SOP, especially the checks they perform before sending a report or the workaround they use when a system fails. Record the walkthrough with a sample input and a sample output.

Have the replacement repeat the task while the outgoing person observes. Record the questions and the corrections in the SOP. A video without a written step is hard to search later; a written step without a sample is hard to verify. Keep both where the task warrants it.

Plan the shadow period

Define a shadow period with a start date, an end date, and a decreasing level of review. In the first week the replacement observes and performs with a reviewer. In the second week the replacement performs with sampling. By the end, the replacement owns the routine with the normal review cadence.

Name the reviewer and the acceptance criteria for each phase. Do not end the shadow period because the calendar says so. End it when the replacement can complete the work with the agreed quality and knows when to stop and escalate.

If the replacement is internal, confirm that the old role is backfilled or the work is removed. A handoff that adds a second job to one person is not a plan.

Test knowledge with real work

Use live or realistic tasks to test the handoff. Include one ordinary case, one exception, and one case where the source is incomplete. Observe whether the replacement finds the right evidence, applies the rule, and escalates at the right point.

Record the result and the gaps. If the replacement cannot complete an exception case, the SOP or the access is incomplete. Repair the cause before the outgoing person leaves, or assign a named owner for the remaining gap.

If the test fails, extend the shadow period and record the specific gap. A calendar end date is not evidence of readiness.

Communicate with customers and vendors

Prepare the messages for customers, vendors, and internal teams that interact with the seat. State the effective date, the new contact, the escalation path, and what stays the same. Get approval from the relationship owner before sending.

Update the contact lists, distribution groups, and system records at the same time. A handoff message that leaves the old name in the portal creates confusion and delays. Record the date of each update so a later question can be traced.

Keep a single contact list for the transition and update it after each change. Multiple lists with different dates are a common source of missed messages.

Close the old access and keep the evidence

Remove the outgoing person's access according to the offboarding rule and record the time for each system. Transfer ownership of files, mailboxes, and calendars before removal. Check that the replacement has the access they need and that no shared credential remains unchanged.

Close the handoff with the register, the test results, the access changes, and the remaining gaps. Set a review date after thirty days to confirm the replacement is stable. The record should show that the transition was completed, not merely announced.

Record the reviewer and the date of the thirty day check. A closure note without a follow up owner is only a hope.