Start from the departure event and the mailbox record

A client contact who leaves can still sit on shared mailbox permissions months later. The audit begins with the departure date, the mailbox, and the list of people who can read or send on behalf of that address. Pull the delegate list from the mail platform rather than from memory. A name on a sticky note is not evidence of current access.

Ask the client for the departure date and the exact mailbox or alias involved. Record whether the mailbox is a personal account, a shared inbox, or a role address. The treatment differs because ownership sits in different places. Write the answer beside the audit row before any permission is changed.

Collect the current permission list with the date and the tool used to read it. Include full-access delegates, send-as rights, send-on-behalf rights, calendar delegates, and forwarding rules. Each one is a separate path into the same mailbox. Missing a path leaves a silent copy of client correspondence.

Compare the permission list with the approved request that created each entry. A permission without a request is a finding even when the person seems trustworthy. Note who granted it and when. The audit is about the record, not about suspicion.

Separate ownership from delegation

Ownership belongs to the client, while delegation is a temporary grant from the owner to a named worker. Write the owner for every shared mailbox and the date the delegation was approved. A mailbox with no owner cannot decide who should keep access. Escalate that gap before removing anything.

Distinguish a role mailbox from a personal mailbox. A role address such as support at the company can pass to a new team without touching any individual account. A personal address must be closed, forwarded under a rule, or left dormant by client decision. Record which choice the client made.

Keep a delegated worker's personal mailbox separate from the client's mailbox rights. A specialist may need to read the shared inbox but should not gain the departed contact's identity. Remove send-as before full access when the client wants a staged change. Stage the change in a written order.

Name the person who can approve a new delegate after the audit. The approver may be the client's operations lead or a named manager in the service team. Record the channel for that approval. Without a current approver, the next request will recreate the same drift.

Test each delegated path with a non-destructive check

Test the permission list without opening client mail. Use the admin console to confirm the delegate entry and its scope. Do not ask a worker to prove access by reading a live message. A read receipt or login test creates its own record and can confuse the client.

Check calendar delegation separately from mail delegation. A calendar editor can see meeting details even when mailbox access is gone. Review the calendar permission list for the same names. Remove entries that no longer match an approved role.

Review forwarding rules, automatic replies, and inbox rules that send copies outside the mailbox. A forwarding rule can outlive every visible delegate. Record the destination and the rule owner. Remove a rule only after the client confirms it is not part of an active service.

Record the result of each test as present, removed, or awaiting client decision. Add the evidence reference and the tester's name. A row that says checked without a result cannot be reviewed. The audit closes on evidence, not on a meeting.

Handle shared and role-based mailboxes

A shared mailbox may serve several clients and several workers at once. Audit it by work lane rather than by person. Map each lane to the workers who need it and the client who owns the address. Remove a worker only when no active lane still depends on that access.

A role mailbox that survives a contact's departure needs a new accountable owner. Assign the owner before the next shift uses the address. Update the signature, the automatic reply, and the escalation line in the same change. A role address that still names a departed person confuses customers.

Check distribution groups and aliases that feed the mailbox. A group membership can grant access without appearing in the mailbox delegate list. Compare the group roster with the current team list. Remove stale members and record the change.

Keep a short handover note for the next reviewer. State which mailboxes changed, which stayed, and which decision is still open. Link the client's approval. A future audit should not need to rebuild the history from email threads.

Close the audit with evidence and a review date

Close the audit only when every row has a result and an owner. Mark the rows that need client approval and the date the request was sent. A row left open without a follow-up date will be forgotten. The closure note should show the remaining risk in plain language.

Send the client a short summary of what was removed and what remains. Name the mailbox, the access type, and the reason for any retained entry. Do not include unnecessary personal details. The client should be able to approve the outcome without opening the admin console.

Set the next review date from the risk, not from the calendar alone. A mailbox tied to a departing executive may need a check in thirty days. A stable role inbox may need a quarterly review. Write the trigger that would force an earlier check.

Use the audit findings to improve the departure checklist. Add mailbox delegation to the same list that covers laptop return and system access. Name the person who confirms the change. A checklist that stops at the login misses the mailbox that outlives it.

For the next step, compare this workflow with Coordinate Access Removal at a Contractor End Date and the operations guide. For access and oversight, use the authoritative planning reference alongside your own policy.