A PWS tells you what the government wants achieved — not how to do it. That shift from activities to outcomes is the whole game. Most contractors read a PWS and write a proposal about what they will do. Winning contractors read the same document and write about what will get done. Here's the difference in practice.
The Federal Acquisition Regulation defines a Performance Work Statement at FAR 2.101 as "a statement of work for performance-based acquisitions that describes the required results in clear, specific and objective terms with measurable outcomes." Read that again slowly. Required results. Measurable outcomes. Not methods. Not procedures. Not hours logged.
The federal government moved toward performance-based service acquisition (PBSA) for a simple reason: prescriptive contracts were generating bad results at high cost. When an agency told a facilities contractor exactly how many times per week to clean a building, they got compliance with the cleaning schedule — not necessarily a clean building. When they shifted to a PWS that required the building to meet cleanliness standards measured through periodic inspections, contractors had to actually deliver the outcome. A 1998 OFPP study found performance-based contracts produced roughly 15% cost savings and nearly 20% higher customer satisfaction compared to traditional requirements-based approaches.
FAR Subpart 37.6 and FAR 37.602 lay out the operational framework. The Office of Federal Procurement Policy has pushed performance-based methods for service contracts since OFPP Policy Letter 91-2 in 1991. Today, performance-based acquisition is the preferred method for service contracts — not just encouraged but the required default that agencies must justify deviating from. A 2026 White House Executive Order directed agencies to accelerate the shift toward outcome-based contracting, citing continued evidence of savings and improved operational performance.
For you as a contractor, this shift matters. A PWS gives you latitude the old SOW never did. You decide howto achieve the performance standards. That's an opportunity to bring efficiency, innovation, and your specific strengths to the work — if you know how to read the document and respond to it properly.
PWS in Plain Terms
A Performance Work Statement describes what the government needs accomplished and how success will be measured. Your proposal must demonstrate that you understand those outcomes, that you have a credible plan to achieve them, and that you can sustain that performance under surveillance. The how is your competitive advantage — own it.
RFPs come with one of three work description formats, and which one you're reading changes your entire proposal approach. Confusing them is a common and costly mistake.
Statement of Work (SOW)— the traditional format. Prescriptive. The government tells you exactly how to do the job: specific tasks, procedures, staffing levels, frequencies, tools. Your proposal responds to each task. You don't get to innovate — you get to prove you can follow directions. SOWs still appear on research and development contracts, highly regulated requirements, and situations where the government wants procedural control.
Performance Work Statement (PWS) — outcome-based. The government defines what must be achieved and the standards against which it will be measured. You decide the approach. Your proposal wins by demonstrating a credible, efficient method to hit those standards. Most service contracts today use PWS format.
Statement of Objectives (SOO) — the highest-level format. The government defines broad objectives without specifying performance standards. You draft the PWS as part of your proposal. This approach is used when the agency wants contractor innovation to define not just the solution but the measurement framework. Responding to an SOO is the most complex and the biggest competitive opportunity — your proposed performance standards can differentiate you significantly.
| Dimension | SOW | PWS | SOO |
|---|---|---|---|
| Government specifies | How to do the work | What outcomes to achieve | High-level objectives only |
| Contractor specifies | Nothing — follow the script | The approach to achieving outcomes | The PWS and the approach |
| Performance standards | Compliance with procedures | Measurable outcome thresholds | Contractor proposes the standards |
| Innovation opportunity | Very low | Moderate | High |
| Proposal complexity | Moderate | Moderate–High | High |
| Common use cases | R&D, regulated processes | Most service contracts | Complex, innovation-driven work |
| QASP written by | Government | Government | Contractor (proposed) |
When an RFP contains an SOO, read it alongside the instructions in Section L carefully. You'll typically be required to include a contractor-proposed PWS as a separate attachment to your technical proposal. That document becomes part of your contract if you win — every standard you propose, you'll be held to.
FAR 37.601 defines five characteristics a contract must have to qualify as performance-based. It must: describe requirements as results rather than methods; include measurable performance standards; include a QASP; include procedures for price reductions when performance falls short; and include performance incentives where appropriate. Every element of the PWS exists to satisfy one or more of these five criteria.
Not every PWS is formatted identically, but every well-written one contains the same substantive elements. Learning to find these regardless of document structure is how you read quickly and respond accurately.
The AQL Is Your Real Target, Not the Performance Standard
Contractors often write proposals promising to hit the performance standard exactly. That's backwards. The performance standard is the ideal. The AQL is the floor. Your Quality Control Plan should be designed to stay consistently above the AQL even when conditions aren't perfect — not to hit the standard on a good day. Evaluators who understand PBSA know the difference and will score your QCP accordingly.
CapturePilot's intelligence features surface prior contracts for the same requirement — including historical PWS language, performance standards, and surveillance methods. You can read the old PWS while the new one is still being drafted.
The Quality Assurance Surveillance Plan is the government's monitoring playbook. FAR 37.604 requires agencies to develop a QASP for performance-based acquisitions. It specifies exactly how they'll verify whether you're hitting the performance standards in the PWS. You need to understand it as well as your own quality control plan.
FAR 46.401 requires QASPs to be prepared in conjunction with the statement of work. FAR 37.601 lists a QASP as one of the five defining characteristics every performance-based contract must have. The QASP typically lives as an attachment to the PWS or is incorporated by reference in the solicitation. Sometimes it's provided in the RFP; sometimes it's developed post-award. When it's attached to the solicitation, read it before you write a single word of your proposal — it tells you exactly what the government is going to measure and how.
The QASP will specify:
The Contracting Officer Representative (COR) is typically the person who executes the QASP day-to-day. They're your primary working-level government contact on a PBSA contract. A healthy relationship with the COR is operationally important — they're the ones who document whether you're performing.
Most contractors read a PWS like a task list. They go section by section, match their capabilities to the requirements, and start writing. That produces an adequate proposal. It rarely produces a winning one.
Read the PWS differently. Start with the performance standards and work backwards. Every standard is a question: what could go wrong that would cause us to miss this? What's our approach to making sure we hit this consistently? Which of our past performance examples demonstrates we can do this?
Then read the QASP against the standards. The surveillance method tells you what the government is most worried about measuring. If they're doing 100% inspection on a particular deliverable, that's the one where quality failures have historically hurt them. Address it specifically in your technical approach.
Your compliance matrix for a PWS-based proposal is built around performance standards rather than task requirements. Every row maps a standard to your proposed approach, your measurement method, your fallback when performance dips, and your reference past performance example. That structure gives evaluators exactly what they need to rate your technical volume.
The Q&A period is underused. Most small businesses skip it or ask surface-level questions. Ask about ambiguous performance standards — specifically, ask how the government interprets the standard and what measurement methodology they plan to use in the QASP. The answers shape your entire approach and you get them before your competitors do.
Every PWS-based contract requires you to submit a Quality Control Plan (QCP) with your proposal — or as a post-award deliverable within a defined number of days after award. When it's a proposal requirement, it's evaluated and scored. A weak QCP is a significant technical vulnerability.
The QCP and the QASP are mirror documents. The QASP describes how the government will verify your performance. The QCP describes how you will ensure your own performance meets the standards before the government checks. An evaluator reading both together should see that your internal controls cover the ground the government will surveil — and then some.
Your QCP needs to address each performance standard in the PWS. For each one, answer:
Set Your Internal Threshold Above the AQL
If the AQL is 95% on-time delivery, set your internal escalation threshold at 97%. That two-point buffer gives you time to identify and fix problems before you fall below the government's acceptable level. Evaluators who understand PBSA look for this — it signals operational maturity, not just compliance.
The best QCPs include trend monitoring: if on-time delivery is slipping from 99% to 98% to 97% over three reporting periods, that trend triggers intervention before the AQL is breached, not after.
Designate a Quality Control Manager by name in your QCP if the PWS allows it. A named QCM with relevant credentials and experience adds credibility the government can verify. If the position is a key personnel slot, the QCM will be evaluated directly.
Past performance on similar contracts matters here too. If you can reference your QCP methodology from a current contract where you've maintained a strong CPARS rating — include it. See our guide to how CPARS ratings are scored to understand what the government records about your quality performance on performance-based contracts.
CapturePilot's proposal features help you build compliance matrices, track performance standards, and structure QCPs that evaluators score highly. See how it works for your team.
Start your 30-day free trialPerformance-based contracts often include financial consequences tied to performance — either positive (award fees, incentive fees) or negative (deductions for falling below AQLs). How you price these into your cost model matters both for your margin and for how the government evaluates your price realism.
Award Fee contracts (CPAF)— A base fee plus an award fee pool the government distributes based on their subjective evaluation of your performance each award period. The RFP will specify what percentage of the total fee is at risk. If 30% of your fee is in the award pool, model your expected performance realistically and don't price assuming you'll earn 100% — most contracts average somewhere between 70% and 85% of the available pool.
Incentive Fee contracts (CPIF) — A more formulaic approach where fee adjusts based on objective performance targets. If you hit the target cost and performance level, you earn a set fee. Underrun costs or exceed performance targets and you earn more. Overrun costs or miss performance targets and your fee drops. These contracts reward efficiency and execution discipline.
Deduction provisions on FFP contracts— Fixed-price performance- based contracts often include a deduction schedule rather than an incentive structure. If you fall below specific AQLs, the government reduces your payment by a defined percentage. These aren't penalties — they're price adjustments reflecting the fact that you didn't deliver what was contracted. Understand the deduction schedule before you sign.
When you price a performance-based contract, build in your quality control costs explicitly. The QCM salary, internal audit time, metrics tracking systems, corrective action capacity — these aren't overhead you can ignore. Contractors who cut QC costs to win the price often find they spend more managing deficiencies and deductions after award than they saved bidding.
For the full framework on pricing federal contracts to win without losing money, see our guide to government contract pricing strategies.
After reviewing proposal debriefings across dozens of performance-based acquisitions, the same patterns show up repeatedly in losing proposals. Most are avoidable.
The most systemic mistake is treating a PWS proposal like a SOW proposal. Compliance checklists and task-by-task responses miss the entire point of performance-based acquisition. The government already knows what tasks are involved. They want to know that you understand what success looks like and that you have a credible, managed approach to delivering it.
Use our guide to government contract debriefings to learn how to extract actionable PWS-specific feedback from a loss — agencies are required to tell you what the technical weaknesses were, and that information is worth more than almost any pre-proposal research.
The best time to engage with a PWS is before it's final — while you can still influence it. Sources sought notices and draft RFPs are opportunities to read the government's initial thinking on performance standards and shape them toward your strengths. Most contractors skip this step.
When a sources sought notice drops, look for any attached PWS or performance description, even if it's labeled as preliminary. Read it against the prior contract PWS if you can find it. Has the government tightened performance standards? Added new QASP requirements? Changed the surveillance method? Each of those changes signals what went wrong on the prior contract — and what they're prioritizing now.
When draft RFPs are posted with a comment period, submit substantive written comments on performance standards that are ambiguous or unachievable. Government acquisition teams read these comments. If you can cite industry benchmarks showing that a proposed AQL is more stringent than what the market can deliver, your comment can result in a revised standard that reflects a realistic level you can hit — and competitors who bid on the final RFP without reading the draft miss that context entirely.
Pre-PWS Intelligence Checklist
The historical PWS is often available through the prior solicitation on SAM.gov, or through a FOIA request if the prior contract is more than a few years old. Reading it tells you more about this requirement than any market research you could do from scratch. The performance standards that have persisted across recompetes are the non-negotiable ones. The standards that changed are the ones where the incumbent struggled.
CapturePilot's market intelligence features pull historical contract data, incumbent performance records, and prior solicitation details so you can build this picture faster. When a PWS-based opportunity enters your pipeline, you can see who ran the prior contract, what the historical performance standards looked like, and whether the incumbent had documented quality issues.
Performance-based contracting rewards preparation more than almost any other acquisition approach. The contractors who win consistently on PBSA contracts aren't the ones who write the most polished prose — they're the ones who understand the performance standards well enough to promise specifically what the government needs and credibly demonstrate that they can deliver it. Get that right and the writing almost takes care of itself.
CapturePilot gives you the intelligence to understand what the government's performance standards mean in practice — before you commit to delivering against them. Book a strategy call to see how it works for your contract categories.