What Is the Proper Action for a COR When Faced With an Issue That May Require Contracting Action

The proper action for a Contracting Officer’s Representative (COR) facing an issue that may require contracting action is to document the facts, avoid directing or negotiating with the contractor, and promptly notify the Contracting Officer (KO) with a clear written summary, while continuing only the surveillance duties already delegated. The COR identifies and reports; the KO decides and acts. This firewall between “watching” and “changing the deal” is the core rule under the Federal Acquisition Regulation (FAR) and agency COR guidance.

The COR role sits at the seam between program execution and contract authority. CORs see problems first because they live in the day-to-day work. That proximity is both the job’s value and its biggest hazard. Understanding why contracting action is reserved to the KO clarifies what a COR should do, what to write, and what never to say.

The delegation mechanism and the authority boundary

Contracting authority flows from statute to the agency head, then downward in writing to warranted KOs. A COR receives only the slice of authority the KO names in a written letter of designation. That letter typically authorizes functions such as monitoring performance, inspecting deliverables, reviewing invoices for allowability of costs, and maintaining surveillance records. It almost never authorizes changing scope, price, schedule, or terms.

The mechanism matters because the contractor performs for the government under a binding instrument. Changing obligations, adding work, relaxing requirements, or waiving defects modifies that instrument. Under the FAR, only a warranted KO acting within authority can bind the government. A COR who says “go ahead and do it, we’ll handle the paperwork” creates an unauthorized commitment. That creates a ratification problem and potential personal exposure.

The deeper “why” is accountability. Funds must be obligated by officials with fiscal authority. If a COR could direct extra work, obligations would escape financial control and audits. The signature wall exists to keep money, scope, and promises synchronized. The COR’s report is the trigger that lets the KO do that legally.

Quantifying the escalation timeline and cost stakes

Contracting action takes time, so late notification is expensive out of proportion to the event. The timeline below shows how an issue matures into a claim when the COR delays. Durations are representative ranges, not fixed rules; they vary by agency and urgency.

The cost stakes are real. Unauthorized commitments must be ratified, and agencies track these as audit findings. Even small drift compounds. A level-of-effort contract billed hourly can accrue unauthorized hours fast. The COR who waits until the monthly invoice to report a performance concern loses the chance to correct course cheaply.

Plainly: a documented issue reported in week one is a management note; the same issue raised in month four is a claim.

Red flags that force immediate escalation

Most issues need a timely memo. Some demand same-day contact with the KO. Watch for these warning signs:

The contractor asks the COR to approve work outside the Statement of Work or to interpret an ambiguity favorably. Performance defects, safety problems, or repeated noncompliance appear that the COR lacks the delegated authority to accept or waive. The contractor claims time is running out and pressures the COR to authorize a change “in the meantime.” The COR is asked to sign a bilaterally signed modification, letter contract, or any document labeled as a change order. Cost or pricing data look inconsistent with the contract, or invoices bill for work not authorized. The COR is told not to tell the KO, or feels pressure from either the contractor or a program office to stay quiet.

Any of these converts a routine report into an urgent notification. Silence here is the failure mode.

Misconceptions that create unauthorized commitments

The most common misconception is that the COR is the government’s “manager” on the contract. The COR manages surveillance, not the agreement. Another is that verbal direction to a contractor is harmless if later documented; in fact, the verbal direction itself may bind or at least trigger a claim.

A subtler error: assuming a problem only counts as “contracting action” if it involves money. Schedule relief, technical direction, and waiver of specifications are all contract changes even when no dollars move. Acceptance decisions can also be reserved to the KO or a separate accepting official.

One professional caveat borders on counterintuitive. Doing nothing is sometimes the correct intermediate action while the KO assesses the issue. A COR should not “fix” a problem by informally coaching the contractor to swap deliverables. That is the COR exceeding the delegation quietly, which is as damaging as a loud unauthorized commitment. Document, notify, then wait for direction.

Practical actions the COR should take

The practical path is short and repeatable. It protects the government and the COR.

Stop and do not direct. Do not tell the contractor what to do about the change; direct them only on surveillance matters within your delegation. Capture facts contemporaneously. Record dates, what was observed, which contract line items are affected, and what the contractor said, without interpretation. Separate observation from recommendation. A COR may describe options for the KO’s consideration, clearly labeled as advice, not direction. Send a written notification to the KO by secure, traceable channel. Use the issue memo format the agency provides. Request clarification if the delegation letter is ambiguous about your authority. Get it in writing before acting. Preserve records until the KO closes the matter. Keep surveillance logs, emails, and inspection results.

A short issue memo typically covers: contract number, date observed, description of the issue, affected requirements, potential impact in plain terms, actions already taken, and a statement that no direction was given to the contractor. That format matches most agency COR notification templates.

Comparing the options the KO may choose

The COR does not select the remedy, but understanding the menu helps write a useful report. The table below contrasts the contracting actions a KO may consider.

Notice the pattern: the COR feeds every row but owns none of them. The value delivered is accurate, timely facts that let the KO choose the least disruptive legal action.

Reconciling the thresholds and knowing the limits

Different documents use different language. FAR-based rules say only KOs can bind the government. Agency COR handbooks say CORs must report promptly and must not direct changes. Some program guidance adds a same-day threshold for safety or urgent issues. Reconciling these is straightforward: treat the strictest applicable threshold as controlling. If any guidance says same-day for safety, that governs. If the delegation letter is narrower than the handbook, the letter governs.

The COR’s authority, in short, is to observe, document, and report. Everything else waits for the KO.

The limits of this guidance are real. Agency COR handbooks, delegation letters, and specific contract clauses can add requirements or narrow authority further. Some agencies use different titles and forms. The general principle is stable, but the operational detail is agency-specific. This article describes general mechanisms, not a substitute for your own delegation letter or the KO’s direction.

This article is general educational information about federal contracting roles, not a legal opinion or a contract-specific directive. It does not create authority or promise any outcome. For decisions on a live contract, follow your written delegation and consult your Contracting Officer, agency counsel, or a qualified local professional.