Write a changelog and email subscribers

A changelog is a clear, honest record of what changed. Describe the change in plain language and explain why it matters to users. If useful, briefly share why you made the change. Keep entries factual and clear rather than promotional, and write them so they make sense to someone reading without context months later.

Write your changelog content in plain language and choose Enhance with AI. AI can organize notes into sections, polish phrasing, maintain a consistent tone, and preserve your original meaning. Review the result: AI assists with clarity and does not replace your judgment. Avoid asking it to invent features, motivations, or strategy, add hype, or explain decisions you do not want to share publicly.

In the publish panel, open Customize email and choose Auto-fill to draft the subject, inbox preview text, and introduction. Edit any of these before sending.

In the publish panel, Recipients includes all subscribers by default. Narrow delivery to one or more contact groups, or select people individually. Contact groups come from Contacts, where you can import a CSV with a group column. Send Test Email sends a preview to your own address only; Save for later keeps the entry as a draft. The panel shows the subscriber count and your plan’s email limit. If the recipient list exceeds the limit, the entry still publishes but no email is sent. Narrow recipients to fit the limit or upgrade before publishing if email delivery is needed.

Choose Keep it off the board for updates intended for a smaller audience, such as beta testers. The entry stays off the Changelogs tab and out of search, but anyone with its link can open it. If your board is connected to Discord and you have selected a changelog channel, Post to #channel on Discord appears; featurevote posts the entry there once. Published entries appear on the Changelogs tab, which appears after your first published entry. Visitors can react to published entries without logging in.