Choose an on-call schedule by matching coverage to the service’s real response needs, then check that the resulting workload is sustainable and fairly shared. There is no universally correct rotation size or shift length: the right design depends on urgency, operating hours, team size, locations, page volume, and how people recover after overnight incidents.
Start with the service’s response target
Set the response expectation from the impact of an incident, not from a convenient rota. Google’s Being On-Call chapter uses five-minute response for highly time-critical services and 30 minutes for less time-sensitive systems as examples. They are illustrations, not mandatory standards. Decide what harm a delayed response could cause, when coverage is required, and what a responder must do after receiving a page.
As an Amazon Associate I earn from qualifying purchases.
- Page for conditions that require prompt human action and are tied to service impact.
- Send non-urgent work through a lower-priority channel so it does not interrupt sleep or focused work.
- Define acknowledgement and escalation expectations, including what happens if the primary does not respond in time.
Choose a rotation that fits the team you actually have
Published staffing figures are useful for testing assumptions, not as universal minimums. Google’s SRE book derives eight engineers for a single-site, 24/7 rotation with two people on call, week-long shifts, and the time allocation in its operating model. A separate Google Cloud article gives six as a rule of thumb for staffing a pager rotation without burnout. These numbers come from different descriptions and assumptions; neither guarantees that a team of that size will be sustainable.
Google’s SRE model also aims for at least 50% of time invested in engineering and no more than 25% spent on call. Those are organizational targets for that model, not cross-industry measurements or a prescription for every small team. The book uses an average of six hours of incident work—including root-cause analysis, remediation, and follow-up—in its workload reasoning; do not treat that as an industry-wide incident average.
#1 Best Overall
- Team Collaboration: you will receive 1 pcs project management planner ; Streamline office workflow using this professional project management board; Ideal for agile teams to visualize tasks and assignments at a glance; It minimizes communication gaps, ensuring members remain aligned with goals to drive operational excellence
- Optimized Size: the 24 x 36 inch project board chart dimensions strike the ideal balance between ample writing space and compact footprint; Large enough to display complex project workflows, and sprint planning details for team visibility, yet sized to fit comfortably in standard conference rooms, huddle spaces, and home offices without overwhelming the area
- Easy Erase Surface: experience smooth writing on this lined white board dry erase surface; Lamination ensures clear writing and effortless cleaning; Each erasure leaves a fresh, clean slate ready for your next brainstorming session or project update
- Deadline Tracking: maintain strict schedules using the structured lined project white board; Dedicated sections for names and dates prevent oversight of critical items; This intuitive design helps managers identify bottlenecks early, ensuring every deadline is met consistently
- Space-saving Setup: maximize vertical space with this project white board for wall; Designed for easy mounting on any flat surface, it keeps key objectives front and center; Ideal for small offices, ensuring project tracking remains a constant, visible part of the daily environment
| Reference | What it says | How to use it |
|---|---|---|
| Google SRE, Being On-Call | Eight engineers derived for a single-site, 24/7 rotation with two people on call, week-long shifts, and the book’s stated time-allocation assumptions. | Use as a model-specific calculation; change the assumptions to reflect your service and staffing. |
| Google Cloud, Why should your app get SRE support? | Six engineers described as a rule of thumb for a pager rotation without burnout. | Use as a rule of thumb, not a guarantee or a formal minimum. |
Before choosing a pattern, estimate how often each person will be primary and secondary, how many nights or weekends each shift includes, and how much incident and follow-up work lands on the person carrying the pager. A small team may need to reduce the service’s coverage promise, share coverage with a related team, add people, or change the service’s operational design rather than simply compress shifts.
Set shift length and recovery rules
Week-long shifts are one example in Google’s SRE material, not a default that every team should adopt. Longer shifts mean fewer handoffs but keep one person responsible for more consecutive days; shorter shifts spread duty differently and create more transitions. Compare the practical burden of each pattern against actual interruptions and coverage needs.
- Define when a person is considered available for engineering work while on call; do not assume they can work uninterrupted on project tasks.
- Agree on recovery time after a disruptive overnight incident, including whether the person can hand off or step away from normal work.
- Review shift transitions so unresolved incidents and relevant context are explicitly handed over rather than left to the next person to rediscover.
Make primary, secondary, and escalation duties explicit
A primary is generally the first responder, but the secondary role can serve different purposes. Google’s SRE guidance describes secondary coverage as fall-through for missed pages, support for non-urgent production work, or in some cases coverage from a related team. Select the arrangement that covers your likely failure modes instead of assigning a secondary without defining the job.
Recommended Free Tools
- State who acknowledges urgent pages and what acknowledgement window applies.
- Specify when the secondary is paged—for example, when the primary misses an acknowledgement or asks for help.
- Set escalation contacts and steps for incidents the rotation cannot resolve alone.
- Document how non-urgent production requests are triaged and who owns them.
Formal incident-management procedures and escalation paths can make on-call more manageable. Keep the procedure accessible to whoever is carrying the pager, and make handoff responsibilities clear at the start and end of every shift.
Rank #3
- MAGNETIC DRY-ERASE SURFACE — The whiteboard design is permanently printed onto durable, industrial‑quality dry‑erase vinyl that won’t smudge and is resistant to stains and ghosting. Its smooth, long‑lasting writing surface is also magnetic, giving you added functionality for notes, magnets, and accessories
- EASY INSTALLATION — Comes complete with durable mounting brackets and hardware, ensuring a secure and effortless wall‑mounting
- DURABLE ALUMINUM FRAME — Built with a sleek 1" aluminum border and a spacious 2.5" deep aluminum tray to keep markers and accessories neatly within reach
- SPACIOUS WRITING SURFACE — Ample writing space with a usable area that extends nearly edge‑to‑edge, measuring just 2" shy of the board’s total dimensions
- Please inspect your whiteboard upon arrival — If you notice any issues, please contact us through Amazon's Buyer-Seller Messaging system
Build fairness and availability into the calendar
A rota is workable only if it reflects people’s real calendars and constraints. Decide how to handle leave, swaps, weekday and weekend distribution, personal preferences, and religious requirements before publishing the schedule. Document who approves a swap and how replacement coverage is confirmed, so an informal change does not leave a gap.
If the team spans locations or time zones, that may reduce the amount of night work for individuals, but it can also add coordination overhead. Assess both effects in the context of your incident handoffs and escalation path; location alone does not guarantee continuous or reliable coverage.
Rank #4
- DRY ERASE PROJECT MANAGEMENT PLANNER: Be made of 250 gsm construction paper, laminated by special formula film that is erasable, make the surface resistant to ghosting or staining. We can erase easily even months later and use this work schedule board over and over again
- PRODUCTIVE PROJECT MANAGEMENT TOOLS: This project management board is a game changer and something physical for managing personal or team projects efficiently. It allows you or members to quickly view and share the status of up to 12 projects at the same time, a very good practical kit of team building
- SCRUM WHITEBOARD FOR OFFICE ESSENTIALS: This project organizer worth the investment for business use. It's easy to use for products development, marketing strategic projects or as a sales goal tracking whiteboard. You can easily measure budget, milestones, resources, inventory and timeline at a glance. It helps you plan, execute, assign tasks efficiently
- MOUNTING IS A BREEZE: This vision board is lightweight and comes with removable mounting stickers. You can mount this program Management Board easily without tools. On the other hand, you can take it down easily too if you need to remount your project board to other place later
- COMPLETE ACCESSORIES INCLUDED: Our huge project manager planner for wall is cost-efficient for daily use in office, home office or family. It comes rolled in a study tube with, premium dry erase eraser, reusable fluorescent colored tabs for entrepreneurs, managers or person working at home
Use incident load to improve the schedule—and the service
Track pages and interruptions per shift, time spent investigating and resolving incidents, recurring problems, and follow-up work. If the same alerts repeatedly consume on-call time, changing the rota alone will not solve the cause. Google’s SRE chapter warns: “Low-priority alerts that bother the on-call engineer every hour (or more frequently) disrupt productivity, and the fatigue such alerts induce can also cause serious alerts to be treated with less attention than necessary.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Review whether each alert merits an urgent interruption, group duplicates, and assign corrective work for recurring or noisy conditions. Google’s Alerting on SLOs workbook describes silencing known alerts for a limited duration and creating tracking tickets for issues that cannot be fixed quickly. Treat silencing as a temporary control with an owner and follow-up, not as a substitute for repairing the underlying problem.
Best Value
- MAGNETIC DRY-ERASE SURFACE — The whiteboard design is permanently printed onto durable, industrial‑quality dry‑erase vinyl that won’t smudge and is resistant to stains and ghosting. Its smooth, long‑lasting writing surface is also magnetic, giving you added functionality for notes, magnets, and accessories
- EASY INSTALLATION — Comes complete with durable mounting brackets and hardware, ensuring a secure and effortless wall‑mounting
- DURABLE ALUMINUM FRAME — Built with a sleek 1" aluminum border and a spacious 2.5" deep aluminum tray to keep markers and accessories neatly within reach
- SPACIOUS WRITING SURFACE — Ample writing space with a usable area that extends nearly edge‑to‑edge, measuring just 2" shy of the board’s total dimensions
- Please inspect your whiteboard upon arrival — If you notice any issues, please contact us through Amazon's Buyer-Seller Messaging system
A practical decision sequence
- Define coverage: write down the hours that need coverage, the service impact of delayed action, and the response target for urgent alerts.
- Assign roles: decide what primary and secondary do, when the secondary is engaged, and how escalation works.
- Model the rota: compare realistic shift lengths and rotation sizes against available staff, weekend distribution, absences, and expected page burden.
- Agree on recovery and swaps: establish post-incident rest expectations, handoffs, leave coverage, and a confirmed swap process.
- Measure and adjust: review actual interruptions and incident work, tune alerting, and revisit the rota when workload or service needs change.
Local labor requirements, compensation, and employment policies are not determined by these operational examples; address them with the appropriate local guidance before publishing a schedule.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
