Most web design contracts include a set number of revision rounds. Most clients don’t know what that means until they’ve used them up — or until an agency bills for a “fourth round” that the client thought was a correction on an existing round.
Here is how revision rounds actually work, what they should include, and how to use them without burning through your allowance on things that should have been caught earlier.
What a Revision Round Actually Is
A revision round is a cycle: you review a deliverable, consolidate your feedback into a single document, the agency implements it, and you review again. One round equals one cycle.
The confusion comes from how “revision” gets defined. Most agencies count a round as one consolidated batch of feedback — all your comments on the current version delivered at once. The agency implements them. That’s round one complete.
What many clients do instead: send feedback in pieces. Review on Monday, email a list. Remember three more things Tuesday, email again. See the update Thursday, send more comments Friday. The agency has now responded four times to one design phase. Depending on the contract language, that could be counted as four rounds — or it creates an informal pile of feedback with no clear close.
A revision round is not:
- A correction to something that was built incorrectly per the approved spec (that’s a bug fix, which is outside revision count)
- A response to a technical error (same — not a revision)
- An iteration when the agency proposes a different direction for your consideration
A revision round is:
- Your consolidated feedback on a deliverable delivered as agreed
- The agency’s implementation of that feedback
- Your final review confirming the round is closed
Get clarity on this definition in writing before the project starts.
How Many Rounds Is Standard
For a typical website design project:
- Wireframes or layout concepts: 1–2 rounds
- Visual design (homepage): 2–3 rounds
- Visual design (interior pages): 1–2 rounds per page type
- Development/staging review: 1–2 rounds
- Final pre-launch review: 1 round
More rounds aren’t automatically better. More rounds often signal unclear feedback in earlier rounds, or a client who keeps changing direction after approvals.
For custom WordPress builds on larger scopes, the revision structure is part of the written scope document. Clients know what’s included and how rounds are counted before a line of code is written.
The Most Common Way Clients Waste Revision Rounds
The single most common pattern: clients approve designs without reviewing them carefully, then use revision rounds on feedback that should have been caught at approval.
This happens because clients rush through reviews. They scan the design on desktop, think it looks fine, approve it, and then look at it on their phone three days later and notice five problems. Or they show it to a colleague who wasn’t involved in the review and suddenly there are new opinions.
How to review a design properly before approving:
- View it on every device you care about — desktop, tablet, phone
- Walk through it from the perspective of a new visitor, not someone who built the business
- Show it to one internal stakeholder whose opinion you trust before approving — not five people, one
- Check every element against your brand assets: color codes, fonts, logo usage
- Read the placeholder copy as if it were real content — does the layout still work?
Thorough review before approval preserves your revision rounds for meaningful direction changes — not corrections you should have caught the first time.
What Counts as Scope Creep vs. a Legitimate Revision
This is where most client-agency disputes originate. The line between a revision (covered in your rounds) and a scope change (billable separately) should be defined in your contract. In practice, it’s often contested.
A revision is a modification to what was agreed in the spec and shown in the mockup. A scope change is:
- Adding a new page, feature, or element that wasn’t in the original scope
- Changing the design direction after approval (not a refinement — a direction change)
- Adding integrations that weren’t specified
- Requesting copy or content work that wasn’t included in the original scope
Lisa ran a law firm and hired an agency for a five-page website. After seeing the homepage design, she decided she also wanted a blog section, a downloadable resources library, and a new “About the Partners” page with individual bios. She framed these as “additions I should have thought of earlier.” The agency quoted them as change orders — $4,200 additional. Lisa felt blindsided. The agency was correct that these weren’t in scope. But neither party had been explicit about what happened when the client wanted to expand scope during the build. A good contract prevents that dispute.
If you want to understand your contractual rights before scope disputes start, the guide to web design contracts covers the specific clauses that protect both parties.
How to Give Feedback in Revision Rounds Efficiently
Feedback delivered in the right format gets resolved faster. Here is what works:
- Annotated screenshots — use tools like Loom, Markup.io, or even Google Slides with screenshots and callouts. Point at the exact element you’re commenting on.
- Numbered items with priority — separate “this must change” from “this would be nice to change.” Agencies should know which is which.
- Consolidated feedback — all feedback from everyone on your side in one document, not separate emails from five people
- Reference material — when you want a different approach, show an example. “More like this” with a link resolves faster than “more modern” without reference
What slows feedback cycles down:
- Verbal-only feedback from calls that gets summarized differently by each party
- Feedback that contradicts previous approvals without acknowledging the direction change
- Feedback delivered in stages after the initial review
- Instructions that describe a feeling rather than a specific change
David ran an architecture firm and started each design review with a 30-minute call where he talked through his impressions, then followed up with an email summary. The problem: his summaries were interpretations of what he’d said on the call, and they didn’t always match. The agency implemented the email version; David remembered the call version. By round two, both parties were frustrated. Starting with the written document — not the call — would have solved it.
What Happens When You Run Out of Rounds
Agencies handle this differently. Some charge a flat per-round fee for additional revision cycles. Some bill hourly. Some build a buffer into the project scope and rarely enforce the limit strictly on clients who give clear, reasonable feedback.
What you should not assume: that additional rounds are free. If your contract says three design revision rounds and you’re requesting a fifth, you are outside the agreed scope. A professional agency will either flag this with a cost estimate or absorb it depending on the relationship and the reasonableness of the request.
To avoid hitting the limit:
- Use each round fully — don’t save minor feedback for “next round” if you can include it now
- Don’t send partial feedback — gather everything before the round opens
- Don’t confuse rounds with weeks — a round is feedback cycle, not a time period
The No-Surprises Approach to Revision Management
The clearest way to avoid disputes about revision rounds is to over-specify at the start. Ask your agency, in writing, before work begins:
- How many revision rounds are included for each deliverable?
- What constitutes a revision round — how is the start and close of a round defined?
- What happens if revisions result from a technical error rather than a preference change?
- What is the cost of an additional round if the included rounds are exhausted?
- Is there a distinction between minor revisions (color tweak, copy adjustment) and major revisions (layout change, new section)?
Get those answers in your contract or a signed scope document. Knowing the rules before the game is better than arguing about them in the fourth quarter.
Frequently Asked Questions
How many revision rounds should be included in a web design contract? For design phases, two to three rounds per major deliverable is typical for a well-managed project. More than three on a single deliverable usually signals either unclear initial direction or unstable decision-making on the client side. Development and staging review typically gets one to two rounds. The specific number matters less than having clear, written definitions of what a round includes and what it doesn’t.
Can I negotiate more revision rounds before signing? Yes. If you know from experience that your internal approval process requires multiple stakeholders, ask for additional rounds upfront. An agency will either include them in the base price or quote them as an add-on. This is a legitimate negotiation point before you sign, but not a reasonable request after you’ve already used your included rounds.
What if the agency implements my feedback incorrectly? That’s not a revision round — that’s a correction. If you provided clear, specific written feedback and the agency implemented something different, the revision cycle needed to fix it should not count against your round allowance. Document the original feedback and the incorrect implementation, and frame it explicitly as a correction request, not a new revision.
Is there a difference between revisions and minor tweaks? There should be — and good contracts define this. Minor tweaks (a font size adjustment, a spacing fix, swapping one word in a headline) are typically handled as corrections rather than full revision rounds. Major revisions (changing a section layout, adding or removing design elements, shifting color palette) are revision-round work. If your contract doesn’t make this distinction, get clarity in writing before you need to use it.
What should I do before my final revision round to make sure I don’t miss anything? Do a comprehensive review of the entire deliverable before opening the final round — not just the parts you know were changed. Check every page on mobile. Test every link and form. Review every piece of copy. Walk through the user flow as a first-time visitor. Export the checklist as a document, mark what passes and what needs attention, and submit everything in one batch. The final round should be a quality check, not a discovery session.