A useful scope creep clause does not make change impossible. It makes change observable, priced, and approved. Adapt this sample to your work and have qualified counsel review contract language for your situation.
Copy this scope creep clause
Scope baseline. The services, deliverables, quantities, formats, assumptions, dependencies, and revision rounds included in this project are those listed in the approved scope of work.
Changes. A request that adds, replaces, reopens, or materially changes an approved deliverable, audience, format, direction, quantity, dependency, or deadline will be reviewed as a change to scope.
Impact review. Before performing changed work, the service provider will describe the requested change and any effect on fees, schedule, deliverables, or client responsibilities.
Approval. Changed work will begin only after both parties approve the impact in writing. Silence, discussion, or receipt of a request does not constitute approval to proceed.
Options. The parties may approve an added fee, trade an existing deliverable, move the request to a later phase, or decline the change and continue with the approved scope.
Fill in these details before you use it
- Link the clause to a specific list of deliverables and exclusions.
- State how many revision rounds are included and what a revision means.
- Name the channel that counts as written approval.
- Define who can approve changes for each party.
- Explain how timeline changes and paused work will be handled.
Use a four-option response when the request arrives
This request changes [baseline item] by [difference]. I can add it for [fee and schedule], trade it for [included item], plan it as a later phase, or continue with the approved scope. Please confirm your preferred option before I schedule the change.
The clause establishes the rule; the response makes the next decision easy. See more scope creep email examples and the complete change request workflow.
Need language for the next request?
Get the free guide with seven calm, practical replies for common extra requests, or use the full system to record scope, calculate impact, and preserve approval.
Frequently asked questions
What should a scope creep clause include?
Identify the approved deliverables and assumptions, define what counts as a change, require a written impact estimate and approval, and state that extra work does not begin until approval.
Does a scope creep clause prevent every extra request?
No. It gives both parties a predictable way to evaluate requests. The goal is not to forbid change, but to make its fee, timing, and tradeoffs visible before work begins.
Can a client trade one deliverable for another?
Yes, when both parties document the trade and confirm that it does not create additional effort, risk, or delay. If it does, use a change request instead.