Private members-only forum

Best contract language to prevent scope creep?

Started by legal_eagle_wannabe · Mar 14, 2025 · 11 replies
For informational purposes only. Not legal advice.
LE
legal_eagle_wannabe OP

Every project I take on, the client keeps adding "small" requests that aren't in scope. By the end I've done 50% more work for the same fixed price. What contract language actually works to prevent this?

JM
Jessica_M_12

Two things that work for me:

1. Explicit exclusions: Don't just list what's included. List what's NOT included. "This SOW does not include: API integrations, mobile responsive design, content creation, SEO optimization..."

2. Change order clause: "Any work not explicitly described in Exhibit A requires a signed Change Order with separate pricing before work begins."

TY
tyler_92_5

Not gonna lie from what I've heard, i switched to "fixed price per phase" with defined milestones. Each phase has specific deliverables. Want something different? That's a new phase with new pricing.

Also helpful: "Revisions limited to 2 rounds. Additional revision rounds billed at $X/hour."

TN
totally_not_spam_2 Attorney

Fwiw from a legal standpoint, your SOW needs to be crystal clear. Courts will interpret ambiguity against the drafter (you). Include:

• Detailed scope with specific deliverables
• Assumptions that must hold true
• Dependencies on client (content, feedback timelines)
• Change order process with written approval requirement
• Price adjustment mechanism for scope changes

The contract won't stop clients from asking. But it gives you leverage to say "happy to do this, here's the change order."

LA
landlordissues_10

After getting burned by scope creep on three consecutive projects, I completely rewrote my contract. Clauses that have actually saved me:

  1. Explicit scope definition with exclusions: "The following items are specifically EXCLUDED from scope: [list]. Any work on excluded items requires a separate SOW and additional fees."
  2. Change order process: "All scope changes must be submitted in writing, acknowledged by Consultant, and accompanied by a signed Change Order specifying additional fees and timeline impact before work begins."
  3. Deemed acceptance: "Deliverables are deemed accepted if Client does not provide specific written objections within 10 business days of delivery."
  4. Round limits for revisions: "Fee includes up to 2 rounds of revisions. Additional revision rounds billed at $X/hour."

The key insight: scope creep is a CONTRACT problem, not a relationship problem. If your contract doesn't define boundaries, your client will naturally expand scope — they're not being malicious, they just don't know where the line is.

PD
pete_driver_28

Liquidated damages clauses need to be a reasonable estimate of actual damages at the time the contract was signed. If the amount is disproportionate to actual harm, courts will often strike it as an unenforceable penalty.