Separate decisions from noise
An executive inbox contains requests, confirmations, notifications, and personal messages in the same stream. The assistant's job is not to read everything but to identify what needs the principal's attention and what can be routed elsewhere. A decision map defines the categories in advance so the sorting is consistent. It also reduces the risk of opening a message that should have stayed private.
The map should start from the work, not from the sender. A message from a board member may be a scheduling note, while a message from a junior colleague may contain a decision that affects a client. Sorting by content type rather than by hierarchy produces a more accurate result. The assistant can then apply the same rules regardless of who wrote in.
Read envelopes and threads, not private content
The assistant can often route a message from the subject line, the sender, the thread history, and the first sentence without reading the full body. Establish a rule that personal, medical, legal, and HR messages are not opened unless the executive explicitly asks. The map should name the categories that are out of scope and the path for handling them. The rule should be visible to anyone who shares inbox access.
When a message is ambiguous, the assistant should ask the executive rather than guess. A short question about whether a thread is private is better than discovering the mistake later. The map should also define who can access the inbox during an absence and what they may read. Privacy is a design requirement, not an afterthought.
Define the five routing lanes
A practical map uses five lanes: decide now, delegate, schedule, file, and do not open. Decide now covers messages that need the principal's judgment within the day. Delegate covers work that belongs to another team, schedule covers time requests, and file covers records that need no action. The fifth lane protects private material.
Each lane should have a clear destination and a service level. Decide-now items go to the morning brief, delegated items go to the named owner with a deadline, and scheduling requests go to the calendar workflow. Filed items go to the correct folder or record system. The assistant should not invent a new lane for every unusual message.
Set a response standard for each lane
The standard should say how quickly the assistant acknowledges, routes, or escalates an item. A client message may need an acknowledgment within two hours, while an internal update may wait until the next briefing cycle. The standard is about the desk's response, not the executive's final answer. It gives senders confidence that the message was received.
For decide-now items, the standard should include a cutoff time after which the item waits for the next brief unless it is a genuine emergency. For delegated items, the standard should require a named owner and a due date before the message leaves the desk. A routing map without service levels becomes a pile of good intentions. The standard is a service promise, not a target for the executive's final reply.
Protect sensitive topics with a named path
Some messages should never pass through the general inbox workflow. Legal disputes, personnel issues, medical information, and board-confidential matters need a named path and a restricted group of readers. The map should identify those topics and the person who handles them. The assistant should know when to stop and redirect rather than continue sorting.
The path should include a secure folder, a retention rule, and a contact for questions. Do not rely on a label alone, because labels can be applied by anyone with access. A named owner and a documented process create accountability. The executive should confirm the path at least once a year.
Review the map monthly with the executive
The inbox changes as the business changes, so the map needs a regular review. Look at the items that were misrouted, the messages that sat too long, and the categories that no longer appear. Ask the executive which decisions should have reached them sooner and which updates could have been filtered out. Adjust the lanes and the service levels accordingly.
Keep the review short and focused on patterns rather than individual messages. A single misrouted email may be an anomaly, while three in a month suggests a rule is unclear. The assistant should bring one suggested change to each review. A map that is never revised becomes a barrier rather than a tool.
Watch for maps that quietly expand
Over time, an inbox map can grow into a surveillance system if every message is logged and every sender is scored. Resist that drift. The map should serve the executive's attention and the desk's workflow, not produce performance data about colleagues. Collect only the information needed to route and review the work.
For related guidance, see our article on setting a first-thirty-minutes briefing routine and our executive support services. The NIST Privacy Framework offers a useful structure for limiting data collection to what the work requires. The framework is a reference for judgment, not a substitute for the office's own policy. That distinction keeps the map practical and defensible.
Key takeaways
- Sort by content type and required action, not by the seniority of the sender.
- Define private categories that are never opened and a named path for sensitive topics.
- Use five lanes with a clear destination and owner for each.
- Set response standards for acknowledgment, routing, and escalation, not just final replies.
- Review misroutes monthly and resist turning the map into a surveillance log.