GUIDE
How to limit client revision rounds without losing the client.
Unlimited revisions usually begin as a kindness and end as an unplanned discount. A clear review process protects both the relationship and the work.
Why unlimited revisions eat your margin
Every revision has a cost. The designer has to reopen files, the developer has to test changes, and the project manager has to interpret a fresh set of requests. When the number of rounds is open-ended, the client has no reason to group feedback or decide what is genuinely important.
The issue is not that clients are difficult. Most are trying to be careful with a purchase they cannot fully assess until they see it. Your job is to give them a safe, simple way to make decisions without quietly moving the finish line.
Put the number of rounds in writing before work starts
State the included number in the proposal, scope and kickoff email. Use plain language: two rounds of consolidated feedback on the supplied design, then one final technical check before launch. A number is easier to honour when it appears before the first draft.
Explain the purpose as a better process, not a restriction. Defined rounds mean the team can schedule the work, the client knows when decisions are needed and everyone can see what happens if more changes are requested.
Define what counts as one round
A round should be one consolidated response from the agreed decision-maker or client team. It is not every note, every email or every small correction. Let clients add as many useful notes as needed inside the round, then ask them to submit one list.
Set a cut-off for late notes. Feedback that arrives after the round is closed belongs in the next included round or in a quoted extra. This removes the argument about whether a change is small enough to squeeze in.
Batch feedback into one list per round
Give the client one review link and one deadline. Ask them to collect internal opinions before submitting feedback to you. A page-specific note is much easier to implement than a message saying something feels off.
Use a short check-in before each round closes. Ask whether all stakeholders have reviewed, whether the list is final and whether any legal or compliance reviewer is still outstanding. A five-minute check can prevent a week of reopened work.
What to do when the rounds run out
Do not negotiate in the middle of an email thread. Confirm what has been delivered, link back to the agreed rounds and give the client two clear options: approve the current version or open a paid extra round with a stated scope and price.
Keep the tone calm. The aim is not to win an argument. It is to let the client make an informed choice while your team retains the capacity promised to other projects.
Price extra rounds up front
Quote the extra-round fee before the project begins. It can be a fixed amount, a time allowance or a new scoped change. What matters is that the client knows there is a path forward rather than an uncomfortable surprise.
Make the extra round useful. State what it includes, who can submit it and when the revised work will be returned. This is also a good place to distinguish genuine defects from new creative direction.
A short script for the awkward conversation
Try this: ‘We have completed the two included review rounds and addressed the consolidated feedback. If you would like to make further changes, I can open an additional round for the agreed fee and schedule it for next week.’ It is direct, professional and leaves room for the client to choose.
For the review process itself, see the guide on <a href="/guides/get-client-feedback-on-a-website">getting clear website feedback</a>, use the <a href="/templates/website-sign-off-form">free sign-off form</a>, and compare <a href="/markup-alternative">Approvela with MarkUp</a>.
Make the process repeatable
The useful part of a review process is that it removes small decisions from the project manager’s day. Give every client the same starting note, the same review deadline and the same definition of a completed round. Repeat the language in proposals, kickoff notes and review reminders. The client then understands that the process is a normal part of delivery, not a rule invented for a single difficult project.
Name one person on each side to consolidate feedback. They do not need to write every note, but they should confirm that the list represents the people who need to sign off. If several stakeholders contribute directly, ask the nominated owner to resolve conflicting requests before the agency begins another version. This protects the relationship as much as the margin because the client sees the decision happening inside their team, rather than receiving competing work from yours.
Keep a short project record after each round: the version reviewed, the deadline, the agreed list, the changes delivered and the next decision. It makes handover easier when a team member is away, gives the client a clear answer when they ask what changed, and avoids the familiar problem of reopening an old email chain. A record is not bureaucracy for its own sake. It is the evidence that turns a vague request into a completed piece of work.
When a client asks for a change outside the agreed round, acknowledge it before estimating it. Explain whether it is a correction, a deferred launch item or a new request. Give a price and a delivery date where appropriate. The client is much more likely to accept an extra cost when it is connected to a visible choice and a clear outcome, rather than appearing as an unexplained invoice after the work is done.
Before the first review, send the client a short note that answers four practical questions: what they are reviewing, who should collect internal feedback, when the response is due and what happens after they submit it. Keep the note close to the project link. If a client can find the rules without searching an old email, they are more likely to use the process well. It also gives your project team one consistent explanation when a new stakeholder joins late.
After each version, close the loop in the same format. Name the version, summarise the material changes, state whether the next step is another review or approval, and include the date by which a decision is needed. A simple update makes progress visible and stops clients treating a delivered version as an invitation to restart the conversation. It gives the agency a fair record if a schedule or scope question arises later.
Related reading
How Approvela helps
Approvela gives clients one private link to review a website, keeps feedback in defined rounds and records the final approval. See how it works, then try the client demo.
IT’S NOT OFFICIAL UNTIL IT’S APPROVELA