PWS

The PWS contrasts with the traditional Statement of Work (SOW), which specifies inputs and methods (how the work must be done). A PWS specifies outputs and outcomes (what the work must achieve). This distinction gives contractors flexibility to propose innovative approaches and efficient methods, while holding them accountable to measurable performance standards.

PWS vs. SOW:

• SOW: "The contractor shall provide three technicians on-site eight hours per day, five days per week."
• PWS: "The contractor shall maintain 99.5% system uptime during core business hours, measured monthly."

The PWS approach is mandated for most DoD service acquisitions under DoD Instruction 5000.74. It is paired with a Quality Assurance Surveillance Plan (QASP) — a government document that defines how the COR will measure and verify contractor performance against PWS standards.

PWS structure typically includes:

• Scope and background
• Specific tasks and deliverables
• Performance standards and acceptable quality levels (AQLs)
• Government-furnished equipment, information, and facilities
• Applicable regulations and standards

Tips for responding to a PWS:

• Propose your specific methodology — the government wants to see how you will achieve the performance standards
• Address each performance standard explicitly and show how your approach meets or exceeds it
• Propose your own quality control plan that mirrors and complements the QASP
• Highlight past performance that demonstrates meeting similar performance standards