How to Detect Scope Creep Before a Project Starts
Scope creep often starts in the contract, not in chat. A pre-kickoff checklist to read SOW language, milestone gaps, and revision traps before Agreement Lock.
Part of Agreement Health™ guides guides →
- scope creep before project
- detect scope creep
- freelance SOW
- agreement health
Teams usually talk about scope creep after the third "small favor." The expensive mistakes are cheaper to catch in the contract, before anyone opens Figma or writes code.
This guide bridges Agreement Health™ (contract risk) and Scope Drift™ (in-project warnings): what to scan before lock, so drift in chat is rare — and billable when it happens.
Pre-lock vs in-flight creep
| Phase | What you are catching | Tool / habit |
|---|---|---|
| Before lock | Vague SOW language, missing milestones, open revisions | Agreement Health review, SOW checklist |
| During delivery | Requests outside locked deliverables | Scope Drift™ warning → change order |
Both matter. Pre-lock work prevents predictable creep; in-flight work catches novel requests.
Pre-kickoff contract checklist
Run this on every uploaded SOW before Agreement Lock™:
1. Deliverables are countable
- Can you list files, pages, screens, or formats without guessing?
- Are "concepts" vs "finals" separated?
- Is source file handoff specified?
Creep signal: "Comprehensive brand system" with no asset list.
2. Milestones map to money
- Does each milestone have an amount and a clear completion event?
- Is there a final milestone for launch/handoff — not buried in "ongoing support"?
Creep signal: One lump sum for "project" with no phase gates.
3. Revisions are bounded
- How many rounds per milestone?
- What happens at the limit — change order or stop?
Creep signal: "Until client satisfaction."
4. Client obligations have dates
- Feedback within X business days
- One designated approver (stakeholder chaos = creep)
- Assets provided by client listed
See Stakeholder review best practices.
5. Out-of-scope is named
- Examples of what is not included (motion, copywriting, print, dev)
- Explicit change-order or rate for extras
Read "Phase 2" language carefully
Contracts that describe future work without pricing invite creep:
- "Initial site" vs "full ecommerce rollout"
- "Brand exploration" vs "full brand guidelines + templates"
- "MVP" vs "production-ready with admin"
If Phase 2 is real, milestone it now or label it a separate engagement.
Use Agreement Health to prioritize fixes
Agreement Health™ flags patterns common in creative SOWs: weak payment terms, unclear scope, high revenue at risk. Use the score to decide what to negotiate first, not whether to take the job.
Pair with: Why freelancers lose money on vague agreements.
When the project is already in flight
If you adopt Zlaip mid-project, catch-up attestation and bootstrap snapshots record where work stands — then Scope Drift™ handles new requests against locked terms going forward.
Bottom line
Scope creep is cheaper to prevent in the SOW than to fight in week six. Scan deliverables, milestones, revisions, and approvers before lock; use Scope Drift when chat outruns the contract.