Beginner Track • Topic 7

Performance Work Statements

A PWS tells the contractor what you need, not how to do it. It's the most common work statement in operational contracting because it puts risk where the expertise is: on the contractor. Learn to read one, write measurable standards, and spot a SOW disguised as a PWS.

The Basics

What Is a Performance Work Statement?

You define the outcome. The contractor figures out how to get there. That's the core idea behind a PWS, and it's the government's preferred approach for service contracts.

1 Quick Refresher: PWS vs. SOW

If you completed the Statements of Work training, you already know the basics. Here's the short version:

SOW: "Do it this way."
Government directs the method.
Government owns the risk.
PWS: "Get me this result."
Government defines the outcome.
Contractor owns the risk.

Most service contracts in operational contracting should be PWSs. If you're buying janitorial services, IT support, equipment maintenance, or consulting, you're almost certainly buying an outcome. You don't need to tell the janitor which mop to use. You need the floor clean.

2 The Key Ingredient: Measurable Standards

A PWS lives or dies on whether its performance standards are measurable. If you can't measure it, you can't enforce it. And if you can't enforce it, you don't have a contract. You have a suggestion.

Good: "Maintain 95% operational availability across all 12 HVAC units, measured monthly." You know exactly what success looks like, you know when to measure, and you can withhold payment or take action if the contractor misses the mark.
Bad: "Ensure HVAC systems are maintained to a high standard." What's "high"? Who decides? This is unenforceable. When the contractor's performance slips and you try to issue a cure notice, they'll argue they met the standard because nobody defined it.

Every performance requirement in the PWS should answer three questions: What is the standard? How do you measure it? What happens if the contractor doesn't meet it?

The "newspaper test." Could a reasonable third party read the requirement and know, without asking anyone, whether the contractor passed or failed? If the answer is no, the standard needs work.

3 Anatomy of a PWS

A PWS follows a similar structure to a SOW, but the requirements section looks fundamentally different. Instead of step-by-step instructions, you'll see outcomes and standards.

1. Scope. Same as a SOW. Brief overview of the contract's purpose and boundaries.
2. Applicable Documents. Standards, regulations, and references the contractor must follow. In a PWS, these tend to be performance standards rather than procedural manuals.
3. Performance Requirements. This is where a PWS diverges from a SOW. Instead of telling the contractor how to do each task, you state the outcome you need and the standard it must meet. "Maintain 95% availability" instead of "Inspect coils quarterly using procedure TC-PM-04."
4. Performance Standards Summary. Often presented as a table that maps each requirement to a measurable standard and an acceptable quality level (AQL). This is the backbone of contract administration. It tells the COR exactly what to inspect and what "passing" looks like.
5. Deliverables. Reports, data, completed work orders. Same concept as a SOW, but in a PWS context the deliverables often tie back to proving the performance standards were met.
6. Period & Place of Performance. When and where. Same as a SOW.
7. Government-Furnished Property / Information. What the government provides. Same concept. Just as important here.

Check the PWS Examples tab to see how this looks on paper, and how it falls apart when done wrong.

4 Common Problems

The same issues from SOWs show up in PWSs, plus a few unique ones:

The "SOW in disguise." The document says "Performance Work Statement" at the top, but every paragraph tells the contractor exactly how to do the work. If you're dictating the method, it's a SOW regardless of what you call it. The label matters because it signals how offerors should propose and how the government will evaluate.
Unmeasurable performance standards. "Maintain equipment to industry standards" sounds professional, but it's useless. Which industry? Which standards? A COR can't inspect against "industry standards." Every standard needs a number, a percentage, a frequency, or some objective benchmark.
Contract clauses in the PWS. Same issue as with SOWs. Termination language, payment terms, and dispute procedures belong in the contract clauses (52.249 series, 52.212-4), not in the work statement. When they show up in both places and say different things, you have a conflict that the contractor will use against you.
No connection between requirements and standards. The PWS lists requirements in Section 3 and performance standards in Section 4, but they don't map to each other. Requirement 3.1 says "maintain HVAC systems" and the performance table measures "customer satisfaction." Those aren't the same thing. Every requirement needs a standard, and every standard needs to trace back to a requirement.

5 Why the Government Prefers PWSs

FAR 37.6 establishes performance-based acquisition as the preferred method for services. That's not just policy preference. There are practical reasons:

Better outcomes. The contractor is the subject matter expert. When you define the "what" and let them handle the "how," they'll typically find more efficient methods than the government would prescribe. They do this work for a living. You don't.
Less risk for the government. When you direct the method (SOW), you own the result. If the method fails, the contractor followed your instructions. When you define the outcome (PWS), the contractor owns the result. If they pick a bad approach, that's on them.
Innovation. A PWS lets contractors compete on method, not just price. One offeror might propose a traditional approach, another might propose an innovative solution that saves time and money. You won't get that innovation if you've already dictated the method.
The practical bottom line: If you find yourself writing step-by-step instructions for a service contractor, ask yourself whether you're solving a real problem or just creating extra work. Most of the time, the answer is to define the outcome, set a measurable standard, and let the contractor do what you're paying them to do.
Interactive Tool

