River
Y CombinatorBacked by Y Combinator
Log InStart Free
FREE TEMPLATE

Deployment Process Documentation Template

Four documents and three sheets that compute the block rate at every pipeline stage, so you know which approval actually catches anything.

Edit with AIDownload (.docx + .csv)

Free download  ·  No account needed

What you get

Pack of 7 files: 4 documents, 3 spreadsheets

Deployment Process Documentation Template
  • Environment DefinitionsDocument
  • Pipeline DiagramDocument
  • Release ProcedureDocument
  • Rollback GuideDocument
  • Environment RegisterSpreadsheet
  • Deployment HistorySpreadsheet
  • Approval GatesSpreadsheet
RiverDeployment Process Documentation Template

Approval Gates

Four stages block something. One decides in under a minute and blocks nothing at all

Six months of deployment history joined against the pipeline's own five stages: how many attempts entered each one, and how many it actually blocked.

StageEnteredBlockedRate
Automated Test Suite1,24018715.1%
Staging Smoke Test1,053413.9%
QA Manual Sign-off1,012212.1%
Change Advisory Board99100.0%
Canary Analysis991282.8%

Zero blocked is not the same as clean

The Change Advisory Board approved every one of 991 requests in a median of 47 seconds, and skipped its own rollback-plan check on 21.6% of them.

Thistledown Systems, a subscription billing platform, ran six months of its own deployment history back through its release pipeline's five stages rather than trusting the stage list on its own. Of 1,240 deployment attempts, every automated stage blocked a real, consistent share: 15.1 percent at the automated test suite, 3.9 percent at the staging smoke test, 2.8 percent at canary analysis. Its Change Advisory Board approval, the one human sign-off in the pipeline, blocked zero of 991 requests over the same six months, deciding in a median of 47 seconds.

A zero-block rate alone could mean the gate is simply redundant with the checks around it. Thistledown's own approval charter names a specific, checkable requirement instead: confirm a rollback plan is attached before signing off. 214 of the 991 requests, 21.6 percent, were approved with no plan attached, meaning the one item the approver's own checklist asks for went unchecked on more than one release in five. DORA's 2019 Accelerate State of DevOps Report found this pattern industry-wide: an external approval body carries no measurable gain in stability and a real cost in speed.

The gap is not abstract. Nine of the window's shipped releases needed an actual rollback rather than a forward-fix hotfix. The six with no plan attached took a median of 52 minutes to execute against 11 minutes for the three that had one, a 4.7x difference on the identical operation. That is the change failure rate DORA's own metric guide defines, split by the one variable a pipeline diagram never shows: whether the approval that let the release ship actually checked anything on the way through.

1,240 attempts, one gate that blocks nothing, and a 4.7x gap in rollback time

The stage-by-stage block rate, the Change Advisory Board's own checklist compliance, and what a skipped rollback plan actually costs.

RiverDeployment Process Documentation Template

Thistledown Systems  ·  6 months  ·  1,240 deployment attempts joined against the pipeline's 5 stages

StageTypeEnteredBlockedRate
Automated Test SuiteAutomated1,24018715.1%
Staging Deploy & Smoke TestAutomated1,053413.9%
QA Manual Sign-offHuman1,012212.1%
Change Advisory Board ApprovalHuman99100.0%
Canary AnalysisAutomated991282.8%
Shipped to 100% rollout963——

Four stages block a real, consistent share of what enters them. The Change Advisory Board blocks nothing across 991 requests spanning six months, and decides in a median of 47 seconds, well under the 15-minute automated observation window one stage later.

The Change Advisory Board's own charter, checked against what it actually approved

Requests approved991Median decision time: 47 seconds
Requests blocked00.0% across the full six-month window
Approved with no rollback plan attached21421.6% of everything it signed off

What a missing rollback plan actually costs, measured against the 9 releases that needed one

Rollback plan attached at approval3 releasesMedian 11 min to roll back
No rollback plan attached at approval6 releasesMedian 52 min to roll back
Difference on the identical operation4.7x

34 of the 963 shipped releases, 3.5%, needed a hotfix or rollback within 14 days. 25 were forward-fixed with no rollback needed. Of the 9 that needed one, whether a plan existed before it was needed is the whole difference between 11 minutes and 52.

Edit with AI

What is in the pack

