Contracting Officer’s Representative (COR): Authority and Limits

A Contracting Officer’s Representative, or COR, is a federal employee delegated in writing to monitor a specific contract’s day-to-day performance on behalf of the Contracting Officer, and the role and limits of a contracting officer’s representative are set out in the designation letter and in FAR 1.602-2. The COR watches the work, checks deliverables, and reviews invoices; the COR cannot change the price, scope, schedule, quality, quantity, or any other term of the contract. Only the Contracting Officer can do that.

That split matters because a single Contracting Officer often carries dozens of contracts at once and relies on CORs for the technical eyes on each one. It also matters because a COR who wanders past the line can create an unenforceable agreement for the contractor and personal liability for themselves.

What a COR Is Authorized to Do

The COR’s job is technical monitoring. Under FAR 1.602-2, the Contracting Officer delegates specific administration and oversight duties to the COR in writing, and those delegated duties define the boundaries of the role.¹ In practice, that means tracking milestones, confirming that deliverables meet technical specifications, and checking that the contractor’s staffing and resources match what was proposed. When something falls short, the COR documents the deficiency and raises it with the Contracting Officer.

Quality assurance sits at the center of the work. The COR inspects deliverables, tests services against performance standards, and reviews technical reports against the contract’s requirements. When a contractor submits an invoice, the COR checks it against actual progress, comparing billed labor hours and material costs to what was observed during the performance period. Rubber-stamped invoices are one of the fastest ways waste creeps into a federal contract, so this verification carries weight.

CORs also give contractors technical direction, clarifying ambiguities in the work description and explaining how tasks should be performed. That guidance has to stay inside the existing scope. Telling a contractor how to build the widget the government ordered is technical direction. Telling them to build a different widget is a scope change, and only the Contracting Officer can authorize it.

A COR may also support oversight of government-furnished equipment, materials, or facilities the contractor uses, watching whether the property is maintained, accounted for, and disposed of according to the contract. When property is lost or damaged, the Contracting Officer and the Property Administrator jointly determine the contractor’s liability and the remedy.²

Where the Authority Comes From

No one just starts acting as a COR. The Contracting Officer issues a written designation letter, and that document is the legal foundation for everything the COR does. Under FAR 1.602-2(d)(7), the letter has to spell out:¹

The scope of authority the COR is exercising on behalf of the Contracting Officer
The limitations on what the COR may not do
The duration of the designation
That the authority cannot be redelegated
That the COR may be personally liable for unauthorized acts

Copies go to the contractor and to the contract administration office so everyone knows who holds what authority. The COR must be a government employee unless agency regulations say otherwise, and the designation is tied to a specific contract or task order.¹ FAR 1.604 requires the COR to keep a dedicated file for each assigned contract, containing at minimum a copy of the designation letter, a description of the delegated duties, a copy of the administration functions that cannot be redelegated, and documentation of all COR actions taken under the delegation.³ That file is auditable and becomes the official record of what the COR observed, communicated, and decided.

What a COR Cannot Do

FAR 1.602-2(d)(5) is blunt: a COR has “no authority to make any commitments or changes that affect price, quality, quantity, delivery, or other terms and conditions of the contract.”¹ A COR cannot direct the contractor to operate in conflict with the contract. Concretely, a COR cannot:

Change the price, delivery schedule, or statement of work
Obligate the government to spend additional funds or shift money between budget line items
Authorize work outside the original contract scope
Terminate a contract for default or convenience
Make final decisions on contractor disputes or claims
Redelegate their authority to anyone else

Only the Contracting Officer can formalize any of that through a written contract modification. The COR handles technical monitoring and guidance; the Contracting Officer handles the legal administration of the agreement.

Apparent Authority Does Not Apply

In private business, a company can sometimes be bound by someone who appeared to have authority even if they didn’t. Government contracting is different. Those who deal with the government carry the risk of verifying that the person they’re dealing with actually has the authority they seem to have. If a contractor follows an unauthorized instruction from a COR, such as adding work the COR verbally approved, the government is not legally obligated to pay for that work. The contractor cannot argue that the COR “seemed” to have the authority. Only the powers explicitly granted in the designation letter count.

This catches contractors off guard more often than it should. A COR who speaks with confidence about the project can give the impression of broader authority than they hold. Careful contractors ask for written confirmation from the Contracting Officer before performing any work that arguably changes scope, schedule, or cost.

When a COR Oversteps

When a COR directs work or makes commitments they had no authority to make, the result is an “unauthorized commitment,” an agreement that does not bind the government because the person who made it lacked authority to make it.⁴ The government can fix this through ratification, but it is not automatic. A ratifying official at or above the level of the chief of the contracting office can approve the commitment only when all of the following are true:

The government received and accepted the supplies or services, or will otherwise benefit from the work
The ratifying official has the authority to enter into the commitment
The contract would have been proper if an authorized contracting officer had made it
The price is fair and reasonable
The contracting officer recommends payment and legal counsel concurs
Funds were available at the time the unauthorized commitment was made

If the government declines to ratify, the commitment sits between the COR and the contractor as a personal matter, not a government obligation. The contractor may hold the individual COR personally and financially liable for costs incurred, and the COR faces potential agency discipline.¹ The personal liability warning that FAR requires in the designation letter is not decorative; it signals how seriously the government treats these boundaries. A contractor left holding unratified work can bring a written claim to the Contracting Officer under the Contract Disputes Act, but winning is hard when the contractor knew or should have known the COR lacked authority.⁵

Ethics Boundaries That Shape the Role

A COR works closely with the contractor, which creates obvious conflict-of-interest exposure. Federal ethics rules apply in full, and the margins are tighter than many new CORs assume.

On gifts, a COR may accept an unsolicited gift worth $20 or less per source per occasion, with a $50 total per source per calendar year. Cash and investment interests like stocks or bonds are never acceptable at any value.⁶ A COR cannot “buy down” a gift that exceeds the threshold by paying the difference. Even a gift technically inside the exception should be declined if accepting it would make a reasonable person question the COR’s impartiality.

The Procurement Integrity Act prohibits anyone involved in a federal procurement from knowingly disclosing contractor bid or proposal information, or source selection information, before contract award.⁷ That covers cost and pricing data, technical evaluations, competitive range determinations, and proposal rankings. For a COR with access to that information, a casual conversation with the wrong person can trigger criminal penalties.

There is also a post-employment cooling-off period. Former officials involved in procurements exceeding $10 million cannot accept compensation from the awarded contractor for one year after their involvement.⁸ CORs who are substantially involved in those larger procurements fall inside that rule. Anyone contacted by a contractor about potential employment has to report the contact in writing to their supervisor and the agency ethics official, and either reject the opportunity or recuse themselves from the procurement.

Evaluating Contractor Performance

One of the COR’s most consequential duties is evaluating contractor performance through the Contractor Performance Assessment Reporting System, or CPARS. These evaluations follow a contractor for years and shape their ability to win future government work. Because the COR observed the day-to-day performance, they typically draft the initial assessment as the Assessing Official or an Assessing Official Representative, depending on agency policy.⁹

CPARS evaluations cover seven standard areas: technical quality; cost control; schedule and timeliness; management and business relations; small business subcontracting; regulatory compliance; and other areas as warranted. Every rating has to be supported by a written narrative grounded in objective data rather than general impressions. “The contractor did a good job” without specifics will get kicked back. The narrative should point to concrete evidence: deliverables accepted on first submission, milestones met or missed, cost overruns or efficiencies. Even a COR not formally designated as the Assessing Official should expect to be consulted as the subject matter expert, since they have the closest view of how the contractor actually performed.⁹

At contract closeout, the Contracting Officer relies on the COR for a completion certificate assessing whether all work was satisfactorily performed. That input feeds the final CPARS evaluation and the decision on whether excess funds should be deobligated. The record the COR built along the way, invoice by invoice and deliverable by deliverable, is what makes those final judgments defensible.

1
Acquisition.gov. 48 CFR 1.602-2 – Responsibilities
2
eCFR. 48 CFR Part 45 – Government Property
3
Acquisition.gov. 48 CFR 1.604 – Contracting Officers Representative
4
eCFR. 48 CFR 1.602-3 – Ratification of Unauthorized Commitments
5
Office of the Law Revision Counsel. 41 USC 7103 – Decision by Contracting Officer
6
eCFR. 5 CFR 2635.204 – Exceptions to the Prohibition for Acceptance of Certain Gifts
7
Office of the Law Revision Counsel. 41 USC Chapter 21 – Restrictions on Obtaining and Disclosing Certain Information
8
Office of the Law Revision Counsel. 41 USC 2104 – Prohibition on Former Officials Acceptance of Compensation
9
CPARS. Guidance for the Contractor Performance Assessment Reporting System