Setting an Inbox Delegation Boundary for a New Executive Assistant

Write the delegation boundary before the first day

A new executive assistant needs a written boundary before touching the inbox. The boundary should say which messages the assistant may read, which may be drafted, which may be sent, and which must go to the executive. It should also name the people who can approve an exception. A verbal overview is not enough for a role that handles sensitive messages.

Start with the categories the executive actually uses: board, investors, direct reports, customers, personal, and unknown. For each category, state the default action and the escalation path. The assistant should not have to guess whether a message is personal or professional just because it arrived in the same inbox. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Include the tone and signature the assistant may use. A draft that sounds like the executive is different from a draft that sounds like an assistant. The boundary should say which one is appropriate for each category. That clarity protects the executive's voice and the assistant's confidence.

The boundary should include examples for each category, especially the ambiguous ones. A message from a board member about a personal matter may belong in the personal category even though it arrives through the board channel. Examples make the category usable under pressure. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Separate reading, drafting, and sending

Reading a message is not the same as drafting a reply, and drafting is not the same as sending. A new assistant may be ready to read and sort messages before being ready to send them. The boundary should show the progression and the sign-off required at each stage. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

For sensitive categories, require a draft review before sending. For routine scheduling, the assistant may send after the calendar owner confirms the time. For financial or legal messages, the assistant should route the message without drafting a substantive response. The categories should be specific enough to use during a busy morning.

Record the exceptions in a short log. If the assistant sends a message that normally requires review, note why and who approved it. The log helps the executive see where the boundary is working and where it needs adjustment. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

A draft can be a full reply or a set of bullet points. The boundary should say which one the assistant is expected to produce for each category. A bulleted draft may be faster for the executive to review. A full reply may be appropriate for a routine acknowledgment.

Name the escalation path for sensitive messages

The boundary should name a primary and a backup person for each sensitive category. If the executive is unavailable, the assistant needs to know who can decide. A path that ends with the executive's name alone is not a path when the executive is traveling. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Escalation should include the information the decision-maker needs: the sender, the request, the deadline. The assistant's recommended next step Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer. The record should name the next action and the person who owns it. Keep the source reference with the case. A later reviewer should be able to continue without asking for context.

If a message is urgent but the category is unclear, the assistant should err toward escalation. A short delay with a clear owner is better than a wrong reply from the assistant. The boundary should say that explicitly so the assistant does not feel penalized for asking. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

The escalation path should include a time expectation. A sensitive message that sits for a day may be worse than a quick holding reply. The boundary can say who sends the holding reply and what it may say. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Review the boundary with real examples

After the first month, review a sample of messages with the assistant. Ask which category was unclear, which draft required the most revision, and which escalation felt unnecessary. The answers show where the boundary is too tight or too loose. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Use de-identified examples in the review. The goal is to improve the written boundary, not to critique the assistant's judgment in front of the team. If the same category causes repeated questions, rewrite the category rather than telling the assistant to use better judgment. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Update the boundary and record the date. A boundary that is never revised becomes a document nobody reads. The [inbox delegation research](/research/auditing-inbox-delegation-boundaries-for-executive-assistants/) describes how to audit the boundary over time. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

When the assistant is on leave, the boundary should name the coverage person and the categories they may handle. A coverage person who has not been trained on the boundary should not inherit the full inbox. The executive should approve the coverage plan in advance. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Update the boundary when the role changes

When the executive changes, the board composition changes, or the assistant takes on a new scope, review the boundary again. A category that was routine under one executive may be sensitive under another. The assistant should not carry an old permission into a new relationship. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Record the new approval path and the date it takes effect. Tell the people who send sensitive messages that the path has changed. A boundary that exists only in the assistant's file is not visible to the senders. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

Keep the current boundary with the role description and the onboarding materials. The next assistant should be able to read it before the first day. That continuity is the point of writing it down. Record the evidence and the next owner before the packet leaves the office. Keep the note usable by the next reviewer.

The boundary should be reviewed when the executive's travel or board cycle changes. A period with more sensitive messages may require a tighter rule. The review can be a short conversation. The change should be written down.

Keep a copy of the boundary where the assistant can find it during a call. A document buried in a folder is not a usable boundary. A one-page summary beside the inbox is more likely to be consulted. The full policy can stay in the shared drive.

Frequently asked questions