How many revisions can I ask for on a website?

Feedback is part of every website project. The question is how much is included in the price. Website revisions are usually limited to a set number of rounds, so both sides know where the project ends. Understanding what counts as a revision helps you get the changes you need without surprise bills.

Here is what is normal and how to make each round count.

Typical rounds of website revisions

These are common patterns, not rules. Your contract should state the exact number. Read what a contract should include.

What counts as a revision

• Changing colours, fonts, spacing or images on an agreed design.
• Reordering sections on an agreed page.
• Editing text you supplied.
• Fixing anything that does not match the agreed design (a bug, not a revision).

What is new scope, not a revision

• Adding pages that were not in the plan.
• Adding features such as booking, a shop or a member area.
• Completely changing a design that was already approved.
• Integrations with new tools.

New scope is normally quoted separately, which is fair because it adds real work.

How to get the most from each round

1. Collect feedback from everyone first, then send one combined list.
2. Number each comment and point to the exact place on the page.
3. Describe the problem, not just the solution.
4. Mark what you like, so it is not changed by mistake.
5. Choose one person to make final decisions.

Example: two ways to give feedback

One client sent fourteen separate emails over two days, some contradicting each other. The designer counted them as three rounds of website revisions, and the client ran out of rounds before the design was right. Another client gathered comments from four managers, removed duplicates and sent one numbered list. Every change fitted into a single round. The number of website revisions was the same in both contracts; the way feedback was given made the difference.

What if I need more rounds?

Ask for an hourly rate or a fixed price for an extra round before you start. Most developers are flexible when changes are clear and reasonable. What causes friction is endless small changes with no end point.

Why limits help you too

Limits keep the project moving and protect your launch date. Without them, projects can drift for months. Agile teams use similar fixed review cycles, described in guides on project scope, for the same reason.

How to plan your feedback sessions

Book a short meeting with everyone who needs to approve the site before each round of website revisions. Walk through the design together on screen and on a phone, agree what must change and what can stay, and assign one person to write the final list. This meeting usually takes less than an hour and prevents the back-and-forth that uses up rounds. It also means the developer receives clear, agreed instructions instead of conflicting opinions from different people. Clear sessions make every round of website revisions count.