Statement of Work

What a statement of work includes

A statement of work sits under a master service agreement, which holds the legal terms. The SOW holds the specifics of one engagement. A usable SOW includes:

• Scope and objectives: what the supplier will do, and what is explicitly out of scope.
• Deliverables: concrete outputs, such as a migrated payroll system, 2,000 resolved tickets a month or a completed training curriculum.
• Timeline and milestones with dates.
• Acceptance criteria: how the client decides a deliverable is done.
• Pricing model: fixed fee, milestone payments, unit pricing or capped time and materials.
• Roles and responsibilities on both sides, including what the client must provide (access, data, decisions).
• Service levels, where the work is ongoing, often in a separate service level agreement.
• Change control: how scope changes are requested, priced and approved.
• Supplier personnel terms: who manages them, where they work, background checks and access.

The weakest SOWs list the people and their rates and call it a project. That is staff augmentation with a different label.

SOW vs staff augmentation

In staff augmentation, the client buys a worker's time. A contractor fills a role, the client's manager directs the work day to day, and the client pays an hourly bill rate. In a true SOW engagement, the client buys an outcome. The supplier decides how many people to use, manages them, and is paid against deliverables or service levels.

The difference matters for three reasons. First, risk: under an SOW the supplier carries delivery risk; under staff augmentation the client does. Second, co-employment and misclassification exposure: when the client directs SOW workers like its own staff, the arrangement starts to look like staff augmentation or even direct employment, with the legal exposure that follows. Third, visibility: SOW spend often sits outside the contingent workforce program and its rate controls.

SOW workers in contingent programs

In many large companies, SOW spend has grown faster than hourly contingent spend, partly because it escapes the rate cards and approvals that a managed service provider program enforces. Managers sometimes route what is really staff augmentation through an SOW to avoid tenure limits or rate caps. Programs respond with SOW management: requiring SOWs to go through the vendor management system, tracking the people working under each SOW (names, location, system access, start and end dates) and reviewing whether each engagement is genuinely outcome-based.

Tracking SOW workers also matters for security and compliance. A company that cannot list who has badge or system access under its SOWs has a security problem, not just a cost problem.

Common mistakes

• Vague deliverables like 'support the HR transformation', which make acceptance impossible.
• Time and materials pricing with no cap, which removes the supplier's delivery risk.
• Client managers assigning tasks, approving timesheets and conducting reviews for SOW workers.
• Rolling SOWs renewed year after year for the same people doing the same work.
• No exit plan: knowledge transfer and documentation obligations at the end of the engagement.

A practical test: if the client could swap the supplier's people out without the supplier's involvement, the engagement probably is not a real SOW.