Skip to contentComing soon: SprintProof for ChatGPT and Codex

Free template

Release plan and release management template

Plan how a feature gets to users, not only how it gets built. Set the goal, split the work into milestones with ranges, give target dates at three confidence levels, and write down the rollout, the go/no-go checks and the way back before launch week. Plus a release management checklist for the process every release follows.

The CSV has live formulas and opens in Google Sheets, Excel and Notion. No sign-up.

In short

A release plan says how one release gets from done to users: scope, milestones with ranges, target dates at 50, 80 and 90% confidence, rollout steps, go/no-go checks and rollback. A release management template sets the process every release follows: types, calendar, roles, readiness checklist and review.

The template

Eight sections, from goal to rollback.

A release plan is read by engineering, support, docs and whoever is on call. Write each section for the person who will act on it.

release-plan-template.md
blank, with guidance
  1. 01

    Release goal and scope

    What users can do after this ships, what is in, and what was cut.

    • What changes for the user, in one sentence?
    • Which parts are in this release?
    • What is deliberately left for later?

    TipCopy the goal and the not-now list from the PRD, so the release plan never disagrees with it.

  2. 02

    Milestones

    The work in two or three steps that each leave the product working, with a range per step.

    • Which parts are in each milestone?
    • Best, likely and worst case per milestone, and PERT
    • Which milestone holds the riskiest part?

    TipPut the riskiest part in the first milestone. If it slips, you learn early, while there is still time to cut scope.

  3. 03

    Target dates

    The finish date at 50%, 80% and 90% confidence, and what each one is used for.

    • Dev-days and date at each confidence level
    • Which date goes on the roadmap?
    • Which date, if any, is promised outside the team?

    TipPlan around 50%, commit to 80%, promise at 90%. One date gets read as a promise whichever one you meant.

  4. 04

    Rollout steps

    How the audience widens: flag on, internal, design partners, everyone.

    • Who sees it at each step, and from which date?
    • What has to be true to move to the next step?
    • Who decides?

    TipGive every step an exit check. A step with no check is a delay, not a safeguard.

  5. 05

    Go/no-go criteria

    Yes-or-no checks that decide whether the release goes out.

    • Do all the done-when items pass in staging?
    • Are tests, limits and permissions in place?
    • Are open decisions, like billing policy, made?

    TipAgree the criteria before the date is close. Written under pressure, they bend to fit the date.

  6. 06

    Dependencies and comms

    What you need from others and who has to be told: support, docs, sales, customers.

    • Which decisions or work come from other teams?
    • Is support briefed, and is the help article written?
    • When and how are customers told?

    TipSupport hears about a change from customers if nobody tells them first. Brief them before the first outside step.

  7. 07

    Rollback plan

    What you do if the release goes wrong, decided before launch.

    • What sign makes you roll back?
    • Is it a flag switch, a revert or a data fix?
    • What happens to data created while it was on?

    TipIf rollback is not one switch, say so now and move the milestone that makes it hard earlier.

  8. 08

    Owners

    One named person per role, so nobody is guessing who decides during rollout.

    • Release owner
    • Engineering and design
    • Billing, support and docs

    TipOne release owner, not a committee. That person calls go or no-go.

Example

A release plan for team invitations, filled in.

The same feature as the other examples, starting next Monday. Parts grouped into three milestones, with the accept flow first because it is the riskiest.

team-invitations-release-plan.csv
example, filled in
INV · RELEASE PLAN · OWNER MARIA K. · START Team invitations: release plan

1 · Release goal and scope

Admins can bring colleagues into the workspace by email without asking us to add them by hand.

Not in this release: Domain auto-join, SSO and SCIM provisioning, CSV import of invitees.

3 · Target dates

ConfidenceDev-daysDone byUse it for
50%23.5Plan the team around it. Do not promise it.
80%26.6The roadmap date.
90%28.6Outside promises, such as customers.

2 · Milestones, in dev-days

MilestoneParts in itOwnerBestLikelyWorstPERTRunning
M1 Accept flowriskiest firstinvitations table, Invite tokens, Invitations API, Accept-invite page, Existing accounts join directlyKen L.5.58.514.59.09.0
M2 Invite and manageInvite modal, Invite email, Pending invites list, Rate limit invite sendsSam O.3.55.5105.914.9
M3 Rules and testsPermission rules, Seat limit check, TestsJonas T.3.55.595.820.7
Total, before overhead and margin12.519.533.520.7

4 · Rollout steps

  • 1 Feature flag on · Our team onlyMove on when: Invite and accept work end to end in staging
  • 2 Internal · Our own workspacesMove on when: No open bugs on the accept flow
  • 3 Design partners · Five partner workspacesMove on when: Invites arrive and no accepts get stuck
  • 4 Everyone · All workspacesMove on when: Go/no-go criteria met

5 · Go/no-go criteria

  • All done-when items pass in stagingMaria K.Open
  • Tests pass in CI, including invite, accept, first loginLena V.Open
  • Rate limit is on: 20 invites per admin per hourKen L.Open
  • Seat limit policy decided and builtTom A.Open
  • Support briefed and help article publishedSupport leadOpen

6 · Dependencies and comms

  • Seat limit decisionTom A., billing · Wed
  • Support briefing: how to resend or revokeSupport lead · Before step 3
  • Help center articleDocs owner · Before step 4
  • Note to workspace ownersMaria K. · After step 3

7 · Rollback plan

  • Trigger: invites fail to arrive, or accepts fail for more than one person in a day.
  • Action: turn the feature flag off. The invite button and accept page are hidden.
  • Data: pending invites stay in the table and work again when the flag is on.

