One link
All feedback in one place, pinned to the element.
No account
Clients respond with no login.
7 steps
From the first note to a documented sign-off.
What is website feedback?
We mean client feedback during the build, not the user feedback of later visitors.
Website feedback is any structured response to a website in progress: your client’s notes on copy, images, layout and function before the site goes live. It’s distinct from the user feedback of later visitors, which is about the usability of the finished site. This guide covers the first case, because that’s where the most time and nerves are lost.
Good website feedback has three properties: it’s tied to a specific element, it’s concretely worded, and it’s collected in one place. Miss one of those and you get room for interpretation, and one planned round becomes three.
The most common website feedback mistakes
Six patterns that show up in almost every stalled web project.
Feedback across too many channels
Email, phone, chat and PDF at once. Nothing is central, everything has to be pieced together.
No fixed contact
Five people give contradictory feedback and no one decides what actually counts.
Taste questions, not goal questions
“I don’t like it” with no direction can’t be acted on and leads straight to the next round.
Unclear location
Descriptions like “the button in the top right” cause mix-ups and follow-up questions.
No defined end
With no agreed round count and no documented sign-off, the loop just keeps spinning.
Feedback on a drip
Individual notes scattered through the day wreck your flow and create moving targets.
How to collect website feedback: 7 steps
This flow is proven in practice and works with any capable tool. What matters is the consistency with which you apply it.
- 1
Name one responsible contact
Have the client appoint a single point of contact who bundles internal feedback, filters it and resolves contradictions first. That way no conflicting notes from five departments land on you.
- 2
Set the feedback frame up front
Define how many revision rounds are included, by when feedback is expected and in what scope. One or two thorough rounds per project phase is the usual standard.
- 3
Ask targeted questions, not taste questions
Don’t ask “Do you like it?”, ask “Does this homepage reach your audience?”. That steers the response toward goals instead of personal taste.
- 4
Collect feedback on the object itself
Let feedback happen where it belongs: right on the live page, on the element in question. That kills ambiguous descriptions like “the button up top” and saves follow-up questions.
- 5
Keep notes concrete and per section
Every comment should say what exactly should change and what result is expected. Concrete feedback per section prevents misinterpretation and rework.
- 6
Implement and show it back visibly
Work through the points in a batch and mark each as done. The client sees at a glance what was taken on and doesn’t have to guess whether their point landed.
- 7
Document the sign-off
Close every phase with a clear approval and record it in writing. That protects both sides and ends the round cleanly.
The step that matters most
Visual feedback on the live page
Instead of describing which element they mean, the client clicks the element on the real page and leaves a comment right there. Every note is unambiguously located, and you see the context at once: which page, which element, which screen state.
That replaces the classic screenshot round of downloading images, adding arrows and sending them back. The time saved is significant, and the notes are more precise.
Feedback with no login raises the response rate
Every extra hurdle costs participation. If a client has to create an account, set a password and confirm an email before leaving a single comment, noticeably fewer people respond. A feedback link that works with no login drops that hurdle to zero.
Field tip
Client · Home
“The headline is too faint, and the button could be bolder.”
Shorten revision loops instead of spinning them
Revision loops can’t be abolished, but they can be shortened sharply. Three levers work hardest.
Agree the round count up front
Put the number of included rounds in the proposal. Extra rounds become a normal, billable event instead of a fight.
Bundle feedback, don’t drip it
Ask for collected feedback per round. That protects your flow and prevents contradictory interim states.
Make progress visible
Mark done points as done. When the client sees their point landed, the follow-up question disappears and trust grows.
From feedback to a binding sign-off
Feedback is only half the job. Only the binding sign-off ends a phase cleanly and protects both sides.
A solid sign-off records which version was approved, when and by whom, ideally with a timestamp and a documented record as a PDF. A traceable sign-off is your evidence if there’s ever a dispute over scope or rework.
The sign-off writes itself
When the client closes the round, bepeq generates a sign-off record as a PDF: with a timestamp, the approved version and any open points. On your agency’s brand if you want.
Try the sign-off with bepeqSign-off record generated automatically
Version: staging.clientsite.com
Jul 8, 2026 · 2:32 PM · IP recorded
2 open points (category B) with a deadline
Choosing the right feedback tool
The right tool takes the coordination off your plate. bepeq is built for exactly these points: feedback happens on the live page, clients need no account, rounds stay traceable, and the sign-off is documented as a PDF.
All 12 criteria as a checklistWhat to look for
- Visual feedback right on the live page, not just on screenshots.
- Client access with no login.
- Clear separation of revision rounds and a traceable history.
- Binding sign-off with a documented record.
- Data processing in the EU.
- An interface a non-technical client understands immediately.
The individual steps in detail
This guide is the overview. Each stage has a practice page with templates to copy.
Your checklist for the next project
Seven points that make the difference
- A single responsible contact on the client side.
- The number of revision rounds fixed in the proposal.
- Feedback collected in one place and on the element.
- Clients give feedback with no login.
- Notes are concrete and per section.
- Done points are visibly marked as done.
- Every phase ends with a documented sign-off.
Common questions about website feedback
How many revision rounds are typical for a web project?
As a rule, one or two thorough rounds per project phase (concept, design, build) are standard and usually included in a fixed price. The key is to agree that number in writing up front, so additional rounds can be billed transparently.
How do I collect website feedback without it turning into chaos?
Collect feedback in one place instead of spread across email, phone and screenshots. The most efficient form is visual feedback right on the live page, where each comment is attached to a concrete element. That keeps every note traceable and nothing gets lost.
Should clients create an account to give feedback?
No. Every hurdle lowers your response rate. A feedback link that works with no login provably leads to more stakeholders actually responding, and faster. Only you, as the agency, need an account.
How do I make the final sign-off binding?
Record the approval clearly and in writing, ideally with a timestamp and a documented sign-off as a PDF. That makes it provable which version was approved, when and by whom, and protects you from later disputes over rework.
What’s the difference between client feedback and user feedback?
Client feedback comes from your commissioning client during the build and concerns content, design and sign-off. User feedback comes later from the visitors of the finished site and concerns usability. This guide is about client feedback in the build-and-approval process.
About this guide
Written by David Malewski, founder of bepeq (DAMA Solutions GmbH), based on work with web, design and marketing agencies. bepeq is a guided tool for website feedback and sign-off. Last updated July 8, 2026.