Map decision rights before delegating an executive inbox

Inbox delegation often begins with access and a vague

Inbox delegation often begins with access and a vague request to "handle what you can." That phrase transfers pressure without defining authority. The assistant can sort messages, draft responses, gather context, and maintain follow-up, but each action carries a different commitment. A meeting acceptance spends calendar capacity. A friendly answer can imply agreement. A forwarded document may widen access. Before a virtual executive assistant works inside a leader's inbox, map decision rights at the message level. The map should tell the assistant which actions are routine, which require a draft, which need explicit approval, and which should be escalated without further handling. It protects the executive's relationships while letting support move predictable work instead of asking permission on every message.

Use recent, representative messages to build the map

Use recent, representative messages to build the map. Categories invented in a workshop often miss how requests actually arrive. Sample scheduling, introductions, internal updates, customer matters, board correspondence, hiring, invoices, travel, personal messages, and unsolicited outreach only where access is authorized. For each case, record the sender relationship, requested outcome, sensitivity, deadline source, existing rule, and consequence of an incorrect response. Remove private content from the working exercise when it is not needed. The aim is to identify recurring decisions, not to reproduce the executive's mailbox. Patterns will emerge: some messages require accurate routing, some need context assembled, and a smaller group need the executive's voice or judgment.

Write permissions as verbs

Write permissions as verbs. "Manage calendar" is too broad. "Offer times within protected scheduling rules" is testable. "Draft a decline for review" is different from "send a decline." A useful map may permit the assistant to acknowledge receipt, request missing logistical details, apply an approved scheduling rule, and file a confirmed reference. It may require approval before accepting an external commitment, sharing a nonpublic document, expressing the executive's view, changing a priority, or promising another person's work. State who can grant an exception and how long a temporary rule lasts. Silence should not count as expanded authority. When the executive is unavailable, the backup path must be explicit rather than improvised under pressure.

Separate the source of truth from the inbox

Separate the source of truth from the inbox. A message may initiate work, but the current commitment belongs in the approved calendar, project record, customer system, or decision log. The assistant should link or record the handoff and avoid maintaining a private shadow list that nobody else can cover. Preserve original wording when tone or obligation matters. If the executive writes "tentative," do not convert it to confirmed in a summary. Track threads waiting for the executive by the decision needed and responsible time, not simply by unread status. An inbox can be empty while important commitments remain unresolved. Conversely, a large unread count may include newsletters that carry no executive decision.

Review drafts as evidence during onboarding

Review drafts as evidence during onboarding. Instead of correcting style alone, ask why the assistant chose to answer, hold, route, or escalate. A polished draft built on an invented assumption is a serious failure. A plain draft that flags missing context may show sound judgment. Give feedback in the form of a reusable boundary: which fact should have been checked, which action was permitted, what required approval, and where the final commitment belongs. Expand rights gradually after consistent handling of routine cases. Restricted topics, personal data, personnel matters, legal communications, board information, and credentials should remain governed by the organization's access policy. Trust does not replace least-privilege design.

Audit the map using mistakes and near misses

Audit the map using mistakes and near misses. Look for unauthorized commitments, preventable executive touches, stale waiting items, repeated clarification, routing loops, and replies reopened because context was wrong. Discuss individual cases without turning one unusual event into a universal rule. If most messages still need approval, the boundary may be too narrow, the map may be hard to use, or the role may lack context. If support sends quickly but the executive repeatedly repairs relationships, the boundary is too broad or review is weak. A sound inbox model produces more than speed. It leaves a traceable commitment, keeps confidential material contained, and makes the stop point obvious. The executive retains decisions that require executive authority; the assistant turns the surrounding preparation and follow-through into dependable operating work.

Give stakeholders a visible route without exposing the delegation

Give stakeholders a visible route without exposing the delegation machinery. Internal partners should know where to send requests, what information helps, and when to expect an acknowledgement. They do not need access to private inbox notes or the executive's full sorting logic. Where a relationship requires the executive's personal response, say so in the map and allow the assistant to prepare background instead of imitating the executive's voice. When responsibilities change, review affected message classes before the new role starts. A founder who joins a board, an executive who takes on a new function, or a team entering a sensitive transaction may face correspondence that old rules do not cover. Suspend automatic handling for those classes until authority and access are confirmed. Test the revised map with examples and keep the effective date. The map should remain short enough to use, with links to detailed policies rather than copied policy text. If it becomes a catalogue of every sender, regroup it around actions and consequences. The point is consistent judgment under known boundaries, not perfect prediction of every email. That standard gives the assistant room to work and gives the executive a clear way to correct the system when circumstances change. Keep a short change note when a permission expands or contracts. The note should identify the approving owner, affected action, effective date, and review trigger. This prevents yesterday's draft rule from being mistaken for today's sending authority and gives backup support a current reference.

Frequently asked questions