How to get client feedback on design: scripts, structure and one place for notes
Clients give better feedback when you ask a narrow question and give them one place to answer. Here are the scripts and the structure.
The short answer
Ask for feedback on one stage at a time, tell the client what to look at and what to ignore, give them a deadline, and collect the answers in one place. Ask what the design does for their goal, not whether they like it. Then merge the notes into a single list and send it back before you change anything.
Vague feedback is usually the result of a vague question. "Thoughts?" gets "can you make it pop".
Say what stage this is
Tell the client what they are looking at. A rough layout and a final render need different feedback, and clients do not know which one they have.
Script for a first look:
Hi Anna, attached is round 1 of the homepage layout. At this stage we are checking structure and copy only. Colours and photos are placeholders. Please send notes by Thursday 5pm. This is one of two included rounds.
Script for a late round:
Hi Anna, round 2 is attached. Layout and copy are locked from round 1. Please check colour, spacing and the logo placement. Anything else will go into a new quote. Notes by Monday noon.
Each script has a stage, a scope, a deadline and a round count. That is the whole trick.
Ask questions that can be answered
Replace open questions with specific ones.
- Instead of "What do you think?", ask "Does the headline say what you sell in one line?"
- Instead of "Do you like it?", ask "Would your customer know what to click first?"
- Instead of "Any changes?", ask "Which one thing would you change before this goes to the board?"
A narrow question gets a note you can act on. It also pulls the client toward their goals and away from personal taste. When the answer is taste anyway, ask: "Is that a problem for your customer, or a preference?" Say it kindly. It works.
A short feedback form
A form keeps notes in the same shape every round. Five questions are enough. Send them in the email, or paste them into a doc or a form.
1. Does this meet the brief? Yes, partly, no. 2. What must change before approval? (max 5 items, in order) 3. What do you like and want kept? 4. Anything missing from the content or copy? 5. Who else has seen this, and did they add notes? Include them here.
Question 3 matters more than it looks. Clients forget to say what they like, and the next round then loses it. Question 5 catches the second reviewer who would otherwise appear after approval.
Make it easy to comment on the exact spot
The best notes point at the thing. "The text on the third slide" is fine. A pin on the image is better. For video, a time such as 0:42 is better than "somewhere in the middle".
A tool helps. In OIO the client opens the project or ticket link with no account, clicks the image to drop a numbered pin and types the note. On video, they comment at a timecode. Each note is tied to the version they are looking at. If a tool is not an option, ask the client to mark up a screenshot or to number their notes against numbered areas of the layout.
Do not ask clients to create an account to comment. Many will not, and the notes arrive by email anyway. For tool choices, see online proofing software for creative studios.
Merge scattered notes into one list
Even with a good form, notes arrive in three places: an email, a chat message and a call. Merge them before you start work.
- Open one document or one ticket for the round.
- Copy every note in, with its source and date.
- Group by area: layout, copy, colour, logo.
- Mark duplicates and contradictions.
- Send the merged list back with: "This is what I will change. Please confirm."
Contradictions are the main reason to do this. If one person wants the logo bigger and another wants it smaller, the studio should not pick. Send both notes to the named approver and wait for one answer. The approval steps are in the client approval workflow guide.
A good test: after you send the merged list, the client should reply "yes" or correct a line. If they send a new set of notes, the first list was incomplete, and that is round 2.
Handle the notes you cannot act on
Some notes cannot be used as written.
"Make it more modern." Reply with two options: "Do you mean a lighter typeface, or more white space? I can show both."
"I will know it when I see it." Offer three small variants and ask which one is closest. Name this as part of the round.
"My wife does not like the blue." Ask the approver whether the blue is a change request. If it is, it goes in the list. If not, it does not.
Keep replies short, specific and polite. Clients give better notes to a studio that has shown it listens.
Chase without nagging
Feedback goes quiet. Set the deadline in the first message, send one reminder on the day before, and one on the day. After that, write: "Without notes by Friday, the delivery date moves by the days lost." Most clients reply within the hour.
OIO shows a Needs feedback marker on a ticket waiting on the client, and sends the client one reminder email a day, which you can switch off.
Keep the notes with the project
Notes that live in an inbox are gone when the person leaves. Keep each round's merged list, the version it applies to and the client's confirmation with the project. When a later dispute starts, you can point to the round, the note and the date.
For archviz work with many rounds, archviz client feedback rounds goes deeper on image notes. To write the round limit into your quote, start with the free quote template.
Doing this in OIO
Upload the work to a ticket on the project, send the link, and let the client pin notes. You resolve each pin as you fix it, upload the next version, and send the link again. A freelancer doing the fixes gets a ticket link with only their brief and files. The client clicks Approve this version when it is right, and OIO records who approved which version and when. Client review starts on Solo at $19 a month.
Questions
How do I ask a client for feedback on a design?
Say what stage it is, what to check, what to ignore and when you need notes. Ask specific questions about their goal, not whether they like it.
What should a client feedback form for designers include?
Five questions: does it meet the brief, what must change, what to keep, what is missing, and who else has seen it. Keep the list of changes to five items.
How do I stop feedback arriving in different emails?
Give one place to comment, such as a link to the version. Merge anything that still arrives elsewhere into one list and send it back for confirmation.
What do I do with feedback I cannot act on?
Ask a narrow follow-up, or offer two or three small options and ask which is closest. Add the answer to the round's list.
How long should a client have to give feedback?
Three working days is common. Put the date in the message, send a reminder, and say what happens if the date passes.