How Scope Creep Happens
You agree to a project scope. You start delivering. A client asks for one small change. Then another. Then a revision to a revision. Six weeks in, you've delivered 60% more work than you scoped — and you're still charging the original price.
Scope creep almost always happens because the project data is poor: the original scope isn't clearly documented, deliverables aren't tracked against what was agreed, and change requests aren't flagged as out-of-scope before work begins.
The Project Data You Need
For every project, capture:
At project start:
- Scope statement (exactly what's included — written, not verbal)
- Deliverables list (what you will hand off, in what format, on what dates)
- Revision policy (how many revision rounds are included)
- Out-of-scope examples (things that would trigger a change order)
During the project:
- Completed deliverables (date delivered, version, client acknowledgment)
- Change requests (what was asked, when, whether it was in-scope or out-of-scope)
- Hours tracked (if you're on retainer or time-based billing)
- Client communications log (key decisions made, approvals given)
See exactly what's wrong with your data — try Sohovi free — try Sohovi free.
At project end:
- All deliverables delivered and confirmed
- Any remaining change requests and their status
- Invoice reconciliation (did you bill what was agreed plus any approved additions?)
The Scope Tracker
A simple project tracker in Notion or a spreadsheet:
| Deliverable | Status | Due Date | Delivered Date | Version | Notes | |---|---|---|---|---|---| | Brand guidelines | Delivered | May 15 | May 14 | v1 | Client approved via email | | Social media kit | In progress | May 31 | — | — | — | | Final logo files | Not started | June 7 | — | — | — |
When a client asks for something not on this list, you have a clear basis for the conversation: "That's not on our original deliverables list — I'd be happy to add it as a change order."
The Change Order Habit
Every out-of-scope request should be captured in a short written confirmation:
"Just confirming our conversation: you'd like me to add [X] to the project scope. This will require approximately [Y hours] at my rate of [Z], totaling [$amount]. I'll add this to the next invoice and start [X] after I receive your confirmation."
Documenting change orders in writing — even just in email — protects your income and professionalizes your client relationships. Clients who respect clear boundaries are better long-term clients.
