Planet RoadmapTemplates
Releases
Product Release Notes Template
Communicate new features and fixes to your users with a structured format that prioritizes value over technical jargon.
When to use this template
- •Publishing a major feature release to a public roadmap or feedback portal.
- •Updating internal stakeholders on weekly or bi-weekly sprint progress.
- •Maintaining a historical log of system changes for compliance and security auditing.
How to fill it in
- 1.Categorize each change under Added, Changed, Fixed, Security, Deprecated, or Removed headings.
- 2.Write a benefit-led summary for major features that explains why the user should care.
- 3.Include direct links to updated documentation or help center articles for complex changes.
- 4.Review the tone guide to ensure technical fixes are explained in plain, non-technical language.
Template preview
Added (New Features)
- ·Multi-factor authentication (MFA) via TOTP apps.
- ·Batch export for time tracking logs to CSV and PDF formats.
- ·Custom field support for Kanban board cards and list views.
- ·New 'Sprint Planning' dashboard for Pro tier users.
Fixed (Bug Fixes)
- ·Resolved an issue where Gantt charts didn't render on Safari 14.
- ·Fixed a race condition in the OKR progress calculation engine.
- ·Corrected tooltip positioning on the mobile project dashboard.
- ·Fixed broken pagination on the public feedback portal.
Changed (Improvements)
- ·Updated the navigation sidebar for better screen reader accessibility.
- ·Optimized database queries resulting in 2x faster page loads.
- ·Standardized date formatting across all global project views.
Copy as Markdown
# Release Notes: [Version/Date] ## 📘 Tone Guide - **Lead with Benefit:** Don't just say what changed; say why it helps the user. - **Be Concise:** Use active verbs and skip the fluff. - **Link Everything:** Direct users to [Documentation URL] for new workflows. - **Human Language:** Avoid internal jargon or database table names. --- ## 🟢 Example: The "Good" vs "Bad" ### ✅ The Good Way (Benefit-Led) **Added: Automated Time Reminders** Never miss a log again. You can now set custom desktop notifications to remind your team to submit their hours at the end of the day. ### ❌ The Bad Way (Technical-Led) **Fixed: Cron Job Refactoring** We refactored the background worker responsible for triggering the notification service to reduce latency by 200ms. --- ## 🚀 Added - [Feature Name]: [Brief description of the value provided to the user]. - [Feature Name]: [Brief description of the value provided to the user]. - [Feature Name]: [Brief description of the value provided to the user]. ## 🔄 Changed - [Improvement]: [What is different now compared to the previous version?]. - [Improvement]: [What is different now compared to the previous version?]. ## 🛠️ Fixed - [Bug Description]: [What was broken and is now working correctly]. - [Bug Description]: [What was broken and is now working correctly]. ## 🔒 Security - [Update]: [General description of security hardening or dependency updates]. ## ⚠️ Deprecated - [Feature/API]: [Warning that this functionality will be removed on Date]. ## 🗑️ Removed - [Feature/API]: [What has been officially retired from the product]. --- *Generated via [Planet Roadmap](https://planetroadmap.com) — The flat-rate project management platform.*
Publish these release notes directly to your public portal in Planet Roadmap to keep your 50 free tracked voters informed of every improvement.
Skip copy-paste. Set up this template inside a Planet Roadmap project in one click.
FAQ
Should I include every small bug fix in public release notes?
No. Focus on fixes that were reported by users or those that significantly impact the user experience. Group minor 'behind-the-scenes' fixes into a single 'Performance & Stability' bullet.
How often should we publish release notes?
Match your release cadence. If you ship daily, a weekly summary is usually best. If you ship in sprints, publish notes immediately following the sprint deployment.
What is the difference between 'Deprecated' and 'Removed'?
Deprecated is a warning that a feature is still functional but will be removed soon (giving users time to adapt). Removed means the feature is gone and no longer accessible.
How do I handle security updates without exposing vulnerabilities?
Use general language like 'Improved session handling' or 'Updated encryption protocols' instead of detailing the specific exploit, especially before users have had time to patch.