A statement of work turns a commercial agreement into an executable piece of work. It should define outcomes, deliverables, responsibilities, acceptance, schedule, price, change and exit clearly enough that the parties can tell whether the work is complete.
This is a procurement operating guide, not legal advice. Use qualified counsel for contract drafting and jurisdiction-specific issues.
TL;DR
Write for outcomes and acceptance, not vague activity.
Make assumptions, dependencies, responsibilities and exclusions explicit.
Connect milestones and payment to objective evidence.
Use change control before work, cost or dates move.
Plan knowledge transfer, data return and exit from the start.
What belongs in a statement of work
Purpose and outcomes. State the business problem and the observable outcome the work must produce.
Scope. Define included work, locations, users, systems, categories or business units.
Deliverables. Describe tangible outputs, format, owner and due date.
Acceptance criteria. Specify how each deliverable is tested, who accepts it, the review period and what happens after rejection.
Responsibilities. Use a clear responsibility model for supplier, buyer and third parties.
Assumptions and dependencies. Record access, data, decisions, resources and predecessor work required.
Exclusions. State what is outside scope to reduce later ambiguity.
Plan and milestones. Connect dates to dependencies, decisions and evidence—not only calendar promises.
Commercial model. Explain fixed price, time and materials, milestone, unit, consumption or outcome-based charging.
Expenses and pass-through costs. Define what is included, approval rules, evidence and mark-ups.
Governance and reporting. Name operational owners, meeting cadence, decisions, status evidence and escalation.
Change control. Require a written impact assessment and approval before scope, price, resources or schedule changes.
Security, data and access. Identify information, environments, locations, user access and return or deletion obligations.
Intellectual property. Align ownership and licences for background material, deliverables, data and third-party components with the main agreement.
Service and quality measures. Define defects, tolerances, response, correction and repeated failure where relevant.
Transition and exit. Specify handover, documentation, knowledge transfer, continuity and final data treatment.
Turn deliverables into acceptance tests
“Implement the platform” is not an acceptance criterion. Better criteria name the environment, configured processes, migrated data, integrations, tests, training, documentation and decision owner. The test should distinguish complete, conditionally accepted and rejected work.
Choose a commercial model that matches uncertainty
Fixed price: works best when scope and acceptance can be defined and change is controlled.
Time and materials: fits uncertain work but needs rate, role, cap, approval and productivity controls.
Milestone: links payment to agreed evidence; milestones must represent value, not arbitrary dates.
Unit or consumption: requires clear units, measurement, forecasts and volume bands.
Outcome-based: requires measurable outcomes, causal boundaries, data access and treatment of external factors.
The change-control minimum
Every proposed change should identify the request, reason, scope impact, commercial impact, schedule impact, risk, affected dependencies and approval authority. Do not allow work to proceed on an informal instruction if the resulting cost or obligation is unclear.
Common failure modes
copying a supplier proposal into the contract without resolving assumptions;
describing effort rather than outcomes;
leaving acceptance subjective or silent;
placing buyer dependencies in meeting notes instead of the SOW;
using day rates without role definitions, caps or approvals;
allowing change by email without commercial impact assessment;
conflicting terms between the SOW and master agreement; and
forgetting transition, data return and knowledge transfer.
How procurement, Legal and the business divide ownership
The business owner defines outcomes and accepts delivery. Procurement tests scope, commercials, competition, supplier capacity and change controls. Legal advises on drafting, enforceability and risk allocation. The supplier validates feasibility, resources, assumptions and evidence. One named owner should coordinate the complete position.
Use Procurement Contract Ownership for post-signature accountability, Contract Management Explained for the operating model and the AI Contract Management Platforms vendor landscape when assessing technology.
FAQ
Is a statement of work the same as a contract?
A SOW is normally part of the contractual documents and should state how it relates to the master agreement and other schedules. The exact legal structure depends on the arrangement.
Who should write the SOW?
The buyer and supplier should develop it collaboratively, with the business owner accountable for outcomes and acceptance and with procurement and Legal reviewing their respective areas.