Statement of work (SOW)
A statement of work defines the specific deliverables, activities, timelines, and acceptance criteria for a project or service engagement. In procurement, SOWs form the basis for services contracts, providing clear expectations that both parties can execute and measure against.
Examples
Consulting engagement: A SOW for a procurement transformation project specifies: deliverables (category strategies for 10 categories), timeline (12 weeks), resources (2 senior consultants, 1 analyst), milestones, acceptance criteria for each deliverable, and payment terms tied to milestone completion.
IT implementation: The SOW for an e-procurement system deployment defines: scope (configure, test, deploy for 500 users), excluded items (data migration from legacy systems), assumptions, dependencies, change request process, and acceptance testing procedures.
Ongoing services: A facilities management SOW specifies service levels for each activity (cleaning frequency, response times for repairs, preventive maintenance schedules) with performance metrics that trigger service credits if not met.
Definition
The SOW is the most critical document in services procurement because services are inherently harder to define and measure than goods. Without a clear SOW, disputes arise over what was expected, what was delivered, and whether the result is acceptable.
Effective SOWs answer: what will be delivered (specific, measurable deliverables), when (timeline with milestones), by whom (resource requirements and qualifications), how quality will be verified (acceptance criteria), and what happens if expectations aren't met (remedies and governance).
Common SOW failures include: vague deliverables that allow different interpretations, missing assumptions that surface as scope gaps, no change control mechanism (leading to scope creep), unrealistic timelines, and acceptance criteria too subjective to enforce objectively.
SOWs are typically incorporated into or referenced by a master service agreement that covers general terms. This structure allows multiple SOWs (for different projects) under one MSA, avoiding renegotiation of legal terms for each new engagement.
Frequently asked questions
What is a statement of work?
A statement of work defines the specific deliverables, activities, timelines, and acceptance criteria for a project or service engagement. In procurement, SOWs form the basis of services contracts, providing clear expectations that both parties can execute and measure against.
Why is the SOW so important in services procurement?
Services are inherently harder to define and measure than goods, and without a clear SOW, disputes arise over what was expected, what was delivered, and whether the result is acceptable. The SOW is the document that settles those questions before the work starts.
What should a statement of work include?
An effective SOW answers what will be delivered (specific, measurable deliverables), when (timeline with milestones), by whom (resource requirements and qualifications), how quality will be verified (acceptance criteria), and what happens if expectations are not met (remedies and governance). A consulting SOW might specify ten category strategies in 12 weeks with named resources and milestone-tied payments.
What are the most common SOW failures?
Frequent failures include vague deliverables that allow different interpretations, missing assumptions that surface later as scope gaps, no change control mechanism (which invites scope creep), unrealistic timelines, and acceptance criteria too subjective to enforce. Each is far cheaper to fix in drafting than in dispute.
How does a SOW relate to a master service agreement?
SOWs are typically incorporated into or referenced by a master service agreement that covers general terms. That structure lets multiple SOWs for different projects run under one MSA, avoiding renegotiation of legal terms for each new engagement.
Previous