Executive decision escalation checklist
A clear checklist for routing requests that exceed an assistant's authority.
- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Define the role
An escalation rule should name the trigger, the decision owner, the context to attach, and the response window. Without those fields, support either interrupts too often or holds work too long.
Set the operating model
Escalate new commitments, sensitive disclosures, policy exceptions, and conflicts between leaders. Routine preparation can stay with support when the expected output and approval boundary are already clear.
Choose with care
Review escalations in the weekly operating meeting. Repeated questions are evidence that the delegation rule needs a better example, not that the assistant should guess.
Related resources
Read also: executive assistant decision rights and executive support confidentiality rules. Source: NIST AI Risk Management Framework playbook.
FAQ
What should support own?
Support should own recurring coordination and preparation with a clear output, owner, and escalation boundary.
When should support escalate?
Escalate when work creates a new commitment, involves sensitive information, exceeds agreed authority, or has no accountable decision-maker.
How should the workflow improve?
Review real misses and rework, then change one rule, template, or handoff that addresses the evidence.
Discuss executive support