How does on-call rotation scheduling work in pagerduty?

Product Analyst

On-call rotation scheduling in PagerDuty is one of its most practically useful features, and understanding how it's structured helps you configure it in a way that's actually fair and functional for your team rather than just technically operational. The fundamental building block is a schedule, which defines who is on-call during which time windows. A schedule in PagerDuty is composed of one or more layers, where each layer represents a set of users and a rotation pattern. The simplest configuration is a single layer with weekly rotations — each person in the layer is on-call for one week at a time, and the rotation cycles through the list automatically. When person A's week ends, the schedule automatically shifts to person B without any manual intervention required. For teams that want more granular coverage — for example, distributing on-call duties by day of week rather than by full week, or separating weekday coverage from weekend coverage — PagerDuty supports multiple layers within a single schedule. You might configure a weekday layer where the on-call responsibility rotates daily among your team, and a separate weekend layer that rotates on a weekly basis, with different people or different rotation periods for each. The layers can also be restricted to specific time windows using the time restrictions feature, so a layer only applies during business hours, or only after midnight, giving you precise control over who is responsible when. Escalation policies are a separate but closely related concept that's worth understanding alongside schedules. An escalation policy defines what happens when an incident isn't acknowledged within a time window. A typical escalation policy might say: notify the current on-call person from Schedule A; if they don't acknowledge within fifteen minutes, notify the engineering manager; if they don't acknowledge in another fifteen minutes, notify the VP of Engineering. Schedules and escalation policies are linked — you attach a schedule to a step in an escalation policy — and the combination gives you both the rotation logic and the fallback logic in one configuration. Override management is particularly important for making on-call rotation sustainable for real teams. When someone is on vacation, traveling, or unavailable during their scheduled on-call week, they can create an override that temporarily assigns their on-call responsibilities to another person for that specific window. Overrides don't change the underlying schedule — when the override period ends, the original rotation resumes — which avoids the messy situation of having to reconfigure the whole schedule every time someone is unavailable. Time zone handling is handled at the user level in PagerDuty, with each team member's notifications going out in their local time, which matters for distributed teams where team members are genuinely spread across multiple time zones. The schedule view itself can be displayed in any time zone, which is useful for managers who need to understand coverage gaps across a globally distributed team. Most of these scheduling features are available across PagerDuty's standard plans, though some of the more advanced scheduling automation features are tier-dependent.