<!-- Release plan · from Chapter 06 of The Product 360 Handbook -->

# Release plan · [Release name] · [Date]

**Outcome:** [What changes for customers]   **PM:** [ ]   **Engineering lead:** [ ]   **Date range:** [earliest to latest] at [confidence]

## Scope
In: [ ]   Out: [ ]   Scope lever if the date is at risk: [ ]

## Flags
| Flag | Type (release / experiment / ops / permissioning) | Owner | Removal task | Expiry |
|---|---|---|---|---|
| | | | | |

## Rollout stages
| Stage | Who sees it | Entry criteria | Exit criteria | Earliest date |
|---|---|---|---|---|
| Internal | [ ] | | | |
| Design partners | [ ] | | | |
| Opt-in beta | [ ] | | | |
| Cohort or percentage | [ ] | | | |
| General availability | [ ] | | | |
| Regions held back | [ ] and why | | | |

## Exit criteria metrics
Error rate: [ ]   Latency: [ ]   Acceptance or adoption metric: [ ]   Support tickets: [ ]   Change fail rate: [ ]

## Kill switch and rollback
Kill-switch owner: [name, role]   Rollback plan: [ ]   Rehearsed on: [date]

## Customer communications
Release notes: [ ]   Admin notices: [ ]   Deprecation notices: [ ]   Status page: [ ]

## Enablement
Support: [ ]   Sales: [ ]   Partners: [ ]   Customer success: [ ]

## Compliance artifacts
[Security documentation, AI documentation, data processing terms, as applicable]

## Decision log
| Date | Decision | Made by | Reason |
|---|---|---|---|
| | | | |