Introduction
The implied duty of good faith and fair dealing is part of every government contract, yet it is frequently pleaded without first asking the question that matters most: what gap is the doctrine supposed to fill?
Contractors often assert breach of the implied duty as a separate count whenever government conduct appears unreasonable. Sometimes the count merely restates an express breach theory. In other cases, it seeks to impose an obligation that cannot be traced to the contract at all. Either approach invites a dismissal fight and can obscure the conduct that actually caused the injury.
A better method begins with the facts. Identify what the government did or failed to do. Determine whether an express contract provision allocates the relevant obligation or risk. Then ask whether a more specific contract doctrine already reaches the conduct. Only if a meaningful gap remains should counsel turn to the implied duty.
The Threshold Inquiry: Is There Actually a Gap?
Before drafting an implied-duty count, counsel should answer two related questions.
1. Does an Express Term Allocate the Obligation or Risk?
Many disputes already fall within an express contractual framework. The contract may address government-furnished property, access to the site, submittal review, inspections, schedule relief, changes, suspensions, or equitable adjustments. If the contract states what the government must do, identifies the contingency at issue, and supplies a remedy, the analysis should begin there.
The existence of an express clause does not automatically foreclose every implied-duty theory touching the same events. The more precise question is whether the implied theory would impose an obligation inconsistent with the clause, enlarge a carefully allocated risk, or merely duplicate the duty and injury already asserted under the contract.
2. Does a More Specific Doctrine Supply the Natural Theory?
Even when no single clause resolves the dispute, a familiar contract doctrine may provide the better fit. Depending on the facts, the challenged conduct may support a claim based on:
- differing site conditions;
- constructive change;
- superior knowledge;
- defective specifications;
- constructive suspension; or
- an express equitable-adjustment provision.
When a more specific doctrine directly addresses the challenged conduct, that theory should ordinarily lead the analysis. That does not make alternative pleading improper. It does mean counsel should be able to explain what distinct work the implied-duty count performs.
The threshold inquiry therefore is not simply whether the same facts could be placed under more than one label. It is whether the implied-duty theory protects a contract-grounded expectation that the express terms and more specific doctrines do not already address.
A Three-Part Framework for Pleading the Claim
Where a genuine gap remains, a useful implied-duty claim can usually be reduced to three components: the challenged conduct, the contract-grounded expectation, and the resulting injury.
1. Identify the Challenged Conduct
The analysis begins with conduct, not labels. “The Government breached the duty of good faith and fair dealing” is a legal conclusion. It tells neither the contracting officer nor the court what happened.
By contrast, an allegation that “the contracting officer withheld approval of a conforming submittal for forty-five days after receiving notice that the submittal controlled the critical path” identifies the actor, the decision, the timing, the information available, and the effect on performance.
That factual discipline serves two purposes. It permits a meaningful comparison between the conduct and the contract, and it exposes whether the proposed theory is truly independent or merely a repackaged express claim.
2. Identify the Contract-Grounded Expectation
The implied duty protects expectations created by the bargain itself. It does not protect a freestanding expectation that the government will act fairly, efficiently, or helpfully.
The question is whether the contract created a reasonable expectation that the government would refrain from conduct that deprived the contractor of the value it reasonably expected from the exchange. The contract’s text, structure, allocation of risk, incorporated documents, and objective context should explain why the expectation arose.
Depending on the bargain, protected expectations may include that the Government:
- will not unreasonably obstruct an approved means of performance;
- will provide property, access, information, or decisions reasonably necessary to proceed;
- will not recapture a specifically bargained-for contractual benefit; or
- will exercise an open-ended contractual discretion consistently with the contract’s purpose.
The formulation matters. “The Government would not obstruct the approved means of performance” is testable against the contract and the record. “The Government would treat the contractor fairly” is not.
3. Connect the Conduct to the Injury
The final step is showing how the challenged conduct interfered with the protected expectation and caused a cognizable injury. Courts frequently discuss that interference through the recurring concepts of hindrance and non-cooperation.
Hindrance generally involves affirmative interference with performance. Non-cooperation generally involves a failure to provide something reasonably necessary for performance. Those labels are useful because they direct attention to what occurred, whether the government’s administration was reasonable in light of the bargain, and how performance was affected.
But hindrance and non-cooperation are not separate sources of the contractual interest being protected. They are recurring ways government conduct may defeat a reasonable expectation created by the contract. The ultimate question remains whether the challenged conduct deprived the contractor of part of the value of its bargain.
Centex: The Bargain, Not the Label, Is the Anchor
Centex Corp. v. United States remains the conceptual anchor because it identifies the protected interest and demonstrates that implied-duty claims are not confined to the familiar construction patterns of delayed approvals, withheld access, or interference in the field.
The contracts in Centex provided valuable tax benefits. Later legislation eliminated those benefits. The Federal Circuit concluded that the government could breach the implied covenant by using its sovereign power to take back a benefit that formed part of the contractual exchange.
The case is important for two reasons. First, it focuses the analysis on the reasonable expectations arising from the bargain. Second, it shows why “hindrance” and “non-cooperation” should not become rigid pleading categories. The relevant conduct in Centex did not resemble ordinary contract administration, but it allegedly destroyed a benefit the contracts had created.
The lesson is not that every disappointed expectation becomes actionable. The expectation must still be grounded in the contract. Centex instead demonstrates that once the bargain creates the expectation, the implied duty may protect it from conduct that the written terms did not expressly anticipate.
The Two Boundary Problems
The doctrine’s limits become clearer when two recurring failure modes are placed side by side.
The Untethered Claim: Dobyns
Dobyns v. United States illustrates the danger of proposing an implied obligation that is not sufficiently tied to the agreement. The doctrine cannot be used to add a general duty divorced from the contractual exchange or to convert objectionable conduct into a contract breach without identifying the promise or expectation the conduct impaired.
The practical question is not merely whether the government’s conduct appears unreasonable. It is whether the asserted obligation can be derived from the contract’s terms, purpose, structure, or allocated risks. Without that connection, the theory is untethered from the bargain.
The Redundant Claim: BGT and The Portland Mint
BGT Holdings LLC v. United States presents the opposite problem. The challenged withholding of government-furnished equipment was addressed by express provisions governing the Government’s rights and the contractor’s adjustment remedy. The implied-duty theory did not fill a gap; it attempted to perform work the contract already performed.
The Portland Mint v. United States reinforces the vulnerability of an implied-covenant count that rests on the same obligation and injury as an express breach claim. Overlapping facts do not necessarily make claims identical, but an implied-duty count adds little when it simply renames the alleged express breach.
These decisions create a useful prefiling test:
- Dobyns asks whether the asserted obligation is tied closely enough to the bargain.
- BGT asks whether the bargain already addresses the conduct so directly that the implied theory is redundant.
A viable claim must occupy the space between those boundaries. It must be grounded in the contract without merely duplicating an express obligation and remedy.
Metcalf: Objective Contract Administration, Not Subjective Bad Faith
Metcalf Construction Co. v. United States is central because it corrected an unduly narrow view of the implied duty. The Federal Circuit rejected the proposition that breach requires conduct specifically designed to reappropriate benefits contemplated by particular contract provisions.
The ordinary implied-duty inquiry is objective. It asks whether the challenged conduct was inconsistent with the contract’s purpose and deprived the contractor of the contemplated value of the bargain. Proof of malice, dishonesty, animus, or a specific intent to injure is not required.
That distinction has practical consequences for both pleading and proof. A claim framed around “bad faith” may send the parties into an unnecessary dispute over motive and may invoke the demanding standards associated with allegations of fraud-like governmental misconduct. An ordinary implied-duty claim should instead identify the contractual expectation, the government’s conduct, the information available when it acted, and the resulting effect.
Tecom, Inc. v. United States makes the same point from another direction. The presumption that government officials act in good faith addresses allegations approaching fraud or quasi-criminal wrongdoing. It does not govern an ordinary contract claim alleging that objective conduct violated the implied covenant.
The strongest record usually concerns what the government knew, what it decided, when it acted or failed to act, what notice it received, and how the decision affected performance. Internal motive may be difficult to discover and often is unnecessary.
Agility: Express and Implied Theories May Require Separate Analysis
Agility Public Warehousing Co. KSCP v. Mattis adds an important qualification. Failure of an express breach theory does not automatically dispose of a properly preserved implied-duty claim.
After construing the written terms, a tribunal may still need to determine whether the government’s conduct defeated a contract-grounded expectation that the agreement did not state expressly. That is the legitimate role of a gap-filling doctrine.
Agility does not license counsel to append an implied-duty count to every express claim. The implied theory must identify a distinct obligation or expectation and must remain consistent with the written contract. But where the express terms leave a genuine gap, the implied-duty theory requires its own analysis rather than automatic rejection merely because an express theory fails.
A Contractor-Focused Example
Assume a construction contract requires the contractor to submit a means-and-methods plan for review but does not specify a review period. The contractor submits a conforming plan, identifies that approval controls mobilization of specialized equipment, and repeatedly advises that continued inaction is delaying the critical path. The Government neither rejects the plan nor requests additional information. It simply leaves the submission undecided for an extended period.
The initial questions should be concrete. Did an express clause establish a review deadline or remedy? Did the Government suspend the work? Did it direct a change? Does another clause allocate the risk of review time? If an express mechanism governs the delay, that mechanism should lead.
If the contract contains no answer, an implied-duty theory may fill the gap. The challenged conduct is the unexplained failure to act on a conforming submission after notice of the effect. The contract-grounded expectation is not a general expectation of promptness. It is the more specific expectation that the Government will exercise its required review function within a reasonable time so that the approved work can proceed. The injury is the resulting delay and associated cost.
The hypothetical also shows why presentation matters. A count alleging only that the Government acted unfairly would be weak. A count identifying the submission, the Government’s review responsibility, the notices, the period of inaction, and the critical-path effect gives the contracting officer and the court a claim they can evaluate.
Presentment: The Theory Must Reach the Contracting Officer
Even a well-founded implied-duty theory can fail before the merits if it was not presented to the contracting officer. The Contract Disputes Act does not permit a contractor to present one dispute to the contracting officer and litigate a materially different dispute based on different operative facts.
The claim need not use perfect legal terminology. It should, however, identify the governmental act or omission, the contract-grounded expectation allegedly injured, the effect on performance or another contractual benefit, and the relief sought. If one count will later encompass several distinct acts of hindrance or non-cooperation, the submission should disclose each material grievance rather than rely on a general demand for compensation.
This is particularly important because “good faith and fair dealing” can become an umbrella phrase covering a number of separate factual theories. A claim based on delayed approvals may not preserve a later theory based on withheld information merely because both are described as breaches of the implied duty. Presentment turns on the operative facts, not the label selected in the complaint.
Counsel should therefore compare the proposed litigation count directly against the certified claim or other written submission. Every material act, expectation, impact, and category of relief in the count should be traceable to what the contracting officer received.
Building the Proof Around the Theory
The evidentiary record should track the three-part framework. Begin with the documents and objective circumstances creating the expectation. Then establish the challenged conduct and its consequences.
The most useful records often include:
- contract provisions, specifications, schedules, and incorporated documents;
- submittal and RFI logs;
- decision dates and approval histories;
- contemporaneous notices and meeting minutes;
- schedule updates and critical-path analyses;
- government-furnished information and property records;
- inspection and quality-control records; and
- cost records connecting the challenged conduct to measurable impact.
The proof should also address reasonableness. If the Government delayed a decision, what information did it possess? Did it identify a contractual or technical basis for withholding action? What notices did it receive concerning the effect of delay? Did the contractor provide the information needed for a decision? Those facts are usually more persuasive than speculation about motive.
Many unsuccessful implied-duty claims are not doctrinal failures. They are proof failures. The theory may be sound, but conclusory allegations, unsupported recollections, and generalized complaints about unfair administration do not establish interference with a contract-grounded expectation.
Conclusion
The threshold question should remain simple: what contractual gap is the implied duty being asked to fill? If an express provision or established doctrine already governs the obligation, risk, and remedy, the implied-duty count may be unnecessary or redundant. If the asserted obligation cannot be tied to the bargain, the theory is untethered.
Between those boundaries lies the doctrine’s proper role. A strong implied-duty claim identifies specific conduct, a reasonable expectation grounded in the contract, the manner in which the conduct defeated that expectation, and a measurable injury. Properly framed, presented, and proved, the implied duty is not a general command that the Government behave fairly; it is a focused gap-filling principle that protects the value the parties reasonably expected from the agreement they made.
Practice Points
- Start with conduct, not conclusions. Identify the actor, act or omission, timing, available information, and effect before naming the doctrine.
- Run the threshold inquiry first. Determine whether an express provision or a more specific doctrine already governs the obligation, risk, and remedy.
- Define the expectation precisely. Tie it to the actual bargain rather than a generalized expectation of fair treatment or efficient administration.
- Focus on objective evidence. Contract provisions, notices, decision dates, schedules, and contemporaneous impacts usually matter more than inferred motive.
- Match the count to the claim. Ensure every material act, expectation, impact, and category of relief in litigation was presented to the contracting officer.
Authorities
Decisions
Agility Public Warehousing Co. KSCP v. Mattis, 852 F.3d 1370 (Fed. Cir. 2017).
BGT Holdings LLC v. United States, 984 F.3d 1003 (Fed. Cir. 2020).
Centex Corp. v. United States, 395 F.3d 1283 (Fed. Cir. 2005).
Dobyns v. United States, 915 F.3d 733 (Fed. Cir. 2019).
Metcalf Construction Co. v. United States, 742 F.3d 984 (Fed. Cir. 2014).
The Portland Mint v. United States, 102 F.4th 1371 (Fed. Cir. 2024).
Tecom, Inc. v. United States, 66 Fed. Cl. 736 (2005).
Other Authorities
Contract Disputes Act, 41 U.S.C. §§ 7101-7109.