What belongs in each field?
The draft includes only the fields you fill in. Missing information is not filled with guesses. Check the release-note writing guide for a complete example and a pre-publish review.
- Title: the useful result, such as “Save your weekly report view.”
- What changed: the actual new behavior, not an internal ticket name.
- Why it matters: the customer task it helps with. Avoid unmeasured time or revenue claims.
- Audience and availability: the role, plan, platform, or rollout restriction. Do not leave readers to guess.
- Next step: where to find the feature and how to use it.
Review before sharing
Confirm the change is actually available, test the instructions, and remove anything that should remain internal. If a rollout is partial, name that limit. A feature planned for next month belongs on a roadmap rather than in a shipped update.
The download is a Markdown file, so you can use it in your existing publishing workflow. Nothing on this page sends email or posts to a portal.
Connect the release to the people who asked
In BuildCaster, create an update, link the shipped ideas, and review the eligible follower count before publishing. Linked cards then show Announced. Sending follower email is an explicit choice.
Explore the changelog workflow if you want the request, roadmap decision, and published outcome to stay connected. The free builder remains usable on its own.