Contracts
Statement of Work vs. Contract: What's the Difference?
Agencies use the terms interchangeably in conversation, but the two documents cover different ground — and knowing which one actually governs scope matters.
"Send over the contract" and "send over the SOW" often mean the same thing in an agency Slack channel. Legally and practically, they don't always refer to the same document — and the distinction is exactly the kind of detail that determines whether a request is in scope or not.
The contract sets the relationship
A contract (sometimes called a master services agreement) covers the terms that apply across the entire working relationship: payment terms, ownership of work product, liability, termination conditions, confidentiality. It's built to be stable — it rarely needs to change project to project, because it's not describing the project. It's describing the relationship the project happens inside of.
The statement of work sets the scope
A statement of work (SOW) describes a specific engagement: what's being delivered, by when, in how many rounds of revision, and — critically — what's explicitly out of scope. This is the document that actually answers "is this request part of what we agreed to?" A contract almost never answers that question directly, because it wasn't written to.
Why the mix-up causes scope creep
When a team treats the two as interchangeable, scope conversations get vague. Someone says "check the contract" when they mean "check the SOW," opens the wrong document, doesn't find anything specific about the request in question, and concludes there's no basis to push back — when the real answer was sitting in a different file. Clear scope decisions require checking the document actually built to define scope, not just whatever's labeled "contract" in the shared drive.
What this means in practice
- Keep the SOW as the single source of truth for deliverables, limits, and exclusions.
- Reference the SOW specifically — not "the contract" generally — when discussing scope with a client.
- When a new engagement starts, write or update the SOW, even if the master contract hasn't changed.
This is also why MarginFlow parses whichever document actually defines scope — SOW, proposal, or contract — rather than assuming one format. Whatever you upload, it extracts the deliverables, limits, and exclusions that determine whether an incoming request is in scope.