Performance Work Statement (PWS)

A Performance Work Statement (PWS) is the contract requirements document used in performance-based acquisitions, specifying measurable outcomes the contractor must achieve and the performance standards against which results will be evaluated, rather than prescribing specific tasks or methods.

What is a Performance Work Statement?

A PWS is the foundational document of a performance-based acquisition (PBA) under FAR 37.601. Instead of telling a contractor how to do the work (as a SOW does), a PWS tells the contractor what results must be delivered and at what quality level. This outcome-focused approach allows contractors to apply their best methods and encourages innovation.

A well-written PWS contains:

• Performance objectives: what the contractor must achieve, stated in measurable terms
• Performance standards: the specific criteria defining acceptable performance (e.g., 99.5% uptime, 4-hour response time, zero critical defects at delivery)
• Acceptable quality levels (AQLs): the minimum threshold of acceptable performance for each standard
• Surveillance methods: how the government will monitor and measure contractor performance
• Incentives and deductions: what happens when performance exceeds or falls below standards

The PWS is paired with a Quality Assurance Surveillance Plan (QASP), which documents exactly how the government's Contracting Officer's Representative (COR) will measure the contractor against the PWS standards. The QASP defines what data will be collected, how frequently, and what thresholds trigger corrective action requests.

Performance standards in a PWS must be objective and measurable, vague requirements like "professional quality" or "timely delivery" are insufficient. Strong PWS standards look like: "95% of help desk tickets resolved within 4 business hours, measured monthly via the agency's ITSM system."

Why the PWS matters for government contractors

The PWS is both your guide to success and your legal standard of performance. Understanding the PWS deeply, knowing exactly what performance standards you will be held to, is essential for pricing, staffing, and managing the contract. Contractors who propose innovative approaches in a SOO-based procurement must develop a strong draft PWS that reflects both ambition and realism: standards that are high enough to score well in evaluation but achievable in practice. Low performance against PWS standards directly affects CPARS ratings, which affect future contract wins. Many contractors build internal dashboards tracking their real-time performance against PWS standards throughout contract performance.

Example

A logistics contract PWS includes: "Delivery Order Fulfillment Rate: The contractor shall fulfill 98% of all delivery orders within the specified delivery window, measured monthly." The QASP specifies that the government's supply chain manager will extract fulfillment data from the contractor's logistics system on the first business day of each month. In months where fulfillment drops below 98%, the contractor receives a formal deficiency notice and must submit a corrective action plan within 5 business days. Three months of fulfillment below 95% triggers a contract performance review and potential cure notice. The contractor builds internal alerts that fire when the running fulfillment rate approaches 98.5%, giving them lead time to prevent a deficiency notice.

Frequently Asked Questions

Who writes the PWS, the government or the contractor?

In traditional performance-based acquisitions, the government writes the PWS as part of the solicitation. In SOO-based acquisitions, offerors write their own draft PWS as part of the proposal. The government's review and acceptance of the draft PWS is part of the source selection process, and the final PWS is negotiated and incorporated into the awarded contract.

What is the difference between a performance standard and an acceptable quality level?

A performance standard defines what should be achieved (e.g., 98% on-time delivery). The acceptable quality level (AQL) is the minimum acceptable threshold, slightly below the standard, before formal action is triggered. For example, a performance standard of 98% delivery might have an AQL of 95% before a deficiency notice is issued.

Can the government change performance standards mid-contract?

Yes, through a bilateral modification signed by both parties. Unilaterally changing what the contractor is measured against would generally be a constructive change entitling the contractor to an equitable adjustment. Performance standard changes require mutual agreement.

Is a PWS required for all services contracts?

No. FAR 37.601 strongly encourages performance-based acquisition for services, but it is not always required. Contracts where the government needs to control methods (e.g., for safety, security, or integration reasons) may still use a traditional SOW. However, OMB has pushed agencies toward PWS-based contracts for most service procurements.