Document an Admin Handoff for a Business Email Workspace

Set the scope and date

Start with the workspace or business unit covered, the handoff date, the outgoing and incoming administrators, and any period when both people will coordinate. Clarify whether the change concerns all workspace administration or only specific duties. Responsibilities and available controls can depend on a person’s role, plan, and provisioning state, so do not assume that every administrator sees the same options.

Record the source of the handoff information and when it was last checked. Mark uncertain details as unconfirmed and assign someone to verify them. This prevents an old note from appearing to be an authoritative account fact.

Make responsibilities explicit

Describe the work the administrator actually handles, rather than relying on a title such as “email admin.” Consider domain and mailbox administration, external sending policies, and coordination of workspace chat, tasks, or calendar where those duties apply. For each responsibility, name the owner, the usual trigger for action, and any approval or escalation route.

Distinguish administration from ordinary mailbox use. For example, state who evaluates a request for a new mailbox, who approves it, and who carries out the change if authorized. Do not document an action as available to the incoming administrator until their role and workspace state permit it.

Responsibility: Review requests for new business mailboxes
Current owner: [Name or role]
Approval from: [Name or role]
Next administrator: [Name or role]
Confirmation: Record the decision and completion in [authoritative record location]

Inventory open requests

Give every unresolved item a short description, requester or affected team, current status, next action, owner, and target follow-up date if one has been agreed. Include dependencies, such as waiting for an internal approval or information from a domain owner. Separate work that is merely being monitored from work that needs an immediate decision.

Avoid copying unnecessary message contents or sensitive personal information into the handoff. Link or refer to the approved record location using your organization’s normal access controls. If a request is resolved during the transition, update its status and note where the completion was recorded.

• Request: [brief description] — Status: [waiting / in progress / blocked]
• Next action and owner: [action] — [person or role]
• Follow-up: [date or agreed trigger] — Record: [approved location]

Point to authoritative records

Name the organization-controlled location that holds the current account and domain records. State which record is authoritative for each subject, such as mailbox ownership, approved administrators, domain responsibilities, policy decisions, and service or renewal information. If records are split across locations, explain which one wins when copies disagree.

Include the record owner, who can update it, and how the incoming administrator requests access. The handoff document should point to records, not quietly become a competing source of truth. Never put passwords, one-time codes, recovery secrets, or private authentication material in it. Store any permitted sensitive records only under the organization’s established security process.

Transfer access without sharing credentials

Have the incoming administrator use their own account and the normal authorized sign-in and account processes. Do not pass along the outgoing administrator’s password or ask anyone to disclose an OTP. Confirm that the incoming person has the required role and can reach the records and workspace functions needed for their assigned duties. Administrative permissions and quotas are enforced server-side.

If access is missing, record the limitation and identify who is authorized to resolve it. Avoid suggesting that a particular control or feature must be present: availability can vary by role, plan, and provisioning. Once the change is complete, make sure ownership of the handoff notes and open requests is clear.

Confirm the handoff and keep it current

Close the loop with a short review between outgoing and incoming administrators. Check that responsibilities have named owners, each open request has a next step, and the authoritative record locations are reachable by the right people. Have the incoming administrator summarize the most time-sensitive items and explain where they would verify a disputed account detail.

Record the date of confirmation and any remaining access or information gaps. Set an appropriate reminder to revisit the handoff when responsibilities, administrators, or workspace arrangements change. The handoff is working when the incoming administrator can find the current records and move the listed requests forward without relying on undocumented knowledge.

Handoff check
[ ] Incoming administrator can access the approved record location.
[ ] Responsibilities and approval routes have named owners.
[ ] Every open request has a status, next action, and owner.
[ ] Unverified details and access gaps are assigned for follow-up.
[ ] No passwords or one-time codes appear in the handoff.