A performance based contract pays the contractor for delivering a defined, measurable result rather than for the hours, staffing, or step-by-step methods used to get there. The client describes what “done” looks like, the contractor decides how to reach it, and payment is tied to whether the work meets the standards written into the agreement. Federal agencies are required to use this approach “to the maximum extent practicable” when buying services under Federal Acquisition Regulation Subpart 37.6, and the model has spread into private-sector construction, IT, and facilities work for the same reason it took hold in government: it moves the question from “did the contractor follow instructions” to “did the job actually get done.”
How It Differs From a Traditional Service Contract
A traditional service contract prescribes staffing levels, work schedules, and procedures. The client dictates the method; the contractor is paid for following it. If the method is flawed, the contractor still gets paid, because compliance was the deliverable.
A performance based contract inverts that. The client sets the end state: a building that passes inspection, a network with 99.9% uptime, janitorial service where 95% of random inspections score “acceptable.” The contractor chooses the approach and carries the risk if the chosen approach fails. FAR 37.6 captures the principle, requiring agencies to describe work “in terms of the required results rather than either ‘how’ the work is to be accomplished or the number of hours to be provided.”
The Contract Documents That Define “Done”
Every performance based contract depends on a document that spells out the required outcome in terms specific enough to be measured. In federal procurement, that document is usually a Performance Work Statement. FAR 37.602 requires a PWS to describe results in measurable terms, allow assessment against performance standards, and rely on financial incentives in a competitive environment to encourage cost-effective methods.
The alternative is a Statement of Objectives. Instead of writing the full PWS itself, the client publishes broad objectives and asks each bidder to propose its own PWS explaining how it would meet them. The SOO must include at minimum the purpose, scope, period and place of performance, background, required results, and any operating constraints. The SOO itself does not become part of the final contract. The winning bidder’s proposed PWS does.
A PWS works best when the client understands the work well enough to define specific outputs and quality levels. A SOO works better when the client knows the goal but wants the market to propose creative approaches. Either way, the contract must also include measurable performance standards and, where appropriate, performance incentives.
Performance Metrics and the Surveillance Plan
The metrics have to be specific enough that two reasonable people reviewing the same data would reach the same conclusion. “Do a good job” is not a metric. “Respond to 95% of service tickets within four hours” is. Every standard should answer three questions: what is being measured, what level is acceptable, and how the measurement will happen.
The Quality Assurance Surveillance Plan
A Quality Assurance Surveillance Plan describes exactly how the client will verify whether the contractor is meeting the standards. The QASP is the client’s tool, not the contractor’s. It sets out systematic monitoring methods, documentation requirements, and the resources devoted to oversight. Its core purpose is ensuring the client “pays only for the level of services received.”
Not every deliverable can be inspected individually. Where 100% inspection is impractical, the QASP should include a sampling guide specifying what will be checked, the Acceptable Quality Level, and how samples will be selected. The AQL is the maximum allowable variance from a standard before the client rejects the service, expressed as a number, a percentage, or a rate per units inspected. When a sample fails to meet the AQL, decision tables help determine whether the failure is the contractor’s fault or stems from something outside its control.
Subjective Standards and the 100% Trap
Some metrics are straightforward: completion dates, error rates, response times. Others require judgment, like customer satisfaction or quality of finish on a construction project. Subjective standards are not inherently weaker, but they need predefined scoring rubrics built into the contract before work begins. Without that rubric, the contractor has no way to calibrate its effort, and any dispute collapses into competing opinions.
The most common drafting mistake is setting the performance standard at 100%. That sounds like high expectations, but it drives up the price because the contractor has to build in the risk that a single failure triggers a penalty. Experienced agencies set the minimum acceptable level below perfection and use incentives to reward performance above that floor.
How Payment Is Structured
If the payment structure doesn’t create meaningful financial consequences tied to outcomes, the metrics and the surveillance plan are just paperwork. Several structures accomplish that in different ways.
Fixed-Price With Incentives
The most common structure pairs a fixed price with adjustments for exceeding or falling short of targets. The contractor quotes a price to deliver the specified results. Incentive fees or award fees provide upside for surpassing baseline expectations. Liquidated damages provide downside for falling short. FAR Subpart 11.5 governs liquidated damages in federal construction contracts, requiring that the daily rate reflect the government’s actual estimated costs from delay, including expenses like renting substitute property or paying additional housing allowances. The daily rate is set during contract formation, not after the delay, which prevents arguments about actual damages later.
Award-Fee Contracts
Award-fee contracts set aside a pool of money the contractor can earn through strong performance but is not guaranteed. Under FAR 16.4, the percentage of the pool the contractor earns depends on an adjectival rating. An “Excellent” rating earns 91% to 100% of the pool, “Very Good” earns 76% to 90%, “Good” earns 51% to 75%, and “Satisfactory” earns no more than 50%. An “Unsatisfactory” rating earns nothing. Unearned award fees cannot roll over to future evaluation periods. If a base fee is included alongside the award fee, it cannot exceed 3% of the estimated contract cost.
Shared Savings
Some contracts include a shared savings clause: the contractor earns a percentage of any cost reductions it generates through innovation. If a facilities contractor redesigns an HVAC schedule and saves the client $50,000 in energy costs, the contractor might keep 20% of the savings. The structure aligns interests because the contractor profits directly from finding efficiencies rather than protecting the status quo.
Prompt Payment Protections
Contractors who deliver verified work are not left waiting indefinitely for payment. The federal Prompt Payment clause at FAR 52.232-25 requires the government to pay a proper invoice within 30 days of receipt or 30 days after acceptance of the work, whichever is later. If payment is late, an interest penalty accrues automatically. If the government still fails to pay the interest penalty within 10 days of paying the overdue invoice, an additional penalty applies upon written demand from the contractor. Private-sector contracts should include similar protections. Without them, the contractor absorbs financing costs that properly belong to the client.
Bonds and Insurance
Because this model shifts execution risk to the contractor, both sides need financial backstops in case the contractor cannot deliver.
Performance Bonds
A performance bond is a guarantee from a third-party surety that the contractor will complete the work as specified. If the contractor defaults, the surety steps in. It might provide financial or technical support to finish the job, hire a replacement contractor, or pay the bond amount to the client. For federal construction contracts over $100,000, the Miller Act requires both a performance bond and a payment bond before award. The performance bond amount is whatever the contracting officer considers adequate to protect the government. State public works projects have similar bonding requirements, with varying dollar thresholds.
Professional Liability Insurance
When a contractor takes responsibility for outcomes rather than for following instructions, the risk of professional errors increases. Errors and omissions insurance, also called professional liability insurance, covers claims arising from mistakes in the contractor’s work product. Federal acquisition regulations require contractors to carry insurance covering the risks to which they are exposed, and professional liability coverage is standard for IT, engineering, and consulting contracts where a flawed deliverable could cause downstream losses. The specific coverage amounts should be written into the contract rather than left to the contractor’s discretion.
Who Owns the Deliverables
Ownership of the work product needs to be settled before the work begins. Performance based contracts are especially prone to intellectual property disputes because the contractor has discretion over methods and often creates proprietary tools, processes, or code along the way.
The cleanest approach is a work-for-hire clause. Under federal copyright law, a commissioned work qualifies as “work made for hire” only if it falls into one of nine specific categories (contributions to a collective work, audiovisual works, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, or atlases) and both parties sign a written agreement designating it as such before the work is created. If the deliverable does not fit one of those categories, it cannot be a work for hire regardless of what the contract says, and the creator retains the copyright.
When work-for-hire does not apply, the contract should include an explicit assignment clause transferring ownership upon delivery and full payment. The contract should also address pre-existing materials. If the contractor uses proprietary tools or code libraries that existed before the contract, the contractor typically keeps ownership of those tools and grants the client a license to use them as part of the delivered product. Failing to draw this line creates problems when the contract ends and one party claims the other is using its property without permission.
What Happens After Award
The Kickoff Meeting
Before work begins, a post-award orientation conference aligns both sides on expectations. FAR Subpart 42.5 requires the chairperson to prepare a signed report covering all items discussed, areas requiring resolution, controversial matters, names of participants assigned to follow-up actions, and due dates. One ground rule matters: the meeting cannot change the contract. Any commitment or direction that amounts to a change has to go through a formal modification.
Ongoing Surveillance and Acceptance
Once work begins, the contractor submits regular performance reports measured against the QASP’s standards. The client verifies those reports through direct inspection, data analysis, or sampling. Under the Prompt Payment clause, government acceptance of services triggers the 30-day payment clock, and services are presumed accepted 60 days after delivery if the government takes no action. That presumption protects contractors from indefinite payment delays caused by slow review.
Federal Performance Ratings
Federal contractors receive formal performance ratings through the Contractor Performance Assessment Reporting System. The ratings follow the contractor into future competitions and directly affect the ability to win new work. The scale runs from “Exceptional” through “Very Good,” “Satisfactory,” and “Marginal” down to “Unsatisfactory.” A contractor cannot receive a rating lower than “Satisfactory” simply for not performing beyond what the contract required. Before assigning a “Marginal” or “Unsatisfactory” rating, the evaluator must reference the specific management tool used to notify the contractor of the deficiency, such as a cure notice or deficiency report.
Termination and Disputes
Termination for Default
When a contractor fails to meet performance standards or falls so far behind that completion looks doubtful, the client can move toward termination for default. Under FAR 49.402-3, the contracting officer must first issue a written cure notice identifying the specific failure and giving the contractor at least 10 days to fix it. The 10-day period can be extended if the situation warrants. Only after the cure period expires without adequate correction can the contracting officer issue a termination for default. This is the harshest outcome: it can trigger liability for excess reprocurement costs, loss of the performance bond, and a damaging CPARS record that follows the company for years.
Termination for Convenience
The government can also end a contract simply because it no longer needs the work, known as termination for convenience. The contractor is entitled to recover costs for work already performed and cannot be stripped of anticipated profits unless there has been a substantial change in circumstances between award and termination. A convenience termination cannot be used as a backdoor to avoid paying for completed work, and courts have held that entering a contract with no intention of fulfilling it constitutes bad faith that voids the convenience termination right.
Dispute Resolution
Disputes over performance ratings, payment deductions, or scope disagreements rarely go straight to litigation. Most performance based contracts include a tiered resolution process. The parties first attempt direct negotiation between executives with settlement authority, typically within 30 days of a written notice of dispute. If negotiation fails, the dispute moves to mediation or arbitration as specified in the contract. Statements made during negotiation are generally treated as confidential and inadmissible in any later proceeding. A thorough paper trail of monitoring activities, inspection results, and communications makes disputes easier to resolve at the earliest possible stage.
When This Model Is the Wrong Choice
Performance based contracting does not fit every procurement. It works when the client can define measurable outcomes clearly and when the contractor has genuine latitude to choose methods. It works poorly when the work can only be described in general terms, when the risk of performance is not reasonably manageable by the contractor, or when regulatory requirements dictate specific processes the contractor cannot change. Research and development contracts often resist this structure because the outcome is genuinely unknown at the outset.
Partial implementation is worse than not using the model at all. Agencies that have applied only selected pieces of the methodology, such as defining performance metrics but not enforcing them through financial consequences, have reported that it actually reduced the quality of services compared to a traditional approach. If the client cannot commit to a real QASP, link payment to verified results, and place meaningful financial risk on the contractor, a traditional contract with detailed specifications will often produce better outcomes.