A public agent is a person authorized to act on behalf of a government body. Federally, you cannot rely on apparent authority — the risk of an unverified warrant sits with you. Here is what authority a public agent can hold, where state law differs, and how to verify it before signing.
A public agent is a person authorized to act on behalf of a government body — a federal contracting officer, a state procurement official, a city manager. It is not a special category of agency law; it is an ordinary agency relationship in which the principal is a government, which sharply limits the authority the agent can exercise.
That limit is the whole point of the term. When you contract with a private company, you can usually rely on the person across the table appearing to have authority. When you contract with the federal government, you cannot. If the official who signed exceeded the authority actually delegated to them, the agreement may not bind the government at all — no matter how reasonable your belief was, and no matter that the government received the benefit.
This article explains what authority a public agent can hold, where the federal rule differs from state law, who bears the loss when authority is missing, and the specific steps to verify authority before you sign.
In ordinary agency law, a principal is bound when the agent acts with actual authority, and often also when the agent acts with apparent authority — where a third party reasonably believes the agent has authority and that belief is traceable to the principal's own conduct (Restatement (Third) of Agency § 2.03).
Government contracting removes the second half of that sentence. In Federal Crop Insurance Corp. v. Merrill, 332 U.S. 380 (1947), the Supreme Court held that "anyone entering into an arrangement with the Government takes the risk of having accurately ascertained that he who purports to act for the Government stays within the bounds of his authority" (332 U.S. at 384). The risk of unverified authority sits with the private party, not the public one.
The Federal Acquisition Regulation says the same thing in operational terms: "Contracting officers may bind the Government only to the extent of the authority delegated to them" (FAR 1.602-1(a)). Contracts may be entered into and signed on behalf of the Government only by contracting officers (FAR 1.601(a)) — not by program managers, not by contracting officer's representatives, not by the technical lead who has been directing your work for six months.
Before you sign anything with a government body, work through this table. The right-hand column is the part most contractors skip.
| Doctrine | What it means | Binds a federal agency? | What to verify before signing |
|---|---|---|---|
| Actual authority (express) | The principal has told the agent, in words, that they may act. For a contracting officer, this is the warrant itself. | Yes — within the stated limits, and only within them. | Ask for the individual's warrant level and any dollar or scope limitations stated on their SF 1402 Certificate of Appointment (FAR 1.603-3(a)). |
| Actual authority (implied) | Acts "necessary or incidental" to achieving the objectives the principal has designated (Restatement (Third) of Agency § 2.02(1)). | Narrowly — statutory and regulatory limits cut it back further than in private agency. | Confirm the act is genuinely incidental to a delegated objective, not an expansion of it. If it changes price, scope or schedule, treat it as requiring express authority. |
| Apparent authority | Third party reasonably believes the agent has authority, based on the principal's conduct (Restatement (Third) of Agency § 2.03). | No. There is no apparent authority against the federal government (Merrill, 332 U.S. at 384). | Nothing to verify — you cannot rely on it. Job titles, org charts, email signatures and long-standing practice are not authority. |
| Ratification | An authorized official later affirms an unauthorized act, giving it effect as if authorized (Restatement (Third) of Agency § 4.01(1)). | Yes, but only formally. FAR 1.602-3 sets seven conditions, including that funds were available when the commitment was made and that legal counsel concurs. | Get the ratification in writing from an official with ratification authority — it may not be delegated below the chief of the contracting office (FAR 1.602-3(b)). |
This is the single most expensive misunderstanding in government contracting. The rationale is structural rather than punitive: as the Federal Circuit put it in Monarch Assurance PLC v. United States, 244 F.3d 1356, 1360 (Fed. Cir. 2001), "if any of three million government employees could, of their own volition, enter into contracts obligating the Government, then federal expenditures would be wholly uncontrollable."
The Government Accountability Office states the consequence plainly: where "a government agent purports to commit the government to a transaction he has no authority to enter, the government is not legally obligated to honor the transaction" (Architect of the Capitol—Contract Ratification, B-306353, Oct. 26, 2005). The same decision confirms the escape hatch: an authorized official with knowledge of the facts may ratify the unauthorized act afterward — which is why FAR 1.602-3 exists, and why an unauthorized commitment is a problem to be fixed rather than a contract to be enforced.
The related doctrine of equitable estoppel fares no better federally. In Office of Personnel Management v. Richmond, 496 U.S. 414 (1990), the Court noted it "has never upheld an assertion of estoppel against the Government by a claimant seeking public funds," and held that erroneous advice from a government employee cannot estop the government from denying a payment not otherwise authorized by law.
It is common to see the federal rule stated as though it were universal American law. It is not. State law varies, and the variation runs mostly through equitable estoppel rather than apparent authority.
Most states, like the federal government, decline to let apparent authority alone bind a public entity. Illinois is explicit about the split: its courts "have long held that equitable estoppel may apply against municipalities, in extraordinary and compelling circumstances … but have never held that apparent authority may apply against municipalities" (Patrick Engineering, Inc. v. City of Naperville, 2012 IL 113148, ¶ 35).
But several states do allow estoppel against a government body in exceptional cases:
The practical takeaway: whether a state or municipal official can bind their entity is a question of that state's law, and the answer is often narrower than a commercial counterparty would expect. Do not assume the federal analysis transfers, and do not assume a state exception rescues a deal that a federal analysis would void.
Two rules point in opposite directions here, and the distinction is whether the agent stayed inside their authority.
An agent acting within authority is generally not personally liable. That has been the rule since Hodgson v. Dexter, 5 U.S. (1 Cranch) 345 (1803), where Chief Justice Marshall held that where a public agent acts in the line of duty and by legal authority, contracts made on the government's account are public rather than personal — they bind the government, not the officer.
An agent acting outside authority may be exposed. Under Restatement (Third) of Agency § 6.10, a person who purports to contract on another's behalf without the power to bind them "gives an implied warranty of authority to the third party and is subject to liability … for loss caused by breach of that warranty" — unless the principal ratifies, the agent disclaimed the warranty, or the third party knew authority was absent.
How § 6.10 interacts with federal officials is complicated by sovereign immunity and the Westfall Act, so treat it as a risk signal rather than a reliable cause of action. Notably, the government itself takes the exposure seriously: federal guidance requires that a contracting officer's representative be told in their designation that they may be personally liable for unauthorized acts.
The verification burden is yours. Four steps, in order:
Two cautions on verification methods that get recommended and shouldn't be. There is no FAR provision entitling you to a copy of the SF 1402; agencies often provide one, but that is practice and FOIA, not a right. And FPDS/SAM.gov is not a warrant-verification tool — it publishes contract action data, not contracting officer authority levels.
The provisions cited above are the currently codified FAR. Under the Revolutionary FAR Overhaul, the model deviation text for Part 1 renumbers them: FAR 1.602-1 becomes 1.402-1, FAR 1.603-3 becomes 1.403-2, and ratification moves from 1.602-3 to 1.405. The substance is largely preserved, with one change worth knowing — the "readily available to the public" sentence in 1.602-1(a) does not appear in the deviation text for 1.402-1. Many agencies have adopted the overhaul by class deviation, so confirm which text your agency is operating under before relying on a specific citation.
Most authority failures are not exotic legal problems. They are document problems: a scope change agreed in an email thread, a signature block naming someone who was never warranted, a term amended in one document and not in the four that reference it.
That is the class of failure structured documents are built to prevent. When the signatory, warrant level and authority ceiling are defined variables rather than retyped text, they stay consistent across every document that references them. When changes route through a defined approval workflow, no one commits the organization by replying to an email. And when every revision is captured in version control, you can show precisely who agreed to what, and when — which is the evidence any ratification request will turn on.
If you contract with public bodies regularly, our contract template library is a reasonable starting point for building authority verification into the drafting process rather than bolting it on at signature.
A public agent is a person authorized to act on behalf of a government body — for example a federal contracting officer, a state procurement official or a city manager. It is not a special category of agency law. It describes an ordinary agency relationship in which the principal is a government, which sharply limits the authority the agent can exercise.
Only the authority actually delegated to them. For federal contracting officers, that authority is set out in an SF 1402 Certificate of Appointment, which states any limits on scope (FAR 1.603-3(a)), and "contracting officers may bind the Government only to the extent of the authority delegated to them" (FAR 1.602-1(a)). Implied authority extends only to acts necessary or incidental to a delegated objective.
Not federally. Under Federal Crop Insurance Corp. v. Merrill, 332 U.S. 380, 384 (1947), a party dealing with the government takes the risk of confirming that the official is acting within their authority. State law varies — some states permit equitable estoppel against a public entity in exceptional circumstances, but apparent authority as such is generally unavailable there too.
Generally not the government, and generally not the agent if they acted within authority (Hodgson v. Dexter, 5 U.S. (1 Cranch) 345 (1803)). An agent who purports to contract without the power to do so breaches an implied warranty of authority and may be liable for the resulting loss (Restatement (Third) of Agency § 6.10), though sovereign immunity complicates this for federal officials. In practice the private party bears the loss unless the commitment is ratified.
Ask for the individual's warrant level and any stated limits — FAR 1.602-1(a) requires that information on those limits be readily available to the public. Ask the contracting office to confirm the appointment is current, since appointing officials maintain files of unterminated appointments under FAR 1.603-3(a). Take any direction with cost, scope or schedule consequences from the warranted contracting officer in writing. Note that there is no public database of contracting officer warrants, and FPDS/SAM.gov does not serve this purpose.
It may be an "unauthorized commitment" — an agreement not binding solely because the government representative lacked authority (FAR 1.602-3(a)). It can be ratified by an official with ratification authority, but only if the government received a benefit, the price is fair and reasonable, funds were available at the time the commitment was made, and legal counsel concurs. Ratification authority may not be delegated below the chief of the contracting office.
Public agents hold only the authority actually delegated to them, and — federally — you cannot rely on how much authority they appear to have. Verify the warrant, confirm it is current, take material direction in writing from the person who holds it, and treat state and local counterparties as a separate legal question rather than an extension of the federal rule.
Last updated: 9 August 2026.
This article is general information about US agency and government contracting law. It is not legal advice, and the rules vary by jurisdiction and by agency. Consult qualified counsel before relying on any authority analysis for a specific transaction.