These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Incident Response Platform
- Features
- On-call coverage
On-call coverage
Plan named responders and escalation levels by service and time.
OverviewOn-call schedule×
Incident Response Platform · On-call coverage
New
On-call schedule
On call shifts
| Name | Starts at | Ends at | Escalation level | Service | Responder | |
|---|---|---|---|---|---|---|
| Shift 639 | 03 Oct | 10 Oct | 260 | SRV-5309 | ||
| Shift 252 | 13 Oct | 17 Oct | 410 | SRV-3659 | ||
| Shift 135 | 10 Oct | 14 Oct | 360 | SRV-8352 | ||
| Shift 918 | 10 Oct | 16 Oct | 820 | SRV-7924 | ||
| Shift 428 | 12 Oct | 17 Oct | 890 | SRV-1313 |
6 of 6 records
Shift 639On call shifts · OCS-36546
Starts at03 Oct
Ends at10 Oct
Escalation level260
ServiceSRV-5309
What you can do
Know who covers the service
Each on-call shift names a service and a responder, with a start, end and escalation level. That gives the Service Manager a concrete coverage plan for a handoff. The schedule can show which person is expected to receive work during a period and where an escalation level applies. The responder can review their own shifts before taking duty.
The shift is a planning record. The incident’s assigned person remains the owner of an actual disruption. When an incident continues beyond the end of a shift, the team should record the new owner on the incident and preserve response events that explain the transfer. A shift change alone does not show who acknowledged the active work.
How the work is organized
- Plan coverage. Enter the service, responder, start and end of each shift so the schedule can be checked before an operating period.
- Review escalation levels. Record the level for each shift and agree how a higher level is contacted when the first responder needs help.
- Handoff active work. Check open incidents and recent response events when the incoming responder takes over.
What to agree during setup
The Service Manager should decide which services need scheduled coverage and who maintains the schedule. Review overlapping and empty periods before relying on the rota. Agree what the escalation level means for each service and how people find the appropriate person after hours. Keep the People records current, especially whether a responder remains active.
If a paging tool is used, its delivery process needs a connection or a team procedure. The shift record supplies a named person and interval; it does not establish that a notification reached them. Use a response event and incident acknowledgment to document what happened after contact.
Check the handoff on an actual case
A service has an evening shift and a following morning shift. An incident opens shortly before the changeover. The first responder records an Acknowledge response event and an investigation update; the Service Manager records the acknowledgment time on the incident. The second responder uses the on-call schedule to confirm coverage, reads the incident update history and accepts the assignment for the remaining investigation. The manager sees the shift plan and the incident owner separately.
If the first responder escalated the issue before leaving, the event should identify who acted and when. The next person can then tell whether escalation was already attempted rather than repeating a page without context. When the service recovers, the assigned responder records the mitigation or resolve event and the Service Manager reviews the incident outcome.
What your team sees
- On-call schedule — Service coverage intervals, responders and escalation levels for planning.
- My on-call shifts — A personal list of assigned coverage periods.
Follow the work through
What it keeps track of
Data model- On call shifts
- Each record is a block of time someone is on call for a service, used to know who to page and when they're covered.
- Services
- Each record is a service the team supports, used to track its importance, health, and who's responsible for it.
- People
- Each record is a team member, used to know their role and whether they're available to respond or be assigned work.
- Incidents
- Each record is a service disruption being tracked, used to see what's broken, who owns it, and how fast it's fixed.
- Response events
- Each record logs one action a responder took during an incident, so the team can trace exactly what happened and when.
Who uses it
Permissions- Service Manager
- , Service Technician
Set up Incident Response Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.