Most web development proposals include a specific number of revision rounds, and most clients aren't quite sure what that means in practice. How many is enough? What counts as a revision? What happens if you run out? This guide demystifies the revision process and helps you use your rounds effectively to get the website you want.
What Is a Revision Round?
A revision round is a cycle of feedback and changes. The agency presents work, you review it and provide feedback, and they implement your requested changes. That complete cycle—present, review, revise—constitutes one round.
For more insights on this topic, see our guide on The Website Discovery Phase: What Happens and Why It Matters.
The key is that all feedback from a given review is submitted together and addressed together. This is different from a drip-feed approach where you send feedback gradually over time. Each batch of consolidated feedback triggers one revision round.
How Many Rounds Are Typical?
Industry standard for most web projects is two to three revision rounds at each major phase: wireframes, design, and development. So a typical project might include:
- Initial wireframes + 2 revision rounds
- Initial design mockups + 2 revision rounds
- Initial development build + 2 revision rounds
This structure allows for meaningful refinement while keeping the project on track. The first round typically addresses major concerns, and the second handles remaining details.
More complex projects or those with multiple stakeholders sometimes include additional rounds, but this usually comes with additional cost.
Why Limit Revisions?
At first, revision limits might seem unfriendly—shouldn't the agency keep working until you're happy? But limits serve important purposes:
Scope Protection
Without limits, projects can spiral endlessly. Every stakeholder can keep adding feedback indefinitely, and no amount of work will ever be "done." Limits create accountability on both sides: the agency must deliver quality work, and the client must provide focused feedback.
Budget Predictability
Unlimited revisions would require unlimited budgets. By defining revision rounds, both parties can agree on a fixed scope and price. You know what you're paying for; the agency knows what they're delivering.
Decision Encouragement
Knowing you have finite revision rounds encourages decisive feedback. Instead of "let's try blue and see how it looks," you think carefully about whether blue is actually what you want before using up a revision round.
Project Momentum
Projects need to move forward. Endless revision cycles keep projects in limbo, delaying launch and the business benefits your new website will deliver.
Making Revisions Count
To get the most from your revision rounds, follow these strategies:
Consolidate Stakeholder Feedback
If multiple people on your team will review the work, gather everyone's input and resolve any conflicts before submitting feedback. Contradictory feedback wastes a revision round trying to serve incompatible directions.
Be Thorough
When reviewing, examine everything—not just what catches your eye immediately. Check every page, every section, every element. Feedback you forget to mention becomes feedback that uses your next revision round.
Prioritize Ruthlessly
Not every observation deserves a revision. Ask yourself: does this change meaningfully improve the website, or am I just nitpicking? Save revision budget for changes that matter.
Provide Clear, Specific Feedback
Vague feedback leads to misinterpreted solutions, which leads to more revision rounds. The clearer your feedback, the more likely you'll get what you want on the first try.
Trust the Process
Don't panic after the first presentation. Initial work is meant to be refined—that's why revision rounds exist. Major concerns in round one are expected; major concerns in round three suggest something went wrong.
What Counts as a Revision?
Understanding what triggers a revision round helps you plan:
This Is One Revision Round
- A single consolidated batch of feedback with 15 items
- Multiple stakeholders' feedback combined into one document
- Detailed requests for multiple pages submitted together
This Is Multiple Revision Rounds
- Feedback submitted on Monday, more on Wednesday, more on Friday
- Different stakeholders sending separate feedback at different times
- "One more thing" after the agency has already started revisions
This Typically Isn't a Revision
- Fixing something the agency got wrong per the spec
- Correcting an error the agency introduced
- Quick questions or clarifications before formal feedback
What Happens When You Run Out?
If you exhaust your included revision rounds but still need changes, you have options:
Additional Paid Rounds
Most agencies will provide additional revision rounds at an hourly or per-round rate. This is typically spelled out in your contract.
Prioritize and Accept
You might decide that remaining issues are minor enough to accept. Not every detail must be perfect for launch—you can always refine after the site is live.
Post-Launch Refinement
Some changes work better as post-launch iterations anyway. Once real visitors use your site, you'll have data to inform improvements that speculation couldn't provide.
Red Flags: When Revisions Go Wrong
Sometimes revision cycles indicate deeper problems:
Needing Many Rounds
If you're consistently maxing out revision rounds or frequently going over, examine why. Possible causes:
- Insufficient discovery led to misaligned expectations
- Too many stakeholders with too many opinions
- Scope wasn't clearly defined
- Communication gaps between you and the agency
Same Issues Recurring
If you provide feedback and the next round still has the same problems, communication is breaking down somewhere. Request a call to ensure mutual understanding.
Big Changes Late in the Process
Major feedback in late revision rounds often signals that early rounds didn't get enough attention, or that stakeholders who should have been involved weren't.
Revision Etiquette
A few principles for maintaining a healthy revision relationship:
- Respond within agreed timelines: Your review delays delay the project.
- Be respectful: Behind every pixel is a human who worked to create it.
- Acknowledge what's working: Feedback shouldn't be exclusively negative.
- Ask questions: If you don't understand why something was done a certain way, ask before demanding changes.
- Trust expertise: The agency's recommendations are informed by experience. Consider them seriously.
Related Reading
- Post-Launch Support: What to Expect in the First 30 Days
- Website Project Communication: Tools and Best Practices
- Website Wireframes Explained: Why Every Project Needs Them
Ready to Start Your Project?
Our clear, structured process ensures revision rounds are productive and projects stay on track. Let's discuss your website needs.
Get in Touch