Website feedback form template for client reviews
A website feedback form template gives every reviewer the same questions, so you get answers you can compare instead of a long email that starts with "a few thoughts". The form below groups its questions by page, content, design and function, with a score and an open question in each group. There is a shorter version for the final sign-off round, and an honest look at when a form works better than comments on the page and when it doesn't.
What a feedback form is good for
Most client feedback arrives as an email, a call or a document full of screenshots. Each reviewer covers different things in a different order, and the big questions, like whether the homepage explains what the business does, often get skipped in favour of a button colour.
A form fixes the order. Everyone answers the same questions about the same page, so you can see quickly where three reviewers agree and where one is on their own. It also prompts people to think about things they would not have mentioned, such as whether the contact form actually sent.
What a form can't do is point. "The second image looks stretched" leaves you guessing which image, on which page, at which screen size. Keep that in mind when you decide what to ask on the form and what to collect another way, which the comparison further down covers.
This form is for reviewing work in progress. If a client wants something new added, like an extra page or a feature, that is a scope change, and our website change request form is the better record for it.
The website feedback form
Each group has a score from 1 to 5 and one or two open questions. The score gives you a quick read across reviewers. The open questions give you something to act on. Swap the parts in curly brackets for your own details, then paste it into Google Forms, Typeform, a document or an email.
How to adapt it for your project
- One page per form. Answers like "the text is mostly fine" are hard to act on when nobody knows which page they mean. For a five-page site, send the form five times with the page address filled in, or add a page picker at the top in your form tool.
- Cut questions that don't fit the round. In a first round about structure, the design score adds noise. Remove it and say so in the email.
- Keep the page address and device fields. They are the only way to get back to what the reviewer saw. A bug that only shows on one phone is impossible to find without them.
- Keep the open questions specific. "Any other thoughts?" invites a long list of small preferences. "If you could change only one thing" gets the change that matters most to them.
A shorter form for the final sign-off
By the last round, broad questions about tone and layout are settled, or they should be. The sign-off form is mostly yes or no, so the reviewer only writes something when there is a real problem. It works best when one person, the approver, fills it in. For the full approval process, see our guide on getting client approval on a website.
Final sign-off form
For the approver, in the last round.The last line matters. Clients often hold back approval over a small wish that could easily wait. Giving those wishes a place to go, separate from the must-fix list, makes it easier to say yes.
Form or comments on the page?
A form and comments on the page answer different questions. A form asks the reviewer to step back and judge. A comment on the page records one thing in one place. Here is when each one fits.
| Situation | Form | Comments on the page |
|---|---|---|
| Does the page do its job? Is anything missing? | Good fit. It asks everyone the same broad question. | Awkward. There is no single spot to pin it to. |
| Comparing answers from several reviewers | Good fit. Scores and answers line up side by side. | Harder. Comments are spread across the page. |
| A wrong word, a stretched image, a gap that looks off | Weak. The reviewer has to describe where it is. | Good fit. The comment sits on the exact element. |
| Something only breaks on one phone | Weak, unless they fill in the device field carefully. | Good fit, if the tool records the device and screen size. |
| Reviewers who won't open another tool | Good fit. Most people have filled in a form before. | Fine if no account or extension is needed. |
| Final yes or no on launch | Good fit, with a short sign-off form. | Good fit, if the tool records an approval. |
The honest weakness of any form is that it loses the location. Even with the page address and device filled in, "the button near the bottom" still leaves you scrolling and guessing, and you can't see what the reviewer saw. The more specific the feedback, the more that costs you.
So a mixed round often works best: the form for the four broad groups, and a review link for the exact fixes. That is the line at the end of the template. With HTMLAnnotate, reviewers click anything on the page to leave a comment pinned to it, with no account. Each new comment saves a small screenshot of what they saw, and the owner also sees the browser, device and screen size. Desktop, tablet and phone comments are kept separate. When the final version is right, the approver can press Approve, which is recorded against that version. HTMLAnnotate doesn't have a form builder, so the broad questions still belong in your form tool.
Tips for getting useful answers
- Say what this round is for. Put it at the top of the email: "This round is about structure and content." It stops a page of notes on fonts that are about to change. Our feedback request email templates include that line for each round.
- Give one date. A specific day gets more replies than "when you have a moment".
- Ask for quotes, not summaries. "Please quote the words" turns "some of the text is wrong" into a list you can fix.
- Ask them to check on a phone. Reviewers tend to look on whatever they are sitting at. The device field on the form is a gentle prompt.
- Read the scores as a signal, not a verdict. A 2 out of 5 on design tells you where to look. The open answer next to it tells you what to do.
- Follow up on vague answers quickly. "It needs more energy" is still useful. Ask one question back while the review is fresh. Our guide to handling vague client feedback has wording for that.
- Send a short guide to first-time reviewers. Our guide to giving useful website feedback takes five minutes to read and makes the open answers much easier to act on.
For the whole process, from the first review link to sign-off, see how to get feedback on a website.
Questions
What questions should a website feedback form include?
Ask who is reviewing, which page and which device, then a short group of questions on each of the page as a whole, the content, the design and how things work. A score from 1 to 5 plus one or two open questions per group is enough. Finish with the one change they would make if they could only make one.
Is a form better than leaving comments on the website?
They do different jobs. A form is good for broad questions that apply to the whole site or a whole page, and for comparing answers from several reviewers. Comments pinned to the page are better for specific fixes, because they keep the exact element, the device and a screenshot. Many teams use both in the same round.
How many questions should a client feedback form have?
Few enough to finish in about 15 minutes for one page. The form on this page has four groups with a score and two open questions each, plus a few details about the reviewer. If a project needs more, send a separate form for each key page rather than one long one.
Should every reviewer fill in their own form?
Yes. Separate answers show where reviewers agree and where they don't, which a single merged reply hides. Ask one person, usually the approver, to settle any disagreements before you start on changes.
What should go in a final sign-off form?
Keep it to yes or no questions: has every agreed change been made, does the site work on a phone, are the contact details and forms correct, and is the site approved to go live. Add a name, a date and a box for anything that must change before launch.
Pair your form with one review link. Reviewers click anything on the page to comment, with no account, and each comment keeps the spot, the device and a screenshot.
Start a free review