How to Manage Client Feedback on Website Projects

Last updated: November 18, 2026

To manage client feedback, keep every comment in one list instead of scattered emails. Sort each one as a bug, a change, new work, or a question. Give it one owner and a status. Then close the loop: tell the client what changed, what did not, and why. The list, not the inbox, is the record of the project.

This guide is for agency teams running feedback rounds on websites: the project manager who owns the client, and the designers and developers who make the changes. It covers what happens after the client replies. For what to send before that, see how to ask for client feedback.

Why Client Feedback Gets Messy

The result is familiar: items get missed, some get done twice, new work slips in unpriced, and the launch meeting turns into an argument about what was agreed. Each of these has the same fix. Move every comment into one list, and treat that list as the record.

The Client Feedback Process in 6 Steps

  1. Open the round. Tell the client what to review, by when, and who should review it. A round with an end date gets more useful feedback than an open thread.
  2. Collect every comment in one place. The best place is the page itself: a comment pinned to an element carries its location, so nobody has to describe where “the second button” is.
  3. Merge duplicates and flag conflicts. When two reviewers ask for the same change, keep one item. When they ask for opposite changes, do not choose between them. Ask the client’s approver to decide.
  4. Sort each item. Is it a bug, a change inside the scope, new work, or a question? Is it clear enough to act on? The table below shows what to do with each.
  5. Give each item one owner and a status. The designer takes visual changes, the developer takes bugs and build changes, and the project manager takes questions and anything that needs the client.
  6. Close the loop. When the round ends, send the client a recap of what changed, what did not, and why. Then ask them to confirm the round is finished.

How to Sort Client Feedback

NN/g suggests sorting design feedback into three groups: to do (feedback you agree with and can act on now), to persuade (feedback you disagree with, which needs a case), and to clarify (feedback you need more information on before you can move). On client work, add one more question: is this inside the agreed scope?

Kind of feedbackWhat it sounds likeWhat to do
Bug“The form does not send.”Fix it. It does not use a revision round.
Change in scope“Make the hero image taller.”Do it in this round.
New work“Can we add a careers page?”Reply with the time and cost and wait for a yes. See how to handle scope creep.
Question“Will this work on my phone?”Answer it, after you have checked.
Needs clarifying“It feels cluttered.”Ask one question to find the cause. See these client feedback examples.
Needs persuading“Make the logo much bigger.”Explain in writing why the current size works, and offer another way to meet the goal.

Some comments are not about this round at all: an idea for next year, a question about hosting, a thought on the brand. Keep them in a separate parking lot so they are recorded without slowing the round down.

Who Owns Client Feedback

RoleOwns
Project or account managerOpening and closing rounds, sorting, every message to the client, and change requests
DesignerVisual changes, and the case for anything in the persuade group
DeveloperBugs, build changes, and checks on real devices
Client approverSettling conflicts between their own reviewers, and confirming each round is finished

One person on the agency side should talk to the client about feedback, even when several people do the work. Clients get consistent answers, and the team does not reply to the same comment three different ways. The client approver matters just as much; our guide to review and approval workflows covers how to set one up.

How to Close the Loop With the Client

NN/g’s guide to closing the loop argues that feedback is valuable only if someone tells people what changed because of what they said, what did not change, and why. It suggests a short recap right after a review: “Here’s what we’re moving forward with, what we’re still investigating, and what we’ve decided not to pursue.”

For anything you did not act on, NN/g uses four parts: name the feedback, state the decision, give the reason, and say what happens next. For example:

Note: Name the feedback: You asked for a much bigger logo in the header.
State the decision: We kept it close to its current size.
Give the reason: At twice the size, it pushes the menu onto two lines on laptop screens.
Say what happens next: We made it 20% larger and gave it more space on each side, so it stands out without moving the menu.

Clients who see that every comment was read keep giving careful feedback. Clients who hear nothing learn to stop, or to repeat themselves louder in the next round.

How to Handle Difficult Client Feedback

Tools for Managing Client Feedback

A shared spreadsheet works for one small site: one row per comment, with columns for page, type, owner, status, and decision. It breaks when comments need screenshots, when several people edit at once, and when developer work lives in a separate tracker. Website feedback tools solve the first problem by letting clients comment on the page itself; our roundup of website feedback tools compares them.

In OverlayQA, clients open a review link and comment on the live site with no account or extension, and can reply to the team. Each comment arrives as an issue with a screenshot, the page address, browser, and screen size. The team sets its type (Bug, Mismatch, Improvement, or General), assigns an owner, adds labels, and moves it from Open to Resolved, and the issue can sync both ways with Jira, Linear, Asana, Trello, and other trackers. When the client clicks Done reviewing, the team sees who signed off on the round.

Frequently Asked Questions

How do you manage client feedback on a website project?

Run feedback in rounds with an end date, collect every comment in one list, sort each one as a bug, a change, new work, or a question, give it an owner and a status, and send the client a recap of what changed and what did not when the round ends.

How do you consolidate feedback from several stakeholders?

Put every reviewer’s comments in the same list, merge the duplicates, and mark the conflicts. Then ask the client’s approver to settle each conflict, rather than choosing between their colleagues yourself.

What is a client feedback loop?

It is the cycle of asking for feedback, acting on it, and telling the client what happened to it. The loop is closed only when the client hears back about each comment, including the ones you did not act on.

Should clients have access to our issue tracker?

Usually not. A tracker is built for the team: internal notes, estimates, and developer detail. Give clients a simple way to comment on the page and see replies, and let those comments flow into the tracker for the team.

How do you handle negative client feedback?

Thank them, then ask what the change is meant to achieve. Negative feedback usually points to a specific cause, such as one image, one color, or the order of sections, and one question is often enough to find it.

What should you do with feedback you will not act on?

Tell the client, in writing. Name the feedback, state the decision, give the reason, and say what happens next. Leaving it unanswered costs more trust than declining it.

Replace the feedback inbox with one list. With OverlayQA, clients comment on the page with no account, and each comment becomes a tracked issue with an owner, a status, and the screenshot attached.