What a Contracting Officer Actually Does

Most people who work near federal contracts learn the roles by accident, usually after something goes wrong. A vendor spends three weeks building a feature because a government engineer asked for it in a Teams call, then discovers nobody will pay for it. A new program manager tells a contractor to shift two people to a different task and finds out later that this was, in legal terms, an unauthorized commitment. A brand-new contract specialist watches a meeting where four government employees give a contractor four different answers and cannot work out which one counts.

The answer to all three situations is the same, and it is unusually crisp for federal work. One person can bind the United States on a contract. That person is the contracting officer. Everyone else in the room, no matter how senior, is advising.

This article explains what that actually means day to day: where the authority comes from, what its limits are, how the contracting officer differs from a contracting officer's representative and from a program manager, what happens when the wrong person gives direction, and how a vendor should route a given question. It is written for two readers at once, the government employee who is new to acquisition and the company employee who keeps talking to the wrong person.

The one signature that matters

Federal contracting authority starts at the top and is delegated down. FAR 1.601 vests authority to contract in the agency head. That authority flows down through appointing officials to individual employees, and FAR 1.601(a) states plainly that contracts may be entered into and signed only by contracting officers.

FAR 1.602-1(a) gives the operative rule: contracting officers have authority to enter into, administer, or terminate contracts and make related determinations and findings, and they may bind the government only to the extent of the authority delegated to them. The same paragraph adds a sentence vendors should remember, because it is a right rather than a courtesy: information on the limits of a contracting officer's authority must be readily available to the public and to agency personnel. You may ask.

FAR 1.602-2 sets out what the job requires. The contracting officer is responsible for ensuring performance of all necessary actions for effective contracting, ensuring compliance with the terms of the contract, and safeguarding the interests of the United States in its contractual relationships. Three duties come with that. Ensure that funds are available and that all legal and regulatory requirements were met before signing. Ensure that contractors receive impartial, fair, and equitable treatment. Request and consider the advice of specialists in audit, law, engineering, information security, transportation, and other fields, as appropriate.

That third duty is the part outsiders miss. A contracting officer is not expected to be the technical expert. They are expected to gather the technical, legal, and financial advice, weigh it, and then make an independent decision that they personally sign. A program office can push hard for an outcome. It cannot sign.

The warrant, and what limits it

The appointment is made in writing on Standard Form 1402, the Certificate of Appointment. FAR 1.603-3 requires that the SF 1402 state any limitations on the scope of authority, other than limits already imposed by law or regulation. People call this document the warrant, and the person who holds it a warranted CO.

Warrants are not identical. Agencies set their own tiers, and a warrant typically carries a dollar ceiling, sometimes a scope restriction such as construction only or simplified acquisitions only. Common tiers track familiar FAR thresholds: the micro-purchase threshold of $10,000 and the simplified acquisition threshold of $250,000, both defined at FAR 2.101. Above those, agencies issue warrants at levels such as $10 million, $50 million, or unlimited. An unlimited warrant is a serious credential and is normally held by experienced officers at a contracting activity.

Selection is regulated too. FAR 1.603-2 tells agency heads to consider experience, training, education, business acumen, judgment, character, and reputation. On the civilian side, the Office of Federal Procurement Policy restructured the Federal Acquisition Certification in Contracting in 2023 into a single FAC-C (Professional) certification aligned to the Defense Department's contracting certification under DAWIA. Defense agencies run their own certification and continuous learning requirements. In both cases the certification is a prerequisite for the warrant, not the warrant itself.

Warrants end. FAR 1.603-4 provides that an appointment terminates by letter unless the certificate itself contains an automatic termination provision, and appointments routinely lapse when someone changes agencies or lets continuous learning hours slide. If your contract has been quiet for a year and the name on your last modification has moved on, ask who the current contracting officer is before you rely on an old email.

PCO, ACO, TCO, and the contract specialist

On a large contract you may deal with more than one warranted officer, each holding a different slice of the work.

The procuring contracting officer (PCO) runs the acquisition and awards the contract. The administrative contracting officer (ACO) handles contract administration after award. On defense contracts, administration is frequently assigned to the Defense Contract Management Agency under FAR 42.202, and FAR 42.302 lists the administration functions the contract administration office normally performs: reviewing the contractor's purchasing system, negotiating forward pricing rates, administering property and quality assurance, approving progress payments, and dozens more. The termination contracting officer (TCO) settles a contract that is being terminated for convenience or default.

Then there is the contract specialist, usually in the GS-1102 contracting job series. Contract specialists write solicitations, run market research, build the price analysis, draft the modifications, and answer most of the email. Many are working toward a warrant. Until they hold one, they cannot bind the government. This confuses vendors constantly, because the contract specialist is the person they actually talk to. Talking to the specialist is correct and productive. Treating the specialist's opinion as an authorization is not.

