Source
On-call schedules, rotations & escalation — found from sitemap — PagerDuty
Checked for PagerDuty on 6 Nov 2026
- Page
- https://docs.pagerduty.com/incident-management/schedules/escalation-policies-and-schedules
- Checked
- 6 Nov 2026, 04:48 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c008d2a936b4222731a90f456899b032054a45228cdb976d04969ad7262cc1ea
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy purpose Report an error
“escalation policies allow you to connect services to on-call schedules, and they ensure that the right people are notified at the right time”
-
Free plan schedule limit Report an error
“Free accounts are limited to one schedule and one escalation policy. Other pricing plans do not have a set limit on the number of schedules and escalation policies.”
-
Notification condition Report an error
“Schedule members will receive incident notifications once the schedule is added to an escalation policy, and a service uses that escalation policy.”
-
Schedule single oncall user Report an error
“only one user per schedule can be on call. In other words, you cannot notify multiple users at once using a single schedule.”
-
Schedule layer precedence Report an error
“the lowest layer on a schedule takes precedence over any others”
-
Multiple user notification Report an error
“adding multiple schedules and/or users to an escalation policy is the only way to notify multiple users at once.”
-
Escalation level minimum gap Report an error
“You must have a minimum of five minutes between escalation levels if you have more than one person/schedule in an escalation level.”
-
Deactivate schedule via policy Report an error
“To pause or deactivate notifications from a service connected to a particular schedule, you can change the escalation policy that the service uses.”
-
Oncall shadowing Report an error
“You can achieve this by creating a dedicated shadow schedule, and placing it alongside the primary on-call schedule on the escalation policy.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The ICT Risk Officer On-call schedules, rotations & escalation
- The IT Operations Manager On-call schedules, rotations & escalation
- The MSP NOC Lead On-call schedules, rotations & escalation
- The Skeptic On-call schedules, rotations & escalation
- The SRE Lead On-call schedules, rotations & escalation