Free, no account needed
Generate an escalation policy, free
When something breaks at 2am, the worst time to decide who gets woken up is in the moment. An escalation policy sets severity levels ahead of time — what counts as critical versus annoying, who owns each level, how fast a response is expected, and the specific trigger that bumps an issue up a level. Describe your team and what actually breaks, and get a policy you can point to instead of relitigating it every incident.
Why
So the worst moment to decide who gets woken up — during an actual incident — isn't the first time anyone thought about it.
What
A severity table (level, owner, response time, trigger) plus a short section on how communication should flow during an active incident.
How
Define severity levels first, then assign an owner and a response-time expectation to each, then write the specific trigger that bumps something up a level.
When
Before the next real incident, ideally right after the last one exposed that nobody agreed on what counted as urgent.
Where
Somewhere reachable at 2am without hunting — pinned in the on-call channel, not three folders deep in a wiki.
No account needed. 3 free generations per day.
Common uses
- Production outages and on-call rotation
- Customer-reported critical bugs
- Security incidents
- Vendor or infrastructure failures