A client feedback process for agencies, from kickoff to sign-off

Most revision pain is not caused by picky clients. It comes from a process nobody wrote down: feedback in five places, from six people, with no deadline and no finish line.

By the VeoRec team · Oct 3, 2026 · 12 min read

A client feedback process is the set of rules for how a client reviews your work: who looks, when, where they write, what counts as one round and how the project ends. Agencies that skip it still have a process. It is just an accidental one, where the marketing lead emails, the founder texts, the sales director comments in Figma a week late, and round two quietly becomes round five.

The deliberate version is mostly a handful of sentences written down early: in the proposal, at kickoff, in each round email and at sign-off. The examples come from website and brand projects at small agencies and freelance studios, but copy, video and campaign work run on the same rules. Every piece of wording below is in a template you can copy.

Why a client feedback process breaks down (it is rarely the client)

Look back at the last project that ran over. The extra rounds probably came from one of four places, and none of them is "the client has bad taste".

• Unclear rounds. The proposal said "two rounds of revisions" and never said what a round is, so every email became a round.
• Too many voices. Three people reviewed separately and their notes contradicted each other, so you designed a compromise that pleased nobody and went again.
• Scattered channels. Notes lived in email, Slack, a call and a PDF with sticky notes. Something got missed, the client noticed, and trust dropped a notch.
• No finish line. Nobody ever said "approved", so a "small tweak" arrived two weeks after launch.

Each of these has a structural fix. None of them needs you to be firmer on calls or better at saying no in the moment. The work happens before the first review, in writing, when everyone is still friendly and nobody is defending a design.

Define one round of feedback before kickoff

The single most useful sentence in an agency contract is the definition of a round. Without it, "two rounds included" means whatever the most frustrated person on the call needs it to mean.

A workable definition has four parts: one consolidated set of feedback, from the agreed review group, in the agreed channel, delivered by a date. Anything that arrives after the date belongs to the next round. A comment from someone outside the group goes back to the consolidator, not into your task list.

You are in good company here. The AIGA Standard Form of Agreement for Design Services, the professional association's model contract for design work, advises that the proposal spell out for each phase what is included, including the number of revisions or refinements, and that requests outside the original scope get a change order: a short document that describes the extra time and money and goes to the client for signature. It also covers client responsibilities and acceptance within a set period, which you will use below.

Then say the definition out loud at kickoff, and repeat it in your client onboarding videos. Clients skim proposals. They remember the person who said, in the first meeting, "Here is how reviews work so you never have to wonder what happens next." Framed as a service, the rule lands as care, not as a fence.

Ask the client to name one consolidator

Contradictory feedback is the most expensive kind. If the marketing lead wants the hero photo bigger and the founder wants it gone, you cannot resolve that from the outside. You can only guess, and every guess costs a round.

So ask, in the proposal and again at kickoff, for one person on the client side who collects everyone's notes, settles disagreements internally, and sends one consolidated list. That person does not need to be senior. They need to be organised and to have the authority (or the access) to get a decision from whoever does.

Map the people early. A short table in the kickoff doc saves a painful conversation in week four, when a director you have never met appears with opinions about the logo.

Watch for the hidden approver: the person who "just wants to see it before it goes live". Ask directly at kickoff whether anyone outside the group could block launch. If the answer is yes, put them in the group now, when their opinion is cheap, rather than at the end, when it costs a rebuild.

When the client cannot name a consolidator

Some clients push back: "We are a committee, everyone needs a say." That is fine. A committee can still produce one list. Suggest they hold a 30 minute internal review for each round, with your walkthrough playing on the screen, and send the agreed notes afterwards. The meeting is theirs, not yours, and it forces the disagreements to happen in their room instead of in your inbox.

With a sole founder, the founder is the consolidator. The risk there is different: feedback arrives in bursts, late at night, from a phone. The fix is the channel and the window, covered next, not another person.

Pick one feedback channel and close the others

Feedback that arrives in five places gets lost in at least one of them. Choose a single home for review comments and make it the only place a note counts.

What that home is matters less than the rule. It can be a shared doc, your project tool, comments in the design file, or comments on a recorded walkthrough. The best choice is the one where a note sits next to the thing it is about, because "the button on the second section" is ambiguous in an email and obvious when it is pinned to the button.

When a note arrives somewhere else, do not quietly act on it. Move it, and say so kindly: "Thanks, I have added this to the review thread so it does not get lost. Could you add any others there too?" Two or three of those and the habit sticks. Acting on stray messages teaches the client that the rule is optional.

Calls are fine for discussion, but a call is not a channel. Whatever was decided on the call gets written into the thread by you, the same day, with a line asking the client to correct anything you misheard.

Present the work so feedback has a target

Sending a link with "Let us know what you think" invites opinions on everything, including things that were settled in round one. The quality of the feedback you get depends heavily on the question you ask.

Every round should come with a short presentation that does three jobs. It reminds the client of the goal ("visitors should understand the pricing in ten seconds"). It shows what changed since last time and why. And it names the two or three decisions you need from them now, while saying what is already settled and should not be reopened.

A three to five minute recorded walkthrough does this better than a meeting for most rounds. The consolidator can watch it when they have time, pause on a section, and share the same link with the founder so everyone hears the same explanation instead of the consolidator's summary of it. With VeoRec for agencies you record the tab with your voice and camera, the link is copied when you stop, and the client watches in the browser without an account. The guide to presenting design work async covers the structure in more detail.

