Issue Escalation Path
Know when and how to escalate.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design an escalation path. Project structure and governance: [GOVERNANCE]. Types of issues that occur: [ISSUE_TYPES]. Decision makers: [DECISION_MAKERS]. Produce: 1. Severity definitions (critical, high, medium, low), each with an example from my project type and a response time. 2. The ladder as a table: Level | Who | Trigger | Maximum time before escalating | What they must bring. Include a rule for when the next level is unavailable (named deputy, then skip a level). 3. The information an escalation must contain: what happened, impact, options, recommendation, and decision needed by when. 4. An issue log template with columns ID | Description | Severity | Owner | Raised | Due | Status | Resolution. 5. A decision tree for deciding whether to escalate. 6. An example escalation message of about 120 words for a supplier delay, using placeholders. Rules: bring options, not just problems; escalate early when the issue touches the critical path; record decisions. Finish with five retrospective questions to improve the path.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.