Clients rarely announce scope creep. They ask for help. A new stakeholder wants another round, a launch date moves forward, or a “small” asset becomes a new channel. The agency loses margin when the request travels from message to production without an explicit commercial choice.
1. Define a boundary people can actually use
A signed statement of work is necessary, but it is usually written for agreement rather than daily delivery. Convert it into an operational scope card: included deliverables, quantities, revision limits, response assumptions, excluded categories, client dependencies and the rate or formula for additions.
2. Separate detection from negotiation
The person receiving a client message should not have to negotiate immediately. Their first responsibility is detection: pause, compare and route. The commercial owner then chooses one of four treatments.
- AbsorbA deliberate relationship investment with an owner and recorded value.
- TradeAdd the request by removing or delaying something of comparable effort.
- DeferMove it into the next sprint, phase or retainer cycle.
- ChargeIssue a priced change with timeline impact and written approval.
3. Put the control where requests arrive
A separate change-order app is easy to ignore. Scope control should appear in Slack, Teams, email or the project tool at the point of commitment. It should show why a request may be outside scope, the likely value, and the next action—without pretending software can make the relationship decision.
4. Price the impact, not the inconvenience
Price should reflect delivery effort, external cost, disruption and urgency. A rush request can be commercially different from identical work scheduled next month. Always show timeline movement alongside price; clients need to see the trade-off, not just a surcharge.
5. Record absorbed work too
Most systems only record approved changes. That hides the most important management signal: value consciously given away. Record absorbed requests with an owner and reason. At renewal, you can distinguish a generous relationship investment from an underpriced retainer.
6. Review patterns monthly
Group scope events by client, request type, account manager and original sales assumption. Repeated “extras” usually point to one of three problems: a quote gap, a delivery habit, or a retainer that no longer matches the client’s needs.
Put it into practice
Run one real request through MarginRail.
Use the client’s wording and the actual commercial boundary. The detector will explain what it sees and draft the calm response your team can adapt.
Test the request →See the agency workflowDraft a change orderCalculate monthly leakage