There was a florist in a town that never made any map who sent me 47 comments, most about a logo we had already signed off. A client feedback round in web design is one agreed batch of change requests against a specific design, gathered and sent together. Give it well by collecting every stakeholder's note into one document tied to the page and its goal.
What is a client feedback round in web design?
A client feedback round is one consolidated set of change requests on a specific deliverable, sent to your designer in a single pass. It is a planned checkpoint in the project, scheduled in advance so everyone knows when notes are due. Most builds have a round after the first full design draft, then a second after those changes land, and sometimes a third for final fixes.
The batching is the whole point. I price and schedule the work around rounds. When I get one clear document, I work through it in order, make every change, and send back a clean version. When notes trickle in over a week, I end up touching the same page five times, and half those edits cancel each other out. A round turnaround on a small marketing site runs about 3 to 5 business days once your notes are in hand.
If you want to see where rounds sit in the wider timeline, I covered that in how I structure a website project from brief to handoff.
How many feedback rounds should a website project include?
Most small business website projects include two to three rounds of revisions. E-commerce builds and larger sites with many templates usually need more, and that number should be written into your contract before anyone starts designing. Industry guidance lands in the same place: most teams offer two to three rounds for standard projects and scale up for complex work.
Here is roughly how I scope rounds by project type.
| Project type | Rounds usually included | What each round focuses on |
|---|---|---|
| One-page or landing site | 2 | Round 1 covers layout and message, round 2 covers polish and copy. |
| Standard 5 to 8 page site | 3 | Structure first, then visual detail, then final fixes. |
| E-commerce or 15+ pages | 3 to 5 | Templates first, then product and category pages, then polish. |
Each round should get more specific as you go. The first one is for big structural calls about layout and message. By the last one you should be adjusting a button color while the bigger decisions stay settled. Extra rounds beyond what is included are normal, and most studios bill them hourly (commonly $90 to $175 an hour) or as a flat change order. They cover work that was never in the original quote.
How do you give web design feedback a designer can use?
Give specific, prioritized feedback that points to the exact element, explains the problem, and ties back to a goal, all collected in one document. Vague reactions are what stretch a two-week project into five. Direct, clear communication between client and designer can cut revision cycles by up to 50%, and most of that gain comes down to how the notes are written.
What good feedback looks like in practice:
- Point to the exact spot. Use the page URL and a screenshot, or name the section. 'The hero' is clearer than 'the top part.'
- Describe the problem and let me find the fix. 'This headline does not tell me what you sell' helps more than 'make it bigger.' I can usually solve the underlying problem better than I can guess at a fix.
- Tie it to a goal. 'Customers call us to book, so the phone number needs to be obvious' gives me something to design toward.
- Rank it. Mark each note as must-change or nice-to-have. The must-changes get handled first, every time.
- Group by page. Keep all notes for one page together so I am not jumping around the site.
- Send it once. One document, one pass. Five emails over four days is five chances to contradict yourself.
The most expensive note I ever get is 'I'll know it when I see it.' It means we are about to pay for three rounds to discover something one good sentence could have told me up front.
What kind of feedback is hard to act on?
Vague, subjective, or contradictory feedback is the hardest to use, because it gives me no problem to solve. 'Make it pop' tells me you are unhappy without telling me why. Here is how the same instinct turns into something I can actually build.
| What you sent | What I hear | A version I can use |
|---|---|---|
| 'Make it pop' | Something feels flat, cause unclear | 'The call-to-action gets lost, can it stand out more?' |
| 'I don't love the colors' | Could be brand, contrast, or mood | 'These blues feel cold, we want warm and friendly.' |
| 'Can we see some options?' | An unbounded redesign request | 'I'm unsure on the hero layout, two directions would help.' |
The pattern is the same every time. Tell me the effect you want or the problem you see, and let me handle the how.
Who should give the feedback?
One person should own and deliver the feedback, even when several people have opinions. Across design teams the standard is that a single person speaks for the client between rounds. Gather your CEO, your office manager, and whoever runs the front desk, settle the disagreements internally, then send me one set of notes.
I once watched a clean draft stall because two partners sent me opposite feedback on the same morning, and each assumed theirs was final. I cannot serve both at once. When contradictions arrive, the project pauses while you sort it out, and that delay sits on the clock. Resolve it on your side first. It is faster for everyone.
When does feedback become scope creep?
Feedback becomes scope creep when it adds new pages, features, or goals that were not in the original brief. Refining what already exists is a revision. Asking for a booking system that was never quoted is new work, and it needs its own line on the estimate. The difference matters because revisions are included in your price, while new work is billed separately.
This is the single biggest reason small projects run late. I broke down the usual culprits in the scope creep patterns that add weeks to a web project. When a feedback note is actually a new request, name it as one, and decide together whether it earns a change order before I start building it.
Before your next design review, do one thing. Open a single document, paste the page link at the top, and write three to five notes ranked must-change or nice-to-have. That one habit will save you a full round.
How long should a feedback round take?
Plan 2 to 4 business days on your side to gather and write feedback, and 3 to 5 business days on mine to apply it to a small site. Larger sites take longer. Blocking out time to review the draft properly beats firing off reactions as you spot them, which is what creates contradictions in the first place.
Can I add more feedback after I approve a round?
Yes, but approving a round closes it, so new notes usually open the next round or get billed as extra work. That is why the approval step is a real decision. Once I move to the next stage, going back costs time and often money, so review carefully before you sign off.
What if our stakeholders disagree?
Settle it before the feedback reaches your designer. I cannot act on contradictory instructions, so two opposing notes will pause the project until someone decides. Pick one internal owner to collect opinions, resolve the conflicts, and send a single document tied to the page and the goal.
Get your website designed before you pay. Subsecond Studio designs and builds websites, web apps, and AI tools, and you approve the design before any payment. Get an estimate
