The Performance Work Statement (PWS) is a Statement of Work (SOW) for Performance-Based Acquisitions that clearly describes the performance objectives and standards that are expected of the contractor. When a contract is awarded, the PWS is legally binding between the contractor and the U.S. Government.
Definition: “A Performance Work Statement (PWS) is a Statement of Work for performance based-acquisitions that describes the required results in clear, specific, and objective terms with measurable outcomes.”
Types of Statement of Works (SOW)
Two types of Statement of Works (SOW) are used throughout the Government and Industry. The first is your traditional SOW which is a document that enables the offeror to clearly understand the government’s needs for the work to be done in developing or producing the goods or services to be delivered by a contractor; the other is a Performance Work Statement (PWS).
- Statement of Work (SOW): For system procurement and Research and Development (R&D) (MIL-HDBK-245)
- Performance Work Statement (PWS): For the acquisition of professional services. (AFI 63-124)
Performance Work Statement (PWS) Regulations
The Federal Acquisition Regulation (FAR 37.602) only requires that agencies, to the maximum extent practicable:
- Describe work in terms of required results rather than “how” the work is to be accomplished or the number of hours to be provided
- Enable assessment of work performance against measurable performance standards
- Rely on measurable performance standards and financial incentives in a competitive environment to encourage innovation and cost-effective methods of performing the work
- Use the Work Statement Writing Guidelines Summary
PWS Main Guidance: Air Force Instruction (AFI) 63-124 Performance-Based Service Acquisitions
Performance Work Statement (PWS) Requirements
The PWS should state requirements in general terms of what (result) is to be done rather than how (method) it is done. The PWS gives the contractor maximum flexibility to devise the best method to accomplish the required result. The PWS must be written to ensure that all offerors compete equally. The U.S. Government must remove any features that could restrict a potential offeror.
However, the PWS must also be descriptive and specific enough to protect the U.S. Government’s interests and promote competition. The clarity and explicitness of the requirements in the PWS will invariably enhance the quality of the proposals submitted. A definitive PWS is likely to produce definitive proposals, thus reducing the time needed for proposal evaluation.
Preparing a Performance Work Statement (PWS)
It begins with an analytical process, often called a “job analysis.” It involves closely examining the agency’s requirements and tends to be a “bottom-up” assessment with “re-engineering” potential. This analysis is the basis for establishing performance requirements, developing performance standards, writing the performance work statement, and producing the quality assurance plan. Those responsible for the mission or program are essential to the job analysis performance. [1]
Six (6) Steps Performance Work Statement (PWS) Job Analysis
This analysis is the basis for establishing performance requirements, developing performance standards, writing the performance work statement, and producing the quality assurance plan.
- Step 1: Conduct Organizational Analysis
- Step 2: Conduct Work Analysis (use Work Breakdown Structure (WBS))
- Step 3: Gather Workload and Resource Data
- Step 4: Analyze Directives
- Step 5: Conduct Performance Analysis
- Step 6: (as required) Analyze Incentives
Performance Work Statement (PWS) Main References
Below is a guidebook that covers all the key aspects of utilizing and developing a PWS.
Handbook: Developing a Performance Work Statement Handbook
Guideline: Work Statement Writing Guidelines Summary
PWS Main Guidance: Air Force Instruction (AFI) 63-124 Performance-Based Service Acquisitions
A Good Performance Work Statement (PWS) has the following attributes: [1]
A solid performance work statement should be thorough and precise, with specified or free-from-ambiguity words, and written with the bidders in mind.
- Specifies requirements clearly to permit the government and offerors to estimate the probable cost and the offeror to determine the levels of expertise, manpower, and other resources needed to accomplish the task.
- States the specific duties of the contractor in such a way that the contractor knows what is required and can complete all tasks to the satisfaction of the contract administration office.
- Written so precisely, there is no question of whether the contractor must perform specific tasks.
- References only the absolute minimum applicable specifications and standards needed. Selectively invokes documents only to the extent required to satisfy the existing requirements.
- Separates general information from the direction to distinguish background information and suggested procedures from contractor responsibilities.
- Avoids directing how tasks are to be performed and states only what results are required.
Developing the Performance Work Statement (PWS)
To create the actual PWS it is best to use an established template from your organization or from a legal entity. Since you already have the task and the content defined, it should be an easy step to plug in your content. A template also makes sure you are addressing all legal questions and you didn’t is any content.
Template: Performance Work Statement
Template: Generic Performance Work Statement Template
Performance Work Statement (PWS) Notional Format:
- Introduction
- General Information
- Background information
- Government/Contractor Furnished Property/Information
- Performance Objectives and Standards
- Applicable documents
- Special Requirements/Constraints (such as security)
- Deliverables
Difference Between a Statement of Work (SOW) and a Performance Work Statement (PWS)
Knowing the differences between a Performance Work Statement (PWS) and a Statement of Work (SOW) is essential in the complex world of government procurement. The expectations and results of contractual agreements between the government and contractors are significantly shaped by these two papers. To shed light on their distinctive qualities, let’s examine the main distinctions and importance of each.
Blog: Solving the Difference Between the SOW and PWS
Performance Work Statement (PWS) vs. Statement of Objective (SOO)
The SOO is a Government prepared document that provides the basic, high-level objectives of the acquisition. It is provided in the solicitation in lieu of a government-written Performance Work Statement. In this approach, the contractors’ proposals contain their statements of work and performance metrics and measures (which are based on their proposed solutions). The use of an SOO opens the acquisition up to a wider range of potential solutions.
AcqNotes Tutorial
AcqLinks and References:
- [1] MIL-HDBK-245D “DoD Handbook for Preparation of Statement of Work” – 3 April 1996
- Air Force Instruction (AFI) 63-124 Performance-Based Service Acquisitions
- Performance Work Statement Template
- Developing a Performance Work Statement Handbook – Sept 2009
- Work Statement Writing Guidelines Summary
- A CORs Guide to Statement of Work and PWS
- Example: Performance Work Statement (PWS) for KC-X Program Office
- Presentation: How To Write a PWS Training
Updated: 2/1/2024
Rank: G3.2