By Mehdi HassanHow many design revision rounds are normal in a web design project?
There's no single standard number of design revision rounds, but most fixed-scope web projects define a small number per phase rather than per project. Our recommendation is two structured rounds for each phase, which in practice gives you several rounds across copy, layout, visual design and build.
The question of how many revisions web design should include usually comes up when a buyer is comparing contracts. One agency offers two rounds, another three, a third offers unlimited. Those numbers aren't comparable unless you also know what counts as a round, which phases they apply to, and what happens after the last one. The revisions clause is one part of a wider agreement, which our web design contract checklist covers clause by clause.
This guide explains why the structure of rounds matters more than their count, and how to set them up so you get a better site, not just more versions of one.
What counts as one revision round?
One revision round is a single consolidated set of feedback from your side, delivered in one place, followed by one revised version from the agency. If feedback arrives in pieces from several people over several days, each piece can end up counted as its own round.
A clear definition protects both sides. It tells you that you can collect every comment from your team before sending it, without using up a round. It tells the agency that it won't be asked to rework the same page five times in a week because five people replied separately. Most contracts that handle this well also ask you to name one decision maker who consolidates and resolves conflicting feedback before it's sent.
- In a round: adjusting copy, swapping images, changing spacing, refining a section, fixing anything that doesn't match the agreed direction.
- Not a round: a defect, like a broken link or a layout bug, which the agency should fix anyway.
- Not a round either: a new page, a new feature or a new direction, which is a change request.
Why do fewer design revision rounds produce better websites?
Fewer, better-structured design revision rounds produce better websites because they force decisions early and keep the work coherent. Each round is a chance to improve the whole page; dozens of small rounds tend to produce a page that's been adjusted everywhere and designed nowhere.
Endless rounds rarely come from a design that's far off. They usually come from decisions that were never made: the message isn't agreed, the audience isn't clear, or too many stakeholders are reviewing visuals against different goals. Each round then fixes one person's concern and creates another's. Two rounds with clear goals push those decisions to the start, where they're cheap.
There's also a quality argument. A designer working toward a defined review can take bigger swings, because the brief is clear and the feedback will be considered. A designer expecting constant small edits plays it safe. The best way to reduce rounds is a strong brief, which our web design brief template helps you write before the project starts.
Most extra revision rounds are decisions that should have been made before the design started.
Are unlimited revisions a good sign?
Unlimited revisions are usually not a good sign, because they shift attention from reaching a decision to producing versions. They can work in subscriptions for small graphics, but for a website they often mean no one is accountable for converging on a final design.
An unlimited revision policy at a design agency can hide three problems. It can hide slow delivery, because the project never formally finishes. It can hide a weak first draft, because the expectation is that you'll iterate toward something good. And it can hide a pricing issue, since an agency can't really afford unlimited work on a fixed fee, so quality or speed tends to give somewhere else.
A defined policy with a clear path for extra rounds is more honest. If you need a third round on one page, a good contract prices it simply or lets you trade it against something else. If you're comparing an affordable web design agency with a higher-priced one, the revision policy is a useful place to see how each one runs projects.
How should revision rounds work across project phases?
Revision rounds should be set for each phase of the project and closed with an approval before the next phase starts. That keeps big decisions, like the message and the layout, from reopening when you're reviewing the final build.
Phase | What you review | Rounds we recommend | Approval locks |
|---|---|---|---|
Copy and structure | Messaging, page order, headlines | 2 | What each page says |
Layout | Wireframes or low-detail designs | 2 | Where things go |
Visual design | Full-fidelity pages in Figma | 2 | How it looks |
Build and QA | Live staging site | 2 | How it works |
Copy goes first for a reason. When the words change after the design is done, the layout often has to change too, which turns one edit into a design round. We start with the words for that reason, so design rounds are spent on design. Accessibility is worth checking at the visual and build phases rather than at the end; our guide to accessible web design lists what to look for.
When does a revision become a change request?
A revision becomes a change request when it adds something new or reverses something already approved: a new page, a new feature, a different layout concept, or a change in direction after sign-off. Change requests should be scoped, priced and approved in writing before work starts.
The line isn't always obvious, so it helps to agree examples upfront. Rewriting a headline during the copy round is a revision. Rewriting every page after the design is approved, because positioning changed, is a change request. Tweaking a section layout is a revision. Adding a new pricing calculator is a change request. A good agency will tell you which side of the line a request sits on before doing the work, not after.
Clear change requests protect your budget as much as the agency's time. Our guide to preventing scope creep in web design explains how to set up a change-order process that keeps the project on budget.
For example, suppose a new executive joins halfway through
For example, suppose a startup approves its homepage design, and a week later a new head of marketing joins and wants a different headline strategy across the site. Treating that as a revision would force the agency to redo approved copy and design inside the existing fee.
Treating it as a change request lets both sides look at it honestly: what needs to change, how much rework that means, and whether it's worth doing now or after launch. Often the right answer is to launch on the approved version and test the new message afterward.
How do you give feedback that lands in one round?
Give feedback that lands in one round by collecting all comments first, naming one decision maker, tying each comment to a goal, and separating must-fix items from preferences. Clear feedback is the client's half of a short revision cycle.
- Review against the brief, not personal taste. Ask whether the page does its job for the reader.
- Collect every comment from your team before sending, and resolve conflicts internally.
- Describe problems, not solutions. The headline doesn't explain what we do is more useful than make it bigger.
- Mark priority. Separate must-change items from nice-to-haves.
- Send it in one place, such as comments in Figma or one shared document.
Rounds are also a useful lens when choosing who to work with. Agencies that explain their revision process clearly tend to run the rest of the project clearly too, one of the signs we list in our guide to the best web design agency for startups.
