How to set up a client feedback process for your web agency
If you have just inherited a project with a 60-message email thread, three PDFs of scribbles and a Slack channel nobody reads, the cause is usually simple: the agency never set a client feedback process. This guide walks through one an agency can adopt in an afternoon: who sends the review link, how many people review, how long each round runs, who consolidates the comments, and when a round is closed.
Why agency feedback ends up in a mess
Most messy threads have the same history. The designer sent the first link. The developer sent a staging link a week later. The account lead forwarded a PDF to the client's marketing team, who replied to that instead. The client's founder replied to the original email with "looks great, a few thoughts" and four bullet points written against the old version. Nobody said when the round ended, so it didn't.
Everyone involved meant well. The trouble was that nobody owned the round. A client feedback process fixes that by answering five questions before the first link goes out:
- Who sends the review link?
- Who reviews, and who has the final word?
- What is each round for, and when does it end?
- Who sorts and answers the comments?
- What has to be true for a round to be closed?
The steps below answer each one. Write the answers on one page, agree them at kickoff, and the rest of the project gets much quieter.
Step 1: one person sends every review link
Pick one person at the agency to own feedback for the project. On most teams that is the project manager. On smaller studios it might be the account lead or the founder. Their job is simple to describe: every review link the client sees comes from them, and every round starts and ends with an email from them.
That means designers and developers stop sending links directly to the client, even when they are only "quickly checking something". They share with the PM, who decides whether it is ready and which round it belongs to. It feels slower for a day and saves weeks, because the client only ever has one current link and one person to reply to.
Use the same review link for the whole stage if you can, publishing each new version to it. Clients bookmark links and reply to old emails. If the link they find always shows the latest version, they can't comment on last week's design by mistake.
Step 2: agree the reviewers and one client lead
At kickoff, ask the client to name the people who will review the site and, separately, the one person who makes the final call. That person is the client lead. They settle disagreements between their own reviewers and give the approval that closes a round. "The leadership team" can't do this job. If the client says a committee decides, ask who chairs it.
Then keep the active group small. Three to five reviewers per round is workable on most agency projects. Every extra person adds comments to read, opinions to weigh and a chance of someone missing the deadline. People who only care about one area, such as legal checking claims and terms, can review that area alone. People who just want to see progress can be told when a round opens and asked to comment only if something is wrong.
Write the list down and send it to the client lead to confirm:
| Person | Role | Reviews | Approves? |
|---|---|---|---|
| Client lead | Final call on conflicts, approves each round | Whole site | Yes |
| Two to four client reviewers | Comment on their own area | Pages and questions listed in the brief | Only if agreed, for example legal |
| Wider client team | Told when a round opens | Final version, one pass | No |
| Agency PM | Sends links, runs rounds, consolidates | Everything | No |
| Designer and developer | Make the changes, answer technical questions | Comments assigned to them | No |
If the project has a long list of stakeholders, our guide to website feedback from many stakeholders goes further into reviewer briefs and settling conflicts.
Step 3: give each round a purpose and a deadline
A round that has no end date never ends. A round with no stated purpose collects every kind of comment at once, so typo fixes sit next to "should we rethink the homepage?" and the big questions get answered last.
Give each round one job and a window of three to five working days. A pattern that suits many agency projects:
| Round | What it's for | Window |
|---|---|---|
| Round 1 | Structure and message: are the right pages and sections there, in the right order? | 5 working days |
| Round 2 | Wording, images, spacing, the phone layout | 5 working days |
| Round 3 | Final fixes and sign-off | 3 working days |
Put the end date in the email subject line, in the review brief and in the project plan. Count working days, and check for public holidays where the client is based. A deadline that lands on a bank holiday is a deadline that slips.
How many rounds you include is a pricing decision as much as a process one. Our post on website revision rounds covers how to choose the number and write it into the proposal.
Step 4: open the round with a short brief
The email that opens a round sets most of what follows. Send it to the whole review group at once, so everyone can see who else is reviewing. It should say:
- which round this is and what it's for;
- the review link, and that comments go on the page, not in email replies;
- which pages or questions each reviewer should focus on;
- the deadline, with a date and a time;
- who the client lead is, and that they will settle any conflicting comments;
- what happens to notes that arrive after the deadline.
The last two points feel awkward to write and are the ones you will be glad of later. If the rule for late notes is in the opening email, applying it in week three is just following the plan. Our feedback request email templates include a first-round email, a second-round email and a polite chaser you can adapt.
Two days before the deadline, send one short reminder to anyone who hasn't commented yet. Keep it to the link and the date.
Step 5: the PM consolidates every comment
Consolidating is where most processes break. A common habit is to ask the client lead to gather everyone's notes into one document. It sounds tidy, but notes lose their context on the way: "this feels heavy" no longer says which section, and a reviewer's question becomes an instruction.
A better split is to have every reviewer comment directly on the page, then divide the consolidation work:
- The client lead settles conflicts between their own people. If marketing wants a longer homepage and the founder wants a shorter one, the agency shouldn't choose.
- The agency PM reads every comment, replies to each one, and sorts it.
Sorting is quick once you have a small set of categories:
| Type | What to do |
|---|---|
| Clear change, in scope | Reply to confirm, assign to the designer or developer |
| Question | Answer it in the thread, or ask the person who knows |
| Vague or unclear | Ask one specific follow-up question |
| Conflicts with another comment | Summarise both views and tag the client lead for a decision |
| Out of scope or changes approved work | Say so politely, offer a quote or the post-launch list |
| Bug or error on our side | Fix it; it never counts against the round |
Reply to every comment, even if the reply is just "Done in the next version". Reviewers who see their notes answered keep commenting in the right place. Reviewers whose notes vanish start emailing again. For the vague ones, our guide to vague client feedback has follow-up questions that turn "make it pop" into something you can change.
When a decision is made, write it in the thread before you resolve it. A decision that only exists in a phone call tends to come back two rounds later.
Step 6: close the round on clear terms
A round is closed when all of these are true:
- The deadline has passed.
- Every comment has a reply and a category.
- Every conflict has a written decision from the client lead.
- The client lead has either approved this version or asked for changes, and said so on the version itself.
Then the PM sends a short closing email: what will change, what was deferred and why, and when the next version will be ready. Stop taking new comments on that version while the team works, so nobody reviews a page that is about to change.
Late notes will still arrive. Read them straight away. If one points to a real problem, such as a wrong price, a legal issue or a broken form, fix it. If it is a preference, add it to the next round or the post-launch list and tell the person where it went.
The final round closes with sign-off on a specific version. Our client website approval guide covers what a clear approval looks like and what to do when a client goes quiet at the end.
If you have inherited a messy thread
You don't need to read every email and reply to each one in turn. Reset the project instead:
- Tell the client lead you are taking over and will send a single list of open items within two days.
- Go through the thread, attachments and chat once, and copy every open request into one list. Note which version each one was written against.
- Mark items that are already done, items that contradict each other and items that look out of scope.
- Send the list to the client lead and ask them to confirm it, cross out anything no longer wanted, and decide the conflicts.
- Make the agreed changes, then open a fresh round on one review link, with a purpose, a deadline and the rules from the steps above.
After that, if someone emails a note, thank them and add it to the link yourself, then reply with where it is. After a round or two, most people start commenting on the page directly.
Your process on one page
Put the agreed answers into a short document and attach it to the kickoff email. Something like this:
| Question | Our answer |
|---|---|
| Who sends review links? | {PM name}, from one review link per stage |
| Who reviews? | {Client lead} plus up to four named reviewers |
| Who has the final word? | {Client lead} |
| Where do comments go? | On the review link, pinned to the page. Not email or chat. |
| How long is a round? | Five working days, three for the final round |
| Who consolidates? | {PM name} replies to and sorts every comment; {client lead} settles conflicts |
| When does a round close? | Deadline passed, every comment answered, client lead has approved or asked for changes |
| Late notes? | Real problems fixed now; preferences go to the next round |
Keep it as a template and reuse it on every project. When the site launches, the same record of approvals feeds into your website handover checklist.
Where HTMLAnnotate fits
You can run this process with email and a spreadsheet. A feedback tool helps mainly by keeping every comment on the page it is about. Here is what HTMLAnnotate does that maps to the steps above.
- One link per stage. Paste a live or staging address, or upload an HTML file or PDF, and send the review link. Reviewers enter a name and email once and need no account or extension.
- Comments pinned to the page, with a screenshot of what the reviewer saw. Desktop, tablet and phone views keep separate comments.
- Versions on the same link. Publish the next version and earlier versions keep their comments. Free keeps 3 versions per page; paid plans keep unlimited versions.
- Sorting tools for the PM: replies, resolve and reopen, labels, priority, an In progress status, assignees, @mentions and an Inbox of every comment across your projects.
- Approve and Ask for changes on each version, so the client lead closes a round on the version itself. You get an email straight away.
- Pause new comments while you work on changes. Existing comments stay visible.
- On Pro and Team, Slack and webhook alerts, and a shared team list. Paid plans add owner, admin and member roles, and Team holds up to 25 people.
Free covers 1 active project with links that last up to 14 days. Pro is $15 a month for one person and Team is $40 a month for five, or less billed yearly, with links that never expire. The details are on the pricing page.
Questions
Who should send the review link to the client?
One person at the agency, usually the project manager or account lead. Designers and developers should share work with the PM, who sends it on. When several people send links, the client ends up with different versions in different emails and replies to whichever they opened last.
How many client reviewers should a website round have?
As few as possible while still including everyone who could block the launch. Three to five active reviewers is a workable number for most agency projects. Others can be told about the round and asked to comment only on their own area.
How long should a client feedback round last?
Three to five working days suits most rounds. Shorter windows get missed by busy people, and longer ones invite second thoughts and late opinions. Put the end date in the email subject line and in the project plan.
Who consolidates client feedback, the agency or the client?
Both have a part. The client lead settles conflicts between their own reviewers, because only they have the authority to. The agency PM sorts every comment into a change, a question or out of scope, replies to each one, and assigns the work. Asking the client to merge everything into one document tends to lose detail and context.
What should we do with feedback that arrives after a round closes?
Read it straight away. If it is a real problem, such as a wrong price, a legal issue or a broken form, fix it. If it is a preference, add it to the next round or a post-launch list and tell the person where it went.
How do I fix a project that is already stuck in a long email thread?
Pause, list every open request from the thread in one place, send that list to the client lead to confirm, then start a fresh round on one review link with a deadline. From then on, point any new emailed notes back to the link.
Run your next round on one link. Clients click the page to comment, with no account, and approve or ask for changes on each version.
Start a free review