Define the administrative responsibilities being transferred
List the records, inboxes and task queues included in the handover. Distinguish permanent transfer from temporary cover and identify what remains with the original team or project manager. An administrator may coordinate document queries without authority to approve their technical answers. Record those boundaries in plain language. Avoid a general statement that the new person owns the project when the actual transfer concerns correspondence, register maintenance and follow-up on decisions made by others.
Prepare an open-task list with current states
For each unfinished item, record the project reference, next action, responsible reviewer and latest update. Separate a request awaiting a response from a response awaiting authorised assessment. Preserve dates and commitments from their approved sources rather than creating new ones during the handover. Include drafts and scheduled messages that could still go out. A list of unread emails alone will miss work being handled through project systems or conversations outside the shared inbox.
Identify the current records and versions
Link to the register or workspace the project team uses as its current record. Explain how superseded documents are marked and where decisions are recorded. Avoid copying the whole project folder into a new location unless that transfer is approved and controlled. The receiving person should be able to trace a task to its supporting correspondence. If two records disagree, give that discrepancy an owner instead of quietly choosing one and leaving the other team unaware.
Verify access and acceptance of responsibility
Check that the receiving person has approved access to the required systems and knows the appropriate review contacts. Do not share passwords or assume a folder invitation transfers authority to approve project decisions. Have the recipient acknowledge the open tasks and identify anything they cannot take on. Arrange cover or escalation for those gaps. Keep temporary access and the return of responsibility under the normal project process so neither person assumes the other is still watching an unattended queue.
Rehearse a fictional leave handover
In a fictional construction team, an administrator goes on leave while a supplier document query and a revised register entry remain open. The receiving colleague uses the handover list to find the original correspondence, checks which reviewer owns the answer and confirms the next follow-up. They discover that one referenced folder is unavailable and resolve access before accepting that task. The example verifies administrative continuity; it does not treat the transfer as approval of project work or completion of an obligation.
Reconcile the first review after transfer
At the agreed review point, check for unaccepted tasks, duplicate follow-up and records still being updated in the old location. Confirm who handles messages that arrive after the transfer date. Close obsolete reminders through the approved process only when their remaining work is accounted for. Record unresolved items with an owner rather than calling the handover finished because the meeting occurred. If cover ends, reconcile changes before handing responsibility back so completed actions are not repeated.