A runbook is not a live escalation path
Escalation procedures often read as complete: tiers named, SLAs listed, a chart with arrows. Diligence fails when nobody can show who answered the last Sev-1 at 02:00, or why a payment dispute bounced between fraud and support for two days.
In escalation procedure audits we score operating effectiveness separately from document design. A dated ticket trail with named owners beats a polished PDF that never survived a real overnight incident.
Assign a fallback contact and a retention path for each severity before the next assurance cycle. Runbooks stay useful; live paths keep them honest.