All guides

How to define a revision round for a website project

“Two rounds of revisions” only helps when both people understand what a round contains.

Give the round a beginning and an end

A practical round starts when you send a named design version for review. The client consolidates feedback from the agreed stakeholders into one response. You implement the agreed changes, then send the next version. A separate set of feedback after that delivery starts another round.

State the feedback deadline and one person who can approve the result. This reduces contradictory instructions without preventing useful feedback.

Separate revisions from a new brief

Moving a button or refining typography can be a revision within the agreed direction. Adding a booking workflow or replacing the approved visual direction may change the scope. Describe examples that fit the project rather than relying on an abstract definition.

Each round includes one consolidated list of feedback on the current version. New pages, new features or a replacement design direction will be estimated separately before work begins.

Handle corrections fairly

A defect in your delivery is different from a client changing their preference. Do not consume a paid revision allowance to fix your own failure to meet an agreed requirement. Record the issue and correct it under the existing agreement.

When the distinction is unclear, compare the request with the approved brief. Explain your interpretation and seek agreement before quoting an extra fee. Clear communication is more useful than treating every comment as a chargeable change.