Knowing how to ask a client for feedback is mostly about making the reply easy. A client who gets "Let me know what you think" has to decide what to look at, how much detail to give and when to answer. A client who gets clear questions and a date can reply quickly.
This guide covers feedback on drafts and work in progress, reply dates, vague or conflicting answers, confirming changes, and feedback at the end of a project. Each section includes an example email.
Why "let me know what you think" gets poor answers
An open request leaves all the work to the client. They may comment on things already agreed, skip the part you needed checked, or say "looks good" and raise real concerns later.
A clear request tells the client what to look at, what is not up for review yet, and when you need an answer.
How to ask a client for feedback: what to include
Every request for feedback on work in progress should cover five points:
- What you are sending. Name the draft and where to find it.
- What stage it is at. Is this an early direction, a near-final version, or a final check? This tells the client how much can still change.
- What you want feedback on. Ask two or three specific questions.
- What is not up for review yet. If the colors are placeholders, say so, or you will get feedback on them.
- When you need the reply, and why. Tie the date to the next step in the project.
What questions should you ask?
Ask questions the client can answer with a decision. Good questions point at one part of the work and offer a clear choice.
Weak question: "What do you think of the homepage?"
Better questions:
- "Does the headline describe what you offer, in words your customers would use?"
- "Is anything missing from the list of services?"
- "Should the booking button go at the top of the page or after the prices?"
If you only need a yes or no, say so: "If the layout works for you, a one-line reply is enough."
How to write an email to a client for feedback
Here is a full example for a draft at the middle stage of a project.
Example email:
Subject: Booking form draft: your feedback by Wednesday 22 October
Hi Dana,
The first draft of the booking form is ready. You can see it here: [link].
This draft is about the steps and the fields. The colors and fonts are placeholders and will match the rest of the site in the next version, so please skip those for now.
Could you answer these three questions?
- Are the steps in the right order for how your customers book?
- Is any field missing, or is there one we can remove?
- Should customers pay when they book, or when they arrive?
I need your reply by Wednesday 22 October so I can build the final version that week. If you need more time, tell me by Monday and we can move the date.
Sam
The subject line carries the reply date, the second paragraph says what to skip, and each question asks for a decision.
How to set a reply date the client will keep
A reply date only works if the client can see why it matters. "By Wednesday" reads as a preference. "By Wednesday so I can build the final version that week" reads as part of the plan.
A few rules help:
- Agree review time at the start. During onboarding, ask how long the client needs to review a draft. Use that number when you set each date.
- Give a date, not a duration. "Within three days" can be read several ways. "By Wednesday 22 October" cannot.
- Say what happens if the date passes. Be calm and specific. For example, you will move to the next task and come back to this one, or the launch date will move by the same number of days.
- Repeat open requests in your regular update. If you send a weekly update, list the feedback you are waiting for in the "what I need from you" part. The weekly client update guide explains that section, and what belongs in a weekly client update covers the rest.
If a late reply will move a launch date, tell the client as soon as you know. The guide on how to tell a client bad news covers that message.
What if the reply date passes?
Send one short reminder the day after. Do not apologize for asking.
Example reminder:
Hi Dana,
A quick reminder about the booking form draft. I have not had your answers on the three questions yet, so I have started on the confirmation emails in the meantime.
If I have your reply by Friday 24 October, the launch date stays as planned. After that, it will move back by a few days. A short reply on question 3 alone would let me keep going.
Sam
How to handle vague client feedback
Vague feedback sounds like "It doesn't feel right yet" or "Can it be more modern?" The client means something real but has not found the words.
Do not guess and start over. Ask a narrow follow-up question, and offer choices so the client can point instead of describe.
Example reply to vague feedback:
Hi Dana,
Thanks for looking at the homepage. I want to make sure I change the right thing. When you say it doesn't feel right yet, is it closest to one of these?
- The headline doesn't sound like your business.
- The page feels too busy.
- The photos don't match the kind of customers you have.
If it's something else, a quick note on which part of the page you looked at when you felt it would help. I can also call you for ten minutes tomorrow if that's easier.
If you talk on a call, send a short written note of what you agreed afterwards.
How to handle conflicting feedback
Conflicting feedback usually means more than one person reviewed the work. Dana wants a short page and her colleague wants every service listed. You cannot satisfy both, and you should not pick one yourself.
The fix starts before the first draft. During onboarding, agree who approves each piece of work and ask one person to collect everyone's comments into a single reply. The client onboarding checklist includes this step.
If conflicting notes still arrive, name the conflict and ask the approver to decide.
Example message:
Hi Dana,
I have two comments on the services page that point in different directions. Priya would like the page shorter, with the top three services only. Tom would like all twelve services listed with prices.
I can build either. Could you let me know which one to go with by Thursday? If it helps, a middle option is the top three services on the page with a link to the full price list.
Sam
This keeps you out of the disagreement and puts the decision in writing.
How to respond to client feedback and confirm it
Once you have the feedback, do not go straight to the changes. First, reply with a short summary of what you will change and what you will not. This is the step that catches misunderstandings while they are still cheap to fix.
Your reply should:
- Thank them briefly. One line is enough.
- List the changes you will make. Use their words where you can.
- Name anything you will not change, and why. For example, a request that is outside the agreed scope, or one that would break something else.
- Give a date for the next version.
Example confirmation:
Hi Dana,
Thanks for the notes. Here is what I will change in the next version:
- Move the booking button above the prices.
- Remove the "company name" field.
- Take payment at the time of booking.
You also asked about a gift card option. That is not part of the current work, but I am happy to send a separate quote for it.
The updated draft will be ready on Tuesday 28 October. If I have misread anything above, tell me before Monday.
Sam
If you disagree with feedback, say so once, plainly, with your reason. Then let the client decide. It is their project.
How to ask a client for feedback at the end of a project
At the end of a project, you are asking how the work and the working relationship went, so you can improve your process for the next client.
Ask soon after delivery, while the project is fresh. Keep it short, and make it clear that a brief answer is welcome.
Example end-of-project email:
Subject: One last question about the website refresh
Hi Dana,
Now that the new site is live, I would like to hear how the project went from your side. Three short questions:
- What worked well about how we worked together?
- Was anything unclear, slow or harder than it needed to be?
- Is there anything you wish I had told you earlier?
A few lines is plenty, and honest answers help me most. If you were happy with the work and would be willing for me to quote you on my website, let me know, but there is no obligation.
Thanks again,
Sam
Keep the request for a testimonial separate from the request for feedback, or make it clearly optional, as in the example. Clients give more honest answers when they are not also being asked for praise.
When you get the answers, thank the client and tell them one thing you will change because of what they said.
Common questions about asking clients for feedback
How do you politely ask a client for feedback?
Be direct and specific. Name the work, ask two or three clear questions, give a reply date with a reason, and offer a way to ask for more time. Clear requests are polite because they save the client effort.
How many times should you follow up on a feedback request?
Send one reminder after the reply date, and mention the open request in your next regular update. If there is still no answer, explain what the delay changes and ask for a short reply on the most important question only.
How do you respond to negative client feedback?
Thank the client, ask questions until you understand the problem, and confirm in writing what you will change. Do not argue point by point. If you disagree with something, explain your reason once and let the client decide.
Conclusion
Learning how to ask a client for feedback comes down to a clear request: what you are sending, what you want them to look at, and when you need the answer. Follow up once if the date passes, turn vague or conflicting notes into a clear choice, and confirm what you will change before you start.
If you want feedback requests to be a normal part of every week, Friday is built around that habit. Each weekly update has a place for what you need from the client and by when. The client reads it in their inbox, opens a private project page without an account, and can reply under the update. You get an email when they do. You can try Friday free for 30 days, no card needed.