Acceptance Criteria

Acceptance criteria are the specific, measurable conditions or standards that a contract deliverable, product, or service must meet in order for the government to formally accept it as fulfilling the contractor's contractual obligation, and to authorize corresponding payment.

What are Acceptance Criteria?

Acceptance criteria define the line between conforming and non-conforming performance. They transform the general requirements of a statement of work into testable, verifiable standards that both the government and contractor can evaluate objectively. Well-written acceptance criteria eliminate subjectivity from the acceptance decision and reduce disputes about whether performance was adequate.

Acceptance criteria vary by contract type. For deliverable-based contracts (reports, studies, plans), criteria typically specify: content requirements (specific sections that must be addressed), format (page limits, templates, file types), accuracy standards (data must reconcile to source systems within a specified tolerance), and completeness (all required elements must be present). For performance-based service contracts, the Quality Assurance Surveillance Plan (QASP) specifies performance standards, response times, error rates, customer satisfaction scores, uptime percentages, that must be met within an acceptable quality level (AQL).

For goods and construction, acceptance criteria include technical specifications, testing requirements, and inspection standards. The government's acceptance of goods is typically conditioned on successful completion of required testing, functional testing, destructive testing, dimensional inspection, or other applicable tests.

Poorly defined acceptance criteria, vague requirements like "high quality" or "satisfactory performance" without measurable standards, are a leading cause of contract disputes and CPARS disagreements, since the parties may have different views of what "satisfactory" means in a specific context.

Why Acceptance Criteria matter for government contractors

Contractors should ensure they fully understand the acceptance criteria for every deliverable before beginning performance. When acceptance criteria are ambiguous, raising the question at the post-award conference or in writing to the COR before the deliverable is due prevents disputes at the acceptance stage. Clear acceptance criteria also protect the contractor, if the deliverable meets all stated criteria, the government cannot legitimately reject it on unstated grounds.

Example

A software development contractor's contract specifies that the production system release must meet the following acceptance criteria before the government accepts it: all functional test cases in the test plan must pass (100%); no Severity 1 or Severity 2 defects may be open at release; system performance under load must meet 99.5% uptime as measured over a 30-day pilot period; all required documentation (installation guide, user manual, API reference) must be complete; and security assessment must be approved by the information system security officer. When all criteria are met and documented, the government executes a formal acceptance letter.

Frequently Asked Questions

What happens if a deliverable is submitted but does not meet all acceptance criteria?

The government rejects the deliverable in writing, specifying which criteria were not met. The contractor must correct the deficiencies and resubmit. Contracts typically specify a cure period for resubmission. Repeated failures to meet acceptance criteria can constitute a material breach and may trigger cure notice or default termination proceedings.

Who has authority to formally accept deliverables?

The COR has authority to accept or reject deliverables in most contracts. The COR's acceptance or rejection must be communicated in writing. The COR cannot waive contract requirements or modify acceptance criteria, only the contracting officer can do that through a formal contract modification.

Can the government accept a non-conforming deliverable?

Yes. The government may choose to accept a non-conforming deliverable with a price adjustment (consideration for accepting less than the full contract requirement) or with documented comments noting the deficiency for correction in future deliverables. Acceptance of a non-conforming item without documenting the non-conformance constitutes constructive acceptance of the deficiency.

What is "constructive acceptance"?

Constructive acceptance occurs when the government fails to reject a deliverable within the contractual review period without documenting a specific deficiency. After the review period expires without rejection, the deliverable is deemed accepted by operation of law, and the government may lose the right to later reject it on grounds that could have been identified during the review period.