Set a Handoff Checklist for Closing a Project Mailbox

Set the handoff boundary first

Agree on what retirement means for this project: the date the team stops using the address, the person who coordinates the transition, and who will handle incoming messages afterward. This does not require that every message be answered before the handoff; it does require that every remaining obligation has an owner.

Keep the project mailbox available while you review and communicate the change. Do not assume that retiring an address automatically transfers its conversations, access, or responsibilities. Those details depend on your organisation’s setup and the actions its authorised workspace administrator can take.

Find conversations that still need attention

Search the mailbox for recent activity and scan older threads that may contain commitments with later due dates. Read the latest replies, then check the context: a message that appears answered may still leave a promised action unfinished. Look for requests awaiting a decision, drafts or documents someone agreed to send, pending approvals, scheduled follow-ups, and questions that arrived near the end of the project.

For each candidate thread, write down its subject, correspondent, last meaningful update, outstanding action, and any date or dependency stated in the conversation. Record the facts rather than relying on memory. If a thread is genuinely complete, mark it as complete in your handoff record so the next owner does not have to guess.

• Check sent as well as received messages for promises made by the team.
• Distinguish “waiting for a reply” from “no action needed”; note who is expected to act.
• Flag sensitive or ambiguous conversations for review by the appropriate team member.

Give every open thread a continuing owner

Assign one accountable person to each unfinished conversation, even when several people will contribute. A team or department can be listed as a supporting group, but it is not a substitute for a named owner who will notice the next step. Ask the person to accept the handoff and confirm what they will do; avoid assigning work by copying someone without agreement.

Include the next action and, where the thread provides one, its deadline or trigger. For example, “send the revised schedule after approval” is more useful than “follow up.” If no date was promised, do not invent one. Have the coordinator resolve unclear ownership before the mailbox is retired.

Thread: [revised schedule] — Owner: [Jordan Lee] — Next action: send the approved version to [client contact] — Timing: after [approval]

Make a handoff record people can use

Keep a concise record in a location the incoming owners are authorised to access. It can be a shared project document or another approved team record; the important point is that it is readable, current, and not dependent on one person’s inbox. Include the mailbox being retired, the transition date, the new contact route, the coordinator, and the open-thread assignments.

Limit the record to information needed to continue the work. Link or refer to the relevant conversation using an internal method your team can access, and note any access restrictions. Ask owners to confirm their assignments, then have the coordinator compare the record against the mailbox once more for missed replies or new commitments.

Tell correspondents where to write next

Send a clear transition notice to active correspondents before the retirement date. State when the project address will stop being the right place to start a new conversation and give the replacement contact address or other agreed route. If existing threads will continue elsewhere, explain whether the new owner will contact them or whether they should reply to a specific address.

Do not imply that messages will be forwarded, monitored, or answered after retirement unless your team has confirmed that arrangement. Mailbox aliases are not automatically independent mailboxes or logins, and forwarding or access options depend on configuration and permissions. If an administrator needs to change mailbox settings, they should confirm what is available for their role and workspace.

Subject: [Project name] contact change

Hello [name],

From [date], please send new messages about [project] to [new contact address]. [Named owner] will continue the open conversation about [topic]. Please reply to [address] if you need to follow up on that thread.

Thank you,
[team name]

Confirm the handoff before retirement

Use a final check rather than treating the announcement as proof that the transfer is complete. Confirm that each open conversation has a named owner and next action, owners have accepted the work, and active correspondents have received the updated route. Check for replies that arrived during the transition and add any new obligations to the record.

If this is a BITTU Mail workspace, domain and mailbox administration is handled in Workspace, and available controls depend on role, plan, and provisioning state. An authorised administrator should confirm the intended mailbox change in the workspace before acting. Keep responsibility assigned and the handoff record accessible according to your team’s process; retirement is not a reason to discard unresolved work.

• No open thread lacks a named person responsible for its next step.
• The replacement contact route is stated consistently in the handoff record and notices.
• The authorised administrator has confirmed the mailbox change, and the team knows who will check for transition-period replies.