A Statement of Work (SOW) is a document that defines the specific deliverables, timeline, pricing, and acceptance criteria for a particular engagement - typically executed under a governing Master Service Agreement. It converts an abstract commercial relationship into a scoped, invoiceable piece of work.
How a Statement of Work works
A software services firm and a manufacturing customer sign a five-year Master Service Agreement covering commercial terms, IP, liability caps, and payment schedules. For each specific project - a data migration, an integration build, or a support engagement - the two parties sign a discrete SOW that names the deliverables, milestones, unit rates, and acceptance test.
Every SOW contains six elements: scope, deliverables and acceptance criteria, timeline, pricing and payment schedule, personnel and dependencies, and change-control process. The MSA governs; the SOW performs.
Where Statements of Work appear in contracts
SOWs sit inside professional services, IT services, marketing agency, and outsourcing agreements. They call off against the MSA the way a purchase order calls off against a framework agreement. Every SOW carries its own contract obligation stack tied to defined deliverables and dates. Without a scoped SOW, disputes over what was actually agreed collapse straight into the MSA dispute-resolution clause.
Statement of Work FAQ
Does a SOW require a separate signature?
Yes. Each SOW is signed by an authorised representative of each party. The MSA governs the terms; the SOW commits both sides to a specific piece of work.
Can an SOW override the MSA?
Only where the SOW says so explicitly and the MSA permits it. Standard drafting states the MSA prevails on conflict unless the SOW is signed by a defined seniority level.
What is the difference between a SOW and a change order?
An SOW authorises the original scope. A change order amends an existing SOW - adjusting scope, timeline, or price - without triggering a new one.
