The short answer: A performance requirements summary is the table that states, for each required service, the performance standard, the acceptable quality level, and the deduction or incentive that applies when performance falls outside it. It is usually attached to the performance work statement as Technical Exhibit 1, and it is the document a contracting officer and a contractor will both point at during a performance dispute. Everything in it should already appear in the work statement; the summary is what makes it measurable.
A PRS has four working columns, and each one answers a different question.
Some agencies add a fifth column naming the surveillance method, which duplicates the quality assurance surveillance plan. That is a matter of local practice. If you do it, the two documents have to be kept in step, because a summary and a plan that name different methods for the same service is a contradiction a contractor will find.
Custodial and grounds services for an office building. Four required services, four rows. Illustrative only: the right values depend on your building, your volume, and what your own staff can surveil.
| Required service | Performance standard | Acceptable quality level | Deduction |
|---|---|---|---|
| Common area cleaning | Cleaned nightly, free of visible debris at the start of each business day | No more than 2 valid occupant complaints per month | 1 percent of the monthly custodial fee per complaint above the AQL, capped at 5 percent |
| Restroom servicing | Serviced twice daily, fixtures clean and supplies stocked | At least 95 percent of inspected restrooms pass | 1 percent of the monthly restroom line item for each full point below 95 percent |
| Grounds maintenance | Mowed during the growing season, turf height between 2.5 and 3.5 inches | No more than 1 missed scheduled cut per season | Cost of the missed cut deducted from the monthly grounds fee |
| Emergency response | On-site assessment and initial mitigation of reported emergencies | Response within 60 minutes during business hours | 2 percent of the monthly fee per late response, capped at 10 percent |
Read across any row and it should hold together on its own: this is the work, this is what good looks like, this is how much shortfall is tolerated, this is what exceeding it costs.
A performance-based service acquisition carries three linked documents, and the summary is the middle one.
All three draw on one set of performance objectives. When they are drafted separately, that spine breaks, and the summary is usually where the break becomes visible.
Most PRS documents live in a word processor, and every acquisition copies the last one. Copying is what makes the criteria editable, and editable criteria are how a summary ends up out of step with the work statement it was attached to. If your summary and your surveillance plan are separate files maintained by different people, expect them to disagree within two acquisitions, and expect to find out during a dispute.
ArcPerform drafts the performance work statement, the performance requirements summary and the quality assurance surveillance plan together from one description, so every objective appears in all three. It marks the standards and quality levels it will not set for you, and an AI review reports contradictions between the three before a solicitation goes out.
It is the table that states, for each required service in a performance-based service contract, the performance standard, the acceptable quality level, and the deduction or incentive that applies when performance falls outside it. It is usually attached to the performance work statement as Technical Exhibit 1.
Four working columns: the required service, the performance standard, the acceptable quality level, and the deduction or incentive. Some agencies add a fifth naming the surveillance method, which duplicates the quality assurance surveillance plan and has to be kept in step with it.
No. The summary states what acceptable performance is and what falling short costs. The surveillance plan states how the Government will check each of those rows, including the method and the frequency. They cover the same objectives from different sides, and they must not disagree about the work.
To the performance work statement, conventionally as Technical Exhibit 1, alongside a deliverables schedule as Technical Exhibit 2. The work statement describes the required results and the summary makes them measurable.
An acceptable quality level that is tighter than the standard it modifies, so the contractor can satisfy the standard and breach the tolerance in the same period. Close behind it are rows with a standard but no quality level, deductions that trace to nothing in the contract, and uncapped deductions.
It should. A task in the work statement with no row in the summary is work the contractor owes that nobody has said how to measure, which means it will not be surveilled and cannot be enforced without an argument.
It can build the table, carry the objectives across from the work statement, and check the rows against the surveillance plan for contradictions. It should not set the performance standard, the acceptable quality level, or the deduction, because those decide what a contractor is paid and are contracting officer judgments.