Changelog
Template
A proven structure for writing release notes that customers actually read. Headline-driven, visual-friendly, and designed for skimming.
The anatomy of a great changelog entry
Most changelogs fail because they're written for developers — dense, technical, and buried. This template structures entries for customer skimming, with clear headlines, benefit-focused summaries, and attribution.
Headline
A benefit-focused, customer-facing title. Not 'Refactored API middleware' but 'Pages load twice as fast now.'
Summary (1-2 sentences)
What changed and why it matters to the customer. The 'so what?' in plain language.
Details (bullet points)
What's new, what's improved, what's fixed. Keep it scannable — 2-4 bullets maximum.
Visual (screenshot/GIF)
Show the change. Before/after screenshots are ideal. Short GIFs for interactive features.
Attribution
Who asked for this? 'Requested by 247 customers' or 'Based on your feedback' — this closes the loop and builds trust.
Call to action
What should the customer do? 'Try it now,' 'Update your settings,' or just 'Learn more.'
Pro tips
Write headlines for a busy customer scanning on their phone. If the headline doesn't grab them, they won't read the rest.
Always include a visual. Entries with screenshots or GIFs get 3-4x more engagement than text-only entries.
Attribute features to customer requests whenever possible. 'You asked, we built' is the most powerful phrase in product communication.
Keep entries to 2-4 per release. If you ship 20 things, highlight the 3 most impactful and link to a full list.
Be consistent with cadence. Weekly works best for momentum. A silent changelog for 3 months erodes trust.
Frequently asked questions
How long should a changelog entry be?
2-minute read maximum. Customers scan changelogs — they're not reading a blog post. Headline + summary + visual + 2-3 bullets is the sweet spot.
Should I include bug fixes in the changelog?
Yes — but as a separate section or collapsed list. Highlight the notable fixes that customers have been complaining about. Skip the 'fixed a typo in settings' items.
More free templates
Put the template into practice
FeatureSay gives you all the tools to collect, prioritize, and act on feedback. Free to start.
Get started free