When Your Contract Is Solid… But Your SOW Breaks the Deal
What happens when your legal agreement is airtight, but your Statement of Work (SOW) blows up your deal?
I recently got a call from a CEO in crisis. His company had a major services agreement with a client, with hundreds of thousands of dollars on the line.
The main contract was solid, well-drafted, and clearly negotiated. The dispute had nothing to do with the main contract.
Instead, it was about the SOW (aka, a Work Order, Task Order, or Project Schedule). It had been handed off to the business executives on the deal to work out.
It was written in pure business shorthand. No attempt to align with the defined terms in the main agreement. Key concepts in casual language that made perfect sense to the people who wrote it… except those people had since left both companies.
My client thought he understood what the deal meant; he just couldn't prove it. And he couldn't show the other side was clearly wrong either.
Either he would have to eat a very bad settlement, or face expensive litigation: lawyers digging through years of emails reconstructing what two sets of executives actually agreed to.
Here is what businesses get wrong all the time:
They insist on a properly drafted master agreement… then leave the SOW entirely to the business team.
But an SOW is not a business memo. Its terms are just as much a part of the legally binding agreement as your indemnification clause or limitation of liability section. It should not get treated like a Post-it note.
The most common SOW problems I see:
• Terminology that doesn't match the defined terms in the main agreement, creating ambiguity about which obligations apply.
• Deliverables and milestones in vague shorthand that only makes sense to the people who wrote it.
• No clear ownership of who is responsible for what, and by when.
• Gaps filled in verbally or by email, with no formal amendment ever made.
How to do it right:
1. Treat the SOW like a contract, because it is part of one. Get counsel involved, or at minimum have counsel review before signing.
2. Mirror your defined terms. If the main agreement uses specific language, the SOW should use the same language, not a paraphrase.
3. Draft it for strangers. Assume every business person who negotiated the deal will be gone by the time a dispute arises. The SOW must stand on its own for executives who were not in the room.
4. Build in an amendment habit. When scope, timelines, or deliverables shift (and they will) document it. A short written amendment now is worth far more than a long litigation later.
None of this is a guarantee. Complex projects shift and informal understandings happen. But clear, well-drafted SOWs dramatically reduce the risk that a business disagreement becomes an expensive legal one.
The main agreement is *not* the whole agreement. Treat the SOW the same way.
ASK A QUESTION OR SCHEDULE A MEETING/CALL.
Disclaimer: This article constitutes attorney advertising. Prior results do not guarantee a similar outcome. MGLS publishes this article for information purposes only. Nothing within is intended as legal advice.