# Release Note Brief

Communicate what changed, who is affected, availability, setup, migration, limitations, known issues, support, rollback, and next steps.

## Usage note

Write from the released build and approved rollout plan. Do not announce a feature as available to everyone when access, plan, region, platform, migration, or rollout stage limits it.

## How to use this template

1. Confirm released behavior, prior behavior, affected users, version, dates, and rollout source.
2. Define user value, availability, prerequisites, migration, limitations, and known issues.
3. Assign product, engineering, support, policy, accessibility, and localization reviews.
4. Draft and test the note, detailed help, links, screenshots, and cross-channel wording.
5. Publish a versioned record and update it as rollout, issues, or availability changes.

## Blank template

### Release facts

- **Release name and identifier:** [Enter]
- **Released build/source:** [Enter]
- **Prior behavior:** [Describe]
- **New or changed behavior:** [Describe]
- **Change type:** [Feature / Improvement / Fix / Deprecation / Migration]
- **Affected users:** [Role/plan/region/platform]
- **Unaffected users:** [Enter]
- **Dates and rollout stages:** [Enter]

### User impact

- **Problem or task improved:** [Evidence]
- **What user can do now:** [Enter]
- **Action required:** [Enter or None]
- **Prerequisites:** [List]
- **Compatibility and data impact:** [Enter]
- **Reversal or fallback:** [Enter]
- **Known limitations:** [List]
- **Known issues and status:** [List]

### Content and support plan

- **Release-note opening:** [Write direct summary]
- **Setup or migration guide:** [Verified route]
- **Support and escalation:** [Enter]
- **Screenshots, commands, labels:** [List]
- **In-product and email messages:** [References]
- **Privacy/security/legal review:** [Status]
- **Localization source-lock and locales:** [Enter]
- **Claims requiring evidence:** [List]

### QA and maintenance

- [ ] Availability matches plan, region, platform, and rollout.
- [ ] Instructions were tested in the released build.
- [ ] Limitations and known issues are visible.
- [ ] Cross-channel dates, names, and status agree.
- [ ] Help and support teams received the final record.
- **Final reviewers and version:** [Enter]
- **Rollout monitoring:** [Errors/access/support]
- **Update owner and trigger:** [Enter]