GUIDE

How to get clear client feedback on a website, not a 40-email thread.

Clear feedback is not about asking clients to write less. It is about giving them one place, one deadline and one decision to make.

Why website feedback goes wrong

A website review often pulls in people who were not in the briefing. Their comments arrive in email, chat messages, screen captures and calls. The team then has to guess which version each comment refers to and whether the client team has agreed internally.

The fix is a process, not another spreadsheet. Give the client a simple route to comment, define who consolidates the feedback and close the round when that feedback is complete.

Ask for feedback pinned to the page

A page-specific note gives the delivery team a location, a request and often enough visual context to act. Encourage clients to describe the desired outcome, rather than prescribing a technical fix they cannot see.

If a note changes the agreed direction, identify it early. It may be valid, but it should be treated as a new decision rather than quietly folded into a final round.

Turn feedback into tasks

Triage notes with the project owner. Group duplicate feedback, clarify vague requests and identify anything that needs a client decision before implementation. The goal is not to create more administration, it is to remove rework.

Keep the source of truth close to the review. When a client asks what changed, you should be able to point from the note to the completed task and then to the version ready for approval.

Make the process repeatable

The useful part of a review process is that it removes small decisions from the project manager’s day. Give every client the same starting note, the same review deadline and the same definition of a completed round. Repeat the language in proposals, kickoff notes and review reminders. The client then understands that the process is a normal part of delivery, not a rule invented for a single difficult project.

Name one person on each side to consolidate feedback. They do not need to write every note, but they should confirm that the list represents the people who need to sign off. If several stakeholders contribute directly, ask the nominated owner to resolve conflicting requests before the agency begins another version. This protects the relationship as much as the margin because the client sees the decision happening inside their team, rather than receiving competing work from yours.

Keep a short project record after each round: the version reviewed, the deadline, the agreed list, the changes delivered and the next decision. It makes handover easier when a team member is away, gives the client a clear answer when they ask what changed, and avoids the familiar problem of reopening an old email chain. A record is not bureaucracy for its own sake. It is the evidence that turns a vague request into a completed piece of work.

When a client asks for a change outside the agreed round, acknowledge it before estimating it. Explain whether it is a correction, a deferred launch item or a new request. Give a price and a delivery date where appropriate. The client is much more likely to accept an extra cost when it is connected to a visible choice and a clear outcome, rather than appearing as an unexplained invoice after the work is done.

Before the first review, send the client a short note that answers four practical questions: what they are reviewing, who should collect internal feedback, when the response is due and what happens after they submit it. Keep the note close to the project link. If a client can find the rules without searching an old email, they are more likely to use the process well. It also gives your project team one consistent explanation when a new stakeholder joins late.

After each version, close the loop in the same format. Name the version, summarise the material changes, state whether the next step is another review or approval, and include the date by which a decision is needed. A simple update makes progress visible and stops clients treating a delivered version as an invitation to restart the conversation. It gives the agency a fair record if a schedule or scope question arises later.

Related reading