Client Feedback

Client feedback is not just “comments on a draft.” In agency work, it is the structured review input that tells the team whether to refine, revise, or close a deliverable. When feedback is clear and consolidated, work moves. When it is scattered across calls, screenshots, and email threads, the project slows down and the team starts guessing which version of reality is current.

That is why feedback has to be treated as a workflow, not as a courtesy. The agency needs one submission channel, one review deadline, and one record of what changed between rounds. Otherwise feedback becomes a moving target, and no one can tell whether the work is actually getting better or just reacting to the loudest comment of the day.

The goal is not to make feedback rigid. It is to make it actionable. Agencies need enough structure that revision rounds stay finite and approvals remain meaningful.

Strong feedback systems are simple. The agency shares work in one place, the client responds through one place, the comments get consolidated by one owner, and the agency closes the round with either an approval or a clearly scoped revision list.

Agencies get into trouble when feedback and approval are treated like the same thing. They are not. Feedback keeps the round open. Approval closes it. If the work can still be changed without a new request, it is not approved yet.

This distinction matters because unclear approvals create rework. A client says the design “looks great,” then comes back a week later with two more stakeholders and a fresh batch of comments. Without a clean approval record, the team has little ground to stand on.

That is why teams benefit from using a content approval workflow or another structured review system. It gives feedback a place to live and gives approvals a timestamp that both sides can point back to later.

Healthy revision rounds are bounded. The agency defines how many are included, what counts as one round, and when a round starts. Usually that means one consolidated response from the client, delivered by a deadline, against one draft.

That structure prevents three common problems: rolling feedback, hidden stakeholder input, and late changes framed as “small comments.” All three create extra work without ever being called a new round.

Not every requested change belongs inside the feedback loop. Some requests alter the direction, quantity, or commercial assumptions of the work. That is no longer revision feedback. That is scope change.

The easiest test is to compare the request against the agreed creative brief and scope. If the client is asking the agency to refine something that already belongs in the brief, that is feedback. If the client is asking for a different deliverable, a new concept, new channels, or a strategic shift, the correct response is usually a change order.

Agencies that do not make that distinction early end up treating scope expansion like “being helpful,” then discover later that the project timeline and margin have both slipped.