How to Set On-Call Response Times and Backup Expectations
Sources and verification
- Source dates
- Oldest source check: 10 September 2026.
- Technical verification
- Separate technical verification has not been recorded.
Publication approval and technical verification are recorded separately. Automated link checks establish reachability, not accuracy. A checked example verifies only its stated test cases, not the whole article or your production setup.
In short
Define acknowledgement, access to investigation tools and restoration as separate expectations. Set each from service impact and realistic responder availability, then specify when the backup takes over. Agree what the on-call person must carry and where they can reliably respond during a shift. Rehearse an unreachable primary and a primary away from a laptop before committing to a response target.
Key takeaways
- Acknowledgement is taking ownership, not fixing the incident.
- A target must include actual access and a fallback person.
- Measure the full path from detection as well as responder acknowledgement.
Name the clocks
A phone notification, an acknowledgement, a first diagnostic action and a restored service are different events. “Respond in five minutes” is ambiguous unless you say which clock starts and what action stops it.
| Measure | Start | Finish |
|---|---|---|
| Delivery delay | Actionable event detected | Required notification received |
| Acknowledgement delay | Agreed notification or incident timestamp | Responder takes ownership |
| Investigation delay | Ownership accepted | Responder can use required tools |
| Restoration duration | Defined incident start | Agreed service health restored |
Keep the definition beside any metric. A team can acknowledge quickly while losing time to expired VPN access.
Set expectations by impact
Choose the urgent path for conditions where prompt human action can change the outcome. Put nonurgent work into a queue with a different target. Use the escalation policy builder to document who is next and when they take over.
The Google SRE on-call guidance (opens in a new tab) is useful background; it does not set a universal response time for your company. Use your service commitments, failure behavior and staffing to select a target.
Agree the practical shift conditions
Write what the primary needs: a charged phone, required notification settings, laptop availability, connectivity and access credentials. State whether being away from a laptop is compatible with the role and for how long. Agree coverage before a planned period without connectivity rather than discovering it during an incident.
If someone is driving or otherwise cannot safely investigate, the fallback should take over. A phone acknowledgement that leaves everyone believing investigation is underway can be worse than a visible escalation.
Run a tabletop before adopting the target
Use an illustrative service and three cases: the primary is at a desk, away from a laptop, and entirely unreachable. For each, ask who sees the alert, who acknowledges, who investigates and when ownership transfers. Then test device delivery and access in a controlled exercise.
Record where the target failed. If the backup is unavailable for the same reason as the primary, adding another notification to the policy will not solve the coverage problem.
Review the agreement after real shifts
Keep interruptions, access delays and fallback use alongside response metrics. Revisit staffing or coverage hours when the requirement cannot be met sustainably. Record compensation and rest arrangements in your team's policy; this guide does not establish employment or legal requirements.
Use the on-call policy template to make the agreement explicit before the next shift.
Did this help?
Your answer helps us improve this guide. We save only the page and your choice for 30 days.
No name, email, or incident details are requested.
Frequently asked
- Do I have to carry my laptop everywhere?
- That depends on the agreed investigation target and backup arrangement. Make the requirement explicit before the shift; do not rely on an unstated expectation.
- Is acknowledgement the same as resolution?
- No. Acknowledgement records ownership. Resolution requires the defined recovery condition and may take much longer.
Sources
Vendor facts change. Each source below shows the date this page last checked it.
- Being on-call — Google SRE. Checked 10 September 2026.
Related
One practical idea, occasionally
The On-Call Brief: short field notes, templates, and operational lessons.
Follow the field guide
Email subscriptions are not open yet. Read new guides in your feed reader — no email address needed.
Subscribe with RSS