How to handle client feedback on design work
A feedback workflow for design agencies: one round per version, one owner on each side, contradictions settled by rule, and a reply to every comment.
· 5 min read · Client delivery
Handle client feedback on design work as a round with edges. Each round belongs to one version. It collects every comment in one place, pinned to the artwork, with one person on the client side who settles contradictions before the studio sees them. And it ends with the agency answering every comment, point by point, before the next version goes out.
Most feedback pain comes from rounds with no edges: comments that arrive whenever, about whichever file, from whoever happened to be copied in.
That cost shows up in the numbers. Cway's 2026 benchmark of packaging artwork approvals found email-run approvals averaged 8.4 revision rounds, against 4.1 where teams used a structured review workflow, and each extra round added 2.3 days (Cway, 2026). Packaging is a different trade from agency brand work, and the report does not publish its sample size, so hold the exact figures loosely. The shape will be familiar to any studio anyway. The rounds you lose are mostly spent coordinating.
This guide is about running the round itself. The decision at the end of it, who can approve and how that approval is recorded, is covered in a client approval workflow that holds up.
Before the round: say what it is for
A feedback round usually goes wrong in the email that opens it. "Here's v2, let us know your thoughts" invites everyone on the thread to have every thought about everything.
The message that opens a round should carry four things:
- The version, by number, and what changed since the last one.
- The questions this round is for. "Does the layout work on a phone?" is a question. "Thoughts?" is an invitation to redesign the logo.
- Who is reviewing, and which of them owns the consolidated answer.
- The date the round closes.
The second point does more work than it looks. Design feedback expands to fill whatever it has not been told about. If round two is about the photography, say so, and the typeface stops being reopened by somebody who joined the call late.
During the round: pin every comment to a version
Every comment should land on the version it is about, at the spot it is about. "The image on page three" becomes a pin on that image, on v2, and it stays attached to v2 when v3 arrives. That one habit ends most arguments about what the client meant, because the comment carries its own context.
It also stops the slow leak into other channels. Remarks on a call are fine. The rule is that whoever heard one writes it up as a pin, the same day, or it did not happen. Clients accept this quickly when pinning is easier than emailing, and the quickest way to make it easier is to stop replying to feedback anywhere else. Running client work from your inbox covers why the inbox loses every time.
Contradictions: settled by a rule the client agreed to
Two stakeholders will disagree. The MD wants the headline louder, the marketing lead wants more white space, and both are in writing on the same version. The designer's instinct is to split the difference. Resist it. A compromise nobody asked for tends to earn a third opinion.
Contradictions belong to the client, and the way to hand them back should be agreed in week one:
- One person on the client side owns the feedback on each deliverable. Other reviewers comment; the owner reconciles.
- When two comments conflict, the studio flags the pair to the owner with a single question: which of these should we do?
- The round stays open until every flagged pair has an answer.
This is where naming a feedback owner pays for itself. A conflict between two people of equal standing is a negotiation. With a named owner above it, it becomes a lookup.
After the round: answer every comment
Most studios skip this step, and clients notice. Before the next version goes out, every comment from the round gets an answer from the agency, in one of three states:
- Done, with the version it was done in.
- Discussed, with what was agreed instead and who agreed it.
- Declined, with the reason.
A comment that vanishes without a reply reads as ignored, even when the change was made. A comment marked done against v3 reads as a studio that listens. The list of answers doubles as the changelog for the next version, so the email that opens round three mostly writes itself.
Declined deserves a word of its own. Clients take a clear no far better than a quiet non-change they discover later. If the request is new work, say so there and then, with a price, instead of absorbing it and resenting it for a month.
Late feedback, after sign-off
Feedback will arrive after a version is approved. The printer rings with a question, or the CEO finally opens the link. Treat it as the first comment of a new round against the approved version. The approval stands. The new round gets its own closing date, and if it changes the scope, that is a commercial conversation held with the record open.
Put that date where the client can see it, or the round drifts. The case for dates a client can actually see is in landing dates, not deadlines.
Questions agencies ask about design feedback
How many feedback rounds should a design project include?
Two per deliverable is a sensible default in a proposal, with a price for a third. The number matters less than the definition. A round is one version, one consolidated set of comments and one closing date, and a round limit you have not defined is a limit you cannot hold.
Should clients give design feedback by email or in a review tool?
In a review tool, pinned to the artwork, with email used only to say a round is open. Email is where version confusion starts, because the comment and the file it refers to travel separately and drift apart.
What if the client will not name a feedback owner?
Default it to whoever signed the contract or the purchase order, tell them so in writing, and route every contradiction to them. Most clients nominate someone else within a round.
Who at the agency should reply to client feedback?
The account or project lead. The designer does the work, and the lead owns the list of answers, so the client hears one voice and the designer is never negotiating scope in a comment thread.
Where HoopoeHQ fits
HoopoeHQ runs feedback rounds this way. Each deliverable lives in the client's own workspace with its versions in order and a compare view between them. Feedback is pinned to the artwork on the version it is about, open and resolved comments sit in separate views, and a reviewer can mark their feedback completed or approve from the same screen. My feedback shows everyone what is waiting on whom. More detail is on the reviews page.
If your last round lived across four email threads and a Thursday call, start a 14-day trial and run the next one in one place.