← Back to shelf

Desk reference

Contracting officer warrants, COR limits, and program managers

Roles that speak for the Government on technical performance versus roles that can bind it to a contract action.

1 / 3

Contracting officer (warrant / written authority)

A () may enter into, administer, or terminate contracts only to the extent of authority delegated in writing — industry often calls that a ; the FAR speaks of appointment and written limits. The check that matters is the written delegation and its limits, not seniority or control. When direction would change price, quantity, delivery, or other terms, route it to an official whose written delegation covers the change — do not treat verbal urgency as a substitute for a mod or order.

Watch for

Don’t confuse seniority, a PM title, a email, or a warm customer relationship with contracting authority. None of those bind the Government.

"Contracting officers may bind the Government only to the extent of the authority delegated to them. Contracting officers shall receive from the appointing authority clear instructions in writing regarding the limits of their authority."

2 / 3

Contracting officer’s representative (COR)

A COR assists in the technical monitoring or administration of a contract under a written designation from the contracting officer. The COR keeps a file that includes that designation and documents actions taken within the delegated authority. Place the COR beside the CO on your org sketch: closest to performance reality, still limited to the written designation for anything that changes the deal. Treat COR guidance as performance insight; treat contractual direction as coming only from someone with authority to change the instrument.

Watch for

Don’t treat the COR as a second contracting officer. Technical-monitoring delegation does not include authority to change , funds, or invent new workstreams outside the contract. “Subordinate to the warrant” is shorthand for that limit — not an org-chart reporting claim.

"A contracting officer’s representative (COR) assists in the technical monitoring or administration of a contract (see 1.602-2(d)). The COR shall maintain a file for each assigned contract."

3 / 3

Government program manager

A (or requiring-activity lead) typically owns mission need, , stakeholder coordination, and much of the requirements dialogue. FAR 15.201 recognizes the program manager as a participant in early exchanges; exact duties are agency-specific. In capture, treat the PM as a primary voice on need and success criteria — and still confirm contractual direction through the CO or another official whose written delegation covers the action.

Watch for

Don’t confuse the PM title, budget visibility, or a PM preference with authority to enter into or change a contract. A preference is not a modification.

Further reading

Browse chapters