Decision by Jonas T. Release owner: Maria K. Design: Priya R. Billing: Tom A.

How to use it

How to fill it in, step by step.

A release plan should fit on one page and be read by everyone involved. If it is longer, the milestones are too big.

  1. 01State the goal and the cut line. One sentence on what users get, then what is in and what is out.
  2. 02Group the parts into milestones. Two or three, each shippable behind a flag. Put the riskiest part first and give each milestone a range.
  3. 03Set the dates at 50, 80 and 90%. Take them from your estimate. Decide which one goes on the roadmap and which one you say to customers.
  4. 04Write the rollout and its exit checks. Flag, internal, design partners, everyone. Each step has a check and an owner.
  5. 05Agree go/no-go and rollback early. Do it while nothing is on fire. Mark each criterion Open until someone has checked it.
  6. 06Tell support and docs before step three. Give them the plan, the date and what to say. Update the status column in the weekly check-in.

Release management

Release management template: the process behind every release

A release management template is the reusable document that sets how a team ships every release, from the calendar and roles to the go/no-go rule and the review afterwards. You fill in the process once, then update the calendar and the log for each release.

release-management-template
blank
  • Release typesMajor, minor, patch and hotfix: what each may contain, who approves it and the lead time.
  • Cadence and calendarHow often you release, the freeze rule, blackout dates and every planned release.
  • RolesWho runs the checklist, owns the scope, deploys, tests and gives the final yes.
  • EnvironmentsDevelopment, staging and production: who can deploy, what data each holds, the check before promoting.
  • Readiness checklistYes-or-no lines, each with an owner, that every release has to pass.
  • Go/no-goWhen the decision is made, who attends, the rule, and where it is written down.
  • Deployment and rollbackThe deployment steps, how it rolls out, what triggers a rollback and who decides.
  • CommunicationWhat the team, support, customers and stakeholders need to hear, and when.
  • Post-release reviewWhat shipped against the plan, the target date against the actual date, and what you change next time.
  • Release logEvery release with its version, type, date and result.

Before you ship

Release readiness checklist

Every line has an owner and a yes/no answer. A release ships only when every line is Yes or marked N/A with a reason.

release-readiness-checklist
14 lines
  1. 1Scope is frozen and matches the release planIf scope moves after the freeze, treat it as a sprint scope change: check it against the goal, size it, then swap something out.
  2. 2All items meet their acceptance criteria
  3. 3Automated tests pass in CI
  4. 4Regression tests pass in staging
  5. 5Security review done for new endpoints, permissions and data
  6. 6Database migrations tested, with a written rollback or a forward fix
  7. 7Feature flags set and owners named
  8. 8Monitoring, alerts and dashboards ready for the new parts
  9. 9Performance checked for the parts that could be slow
  10. 10Release notes written and reviewed
  11. 11Help docs and support briefing ready, known issues listed
  12. 12Legal, privacy or store review done (if needed)
  13. 13Rollback plan written and owner on call during release
  14. 14Go/no-go approver has signed off

Once the release is live, write up how it works with the technical documentation template, so the next person reads what was built, not what was planned.

Release plan vs release management

The process stays the same from release to release. Each larger release gets its own plan.

Release planRelease management
ScopeOne releaseAll releases
OwnerFeature ownerRelease manager or engineering lead
LifespanDone when shippedLiving document, updated for every release
ContentsGoal and scope, milestones, target dates, rollout steps, go/no-go criteria, dependencies and comms, rollback plan, ownersRelease types, calendar, roles, environments, readiness checklist, go/no-go, deployment and rollback, communication, post-release review, release log

Skip the blank page

Let SprintProof draft it with you.

Describe the feature and the planner asks the questions a reviewer would, then drafts the brief, done-when, not-now and parts with ranges. The check library adds the edge cases teams usually find mid-sprint.

Turn this into a reviewed plan

FAQ

Release plan questions

What is a release plan?
A release plan says how a feature gets from done to in use: what is in the release, the milestones and target dates, how it rolls out to users, the checks that decide go or no-go, who must be told, and how to roll back.
Which target date should I put on the roadmap?
The 80% date. It leaves a small chance of a miss and is easier to hold than the 50% date, where about half of releases slip. Use 90% for promises to customers, and use 50% only for planning the team’s work.
How do I open the template in Google Sheets, Excel or Notion?
Download the CSV. In Google Sheets choose File, Import, Upload. Excel opens it directly. In Notion choose Import, CSV. The PERT and total columns are formulas, so they update when you change the milestone ranges. Use the Markdown version if you prefer a document.
What is a release management template?
A reusable document that sets how a team ships every release: release types and cadence, a release calendar, roles and approvals, environments, a readiness checklist, go/no-go and rollback rules, communication and a post-release review. You fill in the process once and update the calendar for each release.
What is the difference between release management and a release plan?
Release management is the process every release follows. A release plan applies that process to one release, with its scope, milestones, target dates and rollout steps. Most teams keep one release management document and write a release plan for each larger release.
What should a release readiness checklist include?
Lines with a yes or no answer, each with an owner. Typical lines: scope is frozen, tests pass in CI and staging, security and data checks are done, migrations have a rollback, release notes and support docs are ready, monitoring is in place, and the go/no-go approver has signed off.

Turn this into a reviewed plan with SprintProof.

Describe the feature and SprintProof turns it into a plan: checked against a library of questions reviewers ask, estimated as a range with 50, 80 and 90% dates, and signed off before anyone starts.