What Is Scope Creep?
Scope creep is a project gradually growing beyond what was agreed — extra features, added pages, "quick" revisions — without matching changes to the fee or the deadline. No single request causes it; it's the accumulation of small additions that were each too minor to renegotiate over.
Why it matters
Scope creep is rarely malicious, which is what makes it expensive: each request feels reasonable, refusing feels petty, and by project's end the effective hourly rate has collapsed. It isn't really a client-behavior problem — it's a contract problem. A deal with a tight scope of work, capped revisions, and a written change-order path makes the growth visible and priced; a vague one makes it invisible and free.
What to watch for
- A vague SOW — creep's precondition (see scope of work).
- Unlimited or uncounted revisions, where polishing never formally ends.
- Fixed fee + open-ended scope — the combination that concentrates all growth risk on the person delivering.
- Feedback from many voices: multiple stakeholders each adding "one thing," with nobody owning the total.
A realistic example
A designer quotes a fixed fee for a logo with two revision rounds — but the contract never says "two." Round three arrives with the marketing lead's notes, round five with the founder's. Each email says "small tweak." By sign-off the project has consumed double its budgeted hours, and there's no line in the contract to invoice against.
What to ask for
- Count what's countable: deliverables, revision rounds, and review cycles as numbers in the SOW.
- A change-order path: new requests get a written mini-quote before the work happens.
- A stated rate for out-of-scope work, so "can you also…" always has a known price attached.
Related terms: scope of work · net 30 · kill fee Related guide: What to negotiate before you sign
Find out whether your contract leaves scope open-ended — 👉 Analyze your contract free, 3 analyses every month, no card.
Not legal advice. This is an educational definition of a common contract term. Details vary by jurisdiction — this page explains common U.S. usage. For high-stakes agreements, have a lawyer review the final version.