5 methods
Compared honestly — including where each one loses information.
11 questions
The checks clients are qualified to make. Copy them into your request.
1 email
The feedback request with link, guidance and deadline — ready to send.
Where each collection method loses information
Every method transports feedback — the question is how much context survives the trip.
Email loses the location (“the banner further down”) and the environment (which device?). Spreadsheets add structure but stay blind — a row can’t point. Meetings produce rich reactions and no record; two weeks later the project runs on memory. Annotated screenshots keep the location but freeze one viewport and one moment. Pinned feedback on the live page keeps location, page, device and browser automatically — the only method where the comment arrives carrying its own context.
The open ask
“Have a look and send us your thoughts”
- Feedback arrives as taste, not as findings
- Locations described, environments unknown
- Trickles in over weeks, across channels
- No defined end — the round never closes
The structured ask
Link + 11 questions + deadline
- The client checks what they’re qualified to judge
- Comments pinned to the exact element
- One round, one deadline, one list
- Late wishes move to the next round — announced upfront
What to ask your client to check
Clients can’t judge kerning — they can judge their business, their customers and their phone. These questions aim exactly there.
The client’s review checklist
- Does the headline say what we do — would a stranger get it in 5 seconds?
- Is anything factually wrong: names, prices, dates, claims?
- Which page did you expect to find that you didn’t?
- Where did you hesitate or feel lost while clicking through?
- Does the tone sound like us — where does it slip?
- On your phone: does anything look broken or feel clumsy?
- Is the main action (contact, booking, purchase) obvious on every page?
- Which image or section feels off-brand — and off how?
- What would a skeptical customer object to that we don’t answer?
- Is anything missing that you promised your own customers?
- If you could change only ONE thing before launch — what?
The feedback request that starts a round
Link, guidance, deadline — three sentences of structure that save a week of chasing.
Subject: Your review round for [project] — until [date] Hi [name], the new site is ready for your review: [review link] Three things that make this fast: 1. Please click directly on the spot you mean and leave your comment there — no need to describe locations. 2. Check it once on your phone too; that's where most visitors will see it. 3. The round runs until [date]. Everything that reaches us by then goes into this revision — later wishes move to the next round. If something is unclear, reply here. Otherwise: the link is all you need, no account, no installation. Thanks! [signature]
The sentence that does the heavy lifting
The collecting, done for you
Send one bepeq link instead: your client comments directly on the live page — desktop and mobile, no login — and the Pilot asks clarifying follow-ups on vague notes while they’re still there. The round has a deadline, and everything lands in one list.
Start bepeq for freeClient
“Not sure about the section up top.”
✦ bepeq Pilot asks back
What exactly bothers you: color, image or text?
Hero image brighter, headline higher contrast.
readyRelated guides
Common questions about collecting feedback
How do I collect website feedback from clients?
Three ingredients: a method that anchors comments to the page (a review link where the client clicks the exact element), a short list of guiding questions so the client knows what to look at, and a deadline that turns “whenever” into a round. The email template on this page combines all three.
What’s the best method to collect website feedback?
Compared honestly: email describes locations and loses context; spreadsheets structure text but stay blind; meetings produce opinions without records; annotated screenshots freeze one viewport. Pinned feedback on the live page keeps location, device and page context automatically — which is why it produces the fewest follow-up questions per comment.
What questions should I ask when requesting feedback?
Ask for verdicts on specifics, not general impressions: facts (names, prices), findability (which page did you miss?), the mobile experience, the main action’s clarity, and the one-thing-before-launch question. The 11 questions on this page cover the checks clients are actually qualified to make — they know their business, not design theory.
How do I stop feedback from trickling in for weeks?
Set a round with a named end date and say what happens to late input — it moves to the next round, it doesn’t block this one. Trickle feedback isn’t a client flaw; it’s the default behavior when no structure says otherwise. One deadline sentence in the request email fixes most of it.