Statement of work (SOW)

A buyer uses a statement of work (SOW) to turn a broad agreement or requirement into a defined package of work. It normally sets out the purpose, scope, deliverables, milestones, roles, dependencies, timetable, acceptance measures, price or charging basis and relevant assumptions. An SOW may be a contract document, an order under a call-off contract or a schedule that sits alongside the main agreement, depending on the buyer’s terms.

What a supplier should check

Read the SOW with the framework or master contract, order form and schedules. Confirm which document controls if there is a conflict, when the commitment starts, what acceptance means, who owns outputs and intellectual property, how changes are approved, and what happens if a dependency is late. Make sure the proposed team, day rates, fixed price or capped time-and-materials basis matches the delivery plan.

Make outputs measurable

Avoid vague outputs such as “support implementation” without a measurable result or acceptance owner. Separate supplier responsibilities from buyer dependencies and identify assumptions that affect price or dates. A signed SOW can create a specific commitment even when the overarching framework does not guarantee spend.

For example, a digital call-off might use an SOW for discovery, a prototype and a service assessment, with milestones and acceptance evidence for each. The supplier should not begin extra work because it appears in a proposal but not in the agreed SOW.

The buyer’s contract documents determine the legal effect; the acronym alone does not.