Executive inbox sender relationship taxonomy
A routing taxonomy that uses relationship context without turning sender labels into automatic priority.
- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Define the role
Classify messages by the relationship, requested outcome, consequence, sensitivity, and response authority involved. Sender identity can supply context, but it should not decide the action by itself.
Set the operating model
Give each class a support action: file, acknowledge, draft, route, protect time, or escalate. State the evidence that moves a message between classes so the rule remains usable during pressure.
Choose with care
Sample the taxonomy during a weekly inbox review. Repeated misroutes may mean the relationship map is stale, the request channel is wrong, or a decision boundary needs a concrete example.
Related resources
FAQ
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Discuss executive support