A statement of work (SOW) is the project-level document that says exactly what a vendor will deliver, by when, how acceptance works and what you will pay. It usually sits under a master services agreement, and in Indian IT and HR outsourcing deals it is the paper that separates buying a service from renting people through staff augmentation.

MSA and SOW: who does what

The master services agreement (MSA) is signed once and fixes the legal terms: liability caps, IP ownership, confidentiality, data protection, termination, dispute resolution. Each SOW then covers one engagement and incorporates the MSA by reference, so a company with one MSA can run twenty SOWs with the same vendor without renegotiating indemnities each time. Neither has its own statute in India; both are ordinary contracts under the Indian Contract Act, 1872. Always check the order-of-precedence clause. Many MSAs say the MSA wins in a conflict unless the SOW expressly overrides a named clause, so a business owner who “agrees” to unlimited liability in a SOW may have agreed to nothing.

What a usable SOW contains

1. Scope, with an explicit out-of-scope list (this is where most disputes start)
2. Deliverables and milestones, each with a date
3. Acceptance criteria and who signs off
4. Commercial model: fixed price per milestone, time and material, or a monthly managed fee
5. Change request process and how changed work is priced
6. Vendor team structure, key roles and governance meetings
7. Client dependencies: access, data, approvals, environments

The HR risk sits in item 6. A SOW that lists named engineers, their hours and their reporting manager on your side, and bills monthly whatever is delivered, reads like labour supply rather than a service. That pulls in principal employer liability and, if the people stay long enough, the argument that they are really your employees, as discussed under independent contractor vs employee. Outcome-based scope, vendor-side supervision and milestone billing keep the line clear.

Frequently asked questions

Is a purchase order the same as a SOW?

No. A purchase order authorises spend and quantity; the SOW defines the work. Finance needs the PO to pay, but delivery disputes are argued on the SOW, so never sign a PO that points to a SOW still in draft.

Who should review a SOW inside the company?

The business owner for scope, finance for the commercial model, legal for conflicts with the MSA, and HR when the vendor’s people will work on site, because on-site deployment can trigger contract labour registration and licence checks.

Fixed price or time and material?

Fixed price suits work you can specify fully, such as an HRMS implementation with a defined module list. Time and material suits evolving work, but you carry the overrun risk and the engagement drifts towards augmentation.

Once SOW spend is spread across many vendors, the discipline that tracks it is contingent workforce vendor management.