Quality Assurance Surveillance Plan (QASP): How to Write One

A quality assurance surveillance plan (QASP) is the document a federal, state, or local agency uses to define how it will monitor a contractor's performance after award: which tasks require surveillance, which methods it will use (random sampling, 100% inspection, periodic checks, customer feedback), and what quality level counts as acceptable.

What a Quality Assurance Surveillance Plan Covers

Federal Acquisition Regulation guidance on government contract quality assurance says QASPs should be prepared alongside the statement of work, not bolted on after award, and should identify all work requiring surveillance along with the method of surveillance for each requirement, according to FAR 46.401. That timing matters for proposal teams: the QASP, or a summary of it, often shows up in Section J of the solicitation, which means bidders can see how the agency plans to score their work before they submit a single page.

A typical QASP, modeled on the structure federal agencies actually use, covers six areas:

• Introduction and performance management philosophy
• Roles and responsibilities for the contracting officer and the contracting officer's representative (COR)
• Performance standards and required quality levels
• Monitoring methodologies and acceptable quality levels (AQLs)
• Quality assurance documentation and feedback loops
• Assessment, reporting, and resolution of performance issues

That structure, drawn from a real federal template published by NIH's Office of Acquisition and Logistics Management, is a useful checklist whether you are the agency writing the plan or the contractor trying to reverse-engineer how you will be graded.

Surveillance itself can happen at the contractor's facility or at the point of delivery, and FAR Subpart 46.4 requires every contract to designate upfront where the government reserves the right to perform it, so contractors should not be surprised by a site visit that was never disclosed.

QASP vs. Performance Work Statement vs. Compliance Matrix

Contractors often confuse the QASP with the documents that sit next to it in the solicitation. Each one answers a different question.

If your team has not written a statement of work or built a compliance matrix yet, start there. The QASP only makes sense once you understand what it is measuring you against.

How to Write a Quality Assurance Surveillance Plan

Whether you are a contracting officer drafting the plan or a contractor building an internal version to track your own performance risk, a quality assurance surveillance plan comes together in four steps.

Define What Requires Surveillance

Pull every deliverable and performance requirement straight from the performance work statement or statement of work. Not every task needs the same level of scrutiny. High-risk or high-visibility requirements, like data security controls or patient-facing service levels, warrant closer surveillance than low-risk administrative tasks.

Set Acceptable Quality Levels

An acceptable quality level (AQL) is the threshold a contractor must meet for a given requirement, stated in specific, measurable terms rather than vague language. "Respond to critical incidents within 4 business hours, 95% of the time" is an AQL a surveillance team can actually score. "Respond to incidents promptly" is not.

Choose Surveillance Methods

Match the method to the risk and the volume of work. Common methods include 100% inspection for critical, low-volume deliverables, random sampling for high-volume recurring tasks, periodic inspection on a fixed schedule, and customer feedback gathered through complaints or satisfaction surveys.

Assign Roles, Frequency, and Documentation

Name who performs surveillance, how often, and where the results get recorded. Most federal QASPs route this through the contracting officer's representative and require a documented, auditable trail connecting each observation back to the specific requirement it addresses.

Common QASP Mistakes That Cost Contractors and Agencies

A handful of gaps show up repeatedly, on both sides of the table:

• Acceptable quality levels that are written too vaguely to score consistently
• Surveillance methods that do not match the actual risk of the requirement (100% inspection on low-risk, high-volume work wastes government resources)
• No clear link back to the performance work statement, so contractors cannot tell what they are actually being measured against
• Missing documentation requirements, which makes it hard to defend a performance rating if a contractor disputes it

For a contractor, the fix starts before award: read the QASP or Section J attachments as closely as the evaluation criteria, because that is exactly what it is.

Why Proposal Teams Should Read the QASP Before They Bid

Most proposal teams focus their energy on the evaluation criteria that determine who wins the award, then treat post-award performance monitoring as someone else's problem. That is a mistake. A QASP tells you, in writing, exactly what the agency will hold you to once you have the contract, and a proposal that promises more than the QASP requires you to deliver sets your delivery team up for a rough first year.

Teams that centralize their content library can pull consistent, pre-approved language on staffing plans, quality control processes, and past performance directly into both the technical proposal and the internal QASP response, instead of reconstructing those answers from scratch every time a new solicitation lands. If your team is rebuilding this from a blank document every cycle, it is worth looking at how a dedicated RFP response platform handles recurring government contracting content like this.