Revision Scope Control (Delivery)

Revision Scope Control (Delivery)

1. 01

   Cap the included revision rounds in the client agreement before generation starts

   Write the number into the statement of work (two rounds is the common ceiling) and state that additional rounds bill at the agency's standard hourly rate. Unbounded revision language is what turns a $1,500 build into a $4,000 loss.

2. 02

   Collect every stakeholder comment in one pass rather than trickling feedback across days

   Route notes through a single shared document with a hard deadline. Sequential feedback loops are the main reason AI-assisted builds still consume senior designer hours.

3. 03

   Separate copy edits from layout edits and price them differently

   Text swaps inside an existing block take minutes; structural changes to a generated layout can force a rebuild of adjacent sections. Tag each request before assigning it.

4. 04

   Rebuild only the affected sections instead of regenerating the full site

   Platforms such as Dorik and Brizy let you regenerate a single block or page. Full-site regeneration resets approved copy and reintroduces errors the client already signed off on.

5. 05

   Log every out-of-scope request with its estimated hours and send a running tally weekly

   A visible tally gives the account lead a factual basis for the change-order conversation and prevents the end-of-project dispute about what was included.

6. 06

   Require written approval on the final revision before the site moves to launch

   An email confirmation of the approved version closes the revision window and protects the retainer from post-launch rework requests.