Inbox Triage for Executives: Draft, Hold, Escalate

An executive inbox is not a to-do list. It is a mixture of decisions, requests, notifications, and noise, all arriving in the same place. An assistant who sorts it well creates time. An assistant who sends replies in the owner's voice creates risk.

The safest useful model has three lanes: draft, hold, and escalate. The assistant moves messages into the right lane with a clear next action. The owner decides what leaves the account.

Table of contents

• Start with the decision, not the sender
• The three lanes
• What the assistant may draft
• What must be held
• What must be escalated immediately
• Measure the queue, not the inbox
• Sources
• Frequently Asked Questions

Start with the decision, not the sender

Sorting by sender feels efficient and produces a tidy inbox that still contains every unresolved decision. Sort by what the message requires:

• No action: archive or label.
• A reply the assistant can draft from an approved answer: draft lane.
• A decision only the owner can make: hold lane with a decision question.
• A time-sensitive risk: escalate lane.

The same sender can produce messages in different lanes. A board member's newsletter is no action; a board member's request for a briefing is a hold.

The three lanes

Every item in a lane needs an owner and a due time. "Review later" is not a lane.

What the assistant may draft

Draft only when the answer comes from an approved source: a scheduling template, a standard acknowledgement, a previously approved position, or a factual status update.

A good draft includes:

• the exact question or request being answered
• the source of the facts used
• any place where the owner must choose
• a note on tone or sensitivity

Do not draft a commitment, a price, a legal position, or a personal message that requires the owner's voice. If the approved answer does not exist, create a hold with the question rather than inventing one.

What must be held

Hold when the message requires judgment, relationship context, or information the assistant cannot verify. Common examples:

• compensation, equity, or contract terms
• performance feedback about a named person
• a conflict between two executives
• a request from a client that changes scope
• a media or investor inquiry
• a personal matter

The hold note should be short and specific: "Decide whether to accept the November 3 date; the client needs an answer by Thursday." The owner should not have to reopen the thread to understand the choice.

What must be escalated immediately

Escalate without waiting for the next review when the message involves:

• a legal threat, subpoena, or regulatory contact
• a security incident, data breach, or credential exposure
• a safety issue
• a harassment or discrimination complaint
• a board or investor matter with a short deadline
• a request from a regulator or law enforcement

Escalation is not a forward with "FYI." It is a notification with the facts, the time received, the immediate risk, and the person who needs to act. If the owner is unreachable, follow the written delegation to the backup.

Measure the queue, not the inbox

Track:

• oldest unreviewed item in the hold lane
• share of drafts returned for a material rewrite
• share of escalations acknowledged within the agreed window
• messages archived with no action but later reopened

Inbox zero is not the goal. A clean inbox with an unread hold item is worse than a messy inbox with a visible decision queue. The O*NET executive administrative assistant profile includes managing correspondence and information; the measure should reflect whether the owner can act, not whether the folder is empty.

Sources

1. O*NET OnLine: Executive Administrative Assistants
2. NIST Privacy Framework
3. U.S. Department of Labor: Hiring
4. Bureau of Labor Statistics: Occupational Outlook Handbook

Frequently Asked Questions

Can the assistant send from the owner's account?

Only under a written rule that names the message types and the review requirement. Drafting is the safer default. Sending on someone's behalf can create commitments the owner did not make.

How quickly should an escalation be acknowledged?

Set a window with the owner and the backup, such as 30 minutes during working hours. The window should reflect the risk, not a generic service level.

What if the owner ignores the hold lane?

Review the oldest items together and decide whether to delegate the decision, decline the request, or change the service level. An ignored queue is a signal that the authority or volume is wrong.

Review cadence

At the end of each week, sample the drafts that were held and the messages that were escalated. Check whether the assistant had enough context, whether the escalation was timely, and whether the executive changed the draft materially. Feed the findings back into the boundary document and the onboarding examples.