FROM THE CADDY METHOD
Still chasing client feedback? How to get design approvals moving
You stop chasing client feedback by finding where your reviews stall, and that's usually before the work leaves the studio or somewhere inside the client's organisation, well before anyone's attitude comes into it. Fix the ask and the approver first, then let reminders do the smaller job they're good at.
A review without a clear ask, an owner and a date is only a suggestion.
Why does client feedback stall?
Client feedback stalls when the person reading your email can't tell what you need from them, or can't give it to you. Most of the time nobody is ignoring you. The review request said "any feedback?" and left the client to work out what kind. Or it went to the marketing coordinator who loves the work and has no authority to sign it off, so it sits in their inbox while they wait for a meeting with the person who does.
Sometimes three stakeholders reply separately, a day apart, and two of them disagree. Sometimes the design is attached to a long email thread where the latest version is hard to find, so the client opens an older one and comments on that. If nobody agreed a review window at kick-off, there's no date to point to when things go quiet. And on the studio side, the follow-up often depends on someone remembering to send it, which works until the week gets busy.
Here's an illustrative moment, the one on the Caddy homepage: the design is ready, and the feedback is somewhere else. Some of it is in an email and one comment arrived as a text to the designer, which doesn't add up to a decision.
Where do your reviews get stuck? Trace one job
You find where your reviews get stuck by following one real job and writing down what happened at each review. Pick a recent job where you waited longest for feedback. Recent enough that the team remembers the details is better than the most painful one.
For each review on that job, note five things:
- What you sent, how you sent it, and what you asked for. Write down the channel (an email, a link, a file, a call) and copy the exact wording of the ask, because "let us know your thoughts" and "please approve the homepage layout" get very different replies.
- Who received it, and whether they could approve it. If the answer is "they had to check with their boss", you've learnt something useful.
- How long until the first reply, and who it came from. Use your own emails and project records for this. Keep the timings for the team; they're for spotting patterns.
- How many separate replies made up one round, and through how many channels. A round that arrived as four emails, a call and a comment on a file is a different problem from a round that arrived late.
- What finally got it moving. A call, a deadline, someone senior getting involved, or a reminder that happened to land on a good day.
Once it's on one page, look for the patterns that tend to show up. Requests that asked for nothing in particular. Reviewers who could comment but couldn't approve. Rounds that were spread across channels so the studio had to stitch them together before starting. Follow-ups that went out late because nobody owned them. You may find one of these or several, and either way you'll know where your waiting comes from.
This is how we start at Caddy: we trace where reviews get stuck before suggesting a clearer way to share work and agree who signs it off. You can read more about how we approach it.
What should a review request include?
A good review request tells the client exactly what to look at, what decision you need, and by when. Before you hit send, check that it has:
- The exact version and where it lives. A named version, such as "Homepage v3", with one link, so nobody has to dig through the thread.
- The one decision you need. "Approve the layout so we can start on inner pages" is easier to answer than "any feedback?"
- The named approver. The person who can say yes, copied in by name, even if others are reviewing too.
- The date feedback is due. Use the review window you agreed at kick-off.
- What happens to the timeline if it slips. Said plainly and kindly, so it isn't a surprise later.
Here's an illustrative example of what that can look like:
Hi Priya, Homepage v3 is ready for you at the link below. The decision we need is whether the layout works, so we can start building the inner pages. Could you send one combined set of notes from you and Tom by [date]? If we hear back later than that, launch moves by the same amount, and we'll confirm the new date with you.
What counts as one round of feedback?
One round of feedback is one consolidated set of notes, on one version, from one named approver. If three people review the work, they agree their notes between them and the approver sends them through together. If a comment comes in on an older version, it waits for the next round or gets checked against the current one first.
Extra rounds, and new requests disguised as feedback, are where extra work tends to slip into a job. Our guide on how to stop scope creep in a design studio covers what to do when that happens.
What should you do when a client goes quiet?
When a client goes quiet, follow up with something new to say, name what the delay changes, and then pick up the phone. A third "just checking in" email gives the client nothing to act on. A better follow-up adds a specific question ("Is the colour direction the sticking point, or is it timing?") or new information, such as a date the team can no longer hold.
If that doesn't get a reply, say what the delay means for the timeline. Moving the timeline when feedback is late is a fair default, and it's easier to explain if you agreed it at kick-off. Then call. A short conversation often finds the real reason, which is frequently that the approver is away or waiting on someone else inside their business.
Some agency terms pages go further and recommend "silence equals approval" clauses, where work is treated as approved if the client doesn't respond in time. In Australia, standard form contract terms with consumers and small businesses can be unfair contract terms, and the ACCC explains the rules on its contracts and unfair contract terms page. In a 2025 case, the ACCC's media release about the care platform Mable lists, among other terms Mable admitted were unfair, a client's service log being automatically deemed approved unless it was disputed within a set time. If you're considering a deemed-approval clause, get legal advice before you rely on it. This guide isn't legal advice.
What should you change once you know your pattern?
Change the smallest thing that fixes the stall your trace found. If reviews kept going to people who couldn't approve, name one approver at kick-off and write their name in the proposal. If nobody had a date to work to, agree review windows for each stage in the quote. Our guide on design studio proposals covers agreeing those windows as part of the case you send. Our guide on quoting design work faster covers what else belongs in that quote. If feedback arrived through every channel at once, pick one place for it and say so in the first review request.
Versioned links help when clients keep commenting on old files. Scheduling the reminder when you send the review means the follow-up goes out whether or not anyone remembers. Our guide on seeing which jobs need you this week shows how to keep every waiting job, and who it's waiting on, in one weekly list. Where comments still arrive scattered, a simple tool, or AI used to pull every comment on a version into one list, can save the designer from rebuilding the round by hand. Try one change on the next job and keep it if it holds.
Questions studios ask about client feedback
How do you stop chasing clients for feedback?
You stop chasing clients for feedback by fixing the review request and the approver before adding reminders. Trace one job to see where your reviews stall, then send each review with one version, one decision, one named approver and a due date.
How long should a client have to give feedback on design work?
Agree it with the client for each stage at kick-off, because there isn't a single standard. Different studios and guides suggest different windows, so pick ones that suit the job and write them into the quote or proposal.
What should you do when a client goes quiet?
Follow up with a specific question or new information, explain what the delay does to the timeline, and then call. Moving the timeline is a fair default when feedback is late.
Is "silence equals approval" a good clause for an Australian studio?
Be cautious, and get legal advice before relying on one. Unfair contract terms rules apply to standard form contracts with consumers and small businesses, and the ACCC has published a case where an automatically deemed approval term was among those admitted to be unfair.
What counts as one round of feedback?
One round is one consolidated set of notes, on one version, from one named approver. See the scope creep guide for handling extra rounds and new requests.
Bring the job you waited longest on
If a job came to mind while you were reading, start there. Bring it to Caddy's free workflow review and we'll help you see where the review stalled before you change anything.