Quality Assurance in Contract Administration

Quality assurance (QA) in contract administration is the set of government activities, inspection, testing, surveillance, and acceptance, designed to verify that contractor work conforms to contract requirements, standards are being met, and deficiencies are identified and corrected before they affect mission outcomes.

What is Quality Assurance in Contract Administration?

FAR Part 46 establishes the government's quality assurance framework for contracts. The government's QA approach is distinct from the contractor's own quality control (QC) program: the government is responsible for verifying conformance, while the contractor is responsible for achieving it. Government QA does not relieve the contractor of its responsibility to deliver acceptable work; it supplements the contractor's own quality processes.

Government QA activities include: reviewing contractor deliverables against acceptance criteria; conducting technical inspections of work in progress; administering the QASP for performance-based contracts; reviewing and approving (or rejecting) contractor test reports and quality control plans; sampling and testing products at the point of delivery; and evaluating contractor management and process quality through audits and site visits.

QA planning begins at contract award, the government establishes its surveillance approach before performance starts. For high-risk or complex technical contracts, the government may embed technical representatives at the contractor's facility (Defense Contract Management Agency performs this function for large defense contractors). For service contracts, the QASP defines what standards will be monitored and how.

Why QA in Contract Administration matters for government contractors

A contractor's CPARS quality rating is directly derived from the government's QA findings during the contract. Contractors that maintain strong internal QC processes, deliver conforming work consistently, and address QA findings promptly earn high quality ratings. Contractors that deliver non-conforming work, fail to address findings, or lack documented QC processes risk "Marginal" or "Unsatisfactory" CPARS ratings with long-lasting competitive consequences.

Example

A defense IT services contractor operates under a contract with an embedded DCMA quality assurance representative. The DCMA rep conducts monthly software delivery quality reviews against the contract's Technical Performance Measures and issues monthly QA reports documenting defect density, test coverage, and software release quality. When test coverage falls below the 85% threshold in month 7, the contractor submits a corrective action plan, implements a code review protocol, and recovers to 92% coverage by month 9, all of which is documented in the CPARS evaluation as demonstrating proactive response to quality issues.

Frequently Asked Questions

What is the difference between government quality assurance and contractor quality control?

The contractor's quality control (QC) program is the contractor's own internal processes for achieving and maintaining the required quality standards, testing, inspections, peer reviews, and process controls. Government quality assurance (QA) is the government's independent verification that the contractor's QC is effective and that deliverables actually conform to requirements.

Is the government required to accept work that passes the contractor's own inspection?

No. The government conducts its own independent inspection and acceptance. Even if the contractor's QC process has accepted work, the government may reject it if its own inspection finds non-conformance. However, if the government accepts non-conforming work with knowledge of the non-conformance, the government may waive its right to reject.

Can QA findings result in price reductions?

Yes. Performance-based contracts with a QASP typically include a Performance Requirements Summary with acceptable quality levels and associated remedies, including payment deductions, when performance falls below the acceptable quality level. These deductions may be applied automatically based on surveillance results.

What happens if the contractor and government disagree on a quality finding?

If the contractor believes a QA finding is incorrect, for example, that a deliverable does comply with the contract requirements, the contractor should first raise the disagreement with the COR. If unresolved, the issue can be escalated to the ACO. For significant disputes affecting payment, formal dispute mechanisms under the Contract Disputes Act apply.