Beginner Track • Topic 6

Statements of Work

The Statement of Work defines the work. It's the single most important document in your contract file because everything (pricing, evaluation, administration, disputes) traces back to what's written here. Learn to read one, spot problems, and know when you're actually looking at a PWS.

The Basics

What Is a Statement of Work?

Before you solicit anything, somebody has to describe the work. That description shapes everything that follows.

1 SOW, PWS, SOO: What's the Difference?

You'll see these three terms constantly. They're not interchangeable, even though people use them that way.

Statement of Work (SOW). The government tells the contractor how to do the work. Step-by-step, method-by-method. "Perform preventive maintenance on all 12 HVAC units monthly using the manufacturer's recommended procedure." The government is directing the process.
Performance Work Statement (PWS). The government tells the contractor what outcome it needs. "Maintain 95% operational availability on all 12 HVAC units." The contractor decides how to get there. We'll cover PWSs in a later training.
Statement of Objectives (SOO). The government describes the problem and asks the contractor to propose a solution. "We need reliable climate control across 6 buildings." The contractor proposes the scope, the method, and the metrics. Also a later training.
In practice? Most of what you'll see in operational contracting is closer to a PWS than a SOW. We're usually buying an outcome. If we knew exactly how to do the work ourselves, we'd do it ourselves. True SOWs are more common in construction, manufacturing to specification, or highly regulated maintenance where the government has a specific process it needs followed.

2 Who Owns the Risk?

This is the practical reason the SOW-vs-PWS distinction matters. It's not just semantics; it shifts risk.

SOW → Government Owns More Risk
You told the contractor how to do it. If the method doesn't produce the result you wanted, that's on you. They followed your instructions.
PWS → Contractor Owns More Risk
You told the contractor what to deliver. If they pick a bad method and miss the target, that's on them. You defined the outcome, not the process.

This is why PWSs are generally preferred for services. You get better results when the contractor (the subject matter expert) has the freedom to choose how to accomplish the mission. And the risk sits where the expertise sits.

3 Anatomy of a SOW

Regardless of whether it's a SOW or PWS, most work statements follow a similar structure. Here are the sections you'll see:

1. Scope. A one-to-two paragraph overview of what the contract covers. It should tell anyone reading it what the buy is about in 30 seconds.
2. Applicable Documents. Standards, regulations, technical manuals, or instructions that the contractor must follow. This is where you'll see references to MIL-STDs, AFIs, manufacturer specs, and the like.
3. Requirements / Tasks. The meat of the document. In a SOW, this is step-by-step direction. In a PWS, this is outcome-based standards. Either way, this section defines what the contractor is responsible for.
4. Deliverables. What tangible items or reports the contractor must hand over. Monthly status reports, inspection records, completed work orders, etc. If you can't name a deliverable, you can't verify the work.
5. Period & Place of Performance. When and where the work happens. This matters for pricing, for labor law compliance, and for knowing which wage determination applies.
6. Government-Furnished Property / Information (GFP/GFI). Anything the government is providing: equipment, facilities, data, access. If it's not listed here and the contractor needs it, expect a claim later.

Check the SOW Examples tab to see how these sections look in a real document and what goes wrong when they're done poorly.

4 Common Problems

After reviewing hundreds of SOWs and PWSs in operational contracting, the same mistakes come up over and over:

Contract clauses hiding in the SOW. This is one of the most common issues. Customers write termination provisions, payment terms, or inspection criteria directly into the SOW. The problem? You already have clauses for that. See FAR 52.249 (Termination series) and FAR 52.212-4 (Commercial Terms and Conditions). When the SOW says one thing and the contract clause says another, you've created an ambiguity that the contractor will exploit. Catch it before you solicit.
Vague, unmeasurable requirements. "Provide maintenance support" means nothing. You can't enforce it, you can't inspect against it, and you can't withhold payment when the contractor underperforms. Every requirement needs to be specific enough that both parties know when it's been satisfied.
Personal services language. If the SOW dictates where the contractor works, when they show up, who they report to, and how they do every task, it starts looking like you're hiring an employee, not a contractor. That's a personal services contract, and it's generally prohibited. Watch for language that puts the contractor under direct government supervision in day-to-day operations.
SOW vs. PWS mismatch. The document says "Performance Work Statement" at the top, but every paragraph dictates a specific method. Or vice versa. The label matters because it signals to offerors what kind of proposal to write and to evaluators how to assess it. If the content doesn't match the label, fix it.

5 When Do You Actually Need a SOW?

Despite everything above, there are times when a true SOW is exactly what you need. The government isn't always buying expertise. Sometimes it knows exactly what it wants done and exactly how.

