The Operations Bill

Before the detail — Artifact: the coverage attestation, costed. Status of what follows: reusable guidance — no standard prices an on-call rotation for you.

Prompt first: draft the bill, not a total

Here is our coverage decision from Lesson 1.3 [paste: tiers, people
per tier, the contract's 24x7 floor], our rota [paste Lesson 2.3's
shape], our exercise cadence [paste Lesson 6.1's cadence], and our
tooling choice [paste: which license shape, from Lesson 2.2's
table].

Draft a staffing bill with one line per input:
  - rotation seats: people x tiers, under the compensation cap
  - backups: the second person per shift the coverage decision
    requires
  - exercises: hours per cycle, from our cadence
  - communications capacity: who staffs the status page and the
    regulator or agency notifications, and for how long per incident
  - tooling: which license shape carries which obligation, if any -
    never a price; license shapes are Lesson 2.2's table, not this
    lesson's to repeat
  - a vendor's own reporting obligation, if our contract requires
    one, as a cost line, not a footnote

State each line in hours, dollars, or calendar time - never a vague
"more coverage." Where we have no number for a line, write MISSING;
do not estimate one.

The agent can total a spreadsheet; only the risk acceptor who signed 1.3’s coverage attestation knows which line is a contractual floor and which is a nice-to-have, so the prompt asks for MISSING rather than an invented average.

People per tier, under the cap

The bill’s first line is arithmetic on inputs this training already set: 1.3’s coverage decision named the tiers and the health caps a rota has to meet, and 2.3’s rota spaced shifts to keep a person’s on-call load inside them. Price it as seats: people, times tiers, at whatever rate the organization pays for on-call time under the compensation cap — the same cap 1.3 used to size the rota in the first place, because it is a workload limit stated as a pay rule, not two separate numbers.

Understaffing a health cap is a risk a named risk acceptor can choose to carry. Understaffing a contractual floor is not a savings at all — it is unfunded contract risk, realized the first week nobody can name a backup for a tier the contract already promised.

Backups, exercises, and communications capacity

A backup is a second seat, not a spare: 1.3 and 2.3 both size the rota assuming one exists for every primary, and this bill prices that seat at the same rate as the primary it backs up, because an unstaffed backup is an unstaffed tier that has not failed yet.

Exercises are a line, not a rounding error. 6.1’s cadence sets how often a drill runs and, where a federal test cycle applies, how often it must; price the hours a commander pool and a clock-owner roster spend on that cadence the same way payroll prices any other recurring meeting, because an exercise nobody funded is an exercise that gets skipped first when the calendar gets tight.

Communications capacity is the line most bills forget entirely: someone staffs the status page and drafts the regulator or agency notification 4.3 and 4.4 require, for however long an incident runs past the first update. Price it in hours per incident at whatever cadence 4.3 sets, not as a flat retainer that assumes every incident is the same length.

Tooling in three shapes, and the vendor’s own bill

2.2 already laid out the tooling landscape in three license shapes — permissive, copyleft, and open-core — and this lesson does not repeat the names or the table; it prices the shape chosen, because a copyleft dependency and a permissive one carry different obligations long before a subscription invoice exists, and that difference belongs on this bill as a line, not as a surprise a contracts reviewer finds later.

Where Meridian’s federal-facing vendor pursues its own cloud authorization, its own reporting bill rides along: the authorizing program’s Ongoing Authorization Report, as currently proposed, would require the vendor to carry every federal-reportable incident — or a written attestation of none — plus lessons learned and the changes that followed, filed on the program’s own cadence. That obligation sits in the vendor’s contract price, not in Meridian’s rotation bill, and it is cheaper to negotiate before signature than to discover mid-incident that nobody budgeted for it.

What the bill buys

The gap this bill closes is the one 1.1 opened with: only 22% of respondents to the SRE Report 2026 said their organizations model the cost of downtime financially, in ways that inform decisions. That identifies a gap in cost modeling, not proof that every respondent omitted non-production exercises from its staffing bill. A staffing bill that names every line — seats, backups, exercises, comms capacity, tooling shape, vendor obligation — is the artifact that lets a leader compare the cost of running the system against the cost of not running it, instead of discovering the second number during an incident.

Stop and escalate when the bill a service actually needs exceeds what leadership will fund — that is 1.3’s stop exit revisited with a number attached, and only the risk acceptor who can sign a written contractual modification, or accept degraded coverage where no binding floor exists, may choose which line goes unfunded.

Key takeaway

The operations bill prices the staffing this training already decided it needs: rotation seats under the compensation cap, backups, exercise hours, communications capacity, a tooling shape’s obligations, and a vendor’s own reporting duty where one applies — every line in hours, dollars, or calendar time, with MISSING where no honest number exists. It is a staffing bill, never a single product-cost line, and the stop exit that closed 1.3 is the same exit this bill can trigger with a number attached. The training’s capstone turns to running the whole system this module priced, end to end, against one incident.

LEADERSHIP DECISION   fund the staffing bill the coverage decision
                      requires, not just the tooling license
PRACTITIONER ACTION   price every line - seats, backups, exercises,
                      comms capacity, tooling shape, vendor
                      obligation - in hours, dollars, or calendar
                      time, with MISSING where no number exists
SUCCESS MEASURE       contract or revenue risk avoided: zero
                      unstaffed lines against a contractual coverage
                      floor at the next review