What Is Scope Drift? Catching Scope Creep Before It Eats Your Margin
Scope Drift™ explained: how out-of-scope requests show up in client chat, when to ignore vs create a change order, and how drift differs from normal revisions.
- scope drift
- scope creep tool
- stop scope creep
- change order
- scope creep
Scope drift is the moment a request steps outside locked deliverables, sometimes obvious ("add six more pages"), sometimes subtle ("can we explore a totally different visual direction?"). If it is not caught early, drift becomes scope creep: unpaid work, blown timelines, and invoices that surprise the client.
Scope Drift™ is Zlaip's primitive for surfacing that moment inline, with Ignore or Create Change Order actions. Here is how drift differs from revisions, how detection works, and what to do when a warning appears.
Scope drift vs included revisions
| Included revision | Scope drift | |
|---|---|---|
| Purpose | Refine agreed direction | Add or change deliverables |
| Example | "Tighten kerning on logo" | "Design a merchandise line from the logo" |
| Contract basis | Revision Boundary™ | Original SOW, needs expansion |
| Billing | Included (until limit) | Change order |
Revisions polish what was sold. Drift sells something new.
How Scope Drift warnings appear
Zlaip listens to Accountability Chat and integrated signals (e.g. Figma comments), passively, without blocking messages. When language suggests out-of-scope work, a Scope Drift card posts inline:
- Ignore, dismiss if the team agrees it was in scope or not actionable
- Create Change Order, start formal scope and billing expansion
Detection is advisory; humans confirm. Nothing silently expands the locked agreement.
Why inline warnings beat end-of-project fights
Drift caught in week two:
- Client sees the boundary while context is fresh
- Creative does not absorb weeks of free work
- Change order feels procedural, not adversarial
Drift caught on the final invoice:
- Relationship damage
- Payment disputes
- "That was always part of the project" vs "That was never in the SOW"
A scope creep tool belongs at the moment of the ask, not in a spreadsheet you update monthly.
What to do when you see a drift card
If the work is truly out of scope:
- Create Change Order, scope, fee, timeline
- Pause related delivery until accepted
- Continue in-scope milestone work if possible
If it was a false positive:
- Ignore with brief note in thread
- Clarify SOW language if the same confusion repeats
Never absorb material drift because the client is friendly. That trains the boundary to be optional.
Scope drift and revision boundaries together
Drift and revisions solve different problems:
- Revision Boundary™, how many times we refine in-scope work
- Scope Drift™, whether the ask was in scope at all
A client can exhaust revision rounds and request drifted work in the same week. Each routes correctly: over-limit refinement → change order; new deliverable → change order.
Bottom line
Scope drift is early warning on scope creep. Scope Drift™ puts that warning in the conversation where decisions happen, so expansion is documented before it becomes margin you will never recover.
Related: Scope creep billing guide · Change order template