What is a Performance Work Statement (PWS)?

A Performance Work Statement (PWS) is a government document that describes the required results of a contract in measurable, outcome-based terms. Unlike a Statement of Work (SOW), which prescribes specific tasks and processes, a PWS tells contractors what to achieve rather than how to achieve it. FAR 37.102 directs agencies to use performance-based acquisition methods to the maximum extent practicable for service contracts, making the PWS the standard work description format for most federal service procurements.

What Is the Difference Between a PWS, SOW, and SOO?

The government uses three primary work description documents, each with a different philosophy:

• Performance Work Statement (PWS): Defines desired outcomes, performance standards, and acceptance criteria. The contractor chooses the approach. The government measures results, not methods. This is the preferred format under FAR 37.102.
• Statement of Work (SOW): Prescribes specific tasks, processes, staffing levels, and methods. The government dictates how work is performed. Common in R&D, construction, and manufacturing contracts where precise methods matter.
• Statement of Objectives (SOO): The broadest format. Describes only the high-level objectives and desired end state. Contractors propose both the approach and the detailed work description. Often used in best-value competitions where the government wants maximum innovation.

According to the Office of Federal Procurement Policy, agencies should use performance-based approaches for service contracts whenever the required outcomes can be objectively measured. The DoD has set a target of using performance-based acquisition for at least 50% of eligible service contract dollars (source: DoD PBA Guidebook). In practice, most IT services, facilities management, and professional support contracts now use a PWS rather than a traditional SOW.

What Are the Standard Sections of a PWS?

While there is no single mandated format, most government PWS documents follow a consistent structure containing 8 to 12 sections. The typical structure includes:

• 1. Scope: High-level description of the work, mission context, and contract objectives
• 2. Applicable Documents: References to regulations, standards, and government publications that apply
• 3. Performance Requirements: Detailed description of each functional area, organized by task or service area
• 4. Performance Standards: Measurable criteria for acceptable performance, including Acceptable Quality Levels (AQLs)
• 5. Deliverables: Reports, plans, and work products the contractor must produce, with format and due dates
• 6. Government-Furnished Property/Information: What the government will provide (facilities, equipment, data, access)
• 7. Personnel Requirements: Minimum qualifications, clearance requirements, and key personnel designations
• 8. Place of Performance: Work location(s), including on-site, off-site, and travel requirements
• 9. Period of Performance: Base period and option periods
• 10. Security Requirements: Clearance levels, CUI handling, CMMC requirements, facility clearances

RFI Hawk's Pre-Sol Document Generator can produce draft PWS documents based on program requirements, following this standard structure and incorporating appropriate FAR/DFARS references for your contract type.

What Is a QASP and How Does It Relate to the PWS?

The Quality Assurance Surveillance Plan (QASP) is the government's companion document to the PWS. While the PWS defines what the contractor must achieve, the QASP defines how the government will verify that the contractor is meeting those requirements. Every performance-based contract should have both a PWS and a QASP.

The QASP typically includes:

• Surveillance methods (periodic inspection, random sampling, customer feedback, automated monitoring)
• Performance metrics tied to each PWS requirement
• Acceptable Quality Levels (AQLs) for each metric
• Remedies for non-performance (corrective action requests, fee reductions, cure notices)
• Frequency of performance assessments

As a contractor, understanding the QASP is just as important as understanding the PWS. The QASP tells you exactly how your performance will be measured and what triggers penalties. When you write your proposal, address each QASP metric explicitly and describe how your quality control process ensures you will consistently meet or exceed the stated standards.

How Should Contractors Read and Respond to a PWS?

Reading a PWS requires a different approach than reading a traditional SOW. Because the PWS focuses on outcomes rather than tasks, you need to reverse-engineer the required work from the stated performance objectives. Here is a structured approach:

• Step 1: Map the requirements. Create a matrix of every performance requirement, the associated standard, and the measurement method. This becomes the foundation of your compliance matrix.
• Step 2: Identify the real workload. Performance requirements imply tasks. A requirement to "maintain 99.9% system uptime" implies 24/7 monitoring, incident response, maintenance windows, and redundancy. Estimate the staffing and resources needed to meet each standard.
• Step 3: Differentiate your approach. Since the PWS does not prescribe methods, this is your opportunity to propose innovative solutions. Automation, proprietary tools, and efficient processes that meet the performance standards at lower cost give you a competitive advantage.
• Step 4: Address risk. Identify which performance standards carry the highest consequences for non-compliance and build mitigation strategies into your proposal.

According to a GAO analysis of service contract protests, approximately 35% of sustained protests involve issues with unclear or ambiguous work descriptions (source: GAO bid protest annual reports). If the PWS contains ambiguities, use the solicitation's Q&A period to seek clarification before submitting your proposal.

What Performance Metrics Are Commonly Used?

Performance metrics in a PWS vary by contract type but generally fall into several categories. Understanding these helps you price your proposal accurately and staff appropriately:

• Timeliness: Response times, delivery deadlines, on-time completion rates (e.g., "resolve critical incidents within 4 hours")
• Quality: Error rates, defect rates, accuracy percentages (e.g., "maintain 98% accuracy in data processing")
• Availability: System uptime, staffing coverage, service hours (e.g., "99.9% uptime during core business hours")
• Customer Satisfaction: Survey scores, complaint rates, feedback mechanisms (e.g., "achieve 4.0/5.0 average satisfaction score")
• Compliance: Adherence to regulations, reporting accuracy, audit findings (e.g., "zero critical audit findings per year")

The best proposals do not just promise to meet these metrics. They describe the internal quality control processes, monitoring tools, and management oversight that will ensure consistent performance throughout the contract period.

Related Resources

Frequently Asked Questions