CLIENT FEEDBACK
What actually counts as a revision round?
“Unlimited revisions” leaves both sides without a clear finish line. A revision round becomes useful when everyone knows what is being reviewed, who collects feedback, and which changes fit.
01One round, one collected set of feedback
An example definition: one revision round is one consolidated list of requested adjustments to the agreed deliverable, supplied by a named client decision-maker. That keeps feedback from arriving across three inboxes over ten days.
02Give people a review window
Ask for feedback within three business days of sending a review link, for example. Explain that delayed feedback can move the delivery estimate. Do not automatically treat silence as approval; ask for an explicit decision.
03Show examples inside and outside the round
Within a homepage design round: refine spacing, adjust type size, replace supplied photos, or reorder agreed sections. A new membership area, a new page, or a completely different approved design direction changes the scope and needs a separate conversation.
04Distinguish fixes from new preferences
A broken form or a layout that fails the agreed acceptance criteria is a defect to fix, not a reason to sell another revision round. Distinguish correction of agreed work from requested additional functionality.
05Write a calm boundary
Try: “The project includes two rounds of consolidated revisions to the agreed pages. If you need additional rounds or new deliverables, I will outline the extra time and price before beginning. Please send one collected feedback list for each round.” Adapt the wording to the actual project.
06Keep the client involved
Show the sitemap and design direction early, while changes are inexpensive. A revision limit should help both sides plan; it works poorly when the client first sees the project just before launch.
Put it into your next project.
Use the free builder to turn the details into a proposal and a separate quote for additional work.
Open the scope builder ↗