A team lead heading out for a week can leave more than an empty chair. Shared mailboxes, approvals, and customer promises often sit with that one person. A delegation plan names who takes each duty, what they may decide, and when the access changes. It also covers the return, when the lead needs the context back. The plan should be written before the leave starts, not on the morning of departure.

Inventory the lead duties

Start with a written list of every mailbox the lead can access. Include shared inboxes, approval queues, and alias addresses that forward silently. A mailbox used once a month is easy to forget and hard to recover when a customer is waiting. The list should name the owner, the purpose, and the usual response time.

Add the duties that are not mailboxes but still block work. Refund approvals, schedule changes, template edits, and access requests often sit with the same person. Each duty needs a substitute and a limit on what the substitute can approve. A delegation that covers email but not approvals will stall on the first exception.

Choose the substitute

Pick a substitute who already knows the queue and the customer promises. The best substitute is not always the most senior person, because a senior lead may already be covering another gap. Choose someone with enough context to say no when a request falls outside the rule. Name a second person for the days the first is off.

Write down what the substitute may and may not do. A substitute may approve a refund under a set amount, but may not change a policy or a contract. The limits should be visible in the delegation note, not only in a conversation. A customer should never hear two different answers because the limits were unclear.

Set the dates and the time zone

Record the exact start and end of the delegation, including the hour. A note that says next week will be interpreted differently by each reader. Use the queue time zone and show it beside the clock time. If the lead travels, say which time zone applies to the return.

Decide when the mailbox access changes. Access should start before the lead leaves so the substitute can see the open work. Access should end after the lead returns and has read the handover. A gap at either end is where unassigned messages collect. Put both changes on the same calendar entry.

Brief the team

Tell the team who is covering each duty and how to reach that person. Post the note in the queue tool, not only in a chat thread that scrolls away. Include the escalation path for a decision the substitute cannot make. The team should not have to guess who is allowed to approve.

Brief the adjacent teams that send work into the mailbox. A finance or legal partner may address the lead by name and wait for a reply. Give them the substitute and the dates in one short message. Adjacent teams are the most common source of a stranded request.

Prepare the customer message

Tell customers only what changes for them. If response times stay the same, say nothing about the leave. If approvals will take an extra day, give the new window in plain language. Do not name the person who is away or describe the internal reason.

Update any auto-reply that speaks for the lead. A stale auto-reply that promises a personal response will create a broken expectation. Point the sender to the shared queue and the new response time. Test the auto-reply from an outside address before the leave begins.

Protect the open promises

List the open promises the lead made before the leave. Include callback times, refund estimates, and approvals that are waiting on one decision. Each promise needs a new owner and a note in the customer record. A promise without an owner is the first thing to fail.

Check the calendar for meetings that produce customer commitments. A lead may promise a fix at a meeting that the substitute does not attend. Move the decision or send the substitute in the lead place. The customer should see one continuous thread, not a change of voice.

Plan the return

Set a return review for the first morning the lead is back. The review should cover open mailboxes, unresolved approvals, and any promise made in the lead absence. The substitute should attend and hand back the context. This meeting is short and it prevents a second week of confusion.

Restore access in a deliberate order. Remove the substitute only after the lead has opened each mailbox and confirmed the queue. Keep the substitute as a backup for one more week. A sudden removal can strand a message that arrived on the return morning.

Watch for stranded work

Count the messages that sat unassigned during the leave. Group them by mailbox, duty, and day. A cluster on one mailbox points to a missing substitute. A cluster on one day may point to a schedule gap rather than an access problem.

Ask the substitute what was hard to decide. The answer often reveals a limit that was too tight or a rule that was never written. Update the delegation note before the next leave. Each absence should leave a better plan than the one before it.

A mailbox delegation plan is a coverage plan for decisions, not only for email. It lists the duties, names the substitutes, sets the dates, and protects the open promises. The plan should be visible to the team and to the partners who send work. When those pieces are ready, a lead can take leave without taking the queue down.