Catch the scope drift before it becomes unpaid work.
Most scope creep is not one big ask. It is a run of small ones, each easy to say yes to, that nobody adds up until the project is over budget. This makes the drift visible while it is still cheap. Your team still decides what is billable, what is a favor, and what to push back on.
A client emails asking for one more round of edits on a page the statement of work already signed off. It reads like a favor, so someone almost just does it.
The request is compared to the signed statement of work and the change log. It does not match anything you agreed to deliver, so it is flagged as out of scope.
Instead of landing quietly in a designer's inbox, the flagged item goes to the person who owns the client relationship, with the original scope line attached.
The lead reads it and chooses: absorb it as a small favor, log it as billable, or write back to reset expectations. The call is theirs. The drift never went unnoticed.
Representative scenario. It shows how the pieces fit, not something that happened to a named agency. The moments are illustrative. They are not a client result.
Three plain tools. One useful change.
Scope Check
Compares each incoming request against the signed scope.
It reads the statement of work and the agreed deliverables, then marks a new request as in scope, out of scope, or unclear. Unclear is a valid answer and routes to a person.Change Detection
Spots when delivered work drifts from what was agreed.
It watches for extra rounds, added pages, new asks bolted onto old tickets, and shifts in what a task actually covers, so slow drift shows up as it happens rather than at invoice time.Needs Review
Collects the flagged items in one place a person owns.
Out of scope and unclear requests land in a routed queue with the relevant scope line attached, so nothing quietly becomes unpaid work in a side conversation.The system prepares the work. A person still decides.
The system never rules on money or favors. It flags and routes; a person chooses whether a change is in scope, billable, or a goodwill call.
Checks run against the actual signed statement of work and logged changes, not a guess about what the client probably meant.
When a request does not clearly fit or fail scope, it is marked unclear and sent to a person rather than forced into a yes or no.
The system does not reply to clients or approve changes on its own. It surfaces the decision to the person who owns the relationship.
Effort and time first. Outcomes later.
Effort and time come first: how much drift gets surfaced and how fast it reaches a decision. Whether this changes margin over a project is a slower, directional read that comes later, once the habit is in place.
Hours get entered and scope changes get logged as they happen, not reconstructed at month end. When that slips, the scope check reports green on bad numbers. A confident all clear built on nothing is worse than no check at all.
See how the Lookout works