Every agency has a version of this story. The brief was clear. The first deliverable was good. Round 1 went fine. Then Round 2 opened and the client said "actually, can we go back to something from Round 1?" And Round 3 introduced a new stakeholder. And Round 4 was mostly undoing Round 3.
By Round 5, nobody is sure what version of the design is current, what was agreed, or whether the project is profitable anymore. This is scope creep — not from a dishonest client, but from a process with no guardrails.
The difference between a revision and a scope change.
A revision is a change that makes the deliverable better match the original brief. A scope change is a change that requires the brief itself to change. Most agencies treat these as the same thing. They're not.
Distinguish them at the start. "The contract includes two revision rounds. A revision addresses feedback within the scope of the brief. Changes to the brief itself are a new statement of work." That sentence, said clearly at kickoff, makes every future conversation crisper.
Run rounds, not threads.
An email thread has no structure. Feedback accumulates, contradicts itself, and has no closing condition. A revision round has a start date, an end date, a scope, and a sign-off condition. When the conditions are met, the round closes. Period.
Name your rounds. "Round 1 — layout review." "Round 2 — copy and detail review." "Round 3 — final polish." The name signals what kind of feedback is in scope. A client who starts giving Round 3 feedback in Round 1 gets a kind redirect: "Let's park that for Round 3. It's captured."
Version everything.
When a round closes, the approved version becomes the baseline. The next round starts from that baseline, not from memory. If a client asks to revisit something from Round 1, you can show them: "We approved this in Round 1 on March 14th. Here's the sign-off record. If you'd like to change it, that's a scope addition at the current rate."
Version history isn't about being adversarial. It's about being professional. A client who can see exactly what was approved and when trusts you more, not less.
Set a revision cap and state it plainly.
"This contract includes two rounds of revisions" is the most important sentence in your proposal. Not buried in section 7. In the first paragraph. Before the price.
When you reach the cap, have the conversation before the work starts: "We're at the end of included revisions. Additional rounds are billed at our day rate. Would you like to proceed?" This is not confrontational. It's a business conversation between adults.
What to do with late feedback.
A client who misses a round deadline has two options: the feedback goes into the next included round (if there is one) or it becomes billable additional work. Neither option is punitive — both are just the consequences of the structure you agreed to.
The move that breaks scope management is extending deadlines out of kindness. One extension trains the client to expect extensions. Two trains them to use them strategically.
kiro tracks every round, every comment, and every sign-off. Free plan included.
Run structured revision rounds