Feedback form examples (with the exact fields for each)
A good feedback form keeps it short, asks one rating question plus one open-ended 'why', and ends with an optional contact field. Below are five complete examples — customer feedback, product feedback, event feedback, employee feedback, and website feedback — each with the exact fields, field types, and real wording you can copy. Most need 4–7 fields; the rating-plus-comment pair does the heavy lifting in every one.
The fastest way to design a feedback form is to start from a working example and trim it to your situation. Each example below lists the fields, the right field type for each, whether it should be required, and example wording. Steal whichever fits and cut anything you won't act on — an unanswered field is wasted effort for the person filling it out.
What makes a feedback form work?
Across every example here, three things stay constant:
- One clear rating question (a 1–5 scale, NPS, or star rating) gives you a number you can track over time.
- One open-ended 'why' question captures the reason behind the score — this is where the actionable insight lives.
- Contact details stay optional, so people can give honest feedback anonymously if they prefer.
Put the rating question first and the open-ended question right after it. People answer a quick rating willingly, and once they've committed to that, they're far more likely to type a sentence explaining it.
1. Customer feedback form
Use this after a purchase, a support interaction, or a service. The goal is a trackable satisfaction score plus the reason behind it.
| Field | Field type | Required? |
|---|---|---|
| How satisfied were you overall? | Rating (1–5) | Yes |
| What's the main reason for your score? | Long text | No |
| Which part of your experience stood out — good or bad? | Multiple choice | No |
| How likely are you to recommend us? | NPS (0–10) | No |
| Email (if you'd like a reply) | No |
Example wording for the standout field: 'Which part of your experience stood out?' with options 'Product quality', 'Price', 'Customer support', 'Delivery / speed', 'Something else'.
Customer feedback questions to use
- How satisfied were you with your experience today?
- What did we do well?
- What could we have done better?
- How likely are you to buy from us again?
- Is there anything else you'd like us to know?
2. Product feedback form
Use this to learn how a feature or product is landing with the people who actually use it. Tie answers to the specific feature when you can.
| Field | Field type | Required? |
|---|---|---|
| Which feature are you giving feedback on? | Dropdown | Yes |
| How would you rate it? | Rating (1–5) | Yes |
| What would make it more useful to you? | Long text | No |
| How often do you use this feature? | Multiple choice | No |
| What were you trying to do when this came up? | Long text | No |
| Can we follow up with you? | No |
Product feedback questions to use
- How easy was this feature to use? (Very difficult to Very easy)
- Did it do what you expected?
- What's one thing you'd change about it?
- What almost stopped you from using it?
- How would you feel if you could no longer use this feature?
3. Event feedback form
Send this within 24 hours of an event, while it's fresh. Keep it under two minutes so people actually finish it.
| Field | Field type | Required? |
|---|---|---|
| Overall, how would you rate the event? | Rating (1–5) | Yes |
| Which session was most valuable? | Multiple choice | No |
| What was the highlight for you? | Long text | No |
| What should we change next time? | Long text | No |
| How likely are you to attend again? | NPS (0–10) | No |
| Name (optional) | Short text | No |
Event feedback questions to use
- How well did the event meet your expectations?
- How would you rate the venue and logistics? (in-person) or the platform and audio (virtual)
- Which topic would you like to see covered next time?
- Was the event the right length?
- Would you recommend this event to a colleague?
4. Employee feedback form
Keep this anonymous to get honest answers. Don't collect names, emails, or anything that could identify a small team.
| Field | Field type | Required? |
|---|---|---|
| How are you feeling about work this week? | Rating (1–5) | Yes |
| Do you have what you need to do your job well? | Multiple choice | No |
| What's working well right now? | Long text | No |
| What's getting in your way? | Long text | No |
| What's one thing leadership could do better? | Long text | No |
Employee feedback questions to use
- On a scale of 1–5, how supported do you feel by your manager?
- Do you feel your work is recognized?
- What would make your day-to-day easier?
- How clear are you on the team's priorities?
- Anything you'd raise if we were talking one-on-one?
5. Website feedback form
Trigger this from a button in the corner of the page or after a key action like checkout. Capture what page they were on so the feedback is actionable.
| Field | Field type | Required? |
|---|---|---|
| What were you trying to do? | Long text | Yes |
| Did you find what you were looking for? | Multiple choice | Yes |
| How easy was the site to use? | Rating (1–5) | No |
| What got in your way? | Long text | No |
| Which page is this about? | Short text or URL | No |
| Email (if you'd like a reply) | No |
Website feedback questions to use
- Were you able to complete what you came to do?
- What's missing or confusing on this page?
- How would you rate the speed of the site?
- What nearly made you leave?
- If you could change one thing here, what would it be?
What are the most common feedback form mistakes?
- Asking 5+ rating questions in a grid — people speed-click straight down the column without reading.
- Making the open-ended 'why' field required, which spikes abandonment. Keep it optional.
- Forcing contact details on a feedback form, which kills honest responses and anonymity.
- Asking for feedback you have no plan to act on — it erodes trust when nothing changes.
- Using a short text field where a multiple choice or dropdown would keep answers clean and comparable.
- Not testing on a phone, where most feedback links get opened.
Each of these forms takes a few minutes to build in a free tool. In Formkii you can pick the right field type (rating, NPS, long text), keep responses anonymous, and watch results come in as live charts, then export to CSV.
How long should a feedback form be?
Aim for 4–7 fields and under two minutes. The rating-plus-comment pair is the minimum that's still useful; everything past that should earn its place by giving you something you'll act on. If you find yourself adding a tenth question, consider whether a separate, deeper survey would serve better.
Frequently asked questions
What should a feedback form include?
At minimum, one rating question (a 1–5 scale, stars, or NPS) and one open-ended 'why' question. Add an optional contact field for people who want a reply. Keep it to 4–7 fields so people actually finish it.
How many questions should a feedback form have?
Four to seven is the sweet spot for most feedback forms. The core is a single rating plus an open comment; extra questions should only exist if you'll act on the answers. Longer forms see sharply lower completion rates.
Should a feedback form be anonymous?
For employee and internal feedback, yes — anonymity produces far more honest answers. For customer or product feedback, make contact details optional so people can reply anonymously or leave an email for follow-up, whichever they prefer.
Can I make a feedback form for free?
Yes. Free form builders like Formkii, Google Forms, and Tally handle every example above at no cost, including rating fields, NPS, and live response charts. The build takes a few minutes per form.