On-Call Rotation and Escalation Basics

An on-call rotation is a schedule that decides who is responsible for responding to production alerts at any given moment. Instead of "everyone is sort of responsible," one named person owns the pager for a defined window, then it rotates to the next person. An escalation policy is the set of rules for what happens when that person doesn't respond. A normal policy looks like: page the primary, wait a few minutes for an acknowledgement, and if nothing comes back, page the secondary. Still nothing? Page the on-call manager. Why formalize it instead of pinging whoever's around? A few reasons. First, it removes the bystander problem. If you message a busy channel at 3am, everyone assumes someone else has it and nobody picks it up. A rotation makes one person clearly accountable. Second, it removes a single point of failure. People sleep, lose signal, or are mid-flight. The escalation chain guarantees that if the first responder is unreachable, the alert still reaches a human instead of dying silently. Third, it protects people. A defined schedule means you know exactly when you're responsible and when you're truly off. Ad-hoc "just ping someone" means everyone is always a little bit on-call, which burns people out. The one distinction worth knowing on day one: acknowledging an alert means "I've got this, stop escalating." Resolving it means "the problem is actually fixed." New people forget to ack, the system thinks nobody responded, and it escalates to their manager at 3am. Don't be that person.