Scope of Work Clause: How Vague Language Leads to Unpaid Overtime
5 min read · Updated April 2026
You quoted a project for a landing page. Three months later you've built five pages, rewritten the copy twice, and attended eleven "quick calls" — all for the original fee. This is scope creep, and it almost always starts with a vague scope of work clause.
A well-written scope of work clause is your best protection against unpaid work. A vague one is an open invitation to do more for the same price.
What is a scope of work clause?
A scope of work (SOW) clause defines exactly what you will deliver, what you won't deliver, and how changes are handled. It sets the boundary between the work you agreed to do and additional work that should be billed separately.
Vague scope (dangerous)
“"Contractor will provide design services and any additional tasks as reasonably requested by Client during the engagement."”
Tight scope (what you want)
“"Contractor will deliver: (1) homepage design mockup (desktop + mobile), (2) up to 2 rounds of revisions. Work not listed above, including additional pages, copy changes, or development tasks, is out of scope and subject to a separate change order."”
Phrases that cause scope creep
- ✗"Additional tasks as needed" or "as reasonably requested" — no limit on what clients can ask for
- ✗"Related services" — anything tangentially connected to the project can be pulled in
- ✗"Until the project is complete" — who defines complete?
- ✗"Ongoing support" without a defined time limit or response SLA
- ✗No revision limit — unlimited revision rounds can multiply your time by 5×
What a strong SOW includes
An explicit deliverables list
Name every deliverable specifically. If it's not on the list, it's not in scope. Include formats, quantities, and versions (e.g., "3 logo variations in SVG and PNG format").
A revision limit
"Up to 2 rounds of revisions" is standard. Anything beyond that triggers a change order at your hourly rate.
A change order process
Define how out-of-scope requests are handled: client submits a written request, you provide a quote, work only begins after approval. This prevents verbal scope creep.
An exclusion list
Explicitly state what is NOT included. "This agreement does not include development, copy writing, SEO, or ongoing maintenance." Exclusions are as important as inclusions.
How Clausix detects scope creep risk
Clausix scans your contract for open-ended scope language, missing revision limits, and absent change order processes. It flags the exact phrases that invite scope creep and explains in plain English why they're risky.
Quick checklist
- ☐Are deliverables listed specifically — not described vaguely?
- ☐Is there a revision limit (e.g., 2 rounds)?
- ☐Is there a written change order process for out-of-scope requests?
- ☐Does the contract explicitly exclude common scope-creep areas (dev, copy, support)?
- ☐Is "project completion" defined with clear acceptance criteria?
Is your scope of work tight enough?
Clausix — the AI contract scanner — spots vague scope language before you sign so you can negotiate a contract that protects your time.
Analyze your contract freeNot legal advice — always consult a licensed attorney for high-stakes matters.