Form · Feedback
Software update feedback form template
A post-release form that treats three kinds of user differently. People who used the new features rate the change, people who noticed but didn't try them say why, and people who missed it entirely say where they'd expect to hear. Anyone who hit a bug describes it, rates how badly it hurts and can attach a screenshot.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
We've just shipped an update. Tell us how it's going for you, it takes about two minutes.
Which version are you using, if you know?
How often do you use the product?
Have you noticed what's changed in this update?
Has the update made your work easier or harder?
Was anything confusing, or in need of a better explanation?
What's kept you from trying them?
Where would you expect to hear about new features?
Have you run into any bugs or problems since the update?
What happened, and what were you trying to do at the time?
How much is it getting in your way?
A screenshot or screen recording helps a lot, if you have one.
Did anything you relied on change or disappear?
Overall, how do you feel about this update?
Leave your email if we can follow up with you.
Ends with
Thanks, this goes straight to the team 🛠️
The flow
Where each answer leads. Every route here is editable once the form is yours.
Short text
Dropdown
Single select
Opinion scale
Long text
Single select
Multi select
Yes / No
Long text
Single select
File upload
Long text
Rating
What this template uses
- Short text
- Dropdown
- Single select
- Opinion scale
- Long text
- Multi select
- Yes / No
- File upload
- Rating
- 5 branches
Questions to consider
- Which changes in this release do you most want feedback on, and should you name them in the question?
- How soon after release will you send it: a few days, or after people have had a week with it?
- Should bug reports from this form go to the same place as your usual support queue?
- Can you prefill the version from the app so users don't have to look it up?
How to use the responses
Sort the bug reports by severity first and reply to anyone blocked by the update the same day. Split the rest by the answer to whether they noticed the changes: the easier or harder scores tell you if the change was right, and the reasons for not trying tell you whether it was explained well. If many people missed the update entirely, change where you announce the next one.
How to customize and share it
- 1Name the headline change in the noticed question, for example "Have you tried the new dashboard?".
- 2Pass the version as a URL parameter from inside the app so the first question fills itself.
- 3Send the link a few days after release, in the app or by email, while the change is still new.
Frequently asked questions
What should I ask users after a software update?
Whether they noticed the change, whether it made their work easier or harder, whether anything broke, and what needs a clearer explanation. Asking what disappeared catches regressions that nobody reports on their own.
When should I send a release feedback form?
A few days to a week after release, so people have used the change but still remember what it replaced.
Can users attach screenshots of bugs?
Yes. Anyone who reports a problem can upload screenshots or a short screen recording along with their description.
Can I embed this form inside my app?
Yes. You can embed it on a web page or open it from a link in the app, and pass the version number through the link.