PWS Examples

Same HVAC scenario as the SOW training, written as a PWS. Click highlighted sections for coaching notes. Blue borders highlight what makes this a PWS. Red borders flag problems.

Performance Work Statement
HVAC Maintenance Services, Building 1240, Wright-Patterson AFB

1.0 Scope

The contractor shall provide all personnel, equipment, materials, and supervision necessary to maintain twelve (12) commercial HVAC units in Building 1240, Wright-Patterson Air Force Base, Ohio. The objective is to ensure reliable heating, ventilation, and air conditioning for approximately 200 building occupants across four floors.

2.0 Applicable Documents

2.1 ASHRAE Standard 55-2023, Thermal Environmental Conditions for Human Occupancy.
2.2 ASHRAE Standard 62.1-2022, Ventilation and Acceptable Indoor Air Quality.
2.3 EPA Clean Air Act, Section 608 (refrigerant handling).
2.4 AFI 32-1001, Operations Management.

3.0 Performance Requirements

3.1 Operational Availability. The contractor shall maintain a minimum 95% operational availability across all 12 HVAC units, measured monthly. A unit is considered "available" when it is capable of maintaining its designated zone within ±3°F of the thermostat setpoint.

3.2 Emergency Response. The contractor shall restore failed HVAC units to operational status within 4 hours of notification during duty hours (0700-1700, Mon-Fri) and within 8 hours during non-duty hours. Notification will be made via the Base Civil Engineer service desk.

3.3 Indoor Air Quality. The contractor shall maintain indoor air quality in compliance with ASHRAE 62.1-2022 at all times. CO2 levels shall not exceed 1,000 ppm in occupied spaces during normal business hours.

3.4 Preventive Maintenance. The contractor shall establish and execute a preventive maintenance program sufficient to meet the availability and air quality requirements above. The specific methods, schedule, and procedures are at the contractor's discretion.

4.0 Performance Standards Summary
Requirement Performance Standard AQL Method
3.1 Operational Availability ≥ 95% monthly availability per unit No more than 1 unit below 95% in any month Monthly report review + random COR spot checks
3.2 Emergency Response Restore within 4 hrs (duty) / 8 hrs (non-duty) No more than 2 late responses per quarter Service desk ticket timestamps
3.3 Indoor Air Quality CO2 ≤ 1,000 ppm during business hours No more than 3 exceedances per quarter Quarterly IAQ spot checks by COR
5.0 Deliverables

5.1 Monthly performance report showing availability percentage per unit, service calls received and resolved, and any corrective actions taken. Due within 10 business days after each month.
5.2 Quarterly preventive maintenance summary documenting the contractor's PM program execution. Due within 15 business days after each quarter.

6.0 Period and Place of Performance

Base period: 1 April 2026 through 31 March 2027. Option Period 1: 1 April 2027 through 31 March 2028. Option Period 2: 1 April 2028 through 31 March 2029. All work performed at Building 1240, Wright-Patterson AFB, OH 45433.

7.0 Government-Furnished Property and Information

7.1 Access to Building 1240 (24/7 for emergency response; normal duty hours for routine work).
7.2 Current HVAC unit inventory, model numbers, and location map (Attachment 1).
7.3 Access to the Base Civil Engineer service desk for service call logging.

TRAINING EXAMPLE | NOT AN OFFICIAL GOVERNMENT DOCUMENT
References

Look It Up

Key references for writing and reviewing performance work statements.

FAR 37.6: Performance-Based Acquisition

The FAR subpart that establishes performance-based contracting as the preferred method for services. Defines what a PWS is and when to use one.

Open FAR 37.6

FAR Part 37: Service Contracting

The broader service contracting subpart. Covers personal services prohibitions, advisory services, and the general framework for buying services.

Open FAR Part 37

OFPP Seven Steps to Performance-Based Acquisition

The Office of Federal Procurement Policy's guide to implementing performance-based service contracts. Practical, step-by-step, and still widely referenced despite its age.

Open Seven Steps Guide (GSA)

FAR 46.4: Government Contract Quality Assurance

How the government inspects and accepts contractor performance. The foundation for how a COR uses the performance standards in your PWS to actually hold the contractor accountable.

Open FAR 46.4

Statements of Work Training

Our SOW training uses the same HVAC scenario. Compare side by side to see how the same requirement looks when the government directs the method vs. defines the outcome.

Open SOW Training

Market Research Training

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

Open Training