Statement of work
|This article does not cite any references or sources. (September 2011)|
A statement of work (SOW) is a formal document that captures and defines the work activities, deliverables, and timeline a vendor must execute in performance of specified work for a client. The SOW usually includes detailed requirements and pricing, with standard regulatory and governance terms and conditions.
Many formats and styles of Statement of Work document templates have been specialized for the hardware or software solutions described in the Request for Proposal. Many companies create their own customized version of SOWs that are specialized or generalized to accommodate typical requests and proposals they receive.
Note that in most cases the Statement of Work is a binding contract. Master Service Agreements or Consultant/Training Service agreements postpone certain work specific contractual components that are addressed in individual Statement(s) of Work.
Areas addressed 
Areas that are typically addressed by a SOW are as follows:
- Purpose: Why are we doing this project? This is the question that the purpose statement attempts to answer.
- Scope of Work: This describes roughly the work that must be done in detail and specifies the hardware and software involved and the exact nature of the work to be done.
- Location of Work: This describes where the work must be performed. This also specifies the location of hardware and software and where people will meet to perform the work.
- Period of Performance: This specifies the allowable time for projects, such as start and finish time, number of hours that can be billed per week or month, where work is to be performed and anything else that relates to scheduling.
- Deliverables Schedule: This part lists the specific deliverables, describing what is due and when.
- Applicable Standards: This describes any industry specific standards that need to be adhered to in fulfilling the contract.
- Acceptance Criteria: This specifies how the buyer or receiver of goods will determine if the product or service is acceptable, what objective criteria will be used to state the work is acceptable. See Acceptance testing
- Special Requirements: This specifies any special hardware or software, specialized workforce requirements, such as degrees or certifications for personnel, travel requirements, and anything else not covered in the contract specifics.
- Type of Contract/Payment Schedule: The project acceptance will depend on if the budget available will be enough to cover the work required. Therefore payments breakdown whether up front or phased will be negotiated very early at this stage.
- Miscellaneous: There are many items that do not form part of the main negotiations but are nonetheless very important to the project. They seem minor but being overlooked or forgotten could pose problems for the project.
United States government contracts 
For U.S. government service contracts, the use of SOWs remains strong, although Statements of Objectives (SOOs) and Performance Work Statements (PWSs) have become increasingly popular due to their emphasis on performance-based concepts such as desired service outcomes and performance standards. SOWs are typically used when the task is well-known and can be described in specific terms. They may be preferred when the government does not desire innovative approaches or considers any deviation in contractor processes a risk. Whereas SOOs establish high-level outcomes and objectives for performance and PWSs emphasize outcomes, desired results and objectives at a more detailed and measurable level, SOWs provide explicit statements of work direction for the contractor or offeror to follow. SOWs are typically replete with "contractor shall" statements and statements of mandatory compliance (e.g., "This task shall be performed in accordance with Agency xyz Directive, dated mm/dd/yyyy"). In practice, SOWs can also be found to contain references to desired performance outcomes, performance standards, and metrics, thus blurring their distinction between SOOs and PWSs. Aside from good practice, there is little government policy guidance that emphatically prescribes how and when to use SOWs versus SOOs or PWSs. Whereas the FAR defines PWS in Part 2 Definitions, and references SOOs and PWSs in Part 37.6 Performance Based Acquisition, SOWs are not addressed. Some industry and agency guides are provided below in External Links.
SOWs are usually contained in the government's solicitation (RFP or RFQ) and carried forward, as may be negotiated with the offeror, into the final contract. In federal solicitations and contracts, SOWs are inserted into Section C "Descriptions/ Specifications"(See Uniform Contract Format, FAR 14.2), but may also be inserted as an attachment in Section J). In task orders, the SOW may simply be included among the terms and conditions of the order itself. The SOW is often supplemented by technical reference documents and attachments. In developing the SOW, it is important to ensure that the statement of work is comprehensive and sufficiently detailed, but that the statements do not duplicate terms and conditions or other provisions elsewhere in the solicitation or contract.
Guidance in MIL-STD-881 and MIL-HDBK-245 says that a Work Breakdown Structure should be used in developing the SOW. This may use the WBS as an outline, where each WBS element (in the same name and numbering) are the sub-parts of the SOW section 3, making the development easier and to improving later billing and tracking. The WBS which focuses on intelligently dividing a heirarchy of the work elements and defining them may then have the SOW in matching sections focus on describing what will be done with that portion or how that portion will be done.
The Statement of Work should be directly linked to deliverables shown in the CDRL form. This is done by having each CDRL entry include reference to the SOW paragraph(s) that produces or uses the item, and the SOW text should be clear where it is discussing a deliverable by using the title or parenthesizing the item number (e.g. "[A-001]").
- MIL-STD-881 series para 2.4 links to WBS and IMP/IMS
- MIL-HDBK-245 series para 3.6.4, 3.8.1
- DI-MGMT-81606 Data Item Descriptions Defining content and structure of SOW when a contractor is to provide one.
- Statement of Work Writing Guide - A do-it-yourself guide to developing an RFP Statement of Work
- How to write the Statement of Work
- Handbook for Preparation of Statement of Work (SOW)