TL;DR / The Direct Answer: When a finding needs to go above your reporting manager, the note must lead with the decision or risk — not the backstory. Use the builder below to draft an escalation email that matches the register your audience expects (RM vs skip-level).
Analyst and consulting teams route findings up a strict chain: reporting manager, then manager, then director. An escalation that uses the wrong tone or buries the ask gets ignored. Pair this with The Executive Summary Translator for the analysis itself and weekly status updates for routine reporting.
Build your escalation prompt
Escalation Note Builder
Plain prompt (copy as-is)
Prompt — Copy into ChatGPT / Claude / Gemini
I need to escalate a finding to my reporting manager. Write a 150-word email that: - Leads with the risk or decision needed (not the backstory) - Includes three bullets: what happened, business impact, what I tried - Ends with one clear ask and a deadline My notes: [PASTE YOUR FINDINGS HERE]
A worked example
Placeholders only. Replace every bracket from your own notes, then remove the brackets before you send.
Sample input
- Issue: a data anomaly or quality issue that affects a leadership decision
- Addressee: direct reporting manager
- What does not match: [metric or file] versus [source]
- Decision blocked: [decision]
- Already checked: [the step you took]
- Need: [decision] by [date]
What good output looks like
- Subject: [metric or file] does not match [source]
- Opening: [the decision or risk, in one sentence]
- What happened: [the mismatch, with no extra figures]
- Impact: [which decision is blocked]
- Already tried: [the step you listed]
- Ask: Please confirm [decision] by [date].
Check before you send
- The first sentence is the decision or risk, not the history.
- If you are writing skip-level, one line says your reporting manager is included.
- No number or name that was not in your notes.
- The ask says what you need and by when.
- The subject names the issue.