Feature Request Form Template

Collect feature ideas with the context your product team needs to evaluate them. This feature request form asks about the user's task, current workaround, and desired outcome before asking for a proposed solution.

Preview on a device
Feature Request Form Preview

'Add an export button' describes an idea. Understanding what someone needs to export, why, and what happens today gives the team a problem to investigate. Keep that context attached to the suggestion.

When to use this feature request form

Use this form for new product requests from current users. It captures one request at a time, rather than rating an existing feature or asking everyone to vote on a roadmap. SurveyLegend helps you collect consistent details without promising that a submission will be built.

To evaluate a capability people already use, try the product feature survey.

7 questions for your feature request form

Use these seven questions as a starting point. Every field is optional. Choose one answer where choices are listed and leave irrelevant text fields blank.

Respondent introduction:
Tell the product team about one improvement you would like. Describe the task without including private data or account credentials. Submitting a request does not guarantee a release or reply. All fields are optional.

Try the survey

A little feedback. A clearer picture.

Explore this 7-question example at your own pace. Every question is optional.

SurveyLegend demo Question 1 of 7

Feature Request Form

01 What are you trying to accomplish in the product?

Share your answer, or skip this question.

02 What makes that task difficult today?

Share your answer, or skip this question.

03 How do you handle the task now?

Share your answer, or skip this question.

04 How often do you need to do this task?

Choose one answer, or skip this question.

05 What would a successful outcome look like?

Share your answer, or skip this question.

06 What feature or change would you suggest?

Share your answer, or skip this question.

07 If the team needs clarification, what email address may it use to contact you?

Share your answer, or skip this question.

Checking submission availability…

This is a demo. We count starts and submissions only. Your answers stay in your browser and are never sent or saved.

0Starts
0Submissions

Activity · no starts yet

How to customize your feature request form

Keep the problem and suggested feature as separate fields. For a product with several modules, add a clearly defined module field only if it helps route requests. Explain who can access contact information and use it only for the stated follow-up.

Before sharing, try the questionnaire with a few intended respondents and clarify anything they interpret differently.

Review SurveyLegend's guide to writing open-ended questions when adapting the problem prompt so users can describe their own task and difficulty.

If you want feedback from a product help page, SurveyLegend explains how to embed request forms on your website.

Printable feature request form template

Use this printable feature request form template at a user workshop where participants can describe one product improvement. It gives people who prefer paper or are less comfortable online another way to respond. Include the same context, questions, and answer choices as the online version. Tell respondents where to return it and who will review it. Paper answers need separate review or manual entry; they are not automatically added to online responses.

Download Feature Request Form Template (PDF)

AI prompt for your feature request form

Turn feature suggestions into problems your product team can investigate.

The prompt below includes all seven questions and their response settings. Copy this prompt into an AI assistant to draft the questions. Review the draft, then build and customize the survey in SurveyLegend before sharing.

Copy the prompt into an AI assistant to draft the questions, then build your survey in SurveyLegend.

Already have an account? Sign in to create your feature request form.

How to use the answers

Group requests by the underlying task and desired outcome before counting feature names. Similar problems may have different suggested solutions, and one idea may serve several tasks. Review frequency and workarounds to choose follow-up conversations. Submission counts alone do not measure market demand or set development priority.

SurveyLegend's guide to analyzing open-ended data provides a process for coding related problems while preserving the detail behind each request.

An action-research study on user feedback recommends specifying what information to collect in relation to the decision it should support. This form applies that idea by keeping the user's task, problem, and desired outcome visible alongside the feature suggestion.

Frequently asked questions

How is a feature request different from a bug report?

A feature request asks for a new capability or change. A bug report describes behavior that is not working as intended. Give users a separate support route when an issue needs help.

Should every request include a proposed solution?

Invite suggestions, but the task and difficulty are often enough to begin investigation. Keep all fields optional so users can explain what they know.

Does submitting a request put it on the roadmap?

No. The team still needs to review usefulness, feasibility, and product priorities. State the actual review process rather than promising delivery.