# Release Plan Template, Free to Fill

Source: https://nerix.ai/templates/release-plan

Plan a software release: scope, dates, testing, rollout, rollback and who tells whom.

## Fill it in and preview

You are signed in. Fill it in your workspace and it is kept as a document you can send, share and have signed. [Open in your workspace](https://app.nerix.ai/documents/templates/release-plan)

### Release plan

**Product:** TidyPlan mobile app **Release:** 4.2.0 **Release manager:** Hamza Idrissi **Planned date:** 14 March 2029

## 1. Goal

Let households share shopping lists in real time, and fix the three most reported crashes.

## 2. Scope

**Included**

Shared lists with live updates Crash fixes for login and photo upload Updated onboarding screens

**Not included**

Dark mode moves to 4.3.0.

## 3. Schedule

| Milestone | Date |

| Code freeze | 2 March |

| Regression testing | 3 to 7 March |

| Beta to 5 percent of users | 8 March |

| Full rollout | 14 March |

| Review | 21 March |

## 4. Testing and quality gates

The release goes ahead only if these are met.

All automated tests pass. No open critical bugs. Manual test of the 20 key journeys on the 6 main devices.

## 5. Rollout

1. Release to 5 percent for 48 hours 2. If crash rate stays under 0.5 percent, go to 50 percent 3. Release to everyone

## 6. Rollback

Switch the feature off with the remote flag within 15 minutes. If the app itself fails, pause the staged rollout and ship 4.2.1 with the fix.

## 7. Communication

Support gets release notes on 10 March. Customers are told in the app on release day. The team channel gets a status update at each step.

## 8. Risks

Store review may take up to 3 days, so submit by 9 March.

## 9. Success checks

Crash-free sessions above 99.5 percent At least 30 percent of households use shared lists within 4 weeks

**Approved by**

______________________ Date: ____________

Templates are a careful starting point, not legal advice. Where the law matters, check what applies where you are.

IT and projects

## What this template is for

A release plan for shipping software safely. Set scope, schedule, testing, rollout, rollback, communication and success checks. Fill it in, then Word or PDF.

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. [See all IT and projects templates](https://nerix.ai/templates/it-projects)

IT and projects

## What you fill in

The form asks for 14 details. The document fills itself in as you type.

- ### Product For example: TidyPlan mobile app
- ### Release name or version For example: 4.2.0
- ### Release manager For example: Hamza Idrissi
- ### Planned release date For example: 14 March 2029
- ### Goal of the release For example: Let households share shopping lists in real time, and fix the three most reported crashes.
- ### What is included One item per line. For example: Shared lists with live updates Crash fixes for login and photo upload Updated onboarding screens
- ### What is not included (optional) optional For example: Dark mode moves to 4.3.0.
- ### Schedule One row for each milestone. For example: Code freeze | 2 March Regression testing | 3 to 7 March Beta to 5 percent of users | 8 March Full rollout | 14 March Review | 21 March
- ### Testing and quality gates For example: All automated tests pass. No open critical bugs. Manual test of the 20 key journeys on the 6 main devices.
- ### Rollout steps For example: 1. Release to 5 percent for 48 hours 2. If crash rate stays under 0.5 percent, go to 50 percent 3. Release to everyone
- ### Rollback plan For example: Switch the feature off with the remote flag within 15 minutes. If the app itself fails, pause the staged rollout and ship 4.2.1 with the fix.
- ### Communication For example: Support gets release notes on 10 March. Customers are told in the app on release day. The team channel gets a status update at each step.
- ### Risks (optional) optional For example: Store review may take up to 3 days, so submit by 9 March.
- ### How we will know it worked For example: Crash-free sessions above 99.5 percent At least 30 percent of households use shared lists within 4 weeks

IT and projects

## What is inside

The parts of this document, in order.

- 1 1. Goal
- 2 2. Scope
- 3 3. Schedule
- 4 4. Testing and quality gates
- 5 5. Rollout
- 6 6. Rollback
- 7 7. Communication
- 8 8. Risks
- 9 9. Success checks

Templates

## How it works

- 01 ### Fill in Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.
- 02 ### Check Read it through. Gaps you have not filled stay marked, so nothing goes out half done.
- 03 ### Download Save it as a Word document to edit further, or as a PDF to send or print.

### Make it yours with AI

Open it in the chat and ask for changes: shorter, firmer, another situation, another language.

[Adapt it with nerix](https://nerix.ai/try?template=release-plan)

### Was this template helpful?

IT and projects

## Questions people ask

### What details does this template ask for?

The form asks for 14 details, starting with Product, Release name or version, Release manager, Planned release date, Goal of the release. 2 more are optional.

### Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

### Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

### Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

### Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

### Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

Templates

## More in IT and projects

- [API integration specification Specify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it. IT and projects](https://nerix.ai/templates/api-integration-specification)
- [Architecture decision record Record a technical decision with its context, options, reasons and consequences, for the team to find later. IT and projects](https://nerix.ai/templates/architecture-decision-record)
- [Bring your own device policy Set the rules for using personal phones and laptops for work: security, privacy, support and leaving. IT and projects](https://nerix.ai/templates/byod-policy)
- [Bug report Report a software problem so a developer can repeat it, judge its impact and fix it. IT and projects](https://nerix.ai/templates/bug-report)
- [Change management plan Plan how people will be told, trained and supported through a big change, and how you will know it worked. IT and projects](https://nerix.ai/templates/change-management-plan)
- [Change request Ask for a change to a project or system, show its impact and record whether it is approved. IT and projects](https://nerix.ai/templates/change-request)

[See all IT and projects templates](https://nerix.ai/templates/it-projects)

Templates

## More kinds of documents

Every category has its own page, so you can see all of its templates at once.

## Use it in nerix

### Use it in nerix

- [Templates](https://nerix.ai/product/templates)
- [Long tasks](https://nerix.ai/product/tasks)
- [Long documents](https://nerix.ai/product/long-documents)

### Learn more

- [How to Make a Document From a Template](https://nerix.ai/help/make-a-document-from-a-template)
- [IT and projects](https://nerix.ai/templates/it-projects)
