Flawsnap
Free trial

How to collect client feedback on a website without the chaos

A review process for agencies and freelancers, with a brief you can send to clients today.

To collect client feedback on a website, give clients one place to leave it, ideally a feedback button on the staging site that captures a screenshot and the page automatically. Send a short brief explaining what to review and how, run feedback in fixed rounds, triage every comment into fix, discuss or later, and tell clients what changed.

Why feedback by email goes wrong

A typical round of client feedback arrives as an email with twelve numbered points, two screenshots from a phone, a voice note and a message in a chat app saying "also the logo". Half the points do not say which page they mean. Two contradict each other. One is about a page that has already changed.

The cost is not the fixes. It is the time spent working out what each comment means, and the risk of missing one. A good process fixes the channel first and the content second.

The process, step by step

  1. 1

    Choose one channel and refuse the others politely

    Whatever you pick, every comment goes there. If feedback arrives by email, copy it in yourself and reply with the link, so clients see where it lives.

  2. 2

    Put the site where the client can review it safely

    Use a staging site with realistic content. Let clients click everything, including forms, without affecting a live site.

  3. 3

    Make feedback point at the page

    The most useful comment is attached to a place on the screen. A feedback widget lets the client circle the problem and sends the URL, browser and screen size with it, which answers most follow-up questions before you ask them.

  4. 4

    Send a short brief

    Tell clients what to look at in this round, what not to worry about yet, and how to leave a comment. A template is below.

  5. 5

    Run fixed rounds with dates

    Open a round, collect for a set period, close it, then work through everything. Continuous trickle feedback makes it impossible to finish anything.

  6. 6

    Triage every comment

    Sort each one into fix now, needs discussion or later / out of scope. Reply to discussion items with a question rather than guessing.

  7. 7

    Close the loop

    When a round is done, send a short summary: what was fixed, what was not and why, and when the next round opens.

A brief you can send to clients

Email to client: how to leave feedback
Subject: The new site is ready for your review (round 1)

Hi [name],

The new site is ready to review at [staging URL].

This round, please look at:
- The home, services and contact pages
- Wording, images and anything that looks broken

Please don't worry about yet:
- The blog (content is still placeholder)
- Final colours on buttons

How to leave feedback:
1. Go to the page with the problem.
2. Click the "Report a bug" button in the corner.
3. Draw a box around the problem and add a short note.
4. Send. It comes straight to us with the page details.

One comment per issue makes it easier for us to track.
This round closes on [date]. We'll send a summary of
changes by [date].

Thanks,
[your name]

Triage rules that keep projects on budget

  • Content changes (text, images) are usually quick. Batch them.
  • Bugs (something does not work as agreed) are fixed within the project.
  • Design opinions ("can it feel more modern?") need a conversation before any work. Ask what they would like to see, with an example.
  • New features are change requests. Log them separately and quote for them.
  • Conflicting comments from two people at the client go back to their decision-maker. Do not choose for them.

Making it easy for non-technical clients

Clients are not testers. Do not ask them for browser versions or console errors. Ask what they were trying to do and what looked wrong, and let the tool capture the rest. Avoid anything that needs an install or an account, because that is where many clients give up and go back to email.

With Flawsnap, clients use a button on the site and do not need an account. Add the staging domain to the project's allowed domains, and the project's categories can route comments to design, frontend or backend. See agency client feedback.

Mistakes to avoid

  • Asking for "any feedback" without saying what is ready to review.
  • Leaving rounds open-ended, so feedback never stops.
  • Fixing comments silently without telling the client.
  • Sharing the production admin login so clients can "just change it".
  • Treating every comment as a must-fix, which turns scope into a moving target.

Questions

How many feedback rounds should a website project have?
Agree the number in the contract before work starts. Two or three structured rounds are common for a small website, with a final check before launch. Anything beyond the agreed rounds is billed as extra work.
Should clients review on desktop or mobile?
Both, if their visitors use both. Ask clients to say which device they used, or use a tool that records it automatically, because many layout issues only appear at one screen size.
What if the client keeps sending feedback by email anyway?
Copy each email comment into your feedback channel yourself and reply with the link. After a round or two, most clients switch to the channel because they can see their comments being tracked.
Can I collect feedback on a site I cannot add code to?
Not with a widget, which needs its script on the page. Use a browser extension or screenshots in that case. Flawsnap's Chrome extension, for Chrome, Edge and Brave, does that for your team.

Try it on your own site

7-day free trial, then $9 a month for Starter or $19 for Pro, per organization, with unlimited team members.

Start free trial Try the live demo

Related

Updated