Escalations go sideways when they’re late, vague, or framed as emergencies. Use this pattern to raise risks early and keep everyone calm.

## Lead with impact, not drama

- Pattern: `Impact: ___ | Scope: ___ | Time: ___`
- Example: `Impact: Checkout failures at 4% of EU traffic. Scope: web only. Time: started 11:20 UTC.`

## Offer options, not just problems

- Pattern: `Option A ___ (risk ___) | Option B ___ (risk ___)`
- Example: `Option A: Rollback 1.14 now (risk: partner API lag). Option B: Patch in place (risk: 2h to validate).`

## Assign owners and clocks

- Pattern: `Owner: ___ | Next update: ___ | Decision by: ___`
- Example: `Owner: @Mara. Next update: 14:00. Decision by: 14:15.`

## Keep the thread short and factual

- One message per update: impact, option chosen, evidence link, next check-in.
- Link graphs/logs instead of screenshots.
- Avoid “checking in?” replies; use reactions for acknowledgment.

## Close the loop

- Pattern: `Resolved: ___ | Outcome: ___ | Follow-ups: ___ (owner, due)`
- Example: `Resolved: rolled back 1.14. Outcome: errors back to baseline. Follow-ups: add synthetic EU check (Alex, Fri).`

Early, structured escalations reduce downtime and stress. Paste the patterns above and run `/clr` to tighten before sending.

Shorter Slack updates with Clear.