Form templates / Software & IT
Feature Request Form
A feature request form should ask for the problem, not the feature. Users are experts in their own frustration and amateurs at solution design - and both are fine.
For software teams, IT departments and managed service providers.
Ask what they do today instead
A request for a specific feature tells you almost nothing about whether to build it. What tells you everything is the workaround: exporting to a spreadsheet twice a week, keeping a second list in a notebook, asking a colleague to check something manually.
So this template asks what they currently do instead and how often. That converts a wish list into a ranked list of real costs - and frequently reveals that three unrelated requests are the same underlying problem.
A record with a timestamp
Every submission is stored with the moment it was made, and exports as a spreadsheet. If a report ever has to be produced - for an insurer, a regulator, a review - it exists, dated, unedited.
A bug report that doesn't need three follow-ups
"It's broken" costs a developer an hour of guessing. Steps to reproduce, expected versus actual, browser and version turn a report into something that can be triaged without a conversation.
Fields make people answer the questions they'd otherwise skip - and being able to filter a month of reports by area or severity tells you where to spend the next sprint.
Route it to the right person
Send every report to whoever needs to act on it by email the moment it arrives, so nothing sits in a queue waiting to be noticed.
Edit it like a document, publish like a link
Add questions, remove questions, change the order and the wording, set your accent colour. When you save, the form is live at its own address - share it by link, QR code or a button on your site, and read the answers in your dashboard.
What this template asks
- Your name
- Email address
- Company
- What's your role?
- What are you trying to do that you can't?
- What do you do instead at the moment?
- How often does this come up?
- Roughly how much time does the workaround cost you each week?
- How much does it matter?
- How do you imagine it working?
- Which part of the product?
- Does this affect other people you work with?
- Let me know if you build this
- I'd be happy to talk it through for 15 minutes
- I'd test an early version
More Software & IT forms
Questions
Should I let users vote on requests?
Voting boards favour whoever is loudest. Asking each requester how the problem affects them, and how often, gives you better data than a vote count from a self-selected group.
How do I close the loop?
Ask whether they'd like to be told if you build it - and then actually tell them. It's the cheapest goodwill available and almost nobody does it.
Can reports be submitted anonymously?
Yes, if you make the name optional. Nothing about the submitter is recorded otherwise - no IP address, no account, no tracking.
Can this go to more than one person?
Yes. Notification recipients are a list, so a report can reach a manager and a safety lead at the same time.
Can I export everything for an audit?
Yes - one click gives you a CSV of every response with its timestamp, which is usually exactly what an auditor or insurer asks for.
Can this feed into our issue tracker?
Point a webhook at your tracker and every submission is posted to it as JSON as it arrives, or pull responses from the REST API. There's also a CSV export for bulk import.
Publish your feature request form today
Start from this template and change anything you like. Free to begin.