Create an escalation plan for my project with clear triggers and paths
Sets out when and how project issues get escalated, to whom, how fast, and what information goes with them.
The prompt
Create an escalation plan for my project.
Project and governance: [SPONSOR, steering group, project manager, workstream leads]
Tolerances agreed with the sponsor: [e.g. "schedule +/- 2 weeks, budget +/- 5%" or "none set"]
Typical issues so far: [WHAT HAS COME UP]
Teams and vendors involved: [LIST]
Preferred channels: [email / Teams or Slack / meeting]
Build:
1. Escalation levels (usually 3): workstream lead, project manager, sponsor or steering group. For each: who, authority they hold, and expected response time.
2. Triggers for each level, tied to tolerances: e.g. milestone at risk by more than X days, budget variance over Y%, a blocked dependency older than Z days, a quality or compliance issue, a conflict between teams that leads can't settle.
3. Time limits: how long an issue stays at one level before moving up.
4. The escalation format: issue, impact, options, recommendation, decision needed, deadline. Give me a template.
5. Rules for urgent escalation outside the normal path (safety, legal, customer impact).
6. How escalations are logged and closed, and how the team is told the outcome.
Return the plan as a one-page table plus the template, and a 3-sentence explanation I can share with the team so escalation feels normal, not like blame.
If no tolerances are agreed, propose them as [PROPOSED - agree with sponsor].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- SPONSOR, steering group, project manager, workstream leads
- e.g. "schedule +/- 2 weeks, budget +/- 5%" or "none set"
- WHAT HAS COME UP
- LIST
- email / Teams or Slack / meeting
- PROPOSED - agree with sponsor
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Build a plan to reduce patient no-showsA targeted no-show reduction plan based on your appointment data, with reminder cadence, scheduling rules, and a fair missed-appointment policy.
- Build a weekly staff schedule that hits my labor cost targetA forecast-driven front- and back-of-house schedule that controls labor cost and follows break and scheduling rules.
- Audit my CRM data quality and fix the biggest gapsA CRM hygiene audit that finds the data problems hurting forecasting and reporting, with fixes, owners, and rules to prevent them.
- Organize a community cleanup of a river, beach, or parkA plan for a volunteer cleanup: assessment, partners, permissions, safety, the event run sheet, and how to keep it going.