Statement of Work (SOW)

A Statement of Work (SOW) is the government-written document within a contract that precisely defines what the contractor must do, specifying the tasks to be performed, deliverables required, standards to be met, and constraints to be observed.

What is a Statement of Work?

A SOW is a prescriptive document, it tells the contractor what to do and how to do it, rather than defining outcomes and letting the contractor determine the approach. SOWs are used when the government has a clear understanding of exactly what it needs and wants to control the method of performance as well as the result.

A complete SOW typically includes:

• Scope of work: the overall purpose and boundaries of the contract effort
• Background: context about the program and current state
• Tasks: a numbered list of specific activities the contractor must perform
• Deliverables: reports, systems, products, or other outputs required, often cross-referenced to a Contract Data Requirements List (CDRL)
• Schedule: when each task and deliverable is due
• Performance standards: quality levels required (often referencing specific standards or specifications)
• Government-furnished items: equipment, information, or facilities the government will provide
• Contractor responsibilities: what the contractor must supply
• Applicable documents: standards, regulations, and references the contractor must follow

The SOW contrasts with the Performance Work Statement (PWS), which describes outcomes and standards rather than specific tasks, and the Statement of Objectives (SOO), which describes goals and allows offerors to propose their own technical approach.

Why the SOW matters for government contractors

The SOW is the core of your contract, every deliverable, every meeting, every system you are obligated to produce is defined here. Reading the SOW carefully before bidding reveals scope risks, understated complexity, and ambiguities that could become costly disputes. After award, the SOW becomes your baseline for managing contract performance: any work the government asks for that is not in the SOW is a potential constructive change that you may be entitled to additional compensation for. Many disputes in contract administration come from differing interpretations of SOW language, investing in a clear, unambiguous SOW during the pre-award phase benefits both parties. Learn more in our guide on how to write a winning government proposal.

Example

The Department of Health and Human Services issues a SOW for IT help desk support. The SOW specifies: Task 1, Operate a Tier 1-3 help desk during business hours; Task 2, Maintain a ticket tracking system with specified data fields; Task 3, Produce monthly performance reports by the 5th of each month; Deliverable 1, Monthly Performance Report (not to exceed 10 pages); Standard, 95% of Tier 1 tickets resolved within 4 hours. A contractor who reads this SOW closely notices that "business hours" is not defined, they submit a question during the RFP Q&A period that results in a clarifying amendment defining business hours as 8 AM to 6 PM Eastern, Monday through Friday excluding federal holidays.

Frequently Asked Questions

What is the difference between a SOW, a PWS, and a SOO?

A SOW specifies how to do the work (task-based, prescriptive). A PWS specifies what results must be achieved (outcome-based, used in performance-based acquisitions). A SOO specifies what the government wants to achieve at a high level, letting offerors propose their own performance standards and approach. SOWs give the government more control; PWS and SOO give contractors more flexibility.

Can a contractor propose changes to the SOW before award?

Yes, in the Q&A process or through RFP comments. After award, changes require a bilateral contract modification signed by the contracting officer. Contractors should not simply start doing things differently than the SOW requires without a formal modification.

What happens when the government asks for work outside the SOW?

Work outside the SOW scope is a candidate for an out-of-scope change order or Request for Equitable Adjustment (REA). Contractors should document all out-of-scope direction in writing and obtain a contracting officer direction before performing it. Performing out-of-scope work without proper authority can result in the work being treated as a gift to the government.

How detailed should a good SOW be?

Detailed enough that a qualified contractor can price the work without significant assumptions, but not so prescriptive that it prevents innovation or causes problems when circumstances change. The right level of detail depends on the procurement type: research contracts warrant less detail than production contracts.