Handling Client Feedback and Revisions
Set revision rules, translate vague feedback like "make it pop" into real changes, and handle endless revision requests.
6 min read
"Can you make the logo bigger?" "Add more colors." "My wife does not like it." Feedback is part of every design job, and it is where many beginners lose time, money and confidence. The designers who grow are not the ones who never get negative feedback. They are the ones with a calm system for receiving it, understanding it and deciding what to do with it.
Key takeaways
- Agree on the number of revision rounds before you start, and write it in the brief.
- Ask for feedback in one list per round, not in twenty separate messages.
- Look for the problem behind the request; "make it pop" usually means something specific.
- Extra rounds and new ideas outside the brief are billable, and saying so politely is professional.
Set the rules before the first draft
Feedback goes wrong when nobody agreed on how it works. Before you start, tell the client:
- How many rounds of revisions are included (two is common for flyers, three for logos).
- What counts as a revision (changes to the agreed design) and what counts as new work (a new concept, a new size, new content).
- How you want feedback sent: one message per round, with all changes listed.
- What happens after the included rounds: each extra round costs a set amount.
How to receive feedback without taking it personally
Your design is not you. When feedback stings, wait before you reply. Then thank the client, repeat back what you understood, and ask about anything unclear. A calm reply builds more trust than a perfect first draft.
Translate vague feedback into design changes
| The client says | What it often means | What you can try |
|---|---|---|
| Make it pop | Nothing stands out; the hierarchy is flat | Increase contrast and size on one key element |
| It looks empty | They are not used to white space, or the main element is too small | Scale up the focal point before adding more items |
| It looks too busy | Too many fonts, colors or elements | Remove, group and align; cut fonts to two |
| Make the logo bigger | They worry their brand is not visible | Make it larger but cleaner, or repeat the brand color |
| Something is off | Alignment or spacing problems | Check margins, alignment and spacing consistency |
| I want it more professional | It feels amateur in type or spacing | Simplify the type, tighten the grid, reduce effects |
The fundamentals behind most of these fixes are in type hierarchy and alignment, balance and proximity.
When to push back
You do not have to accept every change. If a request will hurt the result, explain the trade-off briefly and offer an alternative: "I can make the phone number red, but then the offer and the number compete. What if we make the number bigger instead?" If the client still wants it, do it. It is their project. Your job is to advise, not to win.
Handling endless revisions
- Refer back to the approved brief and the agreed number of rounds.
- Tell the client how many rounds are left before you send each version.
- When the included rounds are used, quote for the next round before you work on it.
- If the project has changed direction completely, treat it as a new brief with a new price.
Present your work so there is less to fix
Do not just send a JPEG and wait. Add two or three lines explaining your choices: why this color, why this layout, what the viewer sees first. Show the design in context with a mockup. Clients who understand the thinking ask for fewer random changes.
Frequently asked questions
How many revisions should I offer?
Two rounds for small jobs and three for logos and branding is a fair start. Price your work so those rounds are covered.
What if the client keeps sending changes one message at a time?
Ask them kindly to collect all changes for the round into one list. Wait for that list before you start editing.
Should I give the editable file after revisions?
Agree on this in the brief. Many designers charge extra for source files, or include them only in higher packages.