01

Environment Definitions

What each environment in the pipeline is for, who can reach it, and specifically where it differs from production in a way that could hide a real defect.

02

Pipeline Diagram

The stage-by-stage flow of the deployment history with entered, blocked, and block rate at every stage, and the one stage that breaks the pattern.

03

Release Procedure

How a change actually reaches production today, written from the deployment history rather than the aspirational description of the pipeline.

04

Rollback Guide

One entry per rollback mechanism, with its measured duration split by whatever condition the data shows actually changes it, not a single blended estimate.

05

Environment Register

One row per environment: purpose, data source, who can deploy, who can view, and how it differs from production.

06

Deployment History

One row per attempt, with its outcome at every stage and whether it needed a hotfix or rollback afterward.

07

Approval Gates

The computed result: entered, blocked, and block rate at every stage, which is the sheet that turns a diagram into a verdict.

How it works

  1. 1

    Open it in River, or download it

    Edit with AI opens the pack as a private Space with the agent ready to run the joins. Download hands you four Word documents and three CSV sheets, no account needed.

  2. 2

    Send the pipeline configuration and the history

    The CI/CD configuration and as much deployment history as you can export, ideally a few hundred attempts with the outcome recorded at every stage.

  3. 3

    Get the block rate at every stage

    River joins the history against the stage list and computes entered, blocked, and block rate per stage, including whether an approval checklist item was actually satisfied.

  4. 4

    See which gate the post-ship failures would have caught

    Every release that needed a hotfix or rollback gets checked against which stage's scope should have caught it, and which stage actually let it through.

Frequently asked questions

Is this template free?

Yes, and the download needs no account, card or email. Edit with AI is the optional half that runs the joins: reconstructing the deployment history stage by stage, computing the block rate at every gate, and attributing every post-ship failure to what the pipeline missed.

What format are the downloaded files?

Four documents as .docx and three sheets as .csv, in one zip. Word, Pages, Google Docs, Excel, Numbers and Sheets open them with nothing to convert. The sheets carry the worked Thistledown Systems example, so the arithmetic is visible before you replace it with your own.

We already have a deployment runbook template. What does this add?

A runbook tells you what each stage is supposed to do. It has no source for whether any stage actually does it. Thistledown's own Change Advisory Board approval blocked zero of 991 requests over six months and skipped its own rollback-plan requirement on 21.6 percent of what it approved, a fact no runbook's rollback section would ever surface on its own.

Does a zero-block approval stage mean we should just remove it?

Not as the first move. A zero-block human approval usually exists to satisfy an audit or compliance requirement that has nothing to do with catching defects. State plainly what the stage is actually accomplishing, separately from what it is failing to accomplish, and let whoever owns that requirement decide if the first justifies the second.

How is this different from an infrastructure-as-code review, a load test report, or an infrastructure inventory?

Three different questions, not variations on one. An infrastructure-as-code review reads what the Terraform or CloudFormation code provisions, and a load test report reports whether a build met its SLO under load; neither reads the approval step in between. An infrastructure inventory resolves who owns what is currently running, which this pack assumes rather than re-derives.

What catches a problem this pipeline's gates all missed?

Nothing in this pipeline, by design. A stage that was never scoped to catch a category of defect is a different finding from one that fails at its own job, and this pack keeps the two separate rather than blaming the nearest gate. Whether your monitoring would catch either kind after the fact is a separate failure mode analysis.

Sources

  1. dora.dev2019 Accelerate State of DevOps Report (opens in a new tab)
  2. dora.devDORA (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

LinkedInGitHubX

Reviewed by

Brian Joseff, Co-founder, River

LinkedInX

More free templates

Cloud Infrastructure Inventory Template

Free cloud infrastructure inventory template that resolves every owner tag against your current roster and checks the DNS zone for records pointing at nothing.

Cloud Tagging Strategy Template

Free cloud tagging strategy template that measures coverage three ways, computes the allocation ceiling before you set a target, and ranks the gap by cost.

Infrastructure Capacity Planning Template

Free infrastructure capacity planning template: every scaling trigger derived from how long its own action takes, so it fires with time left. Word and CSV.

Analytics Request Intake Template

Free analytics request intake template that prices every recurring question's payback in weeks before deciding whether to build it away.

Find out which gate is real

Edit with AI