The agency scope creep survival guide

The average agency loses 15–25% of project margin to scope creep. Almost none of it arrives as a deliberate attempt to get free work. It arrives as: a small clarification that becomes a full revision, a stakeholder who wasn't in the original review who has new opinions, and a version that was 'approved' in a Slack thread but was never formally signed off.

The common thread: a process designed to be flexible enough to accommodate the client ends up flexible enough to accommodate unlimited free work. Here's how to tighten it without losing the client relationship.

Define the revision round in the contract

Your contract should specify: the number of included revision rounds, what constitutes a 'round' (all consolidated feedback received before the deadline), and the rate for additional rounds. Most agencies include this language but don't enforce it because there's no mechanism to prove what round you're on.

A numbered, timestamped review system closes this gap. When every round has a number, a start date, and a close date, the contract clause becomes enforceable. You're not arguing about whether a round happened — you have a record of it.

Close every round formally

The most common source of scope creep is the round that never formally closes. Feedback trickles in after the supposed cutoff. You keep incorporating it because the relationship matters. Three weeks later, you're on what is effectively Round 5 of a contract that included two.

A formal close means: a named approver signs off, the round is marked closed, and any feedback that arrives after close goes into the next round queue. This isn't harsh — it's professional. Clients respect it more than open-ended revision loops.

Name the decision-maker before the round opens

Multi-stakeholder clients are the highest-risk for scope creep. You deliver the work. Person A approves it. Then Person B weighs in. Then the CEO sees it. Now you're on your fourth round of 'final' revisions.

At the start of each round, ask: 'Who is the final decision-maker for this review?' That person's sign-off closes the round. Others can comment. The named approver decides. When the named approver signs, the round is done — regardless of subsequent opinions from other stakeholders.

Create a new version for each round

Version control eliminates a large class of scope creep that comes from confusion. 'But we didn't approve the change to the header.' If you have a versioned canvas, you can show exactly what was in each version and who approved it. Without that record, you're in a memory contest and the client always has more leverage.

Audit your scope creep to find the pattern

Most agencies have one or two client types that generate most of their scope creep. Track your rounds per project for three months. You'll find the pattern: it's usually the client who 'approves' via Slack, the project with no named decision-maker, or the deliverable type where feedback tends to arrive late.

• Track rounds per project — how many rounds did 'two rounds' actually take?
• Log where feedback arrives — email, Slack, or the formal review canvas?
• Note who approved — was there a named approver, or was it 'the team'?
• Calculate cost — hours per additional round × your rate

Once you see the pattern, you can fix the specific process gap rather than trying to control everything simultaneously.