Set severity levels and escalation paths for operational problems
A clear severity matrix with response times, who to call, and when to escalate, so problems reach the right person fast.
The prompt
Help me create a severity and escalation matrix for operational problems in my area.
Operation: [WHAT WE DO - e.g. "regional distribution center", "field service team", "back-office claims processing"]
Types of problems we hit: [e.g. equipment failure, system outage, missed shipments, staffing gaps, safety events, customer complaints]
What we measure impact by: [e.g. orders delayed, customers affected, revenue at risk, safety, regulatory exposure]
People and roles available: [supervisors, on-call manager, maintenance, IT, site leader, executive]
Hours of operation and on-call setup: [DETAILS]
Build:
1. Severity levels (3-4), each with a plain definition and concrete examples from my operation, so two people would classify the same problem the same way.
2. A matrix: severity | who must be told | how (call, text, ticket) | within how long | who leads the response | update frequency.
3. Triggers to escalate up a level (e.g. not resolved within X, impact grows, safety involved) and to downgrade.
4. A short "what to include when you escalate" template.
5. Common failure modes to avoid (silent escalation, everyone gets paged, nobody owns it) and how this design prevents them.
Safety incidents should always follow our legal reporting duties and safety policy; mark where those apply with [CHECK SAFETY POLICY].
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
- DETAILS
- CHECK SAFETY POLICY
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
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.
- Map my process step by step and find the wasteBreaks a workflow into steps and flags waste: duplicate work, unnecessary handoffs, waiting, rework, and steps that add no customer value.
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.
- Create a tagging taxonomy so our team's documents are easy to findDesigns categories, tags, synonyms, and required metadata so people can find documents in SharePoint, Confluence, Notion, or a shared drive.