The short answer: An acceptable quality level is the amount of deviation from the performance standard that the Government will tolerate before performance is judged unacceptable. It is not the standard. The standard says what good looks like; the AQL says how much shortfall is still acceptable. It belongs in the performance requirements summary, in the same row as the standard it modifies, and it is the number a contractor prices against and gets paid against, which is why it is a contracting officer decision rather than a drafting detail.
The two get conflated constantly, and the consequences are expensive, so it is worth separating them with an example.
Performance standard: common areas are cleaned nightly and are free of visible debris, dust and spills at the start of each business day. That is an observable condition. Anyone can walk the floor at 7am and say whether it is met.
Acceptable quality level: no more than two valid occupant complaints per month. That is the tolerance. It concedes that a nightly standard will occasionally be missed and states how often is too often.
A standard with no AQL cannot be failed, because any single miss either breaches the contract or does not, and nobody has said which. An AQL with no standard has nothing to measure against, because a complaint about what is undefined.
Most AQLs take one of four shapes. Choosing the shape is usually easier than choosing the number.
These pair a standard with an AQL in the shape that suits it. They are illustrations of the pattern, not values to copy into your own acquisition: the right number depends on your building, your volume, and what your own staff can actually surveil.
| Required service | Performance standard | Acceptable quality level |
|---|---|---|
| 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 |
| Restroom servicing | Serviced twice daily, fixtures clean and supplies stocked | At least 95 percent of inspected restrooms pass |
| Tier 1 help desk | Calls answered by a live technician during core hours | At least 80 percent of calls answered within 30 seconds, measured monthly |
| Emergency response | On-site assessment and initial mitigation of reported emergencies | Response within 60 minutes during business hours, 90 minutes outside them |
| Guard post staffing | All posts staffed for all scheduled hours | Zero unmanned post hours |
Software can structure the acquisition, draft the work statement in results terms, reason about which surveillance method suits an objective, and check the three documents against each other. Setting the acceptable quality level is different in kind. It decides how much shortfall the Government accepts and, through the deduction, what a contractor is paid. A plausible-sounding number generated to fill an empty cell is worse than an empty cell, because a blank gets noticed in review and a confident sentence does not.
ArcPerform writes the performance work statement, the performance requirements summary and the quality assurance surveillance plan from one description. Where you have supplied a standard or a quality level it reproduces yours. Where you have not, it marks the decision rather than inventing a number, and an AI review reports contradictions between the three documents before a solicitation goes out.
It is the amount of deviation from a performance standard that the Government will tolerate before performance is judged unacceptable. It appears in the performance requirements summary in the same row as the standard it modifies, and it is the tolerance a contractor prices against and is measured against during surveillance.
The standard states what acceptable performance looks like in observable terms, such as common areas cleaned nightly and free of visible debris. The acceptable quality level states how much shortfall is still tolerated, such as no more than two valid complaints per month. A standard with no AQL cannot be failed; an AQL with no standard has nothing to measure against.
It depends on the shape of the work. A count over a period suits discrete failures: no more than two valid complaints per month. A percentage suits high-volume repetitive work you will sample: at least 95 percent of inspected areas pass. A time bound suits response work: on site within 60 minutes during business hours. Zero tolerance suits only work where one failure is genuinely unacceptable, such as an unstaffed guard post.
Start from current performance, so the tolerance is a deliberate change rather than an accident. Match tolerance to consequence rather than tidiness. Confirm the surveillance method in your plan could actually detect a breach. Confirm your own staff can sustain that surveillance across the option years. Then write the deduction against the tolerance, tracing to the inspection and payment clauses.
Only where a single failure is genuinely unacceptable, such as an unmanned security post. Zero tolerance written for rigor rather than necessity is expensive: a contractor who is not permitted to fail prices the risk of failing, and the Government pays for it in the bid.
The contractor can satisfy the standard and breach the tolerance in the same period, which makes the pair unenforceable and the first performance dispute unwinnable. It is the most common internal contradiction in a performance requirements summary and is worth checking before a solicitation is issued.
The FAR does not prescribe specific quality levels. FAR 46.401(a) requires a quality assurance surveillance plan to specify all work requiring surveillance and the method of surveillance, and FAR 37.602 requires a performance work statement to enable assessment of performance against measurable standards. An acceptable quality level is how that measurability is made concrete, and setting it is the contracting officer's judgment.