Executive project dependency escalation note
A focused note for escalating a project dependency while leaders still have meaningful choices.
- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Define the role
State the milestone at risk, dependency, owner, evidence, date it matters, and consequence of delay. Do not escalate a label such as blocked without showing what is waiting and why.
Set the operating model
Offer the smallest useful set of choices and identify the authority each one requires. Project coordination prepares the path; the functional owner remains responsible for technical or operational judgment.
Choose with care
Close the note when the dependency resolves or the decision changes. Repeated escalations should inform a better intake rule, source record, or cross-functional operating cadence.
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