Performance-Based Acquisition (PBA)

Performance-Based Acquisition (PBA) is the government's preferred approach for acquiring services, using performance standards and outcome metrics rather than task prescriptions to define requirements, incentivizing contractor innovation and measuring success by results.

What is Performance-Based Acquisition?

PBA is addressed in FAR 37.601-37.604 and reflects a fundamental shift in how the government acquires services. Traditional acquisitions told contractors exactly what to do and how to do it. PBA tells contractors what results the government needs and lets them determine how to achieve those results.

FAR 37.601 identifies the key elements that make an acquisition performance-based:

1. Describe the work in terms of required results: use a Performance Work Statement (PWS) with measurable outcomes, not a task-prescriptive Statement of Work (SOW)
2. Use measurable performance standards: define what "success" looks like in quantitative terms (time, accuracy, availability, quality)
3. Specify acceptable quality levels (AQLs): define the minimum threshold below which formal corrective action is triggered
4. Develop a Quality Assurance Surveillance Plan (QASP): plan how performance will be measured, how frequently, and what data will be used
5. Use incentives: structure fees, prices, and award terms to reward superior performance and penalize poor performance

PBA also encompasses the solicitation side: using a Statement of Objectives (SOO) instead of a drafted PWS allows offerors to propose their own performance standards and approaches, driving innovation at the proposal stage.

OMB mandates PBA for most service contracts above the simplified acquisition threshold. OFPP's "Seven Steps to Performance-Based Acquisition" provides implementation guidance. Despite this mandate, many agencies still default to task-based acquisition out of familiarity or when requirements are genuinely prescriptive.

Why PBA matters for government contractors

PBA rewards companies with superior operational methodologies, technology, and management systems. If you can achieve the required outcomes more efficiently than the prescriptive approach a government SOW would have mandated, PBA is your competitive advantage. In PBA competitions, technical proposals must demonstrate credibly how the contractor will achieve specific measured outcomes, not just assert that they can. Post-award, PBA provides the contractor freedom to innovate operationally, which can significantly improve margins over a multi-year contract.

Example

GSA's FAS uses PBA to procure facilities management at a federal building campus. Instead of specifying staffing ratios, cleaning schedules, and equipment requirements (the traditional approach), GSA's PWS specifies: cleanliness ratings of 90+ on monthly random inspections (using a standardized rubric), zero maintenance backlog older than 30 days for non-emergency repairs, 100% preventive maintenance schedule completion, and tenant satisfaction scores of 4.0+ on quarterly surveys. The winning contractor uses IoT sensors and predictive maintenance technology to meet these standards with 30% fewer staff than the previous task-based contract specified, and earns 92% of available award fees while spending $800,000 less per year than the previous contract value.

Frequently Asked Questions

Is PBA required for all government service contracts?

FAR 37.601 expresses a preference for PBA "to the maximum extent practicable" for service acquisitions above the simplified acquisition threshold. It is not a strict mandate but a strong directive. Agencies that use task-based SOWs instead must be able to justify why PBA is not appropriate for the specific requirement.

What types of services work well with PBA?

PBA works best for services with measurable outputs: facilities management (cleanliness scores, equipment uptime), IT services (system availability, response times), logistics (on-time delivery rates), and professional services with defined deliverables. Services that are highly variable, exploratory, or genuinely dependent on government direction (such as some advisory services) may be less suitable for strict PBA.

How does PBA affect source selection?

In a PBA competition using a SOO, offerors propose their own PWS, so the technical evaluation includes assessing whether the proposed performance standards are appropriate (ambitious but achievable), the measurement approach is sound, and the methodology credibly supports achieving the standards. This evaluation is more complex than comparing responses to a government-written SOW.

Does PBA reduce the government's workload?

Initially no, developing a good PWS and QASP requires more upfront analysis than drafting a task-based SOW. However, outcome-based oversight (measuring results) is often more efficient than process-based oversight (watching how work is done). Over the life of a contract, PBA's surveillance approach can free up COR time for higher-value activities.