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?
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."
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."
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."
Want to participate in this discussion?
Email owner@terms.law to request access