How to Ask for Client Feedback (With 6 Email Templates)
Last updated: November 6, 2026
To get useful client feedback, send one link to the exact page, say what you want reviewed, ask two or three specific questions, give a date, and name who makes the final call. "What do you think?" invites silence or "looks good". A specific request gives a busy client something they can answer quickly.
This guide is for agencies, freelancers, and in-house teams asking a client to review a website or design while it can still change. It covers what every request needs, what to ask at each stage, and six emails you can copy. If you want a testimonial after the project, that is a different ask, and template 6 covers it. The questions and comments below are illustrations, not quotes from real clients.
Why "What Do You Think?" Gets Bad Feedback
An open question hands the whole job to the client. They have to work out what you want from them, which pages matter, and how much detail is useful, on top of their actual work. So some reply "looks good" to be polite, some rewrite a headline you were not asking about, and some put it off until launch week.
A clearer request fixes most of this, and the request is the one part you control.
What Every Feedback Request Needs
Five parts, in whatever order reads naturally:
- One link: The exact page or build, somewhere they can open without logging in. Several links and attachments leave them unsure which version counts.
- The scope: Say what is finished and what is not, so nobody spends their time on placeholder copy.
- Two or three questions: Name the decisions you need. "Does the pricing table match what your sales team promises?" is easier to answer than "any thoughts?"
- A date and its reason: Give a day and say what it protects, such as "by Thursday, so we can launch on the 14th".
- One decider: If five people will comment, ask who makes the final call when they disagree. Ask before the round starts, not during it.
Note: Ask clients about what only they know: their customers, their offer, their prices, their legal limits. Check the layout, links, and phones yourself first with a website QA checklist, so their time goes on questions you cannot answer.
What to Ask at Each Project Stage
The right question changes as the project moves. Asking about button wording during a first design invites detail you will redo anyway. Asking about page order the week before launch invites a change you cannot afford. NIST's 2002 study on software testing gives a sense of the scale: in its example, an error made at the requirements stage costs 10 times more to fix if it is not found until integration and system testing.
| Stage | Ask | Leave for later |
|---|---|---|
| First design | Does this fit your brand and your audience? What is missing from this page? | Button wording, exact spacing |
| First build | Does the page order match how your customers decide? Is anything in the wrong place? | Copy and images that are still placeholders |
| Content review | Are the facts, prices, and names right? Does your legal team need to see anything? | New sections or pages |
| Before launch | Is anything wrong or missing that would stop launch? Does it look right on your own phone? | Anything that can wait for the next release |
| After launch | Did the project deliver what you wanted? What would you change about how we worked? | A testimonial request in the same breath |
6 Client Feedback Email Templates
Copy these and change the brackets. Keep them short, because a long request is easier to put off.
Template 1: First Review
Use this when the first design or build is ready and most of the content is still rough.
Note: Subject: [Project] first look: 3 questions by [day]
Hi [Name],
The first version of [page] is ready: [link].
It is a first pass, so the images and some of the copy are placeholders. Please skip those for now.
Three things I would like your view on:
1. Does the headline say what you would say to a customer?
2. Is anything missing that your customers always ask about?
3. Does the order of the sections feel right?
If you can reply by [day], we stay on track for [milestone].
Thanks,
[Your name]
Template 2: Final Check Before Launch
Use this when the build is done and you need problems, not new ideas. Saying where new ideas go keeps them from moving the date.
Note: Subject: [Site] goes live on [date]: last check by [day]
Hi [Name],
The site is ready for a final check: [link].
We have tested it ourselves, so please focus on what only you can spot:
1. Are the prices, names, and legal wording correct?
2. Does anything look wrong on your own phone?
Anything that must change before launch needs to reach us by [day]. New ideas are welcome too. We will keep those on a list for after launch.
Thanks,
[Your name]
Template 3: Reminder
Send this as a reply to your first email, a few days before the deadline. Offering a one-line answer and a different reviewer gives them two easy ways out of the silence.
Note: Hi [Name],
A quick nudge on [page]: [link].
A short reply is plenty. If it looks right, just say so and we will move on. If someone else should review it, tell me who and I will send it to them.
We need this by [day] to keep [date].
Thanks,
[Your name]
Template 4: Clarifying a Vague Comment
Use this when a comment such as "the top feels off" could mean several things. Offering choices is easier to answer than asking them to explain design. Once you know what they meant, turn it into an issue a developer can act on.
Note: Hi [Name],
Thanks for this. I want to fix the right thing. When you say [their words], is it closer to:
1. The wording
2. The image
3. The size or spacing
4. Something else
A number is enough, or mark the spot on the page: [link].
Thanks,
[Your name]
Template 5: When Two Reviewers Disagree
Send this to the decider you named at the start. Lay out both options and your recommendation, so they are making a choice instead of starting the discussion again.
Note: Hi [Decider],
[Person A] asked for [option A] on [page] and [Person B] asked for [option B]. We can build either one.
We recommend [option] because [reason].
Can you make the call by [day]? We will hold this item until we hear from you.
Thanks,
[Your name]
Template 6: After the Project
Use this once the work is live. It asks about the project first and treats a testimonial as an optional extra they control.
Note: Subject: Two quick questions about [project]
Hi [Name],
Now that [project] is live, I would like to hear how it went for you.
1. What worked well about working with us?
2. What should we do differently next time?
A line or two is plenty. If you are happy for us to quote any of it on our site, let me know, and we will send you the wording first.
Thanks,
[Your name]
What to Do With the Reply
| The reply | Your next step |
|---|---|
| "Looks good" | If it is the final round, confirm in writing: "Great, we will treat this version as approved for launch." If it is an early round, ask one named question. |
| Silence | Send template 3. If the date passes, say what happens next before you do it. |
| "Make it pop" | Send template 4. Keep their exact words, so they can see you listened. |
| Two people disagree | Send template 5 to the decider you named at the start. |
| A new idea | Add it to the after-launch list. If they want it now, say what it does to the date or budget before you agree. |
Make It Easy to Comment on a Live Site
Email replies lose what a developer needs: which page, which element, and on what screen. A website feedback tool lets the client click the thing they mean, and saves a screenshot and the page URL with the comment.
Test the link before you send it. When we tested 184 domains submitted to our free responsive tester, 52.2% blocked embedding, so a tool that loads the site inside its own page may need a workaround. Open your link in a private window and on your phone, the way the client will.
In OverlayQA, you create a client link for the page and add the client's email. They open it in any browser, including on a phone, with no account, and each comment becomes an issue in your project. We can email the link to them for you.
A welcome note at the top of the comments panel can carry your questions, and they can press Done reviewing when they have finished. There is no approval step on each issue, so ask for final sign-off in writing. These UAT email templates include the wording.
Frequently Asked Questions
How do you politely ask a client for feedback?
Say what is ready, link to it, ask two or three specific questions, and give a date with the reason behind it. A short email that makes the job easy reads as more polite than a long apology for asking.
When should you ask a client for feedback?
Ask at points you agree at the start of the project: after the first design, after the first build, for content, before launch, and after launch. A change costs less the earlier it comes, so an early round is worth asking for even when the work looks rough.
What questions should you ask a client for feedback?
Ask what only they know: whether the facts, prices, and wording are right, whether the page answers their customers' questions, and whether anything would stop launch. Keep it to two or three questions in each round.
What if a client does not respond to a feedback request?
Send a short reminder as a reply to your first email, offer to accept a one-line answer, and ask whether someone else should review it. If the date passes, tell them what you will do next before you do it.
How long should you give a client to review a website?
A few working days for a single page and about a week for a whole site is a reasonable starting point, unless your contract says otherwise. Whatever you choose, name a day instead of saying "soon".
How do you ask a client for final sign-off?
Ask for it separately from feedback, in one sentence with the exact version linked: "Please reply to confirm this version is approved for launch." Keep the reply as your record.
What is the difference between client feedback and a testimonial?
Feedback helps you improve the work or how you run the project, and it can be blunt. A testimonial is a public quote about the result. Ask for them separately, get written permission for anything you publish, and show the client the wording first.
Send clients one link instead of a long email thread. With OverlayQA, clients comment on the page with no account, and each comment becomes a tracked issue with the screenshot attached.