Journal

How to run client feedback rounds that actually end

A simple system for collecting, sorting and closing client feedback so design projects move forward instead of looping.

How to run client feedback rounds that actually end

Every designer has had the project that would not end. The first round of feedback is reasonable. The second contradicts the first. By the fourth, a new stakeholder appears with opinions about the logo you finalised a month ago. Nobody is acting in bad faith, but the project slowly turns into unpaid work.

The fix is rarely a stricter contract alone. It is a feedback process that the client understands from day one and that you run the same way every time. Here is the one we use for website and brand projects.

Agree on the number of rounds before you start

Put the number of revision rounds in your proposal, and define what a round means. We write it like this: one round is a single, consolidated set of feedback from the client on one deliverable, followed by one set of changes from us.

Two rounds per major deliverable works for most projects. Three is generous. More than that usually signals that the brief was unclear, which is a problem to fix earlier, not with more rounds.

Also write down what happens after the included rounds: extra rounds are billed at your hourly or day rate, or as a fixed fee per round. Clients rarely object when they see it upfront. They object when they first hear about it in round five.

Name one decision-maker

Most looping projects have several people giving feedback and nobody responsible for the final call. Ask the client to name one person who collects feedback from their side and approves each round.

This does not stop others from commenting. It means their comments reach you already merged, with conflicts resolved by someone who has the authority to resolve them. If the CEO wants to be involved, ask for their input in round one, not round three.

Collect feedback in one place

Feedback that arrives by email, chat, voice note and a quick call is impossible to track. Pick one channel per project and say so in the kickoff:

  • Comments directly on the design, in Figma or on a staging link with a commenting tool, for visual feedback.
  • A shared document for copy and structural feedback.
  • A short call only to clarify feedback that is already written down.

Set a deadline for each round, such as five working days. When the deadline passes, the round is closed and you work with what you have.

Ask better questions when you present

The way you ask for feedback shapes what you get. "What do you think?" invites taste debates. Questions tied to the brief get useful answers:

  1. Does this page make the main offer clear to a first-time visitor?
  2. Is anything factually wrong or missing?
  3. Which parts feel off-brand, and why?
  4. What, if anything, would stop you from approving this?

Present the work live or in a short recorded walkthrough before sending the link. Explaining the reasoning behind decisions heads off a lot of feedback that comes from simply not knowing why something is the way it is.

Sort feedback before you change anything

When a round closes, do not start editing straight away. Go through every comment and sort it into four groups:

  • Fixes: typos, wrong facts, broken links. Do them.
  • Clear improvements: changes that make the work better against the brief. Do them.
  • Questions: comments you do not understand. Ask once, in writing.
  • Out of scope: new pages, new features or changes to approved work. Quote them separately.

Send this sorted list back to the decision-maker before you start. It shows the client you heard everything, and it turns scope conversations into a calm line item instead of an argument.

Push back with reasons, not taste

Sometimes the right answer to feedback is no. When that happens, explain it in terms of the client's goals, not your preferences.

"We can make the headline smaller, but the testing we did on the first draft showed visitors missed the offer when it was below the fold. Can we try a shorter headline instead?"

Offer an alternative whenever you can. Clients accept a no much more easily when it comes with a better yes.

Close every round in writing

At the end of each round, send a short message: what changed, what was moved to a separate quote, and what is now approved. Ask the decision-maker to confirm. That confirmation is what you point to when someone tries to reopen finished work later.

Approved stays approved. If the client wants to revisit something after sign-off, that is a change request, and it goes through the same quote process as any other new work.

Make the process part of your brand

A clear feedback process is not just protection. It is part of what clients are buying. Put a one-page version of it in your onboarding pack, walk through it on the kickoff call, and run it the same way on every project.

Clients who know how feedback works give better feedback. Projects end on time, you get paid for the extra work that does come up, and the relationship survives the project, which is where repeat work and referrals come from.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts