A Statement of Work specifies the tasks the contractor must perform, the deliverables required, the schedule they must hit, and frequently the methods or standards governing how the work is executed. The SOW is the traditional federal acquisition instrument, predating performance-based acquisition by decades, and remains the structure of choice for construction, system development, well-defined product deliveries, and acquisitions where the government has a strong opinion about how the work should be done. It typically appears as Section C of a Uniform Contract Format solicitation or as an attachment to the basic contract.
A typical SOW includes a background section, a scope statement defining the boundaries of work, a tasks-and-subtasks structure, deliverables with formats and due dates, a schedule with milestones, and applicable government standards by reference. Compliance with the SOW is contractually binding — the contractor must perform the specified tasks and produce the listed deliverables. Deviation requires a modification. SOW-based contracts often include detailed specifications on personnel qualifications, processes, deliverable formats, and review cycles that limit contractor discretion.
For contractors bidding SOW-based work, the proposal must directly address each task and deliverable, demonstrating the technical capability and resources to perform as specified. Pricing must capture the labor required to meet every named task, with no assumption of contractor-driven scope reduction. The SOW is the requirement; the proposal is the commitment to perform it. Misreading the SOW or proposing a streamlined approach not aligned to the specified tasks is the most common cause of post-award scope disputes.