Construction. The government has blueprints, specs, and engineering drawings. The contractor builds to those specs. This is classic SOW territory.
Manufacturing to specification. When the government has a technical data package (TDP) and needs parts built to exact dimensions and tolerances, the SOW directs the process.
Highly regulated maintenance. Aircraft maintenance, nuclear systems, or anything with a technical order that must be followed exactly. The government isn't asking for the contractor's opinion on how to do it; it's directing compliance with a specific procedure.

For most service contracts in operational contracting? You're probably writing a PWS. If you're telling the contractor what tools to use, what hours to work, and exactly how to accomplish each task, ask yourself: do we actually need that level of control, or are we just making more work for ourselves?

Interactive Tool

SOW Examples

Click the highlighted sections to see coaching notes. Blue borders highlight what makes this a SOW (vs. a PWS). Red borders flag problems.

Statement of Work
HVAC Preventive Maintenance, Building 1240, Wright-Patterson AFB

1.0 Scope

The contractor shall perform preventive maintenance on twelve (12) commercial HVAC units in Building 1240, Wright-Patterson Air Force Base, Ohio, in accordance with the manufacturer's maintenance procedures identified in Section 2.0. This contract covers scheduled quarterly inspections and filter replacements for a base period of 12 months with two (2) 12-month option periods.

2.0 Applicable Documents

2.1 Carrier Corporation, WeatherMaker 48TC Series Maintenance Manual, Rev. 4, 2023.
2.2 ASHRAE Standard 180-2018, Standard Practice for Inspection and Maintenance of Commercial Building HVAC Systems.
2.3 AFI 32-1001, Operations Management.

3.0 Requirements

3.1 Quarterly Preventive Maintenance. The contractor shall perform the following on each of the 12 units once per quarter:

a) Inspect and replace air filters (MERV-13 minimum).
b) Inspect evaporator and condenser coils; clean per manufacturer procedure TC-PM-04.
c) Check refrigerant levels and recharge as needed to manufacturer specifications.
d) Inspect electrical connections, contactors, and capacitors.
e) Verify thermostat calibration within ±2°F of setpoint.
f) Lubricate all moving parts per manufacturer-specified intervals.
g) Inspect condensate drain lines and clear blockages.

3.2 Documentation. The contractor shall complete a maintenance checklist (Government-furnished, Attachment 1) for each unit serviced and submit completed checklists to the Contracting Officer's Representative (COR) within 5 business days of each quarterly visit.

4.0 Deliverables

4.1 Completed maintenance checklists per Section 3.2. Within 5 business days after each quarterly visit.
4.2 Quarterly summary report identifying any units requiring corrective maintenance beyond the scope of this SOW. Within 10 business days after each quarterly visit.

5.0 Period and Place of Performance

Base period: 1 April 2026 – 31 March 2027. Option Period 1: 1 April 2027 – 31 March 2028. Option Period 2: 1 April 2028 – 31 March 2029. All work shall be performed at Building 1240, Wright-Patterson AFB, OH 45433. Contractor shall coordinate quarterly visit scheduling with the COR at least 14 calendar days in advance.

6.0 Government-Furnished Property and Information

6.1 Access to Building 1240 during normal duty hours (0700-1700, Mon-Fri).
6.2 Maintenance checklist template (Attachment 1).
6.3 Current HVAC unit inventory and location map (Attachment 2).
6.4 Electrical power at the work site.

TRAINING EXAMPLE | NOT AN OFFICIAL GOVERNMENT DOCUMENT
References

Look It Up

Key references for writing and reviewing statements of work.

FAR Part 37: Service Contracting

The FAR subpart that governs service contracts. Covers performance-based acquisition requirements, personal services prohibitions, and the distinction between SOWs and PWSs.

Open FAR Part 37

FAR 37.6: Performance-Based Acquisition

The specific subpart on performance-based contracting. Explains when and why to use a PWS over a SOW, and the requirements for measurable performance standards.

Open FAR 37.6

FAR 37.104: Personal Services Contracts

The rule on personal services. Defines what makes a contract "personal services" and why it's generally prohibited. Critical reading if your SOW starts dictating contractor schedules and supervision.

Open FAR 37.104

OFPP Policy Letter 93-1

Office of Federal Procurement Policy guidance on performance-based service contracting. The foundational policy document behind the government's preference for PWSs over SOWs.

Open Policy Letter

FAR 52.249: Termination Clauses

The termination clause series. If you find termination language in a SOW, this is where it actually belongs. Know these clauses so you can catch duplicates and conflicts.

Open FAR 52.249

Market Research Training

The SOW drives your market research, and vice versa. Our training covers the full process from requirement to documentation.

Open Training