Contract Surveillance

Contract surveillance is the government's ongoing monitoring of a contractor's performance during contract execution, conducted by the Contracting Officer's Representative (COR) and supporting technical staff to verify that work meets contractual requirements, deliverables are accepted, and performance problems are identified and corrected promptly.

What is Contract Surveillance?

FAR 46.103 and 46.401 establish the government's quality assurance responsibilities for monitoring contractor performance. Contract surveillance encompasses all formal and informal activities through which the government verifies contractor compliance with the contract's statement of work, quality standards, schedule requirements, reporting obligations, and security requirements.

Surveillance methods vary by contract type and complexity. Common approaches include: reviewing and accepting formal deliverables against stated acceptance criteria; observing contractor work performance at the site; reviewing contractor-submitted status reports; spot-checking work products, test results, or service outputs; reviewing financial reports and invoices; and conducting periodic performance review meetings with contractor management.

The Quality Assurance Surveillance Plan (QASP) is the government's written plan describing how surveillance will be conducted for performance-based contracts, specifying which performance standards will be monitored, what surveillance methods will be used, how frequently monitoring will occur, and how deductions will be calculated if performance standards are not met.

Effective surveillance is the foundation of the CPARS evaluation. CORs who maintain contemporaneous surveillance records, documenting what was observed, when, and what the contractor's response was, produce CPARS narratives that are factually grounded and defensible if the contractor disputes their ratings.

Why Contract Surveillance matters for government contractors

From the contractor's perspective, surveillance activities are the direct inputs to CPARS ratings, which drive future business. Contractors should view surveillance not as adversarial oversight but as a continuous feedback loop: problems identified through surveillance should be corrected promptly, and accomplishments should be proactively communicated to the COR to ensure they are captured in the surveillance record.

Example

A facilities management contractor operating under a performance-based contract with a QASP is subject to monthly facility inspection surveys conducted by the COR, who rates cleanliness, responsiveness to work orders, and customer satisfaction on a scored matrix. When three consecutive inspections show a pattern of delayed work order closure, the COR documents the findings, meets with the contractor's program manager, and issues a written notice requiring a corrective action plan. The contractor submits a plan and improves work order closure rates, which is documented before the annual CPARS evaluation.

Frequently Asked Questions

What is a QASP and when is it required?

A Quality Assurance Surveillance Plan describes how the government will monitor contractor performance on performance-based service contracts. FAR 37.604 requires a QASP for all performance-based service contracts. The QASP specifies performance standards, surveillance methods, inspection frequency, and remedies for non-performance.

How often should the COR conduct surveillance activities?

Surveillance frequency is specified in the QASP or the contract and should be risk-based, higher-risk or higher-value activities warrant more frequent monitoring. The FAR provides general guidance that surveillance should be frequent enough to reasonably ensure compliance but not so intrusive as to interfere with contractor operations.

Can a contractor dispute surveillance findings?

Yes. If the contractor disagrees with a COR's finding, for example, that a deliverable was non-conforming or that a service standard was not met, the contractor should first discuss the disagreement with the COR. If not resolved, the contractor may escalate to the ACO or PCO. For significant disputes that affect payment or performance ratings, the formal Contract Disputes Act process may ultimately apply.

What records should the COR maintain for surveillance?

CORs should maintain contemporaneous documentation of all surveillance activities: inspection dates and results, deliverable review notes and acceptance/rejection decisions, performance review meeting minutes, correspondence with the contractor about performance issues, and all corrective action plans received. These records form the evidentiary basis for CPARS evaluations.