CO, COR, and program manager

Here are the three roles that generate most of the confusion, side by side.

Question	Contracting Officer	COR	Program Manager
Source of authority	SF 1402 warrant under FAR 1.603	Written designation under FAR 1.602-2(d)	Agency program authority; none over the contract
Can sign a contract or modification	Yes, within warrant limits	No	No
Can change price, schedule, or scope	Yes, in writing	No	No
Can accept deliverables	Yes	Usually yes, if the designation says so	Only if also appointed as a COR
Can give technical clarification inside the contract	Yes	Yes, within the designated scope	Through the COR, not directly
Typical daily role	Award, modify, resolve disputes, close out	Monitor performance, review invoices, keep the file	Own the mission outcome and the requirement

The COR designation is worth reading closely, because FAR 1.602-2(d) is specific. The contracting officer must designate a COR in writing for contracts other than firm-fixed-price, and for firm-fixed-price contracts as appropriate, unless the contracting officer keeps the duties personally. The COR must be a government employee unless agency regulations say otherwise, must be certified and maintain that certification, and must be designated in a written document that states the scope of authority, the period it covers, and the fact that the authority cannot be redelegated. A copy goes to the contractor and into the contract file.

Then comes the sentence every vendor should be able to recite. 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, and may not in any way direct the contractor or its subcontractors to operate in conflict with the contract terms and conditions.

The program manager sits outside this structure entirely. A federal program manager may control the budget, brief the general or the assistant secretary, and be the reason the contract exists. None of that is contractual authority. A program manager who wants the contract changed asks the contracting officer to change it.

Who may direct work

Work direction breaks cleanly into two categories, and the test is not who is speaking but what is being asked.

Inside the contract. Clarifying an ambiguous requirement, agreeing on a meeting time, choosing between two approaches that both satisfy the statement of work, answering a technical question, reviewing a draft deliverable. A designated COR can do this within the scope of the designation letter. This is the normal daily rhythm of a contract and nobody needs to escalate it.

Outside the contract. Anything that adds work, removes work, moves a delivery date, changes an acceptance criterion, changes the labor mix in a way that affects price, or asks for something the statement of work does not cover. Only the contracting officer can authorize this, and the authorization is a written modification, normally on Standard Form 30.

The gray zone in between is where money gets lost. A COR who says "while you are in there, could you also add the export function" has crossed the line, usually without realizing it. So has a COR who rejects a compliant deliverable because the program office has raised its expectations since award. Both are, in the contractor's view, direction to do work the contract does not require.

Constructive change and why it hurts

The doctrine that covers this is constructive change. It says that when the government causes a contractor to perform work beyond the contract requirements, the law treats the situation as though a change order had been issued, even though no one signed one. The Federal Circuit has stated the test in two parts: the contractor performed work beyond the contract requirements, and that additional work was ordered, expressly or impliedly, by the government or was otherwise caused by government fault. See International Data Products Corp. v. United States, 492 F.3d 1317 (Fed. Cir. 2007).

Constructive change is a remedy, not a plan. Recovering on it means proving after the fact that the extra work happened, that a government official caused it, and what it cost, often through a request for equitable adjustment and sometimes through a claim under the Contract Disputes Act, 41 U.S.C. 7101 to 7109. Claims above $100,000 must be certified under FAR 33.207. The contracting officer must issue a final decision within 60 days for claims of $100,000 or less, and for larger claims must notify the contractor within 60 days of the date a decision will be issued. All of this takes months, consumes people who would rather be building, and often ends in a compromise well below the real cost.

The written route is faster and safer. The Changes clause, FAR 52.243-1 for fixed-price contracts and 52.243-2 for cost-reimbursement, lets the contracting officer direct a change in writing within the general scope of the contract, and gives the contractor a right to an equitable adjustment. The fixed-price version asks the contractor to assert that right within 30 days of receiving the written order, though the contracting officer may act on a proposal submitted any time before final payment. Thirty days from a written order beats two years of arguing about a hallway conversation.

Unauthorized commitments and ratification

If a government employee without authority tells a contractor to do something and the contractor does it, the result is what FAR 1.602-3 calls an unauthorized commitment: an agreement that is not binding solely because the government representative who made it lacked the authority to make it.

The government is not bound by apparent authority. The Supreme Court settled this in Federal Crop Insurance Corp. v. Merrill, 332 U.S. 380 (1947), holding that anyone entering into an arrangement with the government takes the risk of having accurately ascertained that the person purporting to act for the government stays within the bounds of that authority. A confident tone and a government email address are not authority.

There is a cure. Ratification is the act of approving an unauthorized commitment by an official who does have the authority to do so. Under FAR 1.602-3, ratification authority sits above the contracting officer at a level set by agency procedures, and it is limited. The supplies or services must already have been provided to and accepted by the government. The ratifying official must have authority to obligate funds. The resulting contract must be one that would have been proper if an appropriate contracting officer had made it in the first place. A contracting officer must review the transaction and find the price fair and reasonable. Funds must be available, and must have been available at the time the commitment was made.

Ratification is unpleasant for everyone. It generates a memorandum, a legal review, and sometimes a personnel discussion for the employee who gave the direction. Payment is not guaranteed. Contractors who assume ratification will bail them out are underwriting the government's paperwork with their own cash.

How to communicate at each stage

Routing questions correctly is most of the skill. Here is the sequence.

1. Before a solicitation exists. This is the open window. FAR Part 10 requires market research, and FAR 15.201 encourages exchanges with industry before receipt of proposals through sources sought notices, requests for information, industry days, and one-on-one sessions. Talk to program staff, small business specialists, and the contracting shop. General information about agency mission needs and future requirements may be disclosed at any time.
2. After the solicitation is released. The window narrows sharply. FAR 15.201(f) makes the contracting officer the focal point of any exchange with potential offerors once a solicitation is out. Send questions in writing, by the stated deadline, to the address in the solicitation. Answers come back as an amendment to everyone. Calling a friendly engineer at this point puts that engineer, and possibly your bid, at risk.
3. During evaluation. You do not drive this. FAR 15.306 gives the contracting officer three tools: clarifications, communications with offerors before the competitive range is set, and discussions after it is set. If nobody contacts you, that is normal.
4. Right after award or exclusion. Request a debriefing in writing within three days of the notice, per FAR 15.505 and 15.506. On defense contracts, the enhanced debriefing rule at DFARS 215.506-70 lets you submit written follow-up questions within two business days of the debriefing; the agency answers in writing within five business days, and the debriefing is not considered concluded until it does. Those dates matter because the protest clocks under FAR 33.104 and the automatic stay under 31 U.S.C. 3553(d)(4) run off them.
5. During performance. Day-to-day technical traffic goes to the COR. Anything touching cost, schedule, or scope goes to the contracting officer in writing, with the COR copied. Keep a short written record of any direction you receive from anyone. A one-paragraph confirmation email the same day is worth more than a perfect memory two years later.
6. When something goes wrong. Raise it early and in writing to the contracting officer. A request for equitable adjustment filed while the facts are fresh, with the COR's contemporaneous emails attached, resolves far more often than a claim filed at closeout.

Two standing rules apply throughout. The Procurement Integrity Act, 41 U.S.C. 2101 to 2107, implemented at FAR 3.104, restricts disclosure of contractor bid or proposal information and source selection information; do not ask a government employee for something they are not allowed to tell you. And federal employees are covered by the ethics rules at 5 CFR Part 2635, which generally cap gifts at $20 per occasion and $50 per calendar year from one source. Buying the contracting officer lunch is not a relationship-building move. It is a problem for both of you.

What a contracting officer is not

A contracting officer is not the technical decision-maker. They rely on the program office and the COR for that, and FAR 1.602-2(c) requires them to seek specialist advice.

A contracting officer is not your advocate, and not the program office's advocate either. The obligation is to safeguard the government's interests and to treat contractors impartially, fairly, and equitably. Those two duties pull in different directions on a bad day, which is why the job requires judgment rather than a checklist.

A contracting officer is also not a rubber stamp for the program office. Officers routinely refuse to sign things: a sole-source justification that will not survive review, a modification with no funds behind it, a scope change that should be competed. The refusal is the job working correctly.

And a contracting officer is not automatically the same person for the life of the contract. Awards change hands. Administration moves to a different office. Warrants lapse. Confirm the current name before you rely on old direction.

Quick reference

Keep this within reach.

• Ask for the warrant limit. FAR 1.602-1(a) makes it public information. If the officer's ceiling is below your contract value, someone else has to sign.
• Ask for the COR designation letter. FAR 1.602-2(d) requires a copy to be furnished to the contractor, and it states the exact scope of that person's authority.
• Sort every request into inside-scope or outside-scope before you act on it, not after.
• Get outside-scope direction in writing from the contracting officer before you spend an hour on it.
• Confirm verbal direction the same day in a short email to the COR with the contracting officer copied.
• Watch the clocks: three days to request a debriefing, two business days for DoD follow-up questions, 30 days to assert an adjustment under the fixed-price Changes clause, six years to submit a claim under the Contract Disputes Act.
• Verify citations before you quote them. The FAR has been under active rewrite since 2025, and part numbers and clause numbers have moved in places. Check the current text on acquisition.gov rather than an old training deck.

None of this is exotic law. It is a small set of rules about who may say yes, written down in about six pages of FAR Part 1 and enforced by a doctrine that punishes informality. Government staff who learn it stop creating unauthorized commitments. Vendors who learn it stop building things nobody will pay for. Both sides get faster, which is the actual point.