Your Runbook Has No Deadlines: Budgeting Every On-Call Step Before the Page Goes Late

Description and use

The article explains adding explicit time budgets to each runbook step to prevent incidents from exceeding SLA limits.

Problem

Runbooks often lack explicit time budgets for each step, causing incidents to overrun their escalation SLAs.

Outcome

Runbooks with explicit time budgets reduce incident duration and align escalation with SLAs.

Workflow

• Define a time budget, stop condition, and timeout action for each runbook step.
• Sum the declared budgets and compare the total plus escalation hold against the SLA.
• If the total exceeds the SLA, adjust budgets or steps before incidents occur.
• Use a validator script to enforce required fields and budget limits.
• Review and argue the budgets in a code‑review style to ensure defensibility.

Evidence

Most runbooks I read fail for a boring reason: nothing in them has a deadline.

Source

Treat each runbook step as a small contract with three fields: a time budget, a stop condition, and a timeout action.

Source

Worst case here is 120 + 90 + 300 + 240 = 750 seconds, which leaves 150 seconds of slack against a 900-second target.

Source

The script is small on purpose: it validates required fields, sums the declared budgets, and refuses to pass when the total plus the escalation hold exceeds the SLA you pass in.

Source