Write release notes around what changed for the user, who can use it, and what they need to do next. Keep a dated record of notable changes, then turn the relevant entries into a short announcement. A list of internal tasks is raw material, not the finished explanation.
Preparing your first public release? Launch your startup on Maidensail when you are ready to share the product.
Keep the record separate from the announcement
Keep a Changelog describes a changelog as a curated, chronological record of notable changes. Its guidance distinguishes that ongoing record from release notes: an announcement for a single release, drawn from the same material and shaped for its audience.
For a small startup, try keeping one source of truth for what shipped. Include dates and links people can return to. From that record, choose what belongs in an announcement rather than rewriting the history separately for every channel.
An internal cleanup may deserve no public entry if it changes nothing readers need to know. A removed feature, changed workflow, or required upgrade deserves a clear explanation even when it is not exciting marketing news.
Explain the change in the user's terms
For each notable change, answer these questions before writing the final sentence:
- What can someone do now? Describe the action or corrected behavior.
- Who gets it? State plan, device, account, or rollout limits if they apply.
- Where is it? Give the route to the feature or a verified help link.
- Is action required? Say whether users need to change a setting, update software, or move data.
- What remains limited? Mention known limits that affect the promised task.
Do not claim a feature is available to everyone if it is still in a restricted rollout. Verify availability against the release itself, not an earlier roadmap or a draft announcement.
Replace vague praise with a concrete example
Suppose a hypothetical invoicing product adds a date filter to its export screen. An internal note might say, "Export improvements and query refactoring."
A more useful release note could read:
Added a date filter to invoice exports. In Reports, choose a start and end date before downloading the CSV. The filter uses invoice creation dates, not payment dates.
The example tells someone what to try and names a limit. It makes no unsupported claim that the change saves hours or makes reporting twice as fast. Only add performance numbers if you have evidence for the specific comparison.
Make fixes and removals easy to spot
Keep a Changelog groups entries under Added, Changed, Deprecated, Removed, Fixed, and Security. You can borrow those headings when they help readers scan; leave empty headings out.
Use Fixed when the previous behavior was wrong. Use Changed when an intentional behavior now works differently. If something is going away, explain the replacement, timing, and required steps rather than hiding it beneath a general improvement headline. For substantial migration steps, link a separate guide so the announcement stays readable.
Security changes need their own careful communication. Avoid turning a short product update into unreviewed technical disclosure; coordinate the facts and timing with whoever owns the security response.
Check the note against the product
Before publishing, try the described path using an account that matches the intended audience. Confirm the labels, availability, and links. If a change is planned but not shipped, keep it clearly separate from the released items.
Then ask someone unfamiliar with the implementation to read the note. Can they say what changed and what they should do? If not, revise the explanation before adding more detail.
If you are still choosing the work to ship, start with the guide to deciding which feature to build next.
The takeaway
Keep an accurate record, select the changes your readers need, and explain each in terms they can act on. A modest, verifiable announcement is more useful than a polished promise the product cannot yet meet.
Ready to share your product? Launch your startup on Maidensail.
Source note: the changelog distinction and change categories come from Keep a Changelog 2.0.0. The review checklist and invoicing example are suggested exercises, not measured results or claims about Maidensail users.

