SoW (Statement of Work)

A Statement of Work, abbreviated as SoW, is a procurement document that defines the activities, deliverables, timelines, and acceptance criteria a supplier must provide under a contract. SoWs are widely used in private sector procurement, especially for technology, consulting, and professional services contracts. The document closely resembles a Terms of Reference and the two terms are often used interchangeably.

A Statement of Work, abbreviated as SoW, is a procurement document that defines the activities, deliverables, timelines, and acceptance criteria a supplier must provide under a contract. SoWs are widely used in private sector procurement, especially for technology, consulting, and professional services contracts. The document closely resembles a Terms of Reference and the two terms are often used interchangeably.

How an SoW differs from a Terms of Reference

In strict terminology, a SoW tends to be more activity-focused, while a ToR is more outcome-focused. A SoW typically lists the specific tasks the supplier will perform, the deliverables they will produce, and the schedule for completion. A ToR is more likely to describe the broader objectives and let the supplier propose how to achieve them.

The distinction matters less in practice than in theory. Many organisations use the two terms interchangeably, and many real-world procurement documents combine elements of both formats. What matters is that the document clearly communicates what the supplier must do, what they must deliver, and how performance will be evaluated.

Structure of a typical SoW

A standard SoW includes the following elements. The introduction states the purpose and context. The scope section defines what is in scope and, importantly, what is out of scope. Explicit out-of-scope statements help prevent disputes during contract delivery when the buyer wants additional work that was not originally specified.

The activities section lists the specific tasks the supplier will perform, often broken down by phase or workstream. Each activity should be specific enough that both parties can verify whether it has been completed. The deliverables section then lists the tangible outputs the supplier must produce, with format, content, and acceptance criteria for each.

The schedule section establishes when each activity and deliverable must be completed. Sophisticated SoWs use Gantt-style schedules or milestone tables. The acceptance criteria section explains how the buyer will determine whether each deliverable meets the required standard. Without clear acceptance criteria, deliverables can be debated indefinitely, leading to payment delays and contract disputes.

How SoWs work in practice

In a typical contract structure, the master agreement sets out the legal and commercial terms while the SoW specifies the technical work for a particular engagement. Master agreements are reusable across multiple SoWs, allowing the buyer to engage the same supplier for different projects without renegotiating the entire contract each time.

This structure is especially common in consulting and IT services. A consulting firm might have a master services agreement with a corporate client, under which dozens of separate SoWs are issued for different projects over several years. Each SoW is signed independently, has its own price and timeline, and refers back to the master agreement for legal terms.

Change management within an SoW requires structured handling. As work progresses, scope changes are common. Adding new activities, modifying deliverables, or extending timelines should follow a defined change order process. Without disciplined change management, scope creep can erode supplier margins and cause contract delivery problems.

Best practices for writing strong SoW responses

Suppliers responding to bids that include an SoW should mirror the structure of the buyer's document in their response. Section by section, the supplier addresses scope, activities, deliverables, schedule, team, and acceptance criteria. This makes the buyer's evaluation easier and reduces the risk that the supplier's response is judged non-responsive.

Be precise about what is included and what is not. Suppliers who promise too much in the SoW response often regret it during delivery. The acceptance criteria section is particularly important because it determines when payment is triggered and when disputes can arise. Vague acceptance criteria favour the buyer in disputes, so suppliers benefit from negotiating clear, objective criteria during contract finalisation.

Related terms

See Otnox plans to track procurement opportunities across 25 markets.