What Is a Statement of Work?
A statement of work is a formal document that defines the work to be performed under a contract or business agreement. It specifies the deliverables, timeline, responsibilities, acceptance criteria, and commercial terms for a specific engagement. Unlike a general contract (which defines the legal relationship between parties), an SOW defines the specific scope of one particular project or phase. A master services agreement (MSA) often covers the legal framework; the SOW is the attachment that defines what this project will actually do.
- SOW defines scope, deliverables, and schedule for a specific engagement
- MSA defines the overarching legal relationship between two companies
- Change orders are formal amendments to an existing SOW
The 9 Key Sections of a Statement of Work
A complete SOW covers the full scope of the engagement, leaving no ambiguity about what is in scope, out of scope, or dependent on the other party. Every section serves a specific protective purpose.
- Project overview: High-level description of the engagement and its business objectives
- Scope of work: A precise description of every deliverable and task included
- Out of scope: Explicit list of related work NOT included — often the most important section
- Deliverables: Each deliverable with format, quality standard, and acceptance criteria
- Timeline and milestones: Start date, end date, key milestones, and dependencies
- Roles and responsibilities: What the vendor will do vs. what the client must provide
- Assumptions and dependencies: What must be true for this SOW to be achievable
- Change management process: How scope changes will be requested, evaluated, and priced
- Commercial terms: Fees, payment schedule, expenses policy, and invoicing process
Writing the Scope of Work Section
The scope of work section is the most critical and most often written poorly. Effective scope writing is specific and measurable. Avoid phrases like "advise on best practices" or "support the implementation" — these are open-ended and will be interpreted differently by each party. Instead, write "deliver a 20-page best practices document covering X, Y, and Z topics" or "provide up to 10 hours of implementation support per week during the build phase." For each deliverable, define what the output will look like, what format it will be in, and what makes it complete.
Defining Acceptance Criteria
Acceptance criteria specify the conditions under which the client agrees a deliverable is complete. Without acceptance criteria, "done" is subjective — which is the source of most engagement disputes. For each deliverable, document: the format (e.g., Word document, Excel model, working software feature), the quality standard (e.g., reviewed and approved by the Head of Finance), the review period (e.g., client has 5 business days to provide feedback or the deliverable is deemed accepted), and the number of revision rounds included. Acceptance criteria also protect the vendor from open-ended revision loops that add cost without additional compensation.
Managing Scope Creep
Scope creep — the gradual expansion of project scope without a corresponding increase in time or budget — is the leading cause of project cost overruns. An effective change management process in the SOW prevents scope creep by creating a formal path for scope additions. When a client requests something outside the defined scope, the process should be: acknowledge the request, prepare a change order estimate within an agreed timeframe (e.g., 3 business days), and obtain written approval before any out-of-scope work begins. The SOW should explicitly state that verbal approval is insufficient.
- All scope changes require a written change order signed by both parties
- No out-of-scope work begins until the change order is fully executed
- Change orders define additional cost, timeline impact, and revised deliverables
AI-Assisted SOW Writing
FreedomAI can generate a first-draft SOW from a project brief or proposal document. It identifies and pre-populates each section, flags common omissions (such as a missing change management clause or undefined acceptance criteria), and cross-references the deliverables section against the timeline to ensure they are consistent. Legal review is always recommended for SOWs above a certain value threshold — but AI handles the structural and content drafting so your legal team reviews a complete document rather than a blank template.