PagerDuty.

Where PagerDuty fits on a long engagement.

The mechanics are straightforward; the discipline is not. What decides whether an on-call rotation is sustainable is the proportion of pages that are actionable. A rotation where most alerts are noise trains responders to dismiss them, and the one that mattered is dismissed along with the rest.

Tracking that ratio is the single most useful metric in incident response, and it is rarely measured. Teams measure mean time to resolve, which is a lagging outcome, rather than measuring how many pages should have fired at all.

What an assigned team does with PagerDuty.

Distributed teams change on-call arithmetic. A team spread across time zones can cover more of the clock during working hours, which is materially different from one team carrying nights.

Our delivery sits five hours ahead of Northern Europe, which is part of why the working-hours overlap works the way it does — the reasoning is set out in why we deliver from Thailand.

What we use PagerDuty for.

• Escalation that reaches someone Policies with real fallbacks, so an unacknowledged page does not simply stop.
• Alert noise measured and reduced Tracking what proportion of pages were actionable, which is the number that predicts burnout.
• Timelines for post-incident review An automatic record of what happened when, so review is analysis rather than recollection.

How PagerDuty capacity is assigned.

On-call and incident response arrangements are agreed explicitly at scoping, including which hours are covered by whom, as part of how the monthly fee is built.