Statement of work
A statement of work (SOW) is the contract document that narrates what a supplier will deliver on a software project: the activities, the deliverables, the timeline and the standard the client will use to accept each one, so that everything left out of that narrative sits outside the supplier's obligation.
Submit a project Map your scope boundariesReviewed by David Nguyen (CEO) · Updated 14 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while preparing a software contract.
Why does a statement of work matter?
A statement of work is where a scope agreement becomes something a court, an accountant or a project manager can act on. A sales conversation can leave "what exactly are we buying" open in a dozen small ways; a statement of work closes each one by naming the deliverable, the acceptance test and the date. OutsourcingVN is operated by Netbase JSC, and a buyer reading an unfamiliar proposal should expect the statement of work, not the sales deck, to be the document that governs a dispute.
What is an example of a statement of work in practice?
A retailer contracts a supplier to build an order-management module. The statement of work names three deliverables — an order API, an admin screen and a reconciliation report — each with its own acceptance criteria and a delivery date, and it states that inventory forecasting, mentioned in an earlier call, is not part of this contract. Six weeks later the retailer asks for forecasting to be added. Because the statement of work did not include it, the request is priced and scheduled as new work rather than assumed to be already covered.
What are the common misreadings of a statement of work?
A statement of work is not the same document as a quotation or an invoice, even when it carries the commercial terms of the work: its job is to fix what is built and how it is accepted. It is also not a substitute for detailed acceptance criteria written out in full — a short SOW that only names a deliverable in one line still needs the acceptance test spelled out somewhere the two sides agree on, or the deliverable is argued about at the end rather than defined at the start. And a statement of work is not permanent: a change to the agreed deliverables needs its own written and approved change, not a quiet edit to the original document.
Plan the next step for your project
Common questions
No. The master agreement sets the ongoing legal terms between the two parties; the statement of work sets the scope, deliverables and schedule of one piece of work under that agreement.
Either side can draft the first version, but it should be reviewed and signed by both the buyer's budget owner and the supplier's delivery lead before work starts.
Which decisions does a statement of work affect?
Turning a statement of work into a line-by-line map of what is in, excluded, assumed, dependent or deferred is the subject of the software project scope boundaries guide. When you have a draft of what you want built, describe the outcome and the boundary around it, and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.