Primary vs Secondary On-Call

Roles and responsibilities.

Overview

Primary and secondary roles split on-call responsibility cleanly so the team is not coordinating about coordination during incidents. Without explicit roles, every page becomes a question of who acts.

• Explicit roles. Each role has a written responsibility. Primary leads response; secondary backs them up.
• Primary owns response. Acks the page, runs the investigation, makes the calls. One named owner per incident.
• Secondary as backup. Engages when primary cannot ack within 5 minutes, or when the incident escalates beyond what one engineer can hold.
• Sev-1 secondary auto-engagement. Secondary joins automatically on Sev-1, regardless of whether primary asked for help.

The approach

Three habits make the role split work in practice: explicit responsibilities written down, per-Sev-1 secondary engagement, and a documented hand-off contract.

• Explicit responsibilities. Per-role one paragraph in the on-call playbook. Anything ambiguous is decided ahead of time.
• Primary leads. Acks within 5 minutes, drives the bridge, decides on actions. Secondary does not pre-empt.
• Secondary on Sev-1. Auto-engages on Sev-1 declaration. Below Sev-1, secondary engages only when primary asks.
• Hand-off contract. When primary needs to step away (sleep, food, hand-off at end of shift), the contract specifies how the hand-off happens.

Why this compounds

Each correctly-engaged role preserves response speed and on-call sustainability. The compounding works because the team learns to escalate cleanly rather than reluctantly.

• Faster incident response. Clear roles mean less coordination overhead. MTTR improves measurably on multi-engineer incidents.
• On-call sustainability. Secondary as a real backup reduces primary burnout. Engineers know help is available before they ask.
• Workload-matched policy. Sev-1 auto-engagement, lower severities on request. The policy fits the actual blast-radius of each incident class.
• Year-one investment, year-two habit. The first written policy takes effort. By year two, role engagement is reflexive.