If you build websites for clients, you know the review email. It arrives three days late, it's a numbered list with no page names, item four says "the thing we talked about," and item seven contradicts item two.
Then the replies start. Which page? Which button? On your phone or your laptop? By the end you've spent more time understanding the feedback than acting on it.
Client reviews don't have to work this way. Most of the pain comes from three problems: feedback arrives in the wrong place, without context, and without a deadline. Fix those and a review round can take a day instead of two weeks.
1. Set up one place for feedback
Before you send the review link, decide where feedback goes, and make it the only place.
The best place is the site itself. Install a feedback widget on the staging or preview site so the client can comment directly on the page they're looking at. Every comment is tied to a page and an element, so "the thing on the about page" becomes a dot on a specific heading.
If a client sends feedback by email anyway, move it into the same place yourself. One list is easier to work through than five threads.
2. Send a short brief with the link
A review link with no instructions gets you scattered feedback. A short brief gets you focused feedback. Include:
- What to review. "The home, about, and contact pages" beats "the site."
- What not to review yet. If the blog is still placeholder content, say so, or you'll get ten comments about it.
- How to leave feedback. One sentence: "Click the feedback button in the corner, click on anything you want changed, and leave a note."
- The deadline. A specific date and time.
- Who decides. If three people at the client will review, ask them to agree on one person who makes final calls.
3. Ask for the kind of feedback you need
Clients are often unsure what kind of feedback is helpful, so they comment on everything or nothing. Tell them what you're looking for this round:
- Round one: structure and content. Is anything missing? Is anything wrong?
- Round two: design and polish. Does it look and feel right?
- Final round: bugs only. Anything broken, anything that doesn't work on their device.
Separating rounds this way keeps you from redesigning a page in the same week you're fixing typos on it.
4. Triage before you touch anything
When the deadline passes, go through every comment before changing anything. For each one, decide:
- Do it. Clear, in scope, and agreed.
- Ask. Unclear or conflicting. Batch these into one message.
- Not this round. Out of scope or a bigger change. Note it and say so.
Answering all the questions at once, in one message, is the single biggest time saver in a client review.
5. Close each item visibly
As you finish each change, mark it done and let the client see it. A status on each comment, like In Progress or Done, saves the "did you get to my feedback?" email entirely.
At the end of the round, send one summary: what changed, what's waiting on them, and what's moved to a later phase.
Why context changes everything
The quiet benefit of on-page feedback is technical context. When a client says "the form doesn't work," you also get their browser, screen size, the page URL, and any console errors. Half the time, "doesn't work" turns out to be one specific phone, and you can see that in the report instead of finding out a week later.
Next Wednesday: how to turn a bug report into a prompt your AI coding assistant can actually use.