A walkthrough for a round of website design might run like this:

1. The goal, in one sentence. "This page has one job: get a visitor from the ad to a booked demo."
2. What changed since last round, and why. Walk the notes in the order the client sent them, so they can tick them off.
3. What is new. Anything you added that they have not seen, with the reason.
4. The decisions you need. Two or three, phrased as choices: "monthly or yearly prices first?"
5. What is settled. Name it so nobody reopens it by accident.
6. The deadline and the channel. "Notes to me in the review thread by Thursday."

Keep live review meetings for the moments that need them: the first concept presentation, a direction change, or a round where the feedback contradicted itself and needs a conversation.

Ask for feedback in a shape you can act on

"Make it pop" usually comes from a client who has never been told what useful feedback looks like. Tell them, once, early, and give them a format.

Three requests do most of the work. Ask them to point at a place (this heading, this card, 0:42 in the video). Ask them to describe the problem, not the fix ("I cannot tell which plan is recommended" beats "make the middle card orange"). And ask them to mark priority: must change, should change, or just a thought. That last one alone can shrink a round noticeably, because many notes turn out to be thoughts.

Pinning notes to the element matters more on websites than anywhere else, because layouts move. A note stuck to a pixel position on a desktop screenshot points at nothing once the page reflows on a phone. Try the difference here.

These templates cover the moments where wording matters most: the line in the proposal, the request that goes out with each round, the format you ask the consolidator to use, and the sign-off.

Set review windows and say what silence means

A round without a deadline is not a round. It is an open invitation. Agree on a review window at kickoff, usually three to five business days for a design round, and put the actual date in every round email rather than "next week".

Agree two more things while everyone is calm. First, what happens if feedback is late: the schedule moves by the same number of days, because your team was booked for that week. The AIGA guide notes that most design firms specify a day-for-day extension of the final deadline when a client causes a lengthy delay. Second, what silence means. Its guidance on acceptance is that delivered work counts as accepted unless the client objects within a set period, often 5 to 10 days. You may not want to lean on that for creative rounds, but you do want to agree up front what happens when nobody answers.

In practice, the best tool against late feedback is a reminder that is easy to act on. Two days before the window closes, send a short note with the link and the one or two open decisions. People are rarely refusing to give feedback. They are busy, and your email is the fifth thing on their list.

What a late round does to the calendar

Make the cost of lateness concrete for yourself before you explain it to a client. Say round two goes out on Monday the 3rd with a five-business-day window, so notes are due Friday the 7th. Your designer is booked for the revisions on the 10th and 11th, and the build starts on the 14th.

The notes arrive on Wednesday the 12th instead: three business days late. Under a day-for-day clause the build start moves three business days, from Friday the 14th to Wednesday the 19th, and launch moves with it. That is the easy part. The harder part is that your designer's two booked days have passed, so the revisions now compete with whatever they picked up instead. Telling the client on Friday the 7th, the day the window closes, "we have not received notes yet, so the build moves back a day for every business day they are late", is much kinder than revealing it at launch. When the notes do arrive, confirm the new dates in writing, in the same calm tone you used at kickoff.

Turn feedback into a change list and resolve it in the open

When the consolidated list arrives, sort every note before anyone opens a design file. Sorting is where you protect the scope without arguing about it.

Then work through the list where the client can see it. A thread marked resolved, with a short reply ("Done: footer number updated in v2.3"), tells the consolidator exactly what changed and saves them from checking every note by hand. In VeoRec, review comments are timestamped, can be pinned to a point on the frame, take threaded replies, and can be marked resolved; a folder review link puts every recording of the project behind one URL, view-only or open for comments.

Record the next round's walkthrough so it opens with the change list: "You asked for six things, here they are in order." Clients relax when they can see every note answered before they look at anything new.

When round one turns into a new direction

Sometimes the first round comes back with "we have rethought the positioning" or "the board wants it to feel more premium". That is a different brief, not a long list of refinements, and treating it as round one of two sets up a project that runs out of rounds before it starts.

Call it what it is, kindly and quickly. Book a short call, confirm the new direction in writing, and send a revised scope or a change order that resets the rounds for the new concept. Clients usually accept this when you raise it the day the feedback arrives. They resent it when it appears three rounds later as an invoice.

Get a sign-off that holds

An approval is only useful if it names a specific version. "Looks great!" in a chat thread is a compliment. "Approved: homepage v2.3" in the agreed channel is a sign-off.

Ask for it explicitly, every phase, with the sign-off message from the templates above. Then save it with the version it refers to: the link, the date and who approved. If a request arrives after approval, you are not saying no. You are saying "Happy to, here is the change request", and pointing to the agreed process instead of to your patience.

You are not refusing the late change. You are pricing it, and the process you both agreed to is what makes that feel fair.

One more habit: at sign-off, ask the client what made reviews easy or hard this time. Two minutes of honest answers will improve the next project more than any template.

Collect client feedback on the work itself Record a walkthrough, send one link, and let clients leave timestamped notes you can resolve one by one. Free plan included. See VeoRec for agencies

What to do before your next project starts

You do not need new software to start. You need the decisions written down before the first review. Use this list on the next proposal and tick each item as it goes into the document or the kickoff agenda.

If revision rounds are already the problem on a live project, the companion guide on how to reduce revision rounds works upstream of this one: briefs, presentation and scope. Fix the process here, fix the inputs there, and most projects finish in the number of rounds you quoted.