The three phrases that create it
Scope creep almost always traces back to one of three pieces of language.
1. An undefined deliverable
"Website design" is not a deliverable. It's a category. How many pages? How many concepts? Does it include copywriting? Mobile layouts? A deliverable is specific enough that both sides would agree on whether it's finished.
2. "Reasonable" anything
"Reasonable revisions," "reasonable support," "reasonable turnaround." Reasonable is decided by whoever has more leverage after the contract is signed. A number is not negotiable after the fact; "reasonable" always is.
3. No change-order process
If a contract says what the work is but never says what happens when the work changes, every change becomes a conversation instead of a process. Contracts that survive scope creep define the mechanism before it's needed.
What a scope section looks like when it's done properly
Workable: A numbered list of deliverables, a stated revision count, a defined acceptance test ("deliverable is accepted when X"), and a clause stating that work outside the listed deliverables requires a written change order at a stated hourly rate.
Worth pushing back on: A one-line description of the project, "revisions until client is satisfied," no acceptance criteria, and no mention of what happens if the brief changes. Each of those individually is survivable. Together they mean the project ends when the client decides it ends.
Why the acceptance clause matters more than the revision count
Most advice on scope creep focuses on capping revisions. Capping revisions helps, but it addresses the symptom.
The clause that actually ends a project is the acceptance clause — the one that defines when a deliverable is considered complete and payment becomes due. Without it, a project can technically remain open forever even with a revision cap, because nothing in the contract states the point at which the work is done.
The part most guides skip: silence is acceptanceA well-drafted acceptance clause usually includes a deemed-acceptance window — something like "deliverables are deemed accepted if the client does not respond within 10 business days." This is the single most useful sentence a freelancer can add, and it is almost never in a client-supplied template. Without it, a client who simply stops replying can leave a project unfinished and unpaid indefinitely, and nothing in the contract forces a resolution.
Questions to ask before you sign
- Are the deliverables listed specifically enough that we would both agree when they are done?
- How many revisions are included, as a number?
- What happens when work falls outside the listed deliverables?
- Is there a written change-order process, and what rate applies?
- Is there a deemed-acceptance window if the client goes quiet?
- Does the payment schedule tie to milestones or only to final delivery?
Sources
- Project Management Institute — definitions of scope creep and change control in the PMBOK Guide
- U.S. Small Business Administration — guidance on written contracts for small businesses
This is general information, not legal advice. Docly helps you find and understand what a document actually says. It does not tell you whether a clause is enforceable where you live, and it is not a substitute for a lawyer. For a decision with real money attached, get advice from an attorney licensed in your state.
Find out what your contract actually says
Paste a clause or upload the whole document and ask in plain English. Every answer cites the exact line it came from.
Check a clause free →