Release notes are curated, customer-facing announcements. You pick the changes worth telling customers about, and Specsight drafts them in your product’s voice — you edit before anything goes live. Open Release notes from the project rail.
Digests are the internal counterpart: a complete summary of everything that changed, for your team. Release notes are external and curated — only the changes you choose, written for the people who use your product.
Draft release notes
Open Release notes in the rail, then click New release notes.
- Pick the date range
- Choose which changes to announce
- Say what to emphasise (optional)
- Pick a voice
- Click Generate
The draft is usually ready in under a minute. You also get an email — turn it off with the Release notes draft ready switch in account notifications.
You can also ask Ask Specsight to draft release notes for a date range — it creates a draft here to review, and never publishes.
Edit the draft
The draft opens in a block editor: an Introduction at the top, then sections, each with a heading and a list of entries. Switch between the Edit and Preview tabs to see how it will read. Changes autosave as you type.
Add section and Add entry extend the draft. Enhance on a section rewrites its entries in your product’s voice — leave the box empty for a fresh take, or say what should change.
Voices
A voice tells Specsight how to write — who the notes are for and how they should read. Each project can have up to three; without one, Specsight writes in your product’s default voice. Manage them from Voices on the release notes list (Set voice before you have made one), or from New and Edit in the drafting flow.
- Name — how you pick this voice; the only required field
- Audience — who the notes are for, like non-technical customers
- Tone — how they should read, like warm and plain-spoken
- Sections — fixed headings, one per line; leave it empty and Specsight groups the changes itself
- House rules — instructions Specsight follows exactly in every draft
- Language — the language to write in; defaults to English
Delete a voice and the release notes written with it keep their text — they fall back to your product’s default voice.
Publish
Click Publish. Leave Notify your team on to email members, then confirm. The notes go live at a public link anyone can read — no Specsight account needed. Members get an email unless they turned off Release notes published in their settings.
The Public button shows the live link with a copy control. Unpublish takes the page down — the link stops working until you publish again, and republishing restores the same URL.
Published release notes are read-only: unpublish to edit them again, and unpublish before you can delete a set.
Copy as exports the notes as Markdown, Email-safe HTML, or Plain text — before or after publishing.
Draft from a release
To announce a single release, click Draft release notes on its changelog sync entry or detail page. The same button sits on the Latest release card on the project home and in the sync email. The drafting flow opens with that release’s changes already picked.
Statuses
- Generating — Specsight is writing the draft
- Draft — ready to edit and publish
- Failed — open it to see why, then generate a new one
- Published — live at the public link
If the project is re-analysed after a draft was created, the draft carries a note that the selected changes may no longer match the current spec. Published release notes are never flagged this way.