Scope Creep Clause: Template + Examples for Contracts
What a scope creep clause is, the 5 parts it needs, and copy-paste examples for projects and retainers, so extra work gets a price before it starts.
What is a scope creep clause?
A scope creep clause (also called an out-of-scope work clause or change order clause) is the part of your contract that says what happens when a client asks for work you didn't agree to. It defines what counts as extra work, how the client requests it, how it's priced, how it moves the deadline, and that nothing extra starts until the client approves it in writing.
It doesn't stop clients from asking for more. It turns every "can you just…" into a clear next step: a price and a timeline the client says yes or no to.
Why a scope of work alone isn't enough
A good scope of work lists what's included. But it doesn't say what happens when a request falls outside that list. Without a rule, the default is informal: you're on a call, the client asks for "one small thing," and you do it to keep the peace.
Project management guidance draws the same line. A PMI article on preventing scope creep separates the two: scope creep is work done outside the agreed scope without approval or an agreement for extra payment, while a scope change is acknowledged and agreed. Another PMI piece on controlling scope creep recommends agreeing up front on how out-of-scope work will be evaluated, accepted, and performed. Your clause is where that agreement lives.
What should a scope creep clause include?
A useful scope creep clause has five parts: a definition of out-of-scope work, a request process, a pricing rule, a timeline rule, and a no-work-before-approval rule. Leave out any one of them and the gap is where unpaid work slips in.
Part | What it says | Why it matters |
|---|---|---|
1. Definition | What counts as out of scope (new deliverables, extra revisions, changes to approved work, new direction) | Ends "I thought that was included" debates |
2. Request process | Requests come in writing, through one channel | Stops verbal asks on calls from becoming free work |
3. Pricing rule | Your hourly rate or a flat fee per item | Makes the quote predictable, not a negotiation |
4. Timeline rule | Approved extras move the deadline | Protects the original delivery date from silent overload |
5. Approval rule | No extra work starts until the client approves the price in writing | This is the line that actually stops scope creep |
1. Define out-of-scope work
Don't try to list everything you won't do. List the categories:
New deliverables not listed in the scope of work (a new page, a new ad set, a new video cut).
Revision rounds beyond the number included.
Changes to work the client already approved.
A new direction, brief, or strategy after work has started.
Rush requests that need work outside the agreed schedule.
2. Set the request process
Say where requests go (email, a form, a client portal) and that requests made in calls or chats aren't approved until they're confirmed in writing. One channel also gives you a record of what was asked and when.
3. Set the pricing rule
Pick one: hourly at your standard rate, or a flat fee per item from a price list. If changes often cause rework in finished parts of the project, say the quote covers that too. Our guide on how to price a change request shows how to include rework and timeline costs in the number.
4. Set the timeline rule
Extra work takes extra time. State that each approved change comes with an updated deadline, so the client can't add a week of work and keep the old launch date.
5. Require approval before work starts
This is the most important sentence in the clause. A price agreed before the work is just business. A price raised after the work is an argument.
Scope creep clause example for a project contract
Below is example language you can adapt. It's a starting point, not legal advice, so have a lawyer review it for your country and your contract.
Out-of-scope work and changes. The services are limited to the deliverables, revision rounds, and timeline listed in the Scope of Work. Any request for new deliverables, revision rounds beyond those included, changes to work the Client has already approved, or a change in direction is out of scope.
The Client will submit out-of-scope requests in writing to [email / request link]. Requests made verbally or in meetings are not approved until confirmed in writing.
For each out-of-scope request, the [Freelancer / Agency] will send a written quote stating the work, the price, and any change to the timeline. Out-of-scope work is billed at [$X per hour] or the flat fee stated in the quote.
Out-of-scope work will not begin until the Client approves the quote in writing. Approved changes extend the project timeline by the amount stated in the quote.
If your main problem is revision rounds, add a dedicated revision clause too. We cover that, with sample wording, in how to charge for extra revisions.
Scope creep clause example for a monthly retainer
Retainers creep differently. The risk isn't one big change; it's lots of small asks that quietly go past the hours or deliverables you sold. A retainer clause needs a monthly limit and a rule for what happens past it.
Monthly scope. Each month the retainer includes [the deliverables listed in Schedule A / up to X hours]. Unused hours [do / do not] roll over.
Requests beyond the monthly scope will be quoted in writing before work starts, at [$X per hour] or the fee stated in the quote. The Client may approve the extra work, move the request to the next month, or decline it.
Work on requests beyond the monthly scope will not begin without the Client's written approval.
Giving the client three options (pay now, wait until next month, or drop it) keeps the conversation calm. They stay in control, and you never absorb the extra.
Not sure your retainer price leaves room for any of this? The free retainer pricing calculator helps you work out a monthly fee from hours and rate.
Worked example: how the clause plays out (hypothetical)
This is a made-up example to show the mechanics, not a real client.
A freelance web designer signs a five-page website project with two revision rounds per page. Her rate is $60/hour. In week three, the client asks on a call for a sixth page with a booking form.
Without a clause: she says "sure," builds it in about 6 hours, and adjusts the navigation and footer on the other five pages, about 2 more hours. That's 8 hours, or $480 of work, that nobody agreed to pay for, and the launch slips two days.
With the clause: she replies, "Happy to add that. It's outside the five pages in our scope, so I'll send a quote." Her quote: 8 hours × $60 = $480, plus two extra business days on the timeline. The client approves in writing, and the work starts.
Same request, same work. The only difference is that the price was agreed first.
Common mistakes to avoid
Vague scope. "Website redesign" gives a clause nothing to point at. List deliverables with quantities.
No rate. "Additional work will be billed separately" invites a fight about how much. Put the rate in.
Allowing verbal approval. Ask for written confirmation, even a one-line email reply.
Never using it. A clause you don't enforce teaches clients it doesn't apply. Quote the first extra, even if it's small.
Being harsh about it. The clause does the hard part; your reply can stay friendly. For wording, see how to tell a client it's out of scope.
Make the clause easy to follow day to day
A clause only works if each request actually gets checked against it. In practice that means one place for requests, a quick check against the scope, and a quote the client can approve without a long email thread. A simple change request form covers the paperwork, and the free scope creep calculator shows what unquoted extras are costing you each month.
That's the workflow I built Creepless around. Each client gets a private request link with no login. Every request is checked against the scope you set, and extras get a suggested price and a drafted reply. The client approves the quote before any work starts. You can try it in the live demo (the sample clients there are fictional), and the free plan covers 2 clients and 20 AI checks with no card needed.
FAQ: scope creep clauses
Where does a scope creep clause go in a contract?
Put it right after the scope of work or deliverables section, so the client reads what's included and what happens to everything else in the same place. Some contracts call it "Changes" or "Out-of-Scope Work."
Is a scope creep clause the same as a change order clause?
Mostly, yes. A change order clause focuses on the paperwork for approving a change. A scope creep clause usually also defines what counts as out of scope and sets the price and timeline rules. The best version does all of it.
Can I add a scope creep clause to a project that's already started?
Yes, but you'll need the client to agree to it, for example in an updated scope or a short amendment. A friendly way to raise it is: "To keep things fast as requests come in, here's how we'll handle anything beyond the original plan."
Should I charge hourly or a flat fee for out-of-scope work?
Hourly is easier when the work is hard to predict. Flat fees are easier for clients to approve and work well for repeat items like an extra page or an extra revision round. Many freelancers and agencies list both and pick per request.
Do I need a lawyer to write a scope creep clause?
You can draft one yourself from examples like the ones above, but contract rules vary by country, so it's worth having a lawyer review your full contract once.
Creepless checks every client request against the scope you agreed.