================================================================ SCOPE CREEP CONTRACT CLAUSES — PLUG-AND-PLAY TEMPLATES Free resource from SoloStack | solostack.madethis.app ================================================================ 5 contract clause templates that prevent scope creep, plus a 10-point contract review checklist. Copy-paste the language directly into your contracts — adapt names and rates as needed. ================================================================ CLAUSE 1: CHANGE ORDER CLAUSE ================================================================ TEMPLATE LANGUAGE: --- Any work requested by Client that falls outside the scope defined in Section [X] of this Agreement ("Out-of-Scope Work") shall require a written Change Order signed by both parties before work commences. Change Orders will detail the additional deliverables, revised timeline, and additional fees. Freelancer is not obligated to perform Out-of-Scope Work without an executed Change Order. Verbal requests for additional work do not constitute an amendment to this Agreement. --- PLAIN ENGLISH — WHAT THIS PROTECTS AGAINST: Without this clause, a client can argue that you agreed to extra work verbally or that "of course" certain things were included. This forces all scope changes into a written, priced, signed document before you lift a finger. It also removes the awkward "but I asked you about it" debate — there's no signed Change Order, so the work was never agreed to. ================================================================ CLAUSE 2: SCOPE DEFINITION CLAUSE ================================================================ TEMPLATE LANGUAGE: --- The scope of this Agreement is limited to the deliverables expressly described in Exhibit A (Statement of Work). Deliverables not listed in Exhibit A are excluded from this Agreement. If Client requests work that is not described in Exhibit A, Freelancer will provide a written estimate and, upon written approval from Client, execute a Change Order pursuant to Section [X] of this Agreement. Freelancer shall not be responsible for delays or cost overruns resulting from requests for work outside the defined scope. --- PLAIN ENGLISH — WHAT THIS PROTECTS AGAINST: "I assumed that was included" is one of the most common scope creep arguments clients make. This clause cuts that off by making the Statement of Work the single source of truth. If it's not in Exhibit A, it's not included — full stop. It also protects you from delay penalties if scope creep causes timeline overruns. ================================================================ CLAUSE 3: "OUT OF SCOPE" CLAUSE ================================================================ TEMPLATE LANGUAGE: --- The following are explicitly excluded from the scope of this Agreement and will not be performed without an executed Change Order and additional compensation: (a) Revisions or alterations to completed and approved work; (b) Creation of additional deliverables not listed in Exhibit A; (c) Work on related projects, sister projects, or sub-projects not named in this Agreement; (d) Any deliverable requiring skills, tools, or licenses not reasonably associated with the services described herein; (e) Rush delivery of deliverables outside the agreed timeline. Client acknowledges that requesting excluded work verbally, via email, or via any other communication channel does not obligate Freelancer to perform such work. --- PLAIN ENGLISH — WHAT THIS PROTECTS AGAINST: This is your explicit exclusions list. Courts and mediators look for specificity — the more clearly you define what is NOT included, the harder it is for a client to claim "I thought it was covered." Items (c) and (e) are especially important: "can you also just quickly do this for my other project" and "can you rush it" are both classic scope creep moves this stops cold. ================================================================ CLAUSE 4: HOURLY RATE FOR ADDITIONAL WORK CLAUSE ================================================================ TEMPLATE LANGUAGE: --- Any work performed beyond the scope defined in Exhibit A, including work performed prior to execution of a formal Change Order at Client's direction, shall be billed at Freelancer's standard hourly rate of $[RATE] per hour, unless otherwise agreed in writing. Freelancer shall notify Client in writing before beginning Out-of-Scope Work and provide an estimated time requirement. Client's written approval (including email approval) constitutes authorization to proceed and an obligation to pay the resulting fees at the standard hourly rate. --- PLAIN ENGLISH — WHAT THIS PROTECTS AGAINST: This clause pre-establishes your rate for any additions, so there's no negotiation about price after the fact. It also creates a paper trail: if you notify the client in writing that additional work is being done at $[X]/hour, and they respond "ok go ahead," that email exchange is a binding agreement. Note the "prior to formal Change Order" language — this protects you if you've already done the work before realizing it was out of scope. ================================================================ CLAUSE 5: REVISION LIMIT CLAUSE ================================================================ TEMPLATE LANGUAGE: --- This Agreement includes [NUMBER] rounds of revisions for each deliverable. A "revision round" is defined as a single consolidated set of feedback provided by Client within [X] business days of delivery. Additional revision rounds beyond the included [NUMBER] will be billed at $[RATE] per hour, or [FLAT FEE] per revision round, at Freelancer's discretion. Revisions that materially alter the approved direction, scope, or deliverable type (as determined by Freelancer) may be treated as new work subject to a Change Order. --- PLAIN ENGLISH — WHAT THIS PROTECTS AGAINST: "Can we just tweak this one more time?" is revision scope creep. Unlimited revisions = unlimited unpaid time. This clause caps revisions, defines what a revision round is (consolidated feedback, not drip feedback over days), and establishes that direction changes count as new work. The "materially alter the approved direction" language is important: a client who pivots the entire creative direction after three revision rounds is not getting a free rebrand — they're getting a Change Order. ================================================================ 10-POINT CONTRACT REVIEW CHECKLIST Catching scope gaps BEFORE you sign ================================================================ Use this checklist every time you review a contract or send one to a client. Check each box before signing. [ ] 1. DELIVERABLES ARE SPECIFIC The contract names specific, countable deliverables (e.g., "3 blog posts of 1,000 words each" not "blog content as needed"). There's no room for "I thought you'd also do X." [ ] 2. OUT-OF-SCOPE EXCLUSIONS ARE LISTED At least 3-5 explicit exclusions are named in the contract. The more specific, the better. Vague "services not listed" is weaker than naming specific things that won't be covered. [ ] 3. REVISION ROUNDS ARE CAPPED The number of included revision rounds is stated. A definition of "revision round" is included (consolidated vs. drip feedback). What happens after the cap is reached is spelled out. [ ] 4. CHANGE ORDER PROCESS IS DOCUMENTED The contract specifies how Out-of-Scope requests are handled: written request → written estimate → signed Change Order → work begins. The contract explicitly says verbal requests don't count. [ ] 5. TIMELINE IS TIED TO SCOPE The delivery date is conditional on the agreed scope. If scope expands, the timeline can expand too. This prevents you from being penalized for delays caused by scope creep. [ ] 6. YOUR HOURLY RATE FOR ADDITIONS IS PRE-AGREED The contract states the rate at which additional/out-of-scope work will be billed, so there's no negotiation after the fact. [ ] 7. CLIENT APPROVAL PROCESS IS DEFINED The contract specifies how deliverables get approved (written sign-off, email, specific deadline). "Deemed approved if no response in X days" language is included to prevent limbo. [ ] 8. COMMUNICATION CHANNELS ARE SPECIFIED The contract specifies which communication channel is official (email only, project management tool). Scope requests via text or DM are explicitly excluded as binding. [ ] 9. PAYMENT IS TIED TO DELIVERABLES NOT TIME If paying in milestones, each milestone is tied to a specific, defined deliverable — not "when the project feels done" or "when the client is happy." Subjective satisfaction is not a payment trigger. [ ] 10. TERMINATION CLAUSE COVERS SCOPE EXPANSION If the client refuses to use the Change Order process and insists on unpaid scope additions, the contract allows you to terminate with compensation for work completed. You should never be trapped in a project with no exit. ================================================================ BONUS: 3 THINGS TO DO BEFORE SIGNING ANYTHING ================================================================ 1. Read it out loud. Vague language sounds more vague when spoken. If you can't explain what a clause means in plain English, rewrite it. 2. Run the "what if they ask for [X]" test. Think of the 3 most likely scope creep requests for this specific client and project. Does the contract address them? If not, add clauses before signing. 3. Send a scope summary email. Before starting work, send a brief email: "Here's what we've agreed to: [list]. Anything not on this list will require a Change Order. Let me know if I've missed anything." The client's non-objection to this email strengthens your position. ================================================================ Get the full change order template, email scripts, and 12 word-for-word scope creep response scripts at: solostack.madethis.app/resources/freelance-scope-creep ================================================================