The Scope Ratchet/The Flexible Scope
The contract's scope expands beyond what was originally agreed, through mechanisms controlled by the party requesting the expansion. Drafters call it flexibility — the ability to direct work as needs evolve. Responders find themselves doing more than they priced, with no clean mechanism to get compensated.
Appeared in 40 corpus episodes across multiple industries
On this page
What It Is
The contract's scope expands beyond what was originally agreed through change orders, additional services clauses, or evolving requirements — with the expansion mechanism controlled by the party receiving the expanded work.
Two Readings
The same clause. Two entirely different contracts.
Scope needs to evolve as projects progress and requirements become clearer. Building in flexibility to direct additional work without renegotiating the whole contract keeps projects moving and reflects how real work actually happens. Rigidity here creates friction and delays.
You priced a defined scope. Now you're being asked to do more — and the mechanism for compensating you for that expansion is controlled by the party asking for it. You're caught between refusing (straining the relationship) and complying (absorbing the cost).
Recognition Signals
Contract language that signals this pattern is present.
- "Additional services as directed by Client" with no pricing mechanism
- Change order provisions where the client determines scope and compensation
- SOW language ending with "and related tasks as required" or "as agreed"
- No cap on scope expansion
- Compensation for changes left to "mutual agreement" with no fallback if agreement isn't reached
- "While you're at it" language built into the contract structure
The tell: who controls the definition of what's in scope? If it's the party receiving the work, the ratchet is installed.
What to Do
Build a clean change order procedure with defined timelines. The flexible scope works better when it has a mechanism — otherwise disputes about what's included destroy the relationship faster than the cost of the extra work.
Define the baseline scope precisely with explicit exclusions. Add a change order procedure that requires written approval before any out-of-scope work begins, with pricing agreed in advance. No written change order, no obligation to perform. Make this a habit, not a negotiation.
Where It Appears
Cross-industry appearances from the LawSnap corpus.
| Industry | How it appears |
|---|---|
| MSA / SaaS | SOW scope expands through informal requests; vendor absorbs cost or damages relationship by refusing |
| Construction | Verbal directions to proceed without signed change orders; owner later disputes the work was authorized |
| Professional Services | Engagement scope creeps through "while you're at it" requests that individually seem small |
| Employment | Job duties drift from written description, creating mismatch between written scope and actual obligations |
| Government Contracting | Scope changes directed informally, then disallowed at audit because they lacked written authorization |
LawSnap Contract Pattern Library
37 named structural patterns extracted from 107 attorney interviews and MCLE war stories across trucking, healthcare, SaaS, construction, and more. Lawyers across every industry were describing the same traps in completely different vocabulary. We cataloged them.
Browse all patterns arrow_forwardGet notified when new patterns are added.
We're cataloging all 37 patterns from the corpus. One email when new patterns go live — nothing else.
One email per update. No newsletter. Unsubscribe anytime.