Executive assistant escalation note
An escalation note should let the executive understand the problem and make the required choice without reading the entire history. It begins with the verified current state and the decision that cannot be made within delegated authority.
Use a direct subject line that names the issue and deadline. Avoid labels such as "urgent" unless the body explains what will happen and when.
State consequence before history
Explain the material effect of delay or inaction in plain terms. A meeting may be lost, a commitment may slip, or a stakeholder may receive conflicting information.
Include only the history needed to judge the options. Link the full thread or source record for readers who need to inspect it.
Offer credible options
Present the available choices with timing, dependencies, and known drawbacks. Do not hide a material disadvantage to make the recommended option look simpler.
When a preferred course exists, say why it fits the executive's recorded priorities or prior decision. If facts are missing, name the uncertainty instead of filling it with an assumption.
Make the request explicit
Name the person authorized to decide and the latest useful response time. State what the assistant will do if no response arrives only when a fallback has already been approved.
Use the right communication channel for consequence and confidentiality. A sensitive note should not move to a broad chat merely because chat is faster.
Record the result
After the decision, update the system that owns the calendar, task, message, or approval. The escalation note is evidence of the choice, not always its final operating record.
Align recurring cases with the executive assistant approval matrix so the same boundary does not require fresh interpretation each time.