How to structure client feedback on design work

Feedback is where design projects most often lose time. Not because clients are difficult, but because comments arrive in pieces: a message here, an email there, a few notes from a colleague who saw the design for the first time. Each piece can contradict the last, and it's hard to tell when a round of changes is actually finished.

A little structure fixes most of this. This guide covers how to set expectations, a simple format for revision requests, and how to handle changes that fall outside the project.

Set the rules before the first review

The best time to structure feedback is before any design is shown. Agree on three things early, ideally in the proposal and the agreement:

• How many revision rounds are included. A round is one consolidated set of feedback on a deliverable.
• Who sends feedback. One person collects comments from everyone else and sends them together.
• How long feedback takes. For example, "within three working days of each review". Your timeline depends on it.

If these are written down before the first review, you won't have to negotiate them in the middle of a project.

Ask for consolidated rounds

Ask the client to send all feedback on a review in one go. This matters for two reasons.

First, conflicting comments get resolved on the client's side. If the marketing lead wants a bigger headline and the founder wants a smaller one, they decide before it reaches you.

Second, you can make the changes once. Working through a complete list is faster and calmer than reacting to each message as it arrives.

A simple revision request format

A short, consistent form gives every round the same shape. It doesn't need to be complicated.

Write each change as an action

The most useful feedback describes what should change, not just a feeling about the design. Here are some examples of turning vague comments into actionable ones.

You can help clients do this by asking a simple question for each comment: "What would you like to change, and where?"

Use priorities sparingly

Three levels are enough: high, medium and low. High is for things that must change before approval. Low is for things that would be nice if there's time. If everything is marked high, ask the client to choose.

When a request is outside the project

Some requests aren't revisions at all. They're new work: an extra page, a new feature, a change of direction after sign-off. The scope list and the "not included" list in your proposal are how you tell the difference.

When a request falls outside the scope:

1. Acknowledge it. It may be a good idea, and it's worth saying so.
2. Name it. "This is a new page rather than a revision of the agreed design."
3. Offer the options. Quote it as extra work, swap it for something in the current scope, or schedule it for a later phase.

The same applies to rounds. If the project includes two rounds and the client asks for a third, it helps to say so on the request itself, together with the rate you agreed for extra rounds, before you start the work.

Close every round with a clear approval

At the end of each round, ask for an explicit approval: "This round is approved and we can move on to the next phase." A name and a date on the revision request is enough. It turns a stream of comments into a series of decisions, which protects both you and the client.

Common mistakes

• Accepting feedback from several people separately. Ask for one consolidated list.
• Not counting rounds. If rounds aren't tracked, the limit in your agreement doesn't help.
• Fixing comments as they arrive. Wait for the full round unless something is blocking.
• Starting out-of-scope work without saying so. It's much harder to raise afterwards.

Where feedback fits in the project

Structured feedback works best when the goals in your design brief are clear, because you can measure each comment against them. When the final round is approved, the next step is the handoff. See what a website handoff document should include.