Engineering On-Call Rotation

A fair on-call rota with clear escalation, runbooks for every page, alerts worth waking up for, handovers that stick and real support for the engineers and managers carrying the pager.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engineering On-Call Rotation, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Engineering On-Call Rotation

Running a fair on-call schedule with runbooks, escalation paths, sensible alerting and support for the people woken up at night.

  1. Service ownership map for paging
  2. First fair primary and secondary rota
  3. Severity levels and escalation policy
  4. Paging tool set-up and contact test
  5. On-call handbook for responders
  6. Baseline of current paging load
  7. Runbooks for the ten most frequent alerts
  8. On-call pay and time-off policy
  9. Production access readiness for responders
  10. Monday on-call handover routine
  11. Weekly alert review meeting
  12. Monthly paging load report
  13. Quarterly rotation fairness audit
  14. Shift log kept during every shift
  15. Monthly runbook freshness check
  16. Shift swaps and holiday cover process
  17. Monthly paging and escalation drill
  18. Interrupt queue triage during the shift
  19. Shadow and reverse-shadow shifts for new responders
  20. Incident commander role training
  21. First fifteen minutes triage practice
  22. Stakeholder updates during live incidents
  23. Quarterly on-call game day
  24. Safe mitigation moves every responder knows
  25. Handling pages for unfamiliar services
  26. Noisy alert clean-up campaign
  27. Paging on user impact, not on causes
  28. Choosing a paging and scheduling tool
  29. Follow-the-sun or single-timezone cover
  30. Shift length and pattern decision
  31. Routing non-urgent alerts to working hours
  32. Alert grouping and deduplication rules
  33. Auto-remediation for repeat pages
  34. Your first solo week as primary
  35. Peak season and launch cover plan
  36. Holiday period on-call rota
  37. Annual on-call health survey
  38. Six-month rotation retrospective
  39. On-call for a team of three or four
  40. On-call around parenting and caring duties
  41. Supporting responders as a manager
  42. Bringing an inherited service into rotation
  43. Founder as the only on-call engineer
  44. Rest after a rough night
  45. Tiered support and engineering escalation
  46. Contractual response times and on-call evidence
  47. On-call measures dashboard
  48. Vendor and cloud provider escalation contacts
  49. Platform versus product team on-call model
  50. Working-time rules and on-call compliance

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Service ownership map for paging

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Pages go to the wrong person when nobody has written down which team owns which service, queue, cron job and third-party integration. A single table that lists every production component, its owning team and the rotation that gets paged for it ends the 3 a.m. guessing game.

First tasks

  • Export the list of services and scheduled jobs from your deployment platform
  • Add an owning team and paging rotation column to every row
  • Raise each unowned component with the engineering manager by name
  • Link the finished map from the paging tool's service descriptions

First fair primary and secondary rota

A rota that lives in one person's head, or that quietly leans on the two engineers who never say no, burns people out within a quarter. Writing a schedule with a primary and a secondary, equal shift counts and a published calendar makes the load visible and shareable. Aim for at least five or six people per rotation so nobody is on more than one week in five or six.

First tasks

  • List every engineer eligible for on-call and note any agreed exclusions
  • Choose the shift length and the weekday and hour of handover
  • Build twelve weeks of primary and secondary shifts in the paging tool
  • Ask each responder to confirm their dates and flag clashes within a week

Severity levels and escalation policy

When a page is not acknowledged, or the responder is out of their depth, the next step should be automatic rather than a frantic search through chat for someone awake. A short severity scale with response expectations, plus an escalation chain from primary to secondary to manager, removes that decision from the worst moment. Keep it to three or four levels people can recite.

First tasks

  • Draft three or four severity levels with one real past incident as an example for each
  • Set an acknowledgement timeout before a page escalates to the secondary
  • Name the manager or lead who sits at the end of the escalation chain
  • Ask a second engineer to compare the written policy with the tool settings

Make it yours.

Install Engineering On-Call Rotation, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.