Two officials, two sources of authority
FAR 1.601(a) contains one of the shortest and most consequential sentences in federal acquisition: "Contracts may be entered into and signed on behalf of the Government only by contracting officers." Everything about a procurement contract descends from it. The person across the table holds a warrant with a number and a ceiling, and the document they hand you is assembled from clauses a regulation told them to include. An other transaction is not a contract as the FAR defines one, so that sentence does not reach it. Authority to sign one comes from a statute, and the person exercising it is usually called an agreements officer.
The two roles look similar from the outside. Both officials negotiate, both sign, both control money, and they often sit in the same building working the same program. Companies treat them as interchangeable and are surprised later.
The difference is not seniority or skill. One operates inside a body of regulation that supplies most of the answers; the other operates inside a statute that supplies almost none. That drives the intellectual property terms, the payment structure, the audit exposure, the dispute path, and what happens if the relationship goes badly.
What a contracting officer is, exactly
A contracting officer's authority is documented, bounded, and checkable. FAR 1.602-1 gives contracting officers authority to enter into, administer, or terminate contracts and make related determinations and findings, and then immediately limits it: they may bind the government only to the extent of the authority delegated to them, and they are to receive from the appointing authority clear instructions in writing regarding the limits of that authority.
That instruction takes a specific physical form. Under FAR 1.603-3, contracting officers are appointed in writing on an SF 1402, Certificate of Appointment, which states any limitations on the scope of authority. This is the warrant. It has a dollar ceiling and can be restricted by contract type, program, or location. A company that asks to see it is establishing whether the person negotiating can sign what they are describing.
The qualification floor is statutory, not just regulatory. Under 10 U.S.C. § 1724, a member of the DoD acquisition workforce with authority to award or administer contracts above the simplified acquisition threshold must have completed the contracting courses required at that grade, have at least two years of experience in a contracting position, and hold a baccalaureate degree from an accredited institution, plus any additional standards the department sets by contract value and complexity. Carve-outs exist for longtime incumbents and the contingency contracting force. The floor itself is written into law.
FAR 1.602-2 then loads the role with responsibility. The contracting officer must ensure performance of all necessary actions for effective contracting, verify that all requirements of law, executive orders, regulations, and other applicable procedures have been met, confirm sufficient funds are available for obligation, and see that contractors receive impartial, fair, and equitable treatment. An officer who cannot answer "is the money there" cannot sign.
There is a hard edge. If someone without a warrant directs a company to start work, that is an unauthorized commitment. FAR 1.602-3 allows the head of the contracting activity to ratify one, but only where the supplies or services were provided to and accepted by the government and the price is determined fair and reasonable. Ratification is a favor, not a right, and the company carries the risk in the meantime.
What an agreements officer is, exactly
Now the contrast. The title "agreements officer" does not appear in the FAR, because the FAR does not govern the instrument. DoD's prototype authority at 10 U.S.C. § 4022, recodified from the old § 2371b when the FY2021 NDAA reorganized Title 10, names the officials who may exercise it — the Director of DARPA, the Director of the Defense Innovation Unit, the secretary of a military department, and other designated officials — and the authority is then delegated downward inside each component. The person holding that delegation is the agreements officer. A parallel authority for research sits at 10 U.S.C. § 4021, recodified from the old § 2371, reaching "transactions (other than contracts, cooperative agreements, and grants)."
Congressional Research Service analysis makes the structural point plainly: agreements officers are not required to be contracting officers, and entry requirements for the role are lower than those for a warranted contracting officer. Components commonly draw them from the warranted contracting workforce anyway and add other-transaction training on top. That is component policy, not a statutory floor, and it is not uniform. Nothing government-wide prescribes an SF 1402 equivalent.
The consequence is direct. With a contracting officer you ask to see a standard form and read the ceiling off it. With an agreements officer you are asking about a delegation memorandum whose format and conditions are set inside that component. Ask early, in writing, before spending a month negotiating with someone whose signature authority stops below your price.
Share of each term set the parties write themselves, prototype OT
Read each bar as how much of that term set the parties draft themselves under a prototype other transaction. Under a FAR contract nearly all of it arrives pre-answered by a prescribed clause. The bottom row is the statutory floor described below, and it does not move. Editorial weighting, illustrative rather than measured.
The clause problem, which is the whole difference
A FAR contract arrives pre-loaded. The contracting officer selects clauses the regulation prescribes for that contract type, dollar value, and subject matter. If the officer omits a mandatory clause, the omission is often repaired by operation of law — the Christian doctrine holds that certain mandatory clauses are read into a government contract even when left out. A company negotiating a FAR contract is largely negotiating around text it did not write and cannot delete.
An other transaction has no such backstop. No regulation prescribes the clause set, so there is nothing to read in. What the agreements officer and the company put on the page is the entire agreement. Anything neither side wrote is absent: no default license grant, no default termination formula, no default disputes ladder, no default definition of acceptance.
That reframes where risk lives. Under a contracting officer, the risk sits in clauses that already exist and that a company may not have read closely enough. Under an agreements officer, it sits in the space nobody filled — and blank space does not default to neutrality. It defaults to the government's opening template, because that is the document on the table.
So a firm that treats a FAR award as a compliance exercise should treat a prototype agreement as a drafting exercise. Arrive with the background IP schedule built, the milestones you can hit, and the acceptance criteria you will be measured against. An agreements officer has wide latitude to accept sensible terms and little reason to invent them for you.
What does not change when the signature block changes
Flexibility in the agreement is not flexibility in the law
10 U.S.C. § 4022(h) applies procurement ethics requirements to prototype other transactions. Section 4022(c)(1) requires an agreement providing for payments over $5,000,000 in total to include a clause giving the Comptroller General discretion to examine the records of any party or participant, subject to the exceptions that follow it. Appropriations still have a purpose, a time, and an amount, and the Anti-Deficiency Act does not care what the instrument is called. Congressional Research Service analysis notes that non-procurement statutes such as the Trade Secrets Act and the Economic Espionage Act keep applying. Export control, classification, and controlled-unclassified-information handling follow the data, not the signature block.
Side by side on the axes that decide
| Axis | Contracting officer | Agreements officer |
|---|---|---|
| Instrument signed | Procurement contract, order, or modification under the FAR | Other transaction: a prototype agreement under 10 U.S.C. § 4022 or a research transaction under § 4021 |
| Source of authority | FAR 1.601 and 1.602-1, plus the agency's delegation chain | The statute itself, delegated downward inside the component |
| Appointment record | SF 1402 Certificate of Appointment stating the limits of authority (FAR 1.603-3) | A component delegation; no government-wide standard form prescribed |
| Qualification floor | Statutory under 10 U.S.C. § 1724 above the simplified acquisition threshold | Set by agency policy; a contracting warrant is common but not required |
| Where the terms come from | Prescribed clauses, with mandatory ones read in even if omitted | Drafted by the parties; anything unwritten is absent |
| Disputes | Final decision, then the board or the Court of Federal Claims under the Contract Disputes Act | Whatever the agreement's dispute article provides, and nothing more |
| Protest exposure | GAO under the bid protest statute, plus the Court of Federal Claims | GAO generally declines the award itself; narrow avenues remain |
Disputes: the door that is not there
This is the most expensive surprise in the comparison, and entirely predictable from the statutes. The Contract Disputes Act at 41 U.S.C. § 7102(a) applies to contracts made by an executive agency for the procurement of property other than real property in being, the procurement of services, the procurement of construction, alteration, repair or maintenance of real property, and the disposal of personal property. An other transaction is not a contract of those kinds, so the Act's machinery does not attach. Congressional Research Service analysis lists the Act among the procurement statutes from which other transactions are generally exempt.
Follow that through. Under 41 U.S.C. § 7105, the Armed Services Board of Contract Appeals hears appeals from decisions of contracting officers of the covered departments relative to a contract made by that department. No final decision means no appeal to the board: no certified claim, no clock, no interest running from receipt, no body of decisions telling you how this argument usually ends.
What replaces it is the agreement's own dispute article, which deserves closer reading than most of the technical scope. Patterns range from a defined escalation to a named senior official, to non-binding alternative dispute resolution, to a paragraph saying the parties will resolve disagreements in good faith and stopping there. All three are common. Only one tells you what happens on the day good faith fails.
Protests: who you can complain to, and about what
GAO's bid protest jurisdiction is defined by statute. Under 31 U.S.C. § 3551, a protest is a written objection by an interested party to, among other things, a solicitation or other request by a federal agency for offers for a contract for the procurement of property or services. An other transaction is not that contract, which is why GAO generally declines to review the award itself. GAO has taken up the narrower question of whether an agency improperly used other transaction authority in place of a procurement contract; MorphoTrust USA, LLC, B-412711 (May 16, 2016) is the usual citation.
The Court of Federal Claims is the other door, and its wording is wider. Under 28 U.S.C. § 1491(b)(1), the court has jurisdiction over an action by an interested party objecting to a solicitation, to a proposed award or award of a contract, or to "any alleged violation of statute or regulation in connection with a procurement or a proposed procurement." That last phrase is the hook. In Oracle America, Inc. v. United States, 975 F.3d 1279 (Fed. Cir. 2020), the Federal Circuit addressed a challenge connected to a follow-on production award under the prototype authority. The route exists. It is narrow, slow, and expensive.
Read both directions. An award signed by an agreements officer is unusually durable, because the cheap challenge is mostly unavailable to competitors. An award you lose is durable the same way, and debriefs are a courtesy rather than an entitlement.
Who signs what, and in what order
Signature chain on a consortium prototype award
Step six is where companies discover the two roles are not a permanent assignment. Section 4022(f) permits a follow-on production contract or transaction without competitive procedures when competitive procedures were used to select the prototype participants and those participants successfully completed the project. Elect a production contract and the FAR returns in full, with a contracting officer taking the file. Terms negotiated freely in the prototype then meet a clause set somebody else wrote.
Thresholds that pull other people into the room
An agreements officer is not always the last signature. Under 10 U.S.C. § 4022(a)(2), a prototype project expected to cost more than $100 million but not more than $500 million requires a written determination by the head of the contracting activity, or by the agency director in the case of DARPA, the Defense Innovation Unit, or the Missile Defense Agency. Above $500 million the determination rises to the senior procurement executive or the agency director, with congressional notification thirty days in advance. A follow-on production award above $100 million carries its own determination and notification.
One threshold matters at ordinary deal sizes: the $5,000,000 Comptroller General records clause in § 4022(c)(1). That is where an agreement acquires an audit-access obligation by statute rather than by negotiation, far below the levels that trigger senior review.
Timeline claims deserve the same care. The Defense Innovation Unit states publicly that it can award prototype agreements in as few as 60 to 90 days. DoD's own guidance has cautioned that the award process is not always faster than traditional procurement and can take as long or longer. Both are true; the variable is not the instrument but whether the requirement, the money, and the sponsor were settled before the clock started.
Outside DoD, the same title covers different statutes
Other transaction authority is not one authority. It is a family of separate grants with different scopes and different expiration dates, and the person signing under each may carry the same title while working under materially different rules.
- DoD prototypes — 10 U.S.C. § 4022 — The prototype authority, with the four alternative use conditions in subsection (d), the Comptroller General clause in (c), the follow-on production pathway in (f), and procurement ethics applied in (h).
- DoD research — 10 U.S.C. § 4021 — Transactions other than contracts, cooperative agreements, and grants, for basic, applied, and advanced research, with its own provisions on advance payments, recovery of funds, education and training, and protection of certain information from disclosure.
- NASA — 51 U.S.C. § 20113(e) — Authority to enter into and perform contracts, leases, cooperative agreements, "or other transactions as may be necessary in the conduct of its work." The broadest wording in the family, and the basis for the agreements NASA writes outside the FAR.
- DHS — 6 U.S.C. § 391 — Authority comparable to 10 U.S.C. § 4021 for research and development, plus prototype projects under § 4022. The section carries an express expiration date, conditions the authority on issued policy guidance and trained personnel, and requires annual reporting to Congress. Confirm the current expiration before planning around it.
- DOE — 42 U.S.C. § 7256(g) — Research, development, and demonstration transactions, delegable only to an officer of the department appointed by the President with Senate advice and consent, terminating September 30, 2030 under the current text.
The definition that opens the DoD door is separate again. A nontraditional defense contractor, under 10 U.S.C. § 3014 as recodified from the old § 2302(9), is an entity not currently performing and not having performed for at least the one-year period preceding the solicitation any DoD contract or subcontract subject to full coverage under the Cost Accounting Standards. The test is CAS coverage, not size, not revenue, and not whether the firm has held defense work before.
How to tell which official you are dealing with
Five questions, asked early, settle almost everything. None are adversarial, and a competent official on either side of the line answers all five without hesitation.
What instrument is this? Ask whether the award will be a procurement contract or an other transaction, and under which section. "Prototype agreement under 10 U.S.C. § 4022" and "firm-fixed-price contract under FAR Part 12" are different answers with different consequences, and people use the word "contract" loosely.
Who signs, and what is their ceiling? For a contracting officer, ask for the warrant limit. For an agreements officer, ask what the delegation permits and whether this award needs a determination above them.
Where does the term sheet come from? "The standard clauses" means you are in a FAR world and your work is to price what the clauses already say. "Our model agreement" means you are drafting, and you should read the model before you write a price.
What happens when we disagree? Under a contract this has a standard answer. Under an agreement, read the dispute article out loud in the negotiation. If it describes no procedure, that is the finding.
Is a follow-on contemplated, and in what instrument? For a prototype agreement this decides whether the work has a future, and it tells you whether a contracting officer eventually owns the file.
What changes in your posture
Negotiating with a contracting officer is a mapped exercise. The range is narrow, the vocabulary is shared, and most of the value comes from knowing the clause set well enough to see which risks are already allocated to you and pricing them honestly. The officer's obligations under FAR 1.602-2 work in your favor: they must confirm the funds and confirm compliance, so the regulation forces much of the ambiguity out before signature.
Negotiating with an agreements officer is a drafting exercise, and the party that arrives with better paper keeps more of what matters. That is the design of the instrument. The government chose an authority that lets both sides write the deal, and showing up without a draft is not neutrality. It is a concession.
One more effect is worth naming for 2026. The FAR Council is running a rewrite of the regulation under an executive order titled "Restoring Common Sense to Federal Procurement," publishing revised parts along with model deviation text that agencies adopt ahead of final rules. For anyone comparing pathways, the FAR-side answer to "what does the standard clause say" is less settled than it has been in years, and the version an agency is operating under is worth confirming rather than assuming. The other-transaction side is untouched by that churn, for the plain reason that it was never running on the FAR.
Common objections, answered plainly
Isn't an agreements officer just a contracting officer with a different hat?
Often the same person, frequently the same training. The authority is what differs. Signing a FAR contract, that person carries an SF 1402 with a stated ceiling and a regulation that supplies the clause set. Signing a prototype agreement, they carry a component delegation and a document with no prescribed clauses. Same individual, different powers, different remedies for you.
If the FAR does not apply, can the agreements officer agree to anything?
No. Fiscal law binds the transaction regardless of instrument, statute applies procurement ethics requirements to prototype other transactions, agreements above $5,000,000 in payments carry a Comptroller General records clause, and export control and classification follow the work. The officer has latitude over commercial terms, not over law.
Does a consortium manager have signature authority over the government?
No. The consortium management firm holds the base agreement and runs the competition mechanics, but the government's obligation is created by the government's own signature. A manager's guidance on what the government will accept is useful and is not binding on the agreements officer.
Is one pathway better for a company that has never sold to the government?
Neither is a beginner's pathway, and the choice usually is not the company's to make. What a first-time seller controls is preparation: knowing which instrument is on the table, having a background IP schedule ready, and having acceptance criteria worth being measured against in writing.
Bottom line
Ask which official is signing before anything else about terms. A contracting officer brings a regulation that has already answered most of the questions, a warrant you can inspect, and a dispute system with precedent behind it. An agreements officer brings latitude, speed where the requirement and the money are ready, and a document whose gaps are permanent because nothing exists to fill them.
Neither is better in the abstract. The better deal is the one where you knew which set of rules you were in before you priced the work, drafted the terms you needed instead of assuming they were implied, and confirmed that the person across the table could sign what they were describing.
Frequently asked questions
Not as a matter of federal statute. Congressional Research Service analysis states that agreements officers are not required to be contracting officers and that entry requirements for the role are lower. Many components appoint them from the warranted contracting workforce and add other-transaction training, but that is agency policy and it varies. Ask what the component's delegation requires.
For a procurement contract, ask for the SF 1402 Certificate of Appointment; FAR 1.603-3 requires it to be in writing and to state any limits on the scope of authority. For an other transaction there is no equivalent standard form, so ask for the component's delegation and its ceiling, and whether an award of this size needs a determination at a higher level.
Generally no. The Act at 41 U.S.C. § 7102(a) applies to contracts for the procurement of property, services, construction, or the disposal of personal property, and an other transaction is not one of those. Without a contracting officer's final decision there is nothing to appeal to a board of contract appeals under 41 U.S.C. § 7105. The agreement's own dispute article is the whole of the procedure.
Under 10 U.S.C. § 4022(a)(2), a prototype project expected to exceed $100 million but not $500 million requires a written determination by the head of the contracting activity, or the agency director for DARPA, the Defense Innovation Unit, or the Missile Defense Agency. Above $500 million, the senior procurement executive or agency director must make the determination and Congress is notified thirty days in advance.
It depends on the instrument chosen. Section 4022(f) permits either a follow-on production contract or a follow-on transaction, without further competition, when competitive procedures were used to select the prototype participants and the prototype was successfully completed. If the government picks a contract, the FAR applies and a contracting officer takes the file. Settle that while the prototype terms are still open.