Contracting Officer's Representative (COR): Roles and Responsibilities

A Contracting Officer's Representative (COR) is a federal government employee formally designated to assist the Contracting Officer (CO) in the technical monitoring and administration of a contract. CORs occupy a critical oversight position that directly affects contract performance, payment authorization, and compliance with federal acquisition law. This page covers the COR's defined role under federal regulation, how the designation functions in practice, common operational scenarios, and the precise boundaries that separate COR authority from Contracting Officer authority.

Definition and scope

The COR role is established and governed primarily by the Federal Acquisition Regulation (FAR), specifically FAR Subpart 1.602-2, which requires agencies to designate a COR in writing for each contract when the contract will be performed at a location where the CO cannot be present. The Office of Management and Budget's Office of Federal Procurement Policy (OFPP) further codified COR certification requirements through OFPP Policy Letter 05-01, establishing a competency-based framework that all civilian agencies must follow.

A COR must be a federal civilian or military employee — never a contractor — and must hold a valid written designation letter from the CO that defines the specific delegated duties. The COR has no independent contracting authority. All authority flows from, and is bounded by, the written designation letter issued under the CO's warrant.

The scope of COR responsibilities typically encompasses:

1. Technical monitoring — Verifying that contractor deliverables meet the performance standards, specifications, and timelines in the Statement of Work (SOW) or Performance Work Statement (PWS).
2. Acceptance or rejection of deliverables — Documenting whether goods or services conform to contract requirements before recommending payment.
3. Surveillance and inspection — Conducting site visits, reviewing reports, and maintaining a contemporaneous surveillance log.
4. Issue identification and escalation — Identifying deficiencies or potential changes and immediately referring them to the CO rather than resolving them unilaterally.
5. Invoice review — Validating that invoices correspond to completed, accepted work before forwarding to the CO or finance office for payment authorization.
6. Documentation — Maintaining a contract file with all communications, inspection reports, surveillance records, and correspondence.

How it works

After contract award, the CO issues a formal delegation letter to the designated COR. The letter specifies the contract number, the period of designation, and an itemized list of delegated functions. The COR does not sign contracts, issue contract modifications, direct work outside the scope of the existing contract, or authorize changes that affect price, schedule, or performance requirements — those actions remain exclusively with the CO.

The COR's day-to-day work centers on the Quality Assurance Surveillance Plan (QASP), a document that describes how contractor performance will be measured against the contract's standards. The QASP identifies surveillance methods — direct observation, random sampling, periodic inspection, and customer feedback — and assigns each measurable outcome an acceptable quality level (AQL).

When a contractor submits an invoice, the COR reviews it against documented acceptance records and certifies that the billed work was performed and accepted. This certification is a prerequisite for payment processing under the Prompt Payment Act (31 U.S.C. § 3903), which imposes interest penalties on agencies that pay late. COR accuracy at the invoice review stage directly affects an agency's compliance with that statute.

For context on how the COR role interacts with the broader contracting structure, the federal acquisition regulation overview page describes the regulatory hierarchy within which COR duties operate.

Common scenarios

Scenario 1 — Services contract surveillance. On a professional services contract, the COR conducts monthly reviews of deliverable reports, documents deficiencies, and provides written notice to the CO when a contractor misses a milestone. The COR does not instruct the contractor to fix the problem directly without CO involvement if the fix could alter scope.

Scenario 2 — Construction project oversight. On a construction government contracting project, the COR performs site inspections, reviews submittals, and documents site conditions. If the contractor requests a change due to unforeseen site conditions, the COR documents the request in writing and transmits it to the CO — the COR cannot authorize a constructive change.

Scenario 3 — IT and technology contracts. On an IT and technology government contracting task order, the COR monitors system delivery milestones, evaluates technical compliance, and coordinates with agency IT security staff. When the contractor proposes substituting a system component not specified in the contract, the COR refers the matter to the CO for a formal contract modification rather than providing verbal approval.

Scenario 4 — IDIQ task order management. Under an indefinite-delivery indefinite-quantity (IDIQ) vehicle, a separate COR may be designated for each task order, with authority limited to that specific task order's scope and period of performance.

Decision boundaries

The most operationally significant distinction in COR practice is the line between technical direction and a constructive change. A constructive change occurs when a government representative — including a COR — communicates something to a contractor that the contractor reasonably interprets as authorization to perform work outside the contract's existing scope, price, or schedule. Constructive changes can generate valid contractor claims under the Contract Disputes Act (41 U.S.C. §§ 7101–7109), exposing the agency to cost liability.

COR authority — permitted actions:
- Clarifying technical requirements already stated in the contract
- Monitoring and documenting performance
- Accepting or rejecting completed deliverables against existing contract standards
- Certifying invoices for work already accepted
- Reporting performance deficiencies to the CO

CO-only actions — outside COR authority regardless of urgency:
- Issuing, negotiating, or signing contract modifications
- Authorizing additional work beyond the contract's funded ceiling
- Granting extensions to delivery schedules
- Terminating the contract for convenience or default (see contract termination for convenience and contract termination for default)
- Resolving disputes or claims (see government contract disputes and claims)

COR certification requirements vary by contract dollar threshold. The Federal Acquisition Institute (FAI) and the Defense Acquisition University (DAU) administer the three-level COR certification framework established under OFPP guidance: Level I applies to lower-risk contracts, Level II to most standard contracts, and Level III to complex, high-value contracts. Department of Defense CORs follow DFARS 201.602-2 and associated DFARS compliance requirements, which impose additional training and documentation obligations beyond the civilian baseline.

A broader orientation to roles within the acquisition workforce — including how the COR, CO, and program office interact — is available through the government contractor authority home resource pages.