Free tool
Feature Request Template: Free Builder and Examples
Write a feature request with a clear problem, desired outcome and supporting evidence. Copy the blank template or edit the builder and download your request as a text file. No account is needed to use the builder.
Copy a blank feature request template
Use one request for one distinct customer need. A title should make the task recognizable, while the description explains who is trying to do it and what gets in the way. If a detail is unknown, say so. Keep your suggested implementation separate from the result you need so the reviewer can consider other ways to help.
Title: [Task or improvement needed] Audience and situation: [Who needs this; when the task occurs] Problem: [Current obstacle; a recent example] Current workaround: [What happens today; remaining limitation] Desired outcome: [Observable result that would help] Suggested solution, if any: [Proposal, not agreed scope] Evidence: [Source references; distinct people/accounts; estimates labelled] Open question: [Missing detail that changes the next review step]
Example: describe the task behind the feature
This fictional request concerns an imaginary reporting product. “Add scheduled reports” names a feature but leaves several possible problems open. The customer may need to avoid repeated setup, remember a deadline or deliver output automatically. This example identifies repeated setup while keeping manual review as part of the desired workflow.
Title: Reuse report settings for the Monday review Audience and situation: An administrator prepares a team report each Monday. Problem: The administrator recreates the same team and date filters before every review. Current workaround: Rebuild the settings, download the file, check it and send it with commentary. Time spent has not been measured. Desired outcome: Reopen the intended settings and review the output before sharing it. Suggested solution: Saved report settings; suitability still needs checking. Evidence: One fictional customer conversation. No measured account or demand count. Open question: Can current settings already support this task?
The request is ready for a focused investigation, even though reach and implementation cost remain unknown. A reviewer can check existing behavior before proposing new scope. One clear example supports understanding this task; it does not prove that most customers need the same change or that the suggested solution should be prioritized.
How to write the problem, outcome and evidence
In the Problem field, describe the present obstacle and context. “I rebuild the same filters before the weekly review” is more informative than “reporting is bad.” Include the role and current workaround here if they matter. In Desired outcome, describe what the person needs to accomplish; use a separate sentence for a suggested feature rather than presenting it as an agreed requirement.
In Evidence, retain the original source or a safe summary. Distinguish messages from people and accounts: three messages from one account are not three independent customer requests. Label estimated frequency or effort, and avoid inserting a precise saving you have not measured. The fictional starting text in the builder is an example to replace before use.
If the request only names a feature, ask about the last time the customer tried the task. Use the feature request clarification questions and reply template to choose a focused follow-up and record the answer. Clarifying the need is a review step; it does not commit the team to building it.
Copy, download or share your request
Copy the completed builder text for your document or request system, or select Download for a plain-text file. This tool formats your input; it does not verify evidence, estimate effort or create a Word document. You can paste the text into another application and adapt its formatting there.
The builder keeps entered fields in the page URL so a shared link can reopen the same draft. Share copies that link, including its request text. Use public-safe sample wording and keep private account details, source links and customer files in your internal system. Download or copy the text if a shareable URL is unsuitable for the information you need to record.
Use this request in a board saves a draft in the current browser tab and opens signup. You can choose the saved template request when creating a board, then review it before publication. To maintain evidence, ownership and a decision over time, use the feature request tracker template. Keep private planning fields in your internal record.
Feature request or bug report?
Use a feature request to describe a new or improved capability. If an existing task fails its expected behavior, use the bug report template and record the steps, environment, expected result and actual result. If you are unsure which applies, describe what happened and let the reviewer check the intended behavior. The label should help route the evidence without hiding the customer’s task.