The short answer: A performance-based service acquisition needs three documents. The performance work statement (PWS) says what result the Government is buying. The performance requirements summary (PRS) is the table that states, for each required service, the performance standard, the acceptable quality level, and the deduction. The quality assurance surveillance plan (QASP) says how the Government will check. They are not three projects. They are one set of performance objectives written three ways, and the reason they so often contradict each other is that they get written separately, by different people, at different times.
The names get used loosely, so it is worth being precise about which document carries which burden.
FAR 37.602 requires a PWS to describe the requirement in terms of required results rather than the methods of performing the work, and to enable assessment of work performance against measurable standards. That is the whole test. If a paragraph tells the contractor how many people to staff or which product to buy, it has stopped being performance-based. If a paragraph describes a result nobody could measure, it has failed the second half.
A standard PWS carries more than the tasks: general information, definitions, what the Government furnishes, what the contractor furnishes, the specific tasks, applicable publications, and the technical exhibits. Most of that is facts about your acquisition rather than writing: hours of operation, recognized holidays, security requirements, key personnel, phase in and phase out. They are short sections and they are the ones most often left out, which is how a contractor ends up with a claim for work on a holiday nobody named.
The PRS is the table a contracting officer signs against, usually attached to the PWS as Technical Exhibit 1. One row per required service, and four things in each row: the service, the performance standard, the acceptable quality level, and the deduction or incentive that applies when performance falls outside it. What goes in each column, with a worked example.
Two of those four are frequently confused. The standard is what acceptable performance looks like, stated in observable terms: common areas cleaned nightly and free of visible debris. The acceptable quality level is how much deviation the Government will tolerate before performance is unacceptable: no more than two valid complaints per month. A standard without an AQL cannot be failed. An AQL without a standard has nothing to measure against. How to set an acceptable quality level, with worked examples.
FAR 46.401(a) says a QASP should be prepared in conjunction with the statement of work and should specify all work requiring surveillance and the method of surveillance. FAR 46.401(b) adds that each contract shall designate the place or places where the Government reserves the right to perform quality assurance. FAR 37.604 points service acquisitions to subpart 46.4 and permits the Government to prepare the plan or to require offerors to submit one.
That is a short regulatory surface, and it is worth reading literally. The QASP does not restate the standards. It states, for each objective already in the PRS, how the Government will observe performance and how often.
Four methods are in common use. Choosing one is a judgment about volume, consequence, and how much surveillance your own staff can actually sustain. A fuller guide to choosing between them.
The three documents share one spine: the performance objectives. Every objective should appear as a task narrative in the PWS, a row in the PRS, and a surveilled row in the QASP. When they are drafted as three separate deliverables, that spine breaks in predictable ways.
These are the contradictions worth looking for before a solicitation goes out:
Each of these is cheap to fix before award and expensive afterward, because after award the fix is a modification or an argument with a contractor who read the document literally and was entitled to.
Software can structure this work, draft the narrative, reason about which surveillance method fits an objective, and check the three documents against each other. There is a line it should not cross.
An acceptable quality level decides how much deviation the Government will accept before performance is unacceptable. It governs what a contractor is paid. A performance standard decides what the contractor owes. A deduction decides what it costs them to fall short. These are contracting officer judgments with money attached, and a plausible-sounding number generated to fill an empty cell is worse than an empty cell, because a blank gets noticed and a confident sentence does not.
The same applies to facts about the acquisition. A period of performance, a place of performance, security requirements, key personnel: no tool knows these. Printed as a marked blank they tell you what you still owe. Invented, they go into a solicitation nobody authorized.
Read the finished package and ask five questions. Does every objective appear in all three documents? Does every standard state something observable? Does every AQL have a standard it modifies? Could the surveillance method in the plan actually detect a breach of the quality level in the summary? Does every deduction trace to a clause in the contract? Five yes answers is a package that will survive the first performance dispute.
ArcPerform writes the performance work statement, the performance requirements summary, and the quality assurance surveillance plan from one description, structured to FAR 37.602 and FAR 46.401. It marks every judgment it will not make for you, and an AI review reads the finished package back and reports where the three documents contradict each other. No account.
A statement of work describes the work to be performed, often including how. A performance work statement describes the required result and the measurable standard it will be judged against, and leaves the method to the contractor. FAR 37.602 is the operative provision: describe the requirement in terms of required results rather than the methods of performing the work.
The standard says what acceptable performance looks like, in observable terms. The acceptable quality level says how much deviation the Government will tolerate before performance is unacceptable. A standard without an AQL cannot be failed; an AQL without a standard has nothing to measure against. Both belong in the performance requirements summary, in the same row.
FAR 46.401(a) says a quality assurance surveillance plan should be prepared in conjunction with the statement of work and should specify all work requiring surveillance and the method of surveillance. FAR 46.401(b) says each contract shall designate the place or places where the Government reserves the right to perform quality assurance. FAR 37.604 points service acquisitions to subpart 46.4 and permits the Government to prepare the plan or to require offerors to submit one.
100 percent inspection, random sampling, periodic inspection, and customer complaint. 100 percent inspection suits low-volume high-consequence work. Random sampling suits high-volume repetitive work and needs a sample size defensible against a stated acceptable quality level. Periodic inspection suits continuous services. Customer complaint is a supplement rather than a sound primary method, because it measures what people reported rather than what happened.
One row for each required service, carrying four things: the 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.
Yes. They share one set of performance objectives, and writing them separately is the most common reason they end up contradicting each other: an acceptable quality level nothing in the surveillance plan could detect, random sampling with no tolerance to sample against, a deduction that fires on a condition no standard defines, or a task in the work statement with no row in the summary.
It can structure one, draft the task narratives in results terms, reason about which surveillance method fits an objective, and check the three documents against each other. It should not set an acceptable quality level, a performance standard, or a deduction. Those decide what a contractor is paid and are contracting officer judgments. A plausible number generated to fill an empty cell is worse than an empty cell, because a blank gets noticed and a confident sentence does not.