Skip to content
Owner: @lop • live

Transition operating promises

These templates keep transition approvals, escalations, and cadences explicit. Codify your operating promises or Browse the runbooks index. Pair them with the Handover RACI template so every role knows the service level they own during a transition.

Approvals template

Fill this table before the handover call so nobody waits for ad-hoc green lights.

ConditionActionPrimary ownerTime box / SLABackup
Scope change increases effort by >1 sprintRevalidate scope, align on tradeoffs, capture delta in ledgerTransition decider (Product lead)2 business daysEngineering lead
New risk rated Sev-2+ surfacesTriage with receiving team, confirm mitigation owner, update stop ruleFacilitatorSame dayOn-call EM
Resource gap longer than 3 business daysTrigger staffing request, pause handover until backfill is confirmedDelivery lead24 hoursProgram manager
Policy questions outside Band AEscalate to governance owners, log answer in FAQDoc steward48 hoursGovernance backup

Escalation path

When a promise is violated, the on-call should know exactly who to page.

BreachFirst escalationSecond escalationAuto-stop rule
SLA missed by >24hDelivery lead pings facilitator + owning leadProgram sponsorPause transition until next review
Risk not acknowledged in 48hFacilitator pings governance ownerVP sponsorStrip scope to minimum viable handover

Status cadence

SignalAudienceChannelOwnerNotes
Daily checkpoint (10 min)Core transition teamAsync thread with templateFacilitatorShare blockers + highlight upcoming promises
Weekly executive updateSponsors + partner teamsSnapshot doc + link to receiptsProgram managerInclude SLA/RACI deltas + next focus
Release-ready reviewQA, doc steward, product leadLive call + notesQA leadRun Quick-Run

Communication promises

  • Everyone gets the same story — Publish the status snapshot in the same doc you use for RACI, never in DMs.
  • Receipts or it didn’t happen — Every action item references a runbook section or screenshot.
  • “Stop the line” stays literal — Anyone can pause the transition if a promise is at risk; log the pause in the transition doc.

After the handover

  1. Archive the fulfilled promises in the State ledger with the release tag.
  2. Update the Fast support index if new interrupts surfaced during the transition.
  3. Review this page every 6 months—promises that no one owns should be removed or reassigned.

Text © CC BY-NC 4.0 • Code samples MIT • Views are my own.