Federal — Contract Types

FAR Part 16 establishes the federal government's framework for selecting and negotiating contract types in acquisitions. The Part opens with a fundamental premise: agencies have access to a "wide selection of contract types" to accommodate "the large variety and volume of supplies and services required," with types varying according to the degree and timing of cost responsibility the contractor assumes and the profit incentive offered for meeting specified standards (FAR 16.101(a)). The contracting officer's task is to select a type "appropriate to the circumstances of the acquisition" (FAR Part 16 scope).

The two-category taxonomy

FAR 16.101(b) groups contract types into two broad categories: fixed-price contracts (Subpart 16.2) and cost-reimbursement contracts (Subpart 16.3). The regulation describes these categories as a risk continuum. At one end sits the firm-fixed-price contract, under which "the contractor has full responsibility for the performance costs and resulting profit (or loss)"; at the other end sits the cost-plus-fixed-fee contract, under which "the contractor has minimal responsibility for the performance costs and the negotiated fee (profit) is fixed." Between these poles lie incentive contracts (Subpart 16.4), where "the contractor's responsibility for the performance costs and the profit or fee incentives offered are tailored to the uncertainties involved in contract performance."

Each subpart then subdivides further: Subpart 16.2 covers firm-fixed-price contracts, fixed-price contracts with economic price adjustment, fixed-price incentive contracts, fixed-price contracts with prospective price redetermination, and firm-fixed-price level-of-effort term contracts. Subpart 16.3 covers cost, cost-sharing, cost-plus-incentive-fee, cost-plus-award-fee, and cost-plus-fixed-fee contracts. Subpart 16.4 addresses incentive contracting generally. Subpart 16.5 governs indefinite-delivery contracts (definite-quantity, requirements, and indefinite-quantity contracts, commonly called IDIQs). Subpart 16.6 covers time-and-materials and labor-hour contracts.

Statutory limitations and policy constraints

FAR 16.102 imposes three categorical rules. First, contracts resulting from sealed bidding under FAR Part 14 "shall be firm-fixed-price contracts or fixed-price contracts with economic price adjustment" (FAR 16.102(a)). Second, contracts negotiated under FAR Part 15 "may be of any type or combination of types that will promote the Government's interest," except as restricted elsewhere in Part 16, citing 10 U.S.C. 3321(a) and 41 U.S.C. 3901; however, "contract types not described in this regulation shall not be used, except as a deviation under Subpart 1.4" (FAR 16.102(b)). Third, the cost-plus-a-percentage-of-cost contracting system "shall not be used," citing 10 U.S.C. 3322(a) and 41 U.S.C. 3905(a); prime contracts other than firm-fixed-price contracts must include a clause prohibiting such arrangements in subcontracts (FAR 16.102(c)).

FAR 16.102(d) requires that "[n]o contract may be awarded before the execution of any determination and findings (D&F's) required by this part," with minimum D&F content specified in FAR 1.704. This rule operationalizes the statutory and regulatory guardrails: certain contract types—cost-reimbursement contracts under FAR 16.301-3, time-and-materials and labor-hour contracts under FAR 16.601(d), and letter contracts under FAR 16.603—trigger mandatory written determinations before award.

Interaction with commercial-item acquisition

FAR Part 12 imposes an additional constraint. For acquisitions of commercial products or commercial services, FAR 12.207(a) mandates that "agencies shall use firm-fixed-price contracts or fixed-price contracts with economic price adjustment," unless an exception applies. Time-and-materials or labor-hour contracts may be used for commercial services only when competitive procedures are followed (or the agency receives offers from at least two responsible sources under a sole-source justification) and the contracting officer executes a D&F that no other contract type is suitable (FAR 12.207(b)). This overlays Part 16's general framework with a strong presumption against cost-reimbursement and T&M/LH contracts when buying commercial items—Part 12 takes precedence for such acquisitions under FAR 12.102(c).

The upshot for practitioners

The Part 16 framework operates as a constrained menu. The contracting officer must select from the types described in Subparts 16.2 through 16.6 (or seek a Subpart 1.4 deviation for a novel hybrid). Sealed-bid procurements are locked into fixed-price forms. Negotiated procurements permit any type not affirmatively restricted, but commercial-item acquisitions tilt heavily toward firm-fixed-price. Cost-plus-a-percentage-of-cost is categorically forbidden. And for the higher-risk types—cost-reimbursement, T&M/LH, letter contracts—the contracting officer must document the determination that the chosen type is appropriate before issuing the award. The structure presumes that clarity on cost risk allocation, paired with mandatory pre-award justification for the riskiest types, will channel selection toward types that align contractor incentives with Government interests.

Source: FAR 16.101 Source: FAR 16.102 Source: FAR 12.207

The firm-fixed-price (FFP) contract is the baseline contract type in federal acquisition and the government's preferred vehicle when requirements and costs can be determined with reasonable certainty before award. FAR 16.202-1 defines the FFP contract as one that "provides for a price that is not subject to any adjustment on the basis of the contractor's cost experience in performing the contract." The price is locked at award; the government pays that amount regardless of whether the contractor's actual costs overrun or underrun the estimate. This places "maximum risk and full responsibility for all costs and resulting profit or loss" on the contractor, which in turn "provides maximum incentive for the contractor to control costs and perform effectively and imposes a minimum administrative burden upon the contracting parties."

Risk allocation and the profit-or-loss incentive

The risk profile is stark and unambiguous. If the contractor delivers the required supplies or services for less than the contract price, the savings flow to the contractor as additional profit. If costs exceed the price, the contractor absorbs the overrun as a loss—there is no equitable adjustment for inefficiency, only for changes in scope or other affirmative contract modifications. This cost-risk allocation creates a direct financial incentive for cost control and efficiency that is absent in cost-reimbursement contracts, where the government bears cost growth subject only to a ceiling.

The administrative burden is correspondingly light. Because the price is fixed, the government does not audit the contractor's incurred costs during performance (absent an allegation of defective pricing or fraud). There is no need for the contractor to maintain accounting systems compliant with the cost-reimbursement standards in FAR Part 31 or the Cost Accounting Standards in 48 C.F.R. Chapter 99, and no need for DCAA (Defense Contract Audit Agency) floor checks of labor or material charges. The contracting officer's primary enforcement tool is inspection and acceptance under FAR Part 46, not cost surveillance.

The four-prong suitability test under FAR 16.202-2

FAR 16.202-2 establishes when a firm-fixed-price contract is "suitable." The regulation begins with a threshold requirement: the contracting officer must be able to "establish fair and reasonable prices at the outset." This is a mandatory precondition—if the CO cannot make a fair-and-reasonable determination before award, the FFP vehicle is not suitable, full stop.

The FAR then identifies four circumstances (phrased as "such as when") that satisfy the threshold. These are not exclusive, but they are the canonical set:

(a) Adequate price competition exists. When offers are obtained from two or more responsible offerors competing independently under conditions that ensure the prices are set by the market rather than by agreement, FAR 15.403-1(c)(1) provides that the contracting officer may determine price reasonableness on the basis of competition alone, without cost or pricing data. The FFP type is plainly suitable in this scenario because the competitive market has already validated the price.

(b) Reasonable price comparisons are available. The contracting officer may establish a fair and reasonable price through comparison with "prior purchases of the same or similar supplies or services made on a competitive basis or supported by valid certified cost or pricing data." Historical pricing—whether from the agency's own prior buys, GSA schedule pricing, or other-agency contract awards—can anchor price reasonableness when the comparables are recent, involve similar quantities and delivery schedules, and were themselves competitively awarded or cost-validated.

(c) Available cost or pricing information permits realistic cost estimates. Even absent direct price comparables, the contracting officer may use cost or pricing data (certified under the Truth in Negotiations Act if the acquisition exceeds the TINA threshold at FAR 15.403-4, or uncertified data below it) to build up a cost estimate and negotiate a fixed price. The key constraint is "realistic"—the estimate must account for the contractor's actual cost structure, not a theoretical or aspirational baseline. If uncertainties in labor rates, material costs, or technical performance make cost estimation speculative, this prong is not satisfied and the FFP type is unsuitable.

(d) Performance uncertainties are quantifiable and the contractor accepts the risk. The fourth prong acknowledges that even when some performance risk exists—unforeseen technical obstacles, schedule compression, integration challenges—an FFP contract may still be suitable if (i) the contracting officer can identify the uncertainties, (ii) reasonable estimates of their cost impact can be made, and (iii) the contractor is willing to accept a firm fixed price that accounts for those risks. This prong reflects the policy preference for shifting risk to contractors as requirements mature; the government may pay a risk premium in the negotiated price, but in exchange it obtains cost certainty and eliminates the need for ongoing cost oversight.

FAR 16.202-2 applies this suitability framework to two broad categories: (1) "commercial products or commercial services (see parts 2 and 12)," and (2) "other supplies or services on the basis of reasonably definite functional or detailed specifications (see part 11)." For commercial items, FAR Part 12 separately mandates FFP or FP-EPA as the required contract types (FAR 12.207(a)), so the suitability analysis under 16.202-2 is generally satisfied by the commercial-item determination itself. For non-commercial supplies and services, the contracting officer must affirmatively establish that the requirement is defined well enough—through functional or detailed specifications—to permit the price-reasonableness determination.

Interaction with award-fee and performance incentives

FAR 16.202-1 expressly permits the contracting officer to "use a firm-fixed-price contract in conjunction with an award-fee incentive (see 16.404) and performance or delivery incentives (see 16.402-2 and 16.402-3) when the award fee or incentive is based solely on factors other than cost." When layered with these incentives, "the contract type remains firm-fixed-price"—the base price is still not adjustable based on cost experience; only the fee or incentive payment varies based on the contractor's performance against objective quality, schedule, or technical criteria. This hybrid structure preserves the cost-control incentive of the FFP baseline while adding motivational levers for dimensions of performance (on-time delivery, defect rates, user satisfaction) that the fixed price alone does not address.

Mandatory use in sealed bidding; strong preference in commercial acquisition

FAR 16.102(a) mandates that "contracts resulting from sealed bidding shall be firm-fixed-price contracts or fixed-price contracts with economic price adjustment." No other contract type is permitted under FAR Part 14. The policy rationale is straightforward: sealed bidding awards on the basis of price alone (FAR 14.103-1), so the government must be able to compare prices without adjusting for cost uncertainty or fee structures—FFP (or FP-EPA for acquisitions with defined price-adjustment indices) is the only type compatible with that selection mechanism.

For negotiated acquisitions of commercial products or commercial services, FAR 12.207(a) similarly requires agencies to "use firm-fixed-price contracts or fixed-price contracts with economic price adjustment" unless a narrow exception applies. The commercial-item presumption is that market-driven prices are inherently fair and reasonable, and that the additional cost oversight of cost-reimbursement or time-and-materials contracts is both unnecessary and inconsistent with commercial practices. Time-and-materials or labor-hour contracts may be used for commercial services only when the contracting officer follows competitive procedures (or receives at least two offers under a sole-source J&A) and executes a determination and findings that no other contract type is suitable (FAR 12.207(b))—an intentionally high bar.

The upshot for practitioners

The firm-fixed-price contract is the workhorse of federal acquisition. It dominates sealed-bid procurements, commercial-item buys, and production contracts where requirements are stable and cost history is available. Contractors assume cost risk in exchange for the opportunity to earn profit through efficient performance; the government obtains price certainty and minimal administrative overhead. The suitability analysis turns on whether the contracting officer can establish a fair and reasonable price at award—through competition, price comparisons, cost data, or quantified risk assessment. When that predicate is met, the FFP type aligns incentives, reduces disputes over allowable costs, and permits both parties to focus on contract performance rather than cost accounting. When it is not met—because requirements are ill-defined, technical risk is unquantifiable, or no meaningful price history exists—the contracting officer must turn to cost-reimbursement, incentive, or time-and-materials structures that shift risk back to the government and impose the commensurate oversight burden.

Source: FAR 16.202-1 Source: FAR 16.202-2 Source: FAR 16.102 Source: FAR 12.207

Cost-reimbursement contracts sit at the opposite end of FAR Part 16's risk continuum from firm-fixed-price contracts. Where an FFP contract places maximum cost risk on the contractor and provides full profit-or-loss incentive, cost-reimbursement contracts shift cost risk to the government in exchange for the contractor's commitment to perform work whose scope, technical requirements, or cost cannot be estimated with sufficient accuracy to permit a fixed price at award. This contract family is the statutory and regulatory vehicle for research and development, early-stage exploration, and high-uncertainty acquisitions when the government needs the work done but cannot define deliverables or costs tightly enough to shift risk to industry.

The basic mechanism under FAR 16.301-1

FAR 16.301-1 defines cost-reimbursement contracts as those that "provide for payment of allowable incurred costs, to the extent prescribed in the contract." The government reimburses the contractor for costs that satisfy the three-prong allowability test in FAR Part 31 (reasonable, allocable, and determined allowable under the cost principles), subject to a negotiated cost ceiling. The contract establishes "an estimate of total cost for the purpose of obligating funds and establishing a ceiling that the contractor may not exceed (except at its own risk) without the approval of the contracting officer." Cost overruns beyond the ceiling are the contractor's responsibility unless the contracting officer affirmatively raises the ceiling through a contract modification; cost underruns do not increase the contractor's fee (except in incentive-fee variants covered in FAR Subpart 16.4). The government audits incurred costs through the Defense Contract Audit Agency (DCAA) or other cognizant audit authority, applying FAR Part 31 cost principles and, for CAS-covered contractors, the Cost Accounting Standards in 48 C.F.R. Chapter 99. The baseline administrative burden is therefore substantially higher than for firm-fixed-price contracts, where the government does not examine the contractor's books absent a defective-pricing or fraud allegation.

The two-prong application standard under FAR 16.301-2

FAR 16.301-2(a) imposes a mandatory constraint: "The contracting officer shall use cost-reimbursement contracts only when" one of two conditions is satisfied. These are not permissive factors; they are threshold requirements.

Prong (a)(1): Inability to define requirements. The contracting officer may use a cost-reimbursement contract when "circumstances do not allow the agency to define its requirements sufficiently to allow for a fixed-price type contract (see 7.105)." This prong applies when the statement of work must be expressed in general terms—functional outcomes, research objectives, exploratory goals—rather than detailed specifications with measurable acceptance criteria. Early-stage R&D, basic research at universities, and preliminary feasibility studies typically fall here. The regulation ties this prong to FAR 7.105, the acquisition-planning requirement, signaling that the contracting officer must affirmatively document in the acquisition plan why the requirement cannot be defined with the specificity that a fixed-price vehicle demands.

Prong (a)(2): Uncertainties in cost estimation. Alternatively, the contracting officer may use a cost-reimbursement contract when "uncertainties involved in contract performance do not permit costs to be estimated with sufficient accuracy to use any type of fixed-price contract." This prong recognizes that even when the deliverable is well-defined, technical risk, integration unknowns, or novel labor-mix requirements may make pre-award cost estimation speculative. A development program for a first-of-kind system, a software integration effort where the legacy code baseline is poorly documented, or a rapid-prototype effort on a compressed schedule may all satisfy this prong. The key word is "accuracy"—the regulation does not require absolute certainty (no acquisition has that), but it does require that cost uncertainty be substantial enough that shifting cost risk to the contractor via a fixed-price ceiling would be neither fair nor likely to yield realistic proposals. When cost history is thin, comparable programs are absent, or the technical approach is still maturing, this prong is met.

Prong (b): Mandatory acquisition-plan documentation. FAR 16.301-2(b) requires the contracting officer to "document the rationale for selecting the contract type in the written acquisition plan and ensure that the plan is approved and signed at least one level above the contracting officer (see 7.103(j) and 7.105)." This is a categorical rule—there is no cost-reimbursement contract award without an approved acquisition plan containing a contract-type justification signed by a reviewing official above the contracting officer. The policy aim is heightened scrutiny: because cost-reimbursement contracts impose ongoing cost-surveillance burden and expose the government to cost growth, the FAR requires an explicit, reviewable determination that the two application prongs are satisfied before the contracting officer may proceed.

Four mandatory prerequisites under FAR 16.301-3(a)

Even when the FAR 16.301-2 application test is met, FAR 16.301-3(a) imposes four additional prerequisites that must be satisfied before award. These are cumulative; if any one is not met, the cost-reimbursement contract may not be used.

(1) [Omitted—substantive requirement not separately enumerated in current FAR 16.301-3(a)]. The current FAR structure at 16.301-3(a) opens directly with prong (2); prong (1) was removed in a 2011 FAR rule on proper use and management of cost-reimbursement contracts. The four operative prerequisites today are numbered (2) through (4) in the regulation, with (4) containing two sub-prongs.

(2) Written acquisition plan approved one level above the CO. This reiterates and operationalizes the documentation requirement in FAR 16.301-2(b). The acquisition plan must be signed by an official at least one level above the contracting officer. Delegation below that level is not permitted. This ensures institutional review before committing the government to the cost-surveillance and oversight obligations inherent in cost-reimbursement contracting.

(3) Adequate contractor accounting system. The contracting officer must determine that "the contractor's accounting system is adequate for determining costs applicable to the contract or order." This prerequisite is enforced through the contractor's accounting-system approval status maintained by the cognizant Defense Contract Management Agency (DCMA) or civilian-agency equivalent. If the contractor's system has a significant deficiency identified by DCAA or DCMA, the system is not "adequate," and the contracting officer may not award a cost-reimbursement contract (or must condition award on corrective action). The accounting-system adequacy determination is typically documented in a pre-award survey or by reference to the contractor's current system-approval memorandum. For cost-reimbursement contracts subject to the Cost Accounting Standards (generally, contracts over the CAS threshold at FAR 30.201-4), the contractor must also have disclosed cost-accounting practices and be in compliance with applicable CAS standards; a noncompliant system fails this prerequisite.

(4) Adequate government resources for award and management. FAR 16.301-3(a)(4) requires that "prior to award of the contract or order, adequate Government resources are available to award and manage a contract other than firm-fixed-priced (see 7.104(e))." The regulation defines "adequate resources" to include two elements: first, "appropriate Government surveillance during performance in accordance with 1.602-2, to provide reasonable assurance that efficient methods and effective cost controls are used"; second (added by the 2011 FAR rule), the contracting officer must ensure that at least one qualified contracting officer's representative (COR) is designated before award. The COR must be trained and certified under agency policy implementing FAR 1.602-2. The policy intent is to prevent cost-reimbursement contracts from being awarded when the program office or contracting activity lacks the personnel, audit support, or technical-surveillance capacity to monitor contractor performance and review incurred-cost submissions. If DCAA coverage is unavailable, if no qualified COR can be assigned, or if the contracting office is already at capacity for cost-reimbursement oversight, this prerequisite is not satisfied and the contract may not be awarded as cost-reimbursement—the contracting officer must either obtain the resources, restructure the acquisition as fixed-price with narrowed scope, or delay the procurement until resources become available.

Categorical prohibition for commercial items under FAR 16.301-3(b) and FAR 12.207

FAR 16.301-3(b) states flatly: "The use of cost-reimbursement contracts is prohibited for the acquisition of commercial products and commercial services (see parts 2 and 12)." This prohibition is absolute. If the supplies or services meet the commercial-item definition in FAR 2.101—offered to the general public, evolved from a commercial item, or of a type offered to the general public—then cost-reimbursement contracting is not available, full stop. The government must use firm-fixed-price or fixed-price with economic price adjustment under FAR 12.207(a), or (for commercial services only) time-and-materials or labor-hour contracts under the narrow exception in FAR 12.207(b), which requires a determination and findings that no other contract type is suitable. The policy rationale is straightforward: commercial pricing is market-driven, and the FAR presumes that commercial suppliers will not accept cost-reimbursement terms (which require cost-accounting-system adequacy, CAS compliance for large contractors, disclosure of cost or pricing data, and government audit of incurred costs). The prohibition applies even when the commercial item is being modified or integrated into a noncommercial system; if the contract's principal purpose is acquisition of a commercial product or service, FAR Part 12 governs and cost-reimbursement is unavailable.

The five contract types within FAR Subpart 16.3

FAR Subpart 16.3 enumerates five cost-reimbursement contract types, each differing in fee structure and risk-sharing. Three are covered within the subpart; two are cross-referenced to FAR Subpart 16.4 on incentive contracts.

Cost contracts (FAR 16.302): The contractor receives no fee—only reimbursement of allowable costs. FAR 16.302(b) states this type "may be appropriate for research and development work, particularly with nonprofit educational institutions or other nonprofit organizations." For-profit contractors rarely accept cost-no-fee terms; the type is used almost exclusively with universities, federally funded R&D centers, and nonprofit research institutes where the organizational mission, rather than profit, motivates contract performance.

Cost-sharing contracts (FAR 16.303): The contractor receives no fee and is reimbursed for only an agreed-upon portion of allowable costs. FAR 16.303(b) permits use "when the contractor agrees to absorb a portion of the costs, in the expectation of substantial compensating benefits." Those benefits might include commercialization rights to government-funded research, access to government test facilities, or enhancement of the contractor's technical reputation. Like cost contracts, cost-sharing is rare in production contracting but appears in cooperative R&D agreements, public–private partnerships, and Other Transaction Authority (OTA) prototypes where the contractor has an independent business interest in the technology being developed.

Cost-plus-incentive-fee (CPIF) contracts (FAR 16.304): Covered in detail in FAR Subpart 16.4, Incentive Contracts (specifically FAR 16.405-1). The contract establishes a target cost, a target fee, a fee-adjustment formula, and a ceiling cost. If actual costs underrun the target, the contractor earns additional fee per the formula (subject to a maximum fee); if costs overrun, fee decreases (subject to a minimum fee, which may be zero). CPIF contracts are appropriate when a cost-reimbursement vehicle is necessary under FAR 16.301-2 and the contracting officer can negotiate a realistic target cost and a fee formula likely to motivate effective cost control. All limitations in FAR 16.301-3 apply.

Cost-plus-award-fee (CPAF) contracts (FAR 16.305): Also covered in FAR Subpart 16.4 (FAR 16.401(e) and 16.405-2). The contract provides a base fee (which may be zero) fixed at inception, plus an award-fee pool that the contractor may earn based on the government's subjective evaluation of performance against criteria in an award-fee plan. The evaluation addresses cost control, schedule adherence, technical performance, and other factors the parties negotiate into the plan. Award-fee contracts are used when objective cost or performance targets cannot be established in advance—common in service contracts, systems engineering and technical assistance (SETA), and long-duration development programs. The fee is not formulaic; it turns on the fee-determining official's judgment, documented in periodic award-fee-determination memoranda. FAR 16.401(e) contains detailed suitability and limitation rules.

Cost-plus-fixed-fee (CPFF) contracts (FAR 16.306): The government pays allowable incurred costs plus a negotiated fee that is fixed at contract inception. FAR 16.306(a) explains that "the fixed fee does not vary with actual cost, but may be adjusted as a result of changes in the work to be performed under the contract." A CPFF contract "permits contracting for efforts that might otherwise present too great a risk to contractors, but it provides the contractor only a minimum incentive to control costs." The fee is invariant with cost performance; whether the contractor incurs 80% or 120% of the estimated cost, the fee remains the same (subject only to equitable adjustment if scope changes). This fee structure makes CPFF the cost-reimbursement type of last resort when the work must be done, the contractor will not accept cost risk, and no meaningful cost-incentive formula can be devised. FAR 16.306(c) states that a CPFF contract is suitable when the conditions of FAR 16.301-2 are present and, for example, the contract is for research, preliminary exploration, or study where the level of effort is unknown, or for development and test when a CPIF contract is not practical. The regulation cautions that CPFF "normally should not be used in development of major systems (see part 34) once preliminary exploration, studies, and risk reduction have indicated a high degree of probability that the development is achievable and the Government has established reasonably firm performance objectives and schedules"—in other words, once a program matures to the point that cost targets can be set, the contracting officer should transition to CPIF or a fixed-price incentive structure. CPFF contracts come in two forms: completion (the contractor must complete and deliver a specified end product) and term (the contractor provides a specified level of effort over a stated period). FAR 16.306(d)(3) states a preference for the completion form "whenever the work, or specific milestones for the work, can be defined well enough to permit development of estimates within which the contractor can be expected to complete the work." The term form may be used only when the contractor is obligated to provide a specific level of effort within a definite time period—common in advisory and assistance services, SETA contracts, and research conducted by nonprofit institutions.

The upshot for practitioners

Cost-reimbursement contracting is heavily regulated and bureaucratically demanding. It requires affirmative findings that requirements cannot be defined or costs cannot be estimated with accuracy (FAR 16.301-2); a written, reviewed acquisition plan (FAR 16.301-2(b) and 16.301-3(a)(2)); an adequate contractor accounting system (FAR 16.301-3(a)(3)); and government resources sufficient to manage cost surveillance and appoint a trained COR before award (FAR 16.301-3(a)(4)). It is categorically unavailable for commercial items (FAR 16.301-3(b)). When these gates are cleared, the contracting officer selects from five contract types—cost-no-fee, cost-sharing, CPIF, CPAF, or CPFF—based on fee philosophy, the feasibility of cost or performance targets, and the degree of cost-control incentive the government wishes to impose. The structure presumes that shifting cost risk to the government is justified only when uncertainty is genuine, oversight resources are committed, and the contractor's accounting practices can withstand audit. The administrative price is ongoing cost review under FAR Part 31, DCAA audits, and voucher-by-voucher reimbursement—an overhead the government accepts when the mission requires work that cannot wait for requirements to crystallize or costs to become predictable.

Source: FAR 16.301-1 Source: FAR 16.301-2 Source: FAR 16.301-3 Source: FAR Subpart 16.3

Time-and-materials (T&M) and labor-hour (LH) contracts occupy a distinct middle position in the FAR Part 16 risk taxonomy. They are neither fixed-price nor cost-reimbursement contracts (FAR 16.101(b) and 16.3, note); instead, they blend elements of both. The contractor bears risk on labor efficiency (through fixed hourly rates that include wages, overhead, G&A, and profit) but the government bears risk on the total hours required and the actual cost of materials. This hybrid structure generates two policy concerns that thread through FAR Subpart 16.6: first, T&M and LH contracts "provide no positive profit incentive to the contractor for cost control or labor efficiency" (FAR 16.601(c)(1)), so the government must accept ongoing surveillance obligations similar to cost-reimbursement contracts; and second, because the final price is unknown at award, the FAR treats T&M and LH contracts as disfavored vehicles—permitted only when fixed-price contracting is not possible and hedged by mandatory determinations and findings, a ceiling-price requirement, and categorical restrictions for commercial items.

The two contract types — T&M versus LH

FAR 16.601(b) defines a time-and-materials contract as one that "provides for acquiring supplies or services on the basis of (1) Direct labor hours at specified fixed hourly rates that include wages, overhead, general and administrative expenses, and profit; and (2) Actual cost for materials (except as provided for in 31.205-26(e) and (f))." "Materials," as defined in the payment clause at FAR 52.232-7 for non-commercial T&M contracts (and at FAR 52.212-4 Alternate I for commercial items), includes direct materials, subcontracts for supplies and ancillary services, other direct costs, and applicable indirect costs. This broad definition means that subcontracts, travel, and other-direct-costs are reimbursed at actual cost on a T&M contract (subject to FAR Part 31 allowability and reasonableness standards), not at a fixed rate.

FAR 16.602 defines a labor-hour contract as "a variation of the time-and-materials contract, differing only in that materials are not supplied by the contractor." All application and limitation rules in FAR 16.601(c) and (d) apply equally to labor-hour contracts (FAR 16.602). The LH vehicle is common in pure-services acquisitions—professional services, systems engineering and technical assistance (SETA), administrative support—where the government separately procures or already owns the materials, equipment, or supplies, and the contractor provides only labor.

The narrow application standard under FAR 16.601(c)

FAR 16.601(c) establishes a negative threshold condition for both T&M and LH contracts: "A time-and-materials contract may be used only when it is not possible at the time of placing the contract to estimate accurately the extent or duration of the work or to anticipate costs with any reasonable degree of confidence." This is a strict "only when" rule—if the contracting officer can estimate extent, duration, or costs with reasonable confidence, the T&M or LH vehicle is not permitted; a fixed-price type must be used instead (or, if cost uncertainty is coupled with requirement uncertainty, a cost-reimbursement type under FAR 16.301-2).

The application standard turns on two factual predicates. First, extent or duration must be unestimatable. Typical scenarios include emergency repair services where the fault has not yet been diagnosed; on-call technical support where demand fluctuates unpredictably; staff augmentation where the precise mix of labor categories and hours needed will vary with mission tempo; and surge support where the requirement may scale sharply in response to operational needs. If historical data, similar prior buys, or a well-defined statement of work permit the contracting officer to forecast the labor hours or deliverables with reasonable accuracy—even if some variance exists—the "extent or duration" prong is not satisfied.

Second, costs must not be anticipatable with reasonable confidence. This prong overlaps with but is broader than the first. Even when hours are uncertain, costs might still be estimatable if wage rates, material pricing, and overhead factors are stable and well-documented. Conversely, if labor-mix uncertainty, volatile material markets, or lack of cost history make pre-award cost estimation speculative, this prong is met. The contracting officer's determination is inherently judgmental—the FAR does not define "reasonable degree of confidence"—but the regulation's policy tilt is clear: when doubt exists, favor a fixed-price vehicle and require the contractor to price the uncertainty into its proposal, rather than defaulting to T&M and transferring cost risk to the government.

FAR 12.207(b) layers an additional commercial-item constraint: T&M or LH contracts for commercial services may be used only when (1) the contracting officer uses competitive procedures (or receives offers from at least two responsible sources under a sole-source justification and approval) and (2) the contracting officer executes a determination and findings that no other contract type is suitable (examined below). This requirement ensures that the contracting officer cannot bypass the firm-fixed-price mandate in FAR 12.207(a) simply because a commercial vendor offers hourly-rate pricing. The commercial-item presumption remains FFP; the T&M exception is narrow and conditional.

Surveillance obligation under FAR 16.601(c)(1)

FAR 16.601(c)(1) imposes an affirmative duty on the government: "A time-and-materials contract provides no positive profit incentive to the contractor for cost control or labor efficiency. Therefore, appropriate Government surveillance of contractor performance is required to give reasonable assurance that efficient methods and effective cost controls are being used." This language parallels the surveillance requirement for cost-reimbursement contracts in FAR 16.301-3(a)(4). In practice, it means the contracting officer must assign a qualified contracting officer's representative (COR) to monitor labor charging, review invoices for reasonableness, and verify that the contractor is not padding hours or assigning overqualified (higher-rate) personnel to tasks that could be performed by less expensive labor categories. The government does not audit incurred costs under FAR Part 31 in the same depth as on cost-reimbursement contracts—because labor is paid at fixed hourly rates, not actual cost—but the invoice-review and performance-monitoring burden is substantially higher than for firm-fixed-price contracts, where the government's oversight typically ends at inspection and acceptance.

Mandatory determination and findings under FAR 16.601(d)(1)

FAR 16.601(d)(1) prohibits award of a T&M or LH contract or order unless "the contracting officer prepares a determination and findings that no other contract type is suitable." This is a categorical rule—there is no T&M or LH contract without a D&F. The D&F must be (i) signed by the contracting officer prior to execution of the base period or any option periods; and (ii) approved by the head of the contracting activity prior to execution of the base period when the base period plus any option periods exceeds three years.

The content requirement is specified separately (though not explicitly enumerated in FAR 16.601(d)(1) itself; it appears in the broader D&F guidance at FAR 1.704 and in recent FAR Council clarifications). The D&F must contain "sufficient facts and rationale to justify that no other contract type is suitable," including an explanation of why the acquisition does not meet the suitability tests for firm-fixed-price (FAR 16.202-2), fixed-price with economic price adjustment (FAR 16.203), or cost-reimbursement (FAR 16.301-2) contracts. In practice, the D&F should address why extent and duration cannot be estimated, what market research was conducted, whether portions of the requirement could be severed out for fixed-price award, and what surveillance measures the government will employ to mitigate the lack of cost-control incentive.

For indefinite-delivery contracts (IDIQs) that authorize T&M orders, the D&F requirement applies at the basic contract level; a separate D&F is not required for each individual order issued under that contract, provided the order falls within the general scope of the basic contract's T&M authorization. However, if the order changes the general scope or raises the ceiling price beyond the contemplated range, FAR 16.601(e) imposes additional documentation requirements (discussed below).

The ceiling-price requirement under FAR 16.601(d)(2)

FAR 16.601(d)(2) mandates that "the contract or order includes a ceiling price that the contractor exceeds at its own risk." This is a floor requirement—every T&M and LH contract must have a not-to-exceed ceiling. The ceiling operates as a funding and risk-allocation mechanism: the government's payment obligation is capped at the ceiling; if the contractor incurs costs beyond the ceiling and the contracting officer has not raised it through a contract modification, the contractor absorbs the overrun.

The ceiling is not a cost estimate (though it is typically set with reference to an estimated number of labor hours and anticipated material costs). It is a maximum price. Contractors may not invoice beyond the ceiling without a modification; program offices may not obligate beyond the ceiling without new funds and a bilateral amendment. The ceiling-price requirement distinguishes T&M and LH contracts from pure cost-reimbursement contracts, where the estimated cost is merely a planning figure and the government's obligation runs to all allowable, allocable, and reasonable costs up to a separately stated ceiling (if one exists under the particular cost-reimbursement variant). On T&M and LH contracts, cost risk above the ceiling shifts to the contractor—a partial fixed-price feature.

FAR 16.601(e) adds a post-award discipline: prior to an increase in the ceiling price, the contracting officer must (1) conduct an analysis of pricing and other relevant factors to determine whether the increase is in the government's best interest, (2) document the decision in the contract file, and (3) when the change modifies the general scope of the contract, follow the competition procedures in FAR 6.303 (for contracts) or FAR 16.505(b)(2) (for orders under multiple-award IDIQs). This rule prevents the contracting officer from serially raising the ceiling to accommodate scope creep or contractor inefficiency without re-evaluating whether continued performance under T&M terms remains appropriate or whether a new competitive acquisition (or a transition to fixed-price for the remaining work) is warranted.

The upshot for practitioners

Time-and-materials and labor-hour contracts are tools of last resort within the FAR Part 16 menu. They are authorized only when extent, duration, or costs cannot be estimated with reasonable confidence at the time of award—not merely when the contractor prefers hourly billing or the government finds cost estimation inconvenient. Award requires an affirmative written determination, signed by the contracting officer and (for periods of performance over three years) approved by the head of the contracting activity, that no other contract type is suitable. Every contract must include a not-to-exceed ceiling, and every ceiling increase must be analyzed and documented before execution. The government must commit to meaningful performance surveillance, because the contract structure eliminates the contractor's profit incentive to control costs or improve labor efficiency. For commercial-item acquisitions, the bar is even higher: competitive procedures (or at least two offers) are mandatory under FAR 12.207(b), reinforcing the policy preference for firm-fixed-price contracting when buying from the commercial marketplace. When these gates are cleared, T&M and LH contracts provide flexibility for requirements whose scope or cost truly cannot be defined at award—emergency response, unpredictable technical support, surge staffing. But that flexibility comes at a price: administrative overhead comparable to cost-reimbursement contracts and exposure to cost growth if surveillance is lax or ceiling increases are approved without rigorous scrutiny.

Source: FAR 16.601 Source: FAR 16.602 Source: FAR 12.207

The indefinite-quantity contract (IDIQ) is one of the most widely used contract vehicles in federal acquisition. Pursuant to 10 U.S.C. § 3401 and 41 U.S.C. § 4101, indefinite-quantity contracts are also known as delivery-order contracts (when supplies are involved) or task-order contracts (when services are involved). The nomenclature is interchangeable in practice; the underlying FAR framework is the same. IDIQs are the structural foundation for the General Services Administration's Federal Supply Schedule contracts (governed separately under FAR Part 8 and FAR Part 38, which take precedence over FAR Subpart 16.5 per FAR 16.500(c)), government-wide acquisition contracts (GWACs), and thousands of agency-specific multiple-award vehicles. For practitioners, the three critical elements are the minimum-guarantee requirement, the statutory preference for multiple awards, and the fair-opportunity procedures that govern task-order competition.

Description and application under FAR 16.504(a) and (b)

FAR 16.504(a) defines an indefinite-quantity contract as one that "provides for an indefinite quantity, within stated limits, of supplies or services during a fixed period." The government places orders for individual requirements as they arise; the contract does not commit the government to purchase any specific quantity beyond a stated minimum. Quantity limits may be expressed as number of units or as dollar values. The contract must require the government to order—and the contractor to furnish—at least a stated minimum quantity of supplies or services. In addition, if ordered, the contractor must furnish any additional quantities, not to exceed a stated maximum. To ensure the contract is binding (a requirement under general contract-formation principles), FAR 16.504(a)(2) mandates that "the minimum quantity must be more than a nominal quantity, but it should not exceed the amount that the Government is fairly certain to order." A minimum guarantee of one dollar, or a single unit with no real prospect of exercise, is not enforceable; the minimum must reflect a genuine commitment. The contracting officer should establish the maximum quantity "based on market research, trends on recent contracts for similar supplies or services, survey of potential users, or any other rational basis" (FAR 16.504(a)(1)).

FAR 16.504(b) states that contracting officers may use an indefinite-quantity contract when "the Government cannot predetermine, above a specified minimum, the precise quantities of supplies or services that the Government will require during the contract period, and it is inadvisable for the Government to commit itself for more than a minimum quantity." The regulation adds that "the contracting officer should use an indefinite-quantity contract only when a recurring need is anticipated." One-time buys with known quantities are inappropriate for the IDIQ vehicle; those should be structured as fixed-quantity contracts. The IDIQ type is designed for programs with predictable demand patterns but uncertain order timing or quantities—help-desk support, base operations contracts, IT services, construction task orders, research and development with phased funding, or any requirement where the government wants pre-competed pricing and pre-vetted contractors on standby but cannot commit to firm quantities at the outset.

The multiple-award preference under FAR 16.504(c)(1)

FAR 16.504(c)(1)(ii) imposes a statutory preference for multiple awards of indefinite-quantity contracts: "Except for indefinite-quantity contracts for advisory and assistance services as provided in paragraph (c)(2) of this section, the contracting officer must, to the maximum extent practicable, give preference to making multiple awards of indefinite-quantity contracts under a single solicitation for the same or similar supplies or services to two or more sources." This is not merely a best practice; it is a mandatory preference. The contracting officer must determine whether multiple awards are appropriate as part of acquisition planning. When structuring a multiple-award IDIQ, the contracting officer must avoid situations in which awardees specialize exclusively in one or a few areas within the statement of work, thus creating the likelihood that orders in those areas will be awarded on a sole-source basis—though the regulation acknowledges that "each awardee need not be capable of performing every requirement as well as any other awardee under the contracts" (FAR 16.504(c)(1)(ii)(A)).

The contracting officer may make a single award only when one of the following conditions applies (FAR 16.504(c)(1)(ii)(B)):

1. Only one awardee is capable. The contracting officer determines that only one contractor is capable of providing the supplies or services required at the level of quality required because the supplies or services are unique or highly specialized.

1. Multiple awards not in the best interest. The contracting officer determines that multiple awards for the same or similar supplies or services would not be in the government's best interest. This determination must be documented in the acquisition plan or contract file (FAR 16.504(c)(1)(ii)(C)).

1. Total estimated value at or below the simplified acquisition threshold. The total estimated contract value (including all options) does not exceed the SAT (currently $250,000).

1. Advisory and assistance services exception. For indefinite-quantity contracts for advisory and assistance services that exceed three years and $20 million (including all options), a separate set of rules applies under FAR 16.504(c)(2): the contracting officer must make multiple awards unless a written determination is executed that "the services required are so unique or highly specialized that it is not practicable to make multiple awards."

Head-of-agency determination for single awards over $150 million under FAR 16.504(c)(1)(ii)(D)

No task- or delivery-order contract in an amount estimated to exceed $150 million (including all options) may be awarded to a single source unless the head of the agency (not delegable to the contracting officer) determines in writing that one of the following applies:

(i) Integrally related tasks. The task or delivery orders expected under the contract are so integrally related that only a single source can reasonably perform the work.

(ii) Firm-fixed-price exception. The contract provides only for firm-fixed-price task or delivery orders for (A) products for which unit prices are established in the contract, or (B) services for which prices are established in the contract for the specific tasks to be performed.

(iii) Only one source qualified. Only one source is qualified and capable of performing the work at a reasonable price to the government.

(iv) Exceptional public-interest circumstances. It is necessary in the public interest to award the contract to a single source due to exceptional circumstances. When this ground is invoked, the head of the agency must notify Congress within 30 days after the determination (FAR 16.504(c)(1)(ii)(D)(2)).

This $150 million single-award gate is in addition to any applicable FAR Part 6 justification and approval requirements, and it does not apply to architect-engineer services awarded under FAR Subpart 36.6 (FAR 16.504(c)(1)(ii)(D)(3)). For DoD procurements, DFARS 216.504(c)(1)(ii)(D) overlays an additional rule: the senior procurement executive (not the FAR's "head of the agency") has the determination authority, and when applying prong (i), the determination must find that only a single source can efficiently perform the work (a stricter standard than the FAR's "reasonably"). Further, under 10 U.S.C. § 3403(d)(3) as implemented by DFARS 216.504(c)(1)(ii)(D)(3), the determination is not required if a justification and approval has already been executed under FAR Subpart 6.3 and DFARS Subpart 206.3—Congress recognized that dual documentation would be redundant when the single award has already been justified under the sole-source or limited-competition rules.

Fair opportunity for task orders under multiple-award IDIQs — FAR 16.505(b)(1)

When the government makes multiple awards of indefinite-quantity contracts, the ordering procedures in FAR 16.505(b) apply. FAR 16.505(b)(1)(i) establishes the baseline rule: "The contracting officer must provide each awardee a fair opportunity to be considered for each order exceeding the micro-purchase threshold issued under multiple delivery-order contracts or multiple task-order contracts," except as provided in FAR 16.505(b)(2) (discussed below). "Fair opportunity" does not mean full and open competition under FAR Part 6, nor does it mean negotiated source selection under FAR Part 15. The competition requirements in FAR Part 6 and the formal source-selection procedures in FAR Subpart 15.3 do not apply to the ordering process (this is explicit in the legislative history and reinforced in GAO decisions interpreting the fair-opportunity standard). Instead, FAR 16.505(b)(1)(ii) grants the contracting officer "broad discretion in developing appropriate order placement procedures." The contracting officer should keep submission requirements to a minimum and may use streamlined procedures, including oral presentations. For orders that do not exceed the simplified acquisition threshold, the contracting officer need not contact each of the multiple awardees before selecting an order awardee if the contracting officer has information available—such as recent price history, past performance on earlier orders, or an awardee's disclosed capabilities at the basic-contract level—to ensure that each awardee is provided a fair opportunity to be considered.

Enhanced procedures for orders exceeding $7.5 million under FAR 16.505(b)(1)(iv)

For task or delivery orders in excess of $7.5 million, the fair-opportunity requirement imposes minimum procedural safeguards that parallel (but do not fully replicate) FAR Part 15 negotiated procurement. The contracting officer must provide:

(A) A notice of the task or delivery order that includes a clear statement of the agency's requirements;

(B) A reasonable period of time to provide a proposal in response to the notice;

(C) Disclosure of the significant factors and subfactors, including cost or price, that the agency expects to consider in evaluating proposals, and their relative importance;

(D) Where award is made on a best-value basis, a written statement documenting the basis for award and the relative importance of quality and price or cost factors; and

(E) An opportunity for a postaward debriefing in accordance with FAR 16.505(b)(6), following the procedures in FAR 15.506.

Importantly, even for orders over $7.5 million, FAR 16.505(b)(1)(v) states that "formal evaluation plans or scoring of quotes or offers are not required." The contracting officer retains discretion to tailor the evaluation approach to the complexity and value of the requirement.

Exceptions to fair opportunity under FAR 16.505(b)(2)

FAR 16.505(b)(2)(i) enumerates seven exceptions to the fair-opportunity requirement. When one of these exceptions applies and the order exceeds the simplified acquisition threshold, the contracting officer must prepare and obtain approval for a written justification meeting the content requirements in FAR 16.505(b)(2)(ii)(D) and the approval thresholds in FAR 16.505(b)(2)(ii)(C). The seven exceptions are:

(A) Unusual urgency. The agency's need for the supplies or services is of such unusual urgency that providing fair opportunity to all contractors would result in unacceptable delays.

(B) Only one contractor capable. Only one contractor is capable of providing the supplies or services required at the level of quality required because the supplies or services ordered are unique or highly specialized.

(C) Logical follow-on. The order should be issued on a sole-source basis in the interest of economy and efficiency because it is a logical follow-on to an order already issued on a competitive basis (i.e., an order that itself received fair opportunity). This exception permits the government to continue work with the same contractor when switching would impose startup costs, require knowledge transfer that outweighs competitive benefits, or disrupt an integrated program.

(D) Minimum guarantee. It is necessary to satisfy a minimum guarantee. Every IDIQ has a stated minimum quantity that the government must order; when the contract period is nearing expiration and the minimum has not been met, the contracting officer may place a sole-source order to satisfy the guarantee without providing fair opportunity to the other awardees.

(E) Statute authorizes or requires a particular source. For orders exceeding the simplified acquisition threshold, a statute expressly authorizes or requires that the purchase be made from a specified source. This exception is rarely invoked; it typically arises under small-business set-aside statutes (though small-business set-asides among multiple awardees are separately addressed in exception (F)) or unusual program-specific authorizations.

(F) Small business, 8(a), HUBZone, SDVOSB, or WOSB set-aside. The contracting officer sets the order aside for small business concerns under FAR Part 19 (or for 8(a), HUBZone, service-disabled veteran-owned, or women-owned small business concerns) and (i) the contract was awarded under full and open competition, or (ii) the contract was awarded under full and open competition after exclusion of sources under FAR Subpart 19.5 or 19.14, and all contract awardees are small business concerns eligible under the particular set-aside. In other words, if the basic IDIQ contract included both small and large businesses (under unrestricted full and open competition), the contracting officer may set aside individual orders for eligible small businesses without providing fair opportunity to the large-business awardees. If the basic contract was itself set aside—so all awardees are small businesses—then setting an order aside for a narrower category (e.g., 8(a) only) likewise does not require fair opportunity to the non-eligible awardees. This exception is one of the most commonly used in practice.

(G) DoD, NASA, and Coast Guard only — exceptions to competition under FAR 6.302. For orders placed by the Department of Defense, NASA, or the Coast Guard, fair opportunity is not required when the order meets an exception to full and open competition in FAR 6.302—other than FAR 6.302-7 (public interest), which requires congressional notification. This exception effectively allows DoD, NASA, and Coast Guard to apply the sole-source or limited-competition justifications familiar from FAR Part 6 to task-order placement under multiple-award IDIQs.

Justifications for exception to fair opportunity above the simplified acquisition threshold must be posted publicly (except when the exception is invoked under FAR 16.505(b)(2)(i)(A), urgency, in which case posting must occur within 30 days after award per FAR 5.301). The contracting officer must carefully screen all justifications for contractor proprietary data before public release.

Protest jurisdiction under 10 U.S.C. § 3406(f) and 41 U.S.C. § 4106(f)

One of the most consequential features of the IDIQ framework is the limitation on protest rights. Under the Federal Acquisition Streamlining Act of 1994 (FASA), Congress erected a jurisdictional bar: protests of task-order or delivery-order awards are generally not authorized, except under two narrow grounds. For DoD, NASA, and Coast Guard procurements, 10 U.S.C. § 3406(f)(1) permits a protest only (A) on the ground that the order increases the scope, period, or maximum value of the contract under which the order is issued, or (B) for an order valued in excess of $35 million. (The threshold was increased from $25 million to $35 million by section 885 of the FY 2025 National Defense Authorization Act, effective December 23, 2024.) For civilian-agency procurements, 41 U.S.C. § 4106(f)(1) imposes the same structure but sets the dollar threshold at $10 million (unchanged as of May 2026).

Notwithstanding 31 U.S.C. § 3556 (which gives GAO general bid-protest jurisdiction), the Comptroller General has exclusive jurisdiction of protests authorized under the dollar-threshold prong—neither the Court of Federal Claims nor an agency-level protest forum may hear such protests. For scope/period/maximum-value protests under prong (A), both GAO and the COFC retain jurisdiction under their general bid-protest authorities, but GAO is the far more common forum. Small-business size-status protests for set-aside orders remain within SBA Office of Hearings and Appeals jurisdiction under FAR 19.302 and are not subject to the FASA bar.

The jurisdictional-value determination for protests under prong (B) turns on the value of the order as awarded, including option years when the government evaluated total price (including options) during the ordering competition. GAO will not look beyond the awarded amount to establish jurisdiction except in "unique or extraordinary circumstances," such as when the government used unconventional compensation methods or atypical price-evaluation techniques. A protester cannot manufacture jurisdiction by alleging that the agency violated a procurement regulation (e.g., FAR 15.206(a)) if the substantive protest would not change the awarded value—the protest threshold is a pure dollar gate, not a gateway to merits review of orders below the threshold.

The upshot for practitioners

The indefinite-quantity contract is the workhorse of federal services acquisition and a major channel for supply procurement via GSA schedules and agency vehicles. It blends pre-competed contract award (full FAR Part 6 competition and FAR Part 15 evaluation at the basic-contract level) with streamlined order placement (fair opportunity, not full competition, at the task-order level). The minimum-guarantee requirement ensures the contract is binding and gives the contractor a floor revenue commitment; the maximum quantity disciplines the government's obligation and caps the contractor's performance risk. The statutory multiple-award preference reflects Congress's judgment that competition at the order level—enabled by multiple contract holders—drives better pricing, spurs innovation, and reduces the risk that a single awardee becomes entrenched. The fair-opportunity framework balances speed and flexibility with procedural fairness, permitting oral competitions, streamlined evaluations, and rapid award for urgent requirements while mandating heightened process discipline (evaluation-factor disclosure, written award rationale, debriefing rights) for orders over $7.5 million. The protest bar insulates the vast majority of task-order competitions from GAO and COFC review, a policy choice Congress made in 1994 to prevent the streamlined ordering process from collapsing under the weight of serial protests—disappointed awardees may complain to the agency's task-order ombudsman (required under FAR 16.505(b)(8)), but absent a $35 million / $10 million order or a colorable scope-increase claim, they have no right to external review. Practitioners negotiating onto a multiple-award IDIQ should therefore view the contract award as the critical gate (where full protest rights apply) and should assume that order-level disputes will be resolved through performance incentives, past-performance feedback, and the next fair-opportunity competition rather than through bid protests.

Source: FAR 16.504 Source: FAR 16.505 Source: 10 U.S.C. § 3406 Source: 41 U.S.C. § 4106

The fixed-price incentive (firm target) contract—FPIF in government shorthand—occupies a crucial middle position in the FAR Part 16 risk spectrum. It sits between the firm-fixed-price contract (where the contractor bears all cost risk and earns all savings or absorbs all overruns) and cost-reimbursement contracts (where the government bears cost risk subject to a ceiling). The FPIF vehicle gives the government the cost-control incentive of a fixed-price contract while acknowledging that cost uncertainty at award is real enough that the parties cannot yet lock in a final price—so they negotiate a formula that will adjust profit (but not price beyond a ceiling) based on the relationship between target cost and final negotiated cost after performance. FAR 16.403-1 governs the firm-target variant; FAR 16.403-2 covers the successive-targets variant (used when initial cost information is insufficient even to set firm targets at award). This section addresses the firm-target type, the workhorse of production contracting when cost history exists but performance risk or learning-curve uncertainty make a pure FFP contract inappropriate.

The four negotiated elements under FAR 16.403-1(a)

FAR 16.403-1(a) defines the FPIF contract as one that "specifies a target cost, a target profit, a price ceiling (but not a profit ceiling or floor), and a profit adjustment formula." These four elements are "all negotiated at the outset." The contract does not establish a final price at award—final price is determined after performance by applying the formula to the final negotiated cost. But the ceiling is fixed: "the price ceiling is the maximum that may be paid to the contractor, except for any adjustment under other contract clauses" (e.g., equitable adjustments for scope changes). If the final negotiated cost exceeds the ceiling, the contractor absorbs the difference as a loss. This ceiling feature makes the FPIF contract a true fixed-price vehicle under the FAR Part 16 taxonomy, even though profit adjusts with cost performance.

Target cost is the parties' best pre-award estimate of what performance will cost, negotiated using cost or pricing data under FAR 15.403-4 (certified if the contract exceeds the Truth in Negotiations Act threshold, currently $2.5 million for most acquisitions as of October 1, 2025, per FAR 15.403-4(a)(1)). Target profit is the profit percentage or dollar amount the contractor will earn if actual cost exactly equals target cost. The target price (the sum of target cost plus target profit) is not separately negotiated but follows directly from the first two elements and appears throughout FPIF contract administration.

The profit adjustment formula is typically expressed as a share ratio—for example, 80/20, 70/30, or 50/50. The first number is the government's share of cost variance (savings or overruns); the second is the contractor's share. Under an 80/20 share line, if the contractor underruns target cost by $1 million, the contractor's profit increases by 20% of the $1 million ($200,000), and the government retains 80% ($800,000) as a price reduction. Conversely, if the contractor overruns target cost by $1 million, the contractor's profit decreases by $200,000 (the contractor absorbs 20% of the overrun), and the government pays an additional $800,000 (80% of the overrun) up to the ceiling price. The formula incentivizes cost control—underruns increase profit, overruns erode it—but the government captures the majority of any savings.

Formula mechanics: underruns, overruns, and the point of total assumption

When performance is complete, the parties negotiate final cost under the procedures in the contract's price-revision clause (FAR 52.216-16, Incentive Price Revision—Firm Target). Final cost is the sum of all allowable, allocable, and reasonable costs incurred, applying the cost principles in FAR Part 31. (This is why FAR 16.403-1(c)(1) requires an adequate accounting system—discussed below—the government must be able to audit incurred costs to establish final cost.) The contracting officer and the contractor negotiate final cost; if they cannot agree, FAR 52.216-16(e) provides that "the Contracting Officer shall determine the final cost" unilaterally, subject to the disputes process under FAR Subpart 33.2.

Once final cost is established, the formula determines final profit:

• If final cost < target cost (underrun): Final profit = target profit + (contractor's share % × underrun amount). The contractor earns more than target profit. Final price = final cost + final profit, which will be less than target price—the government pays less than expected.

• If final cost = target cost (on target): Final profit = target profit. Final price = target price.

• If final cost > target cost but remains below the point where profit is exhausted (overrun within the share range): Final profit = target profit − (contractor's share % × overrun amount). The contractor earns less than target profit (profit erodes), but profit may remain positive if the overrun is modest. Final price = final cost + final profit, which will be greater than target price but less than or equal to ceiling price—the government pays more than target but is protected by the ceiling.

• If final cost drives profit to zero or negative, or if final price would exceed the ceiling: The contractor has absorbed all target profit through the share ratio and begins absorbing cost overruns dollar-for-dollar. Final price is capped at the ceiling. FAR 16.403-1(a) states: "If the final negotiated cost exceeds the price ceiling, the contractor absorbs the difference as a loss."

Practitioners commonly calculate the point of total assumption (PTA)—the final cost level at which the share-ratio formula would drive final price exactly to the ceiling price, meaning the contractor has absorbed all profit and begins incurring net losses. The PTA is a derived value (the FAR does not define or require it), calculated as:

PTA = Target Cost + ((Ceiling Price − Target Price) / Contractor Share Ratio)

For example, if target cost is $10 million, target profit is $1 million (target price $11 million), the ceiling is $13 million, and the share ratio is 70/30 (government 70%, contractor 30%), the PTA is:

PTA = $10M + (($13M − $11M) / 0.30) = $10M + ($2M / 0.30) = $10M + $6.67M = $16.67M.

If final cost reaches $16.67 million, the contractor's profit has been reduced by $1 million (30% of the $6.67M overrun), so final profit is zero and final price is $16.67M, which exceeds the $13M ceiling. The government pays only $13M; the contractor absorbs $3.67M as a loss. In practice, contractors monitor cost performance closely and—if trending toward the PTA—typically seek contract modifications (scope reduction, ceiling increase, or schedule relief) before performance becomes financially unsustainable. (This is a commercial response, not a FAR-mandated process.)

The suitability standard under FAR 16.403-1(b)

FAR 16.403-1(b) states that an FPIF contract "is appropriate when the parties can negotiate at the outset a firm target cost, target profit, and profit adjustment formula that will provide a fair and reasonable incentive and a ceiling that provides for the contractor to assume an appropriate share of the risk." This is a judgment call. The regulation identifies the two critical predicates: (1) the contracting officer and contractor can agree on a realistic target cost before award (which presupposes some cost history, similar prior programs, or sufficient technical maturity to permit cost estimation with reasonable confidence), and (2) the share ratio and ceiling can be set such that the contractor bears enough risk to motivate cost control but not so much that the contractor refuses to bid or demands an excessive risk premium in target profit.

FAR 16.403-1(b) adds a profit-calibration rule: "When the contractor assumes a considerable or major share of the cost responsibility under the adjustment formula, the target profit should reflect this responsibility." A 50/50 share ratio (equal cost-risk sharing) or a contractor-unfavorable ratio like 60/40 (contractor absorbs 40% of variance) imposes significant cost risk on the contractor, so target profit must be higher than on contracts with less risk. The profit analysis in FAR 15.404-4 (the weighted-guidelines method) explicitly accounts for cost risk; contracting officers applying that method to an FPIF negotiation assign higher profit weights to reflect the contractor's assumption of cost responsibility through the share ratio.

The two mandatory limitations under FAR 16.403-1(c)

FAR 16.403-1(c) imposes two threshold requirements—"This contract type may be used only when" both are met. (Emphasis added; these are gates, not factors.)

(1) Adequate contractor accounting system. "The contractor's accounting system is adequate for providing data to support negotiation of final cost and incentive price revision." This is the same accounting-system adequacy requirement that applies to cost-reimbursement contracts under FAR 16.301-3(a)(3). The contracting officer must verify—typically through a pre-award accounting-system audit conducted by the Defense Contract Audit Agency (DCAA) for DoD contracts, or the cognizant civilian-agency auditor for non-DoD contracts—that the contractor's system can segregate direct costs by contract, apply indirect-cost pools, and generate reliable incurred-cost data. If the contractor's accounting system has a significant deficiency (as defined in DFARS 252.242-7006 or civilian-agency equivalents), the system is not adequate and the contracting officer may not award an FPIF contract. For contractors required to comply with the Cost Accounting Standards (generally, contracts over the CAS-coverage threshold at FAR 30.201-4), an adequate system also presumes CAS compliance; major CAS noncompliance findings typically render a system inadequate for purposes of final-cost negotiation.

(2) Adequate cost or pricing information at award. "Adequate cost or pricing information for establishing reasonable firm targets is available at the time of initial contract negotiation." This prong distinguishes the firm-target variant from the successive-targets variant in FAR 16.403-2. If cost or pricing data are insufficient to permit negotiation of a realistic target cost at award—because the requirement is early-stage, the contractor has no relevant cost history, or technical uncertainty makes pre-award cost estimation speculative—the FPIF vehicle is not suitable. The contracting officer must either use a successive-targets contract (which sets initial targets and then re-negotiates firm targets at a specified production point) or move to a cost-reimbursement contract under FAR 16.301-2. The "adequate information" test is less stringent than the "fair and reasonable price" standard for firm-fixed-price contracts under FAR 16.202-2—the FPIF contract tolerates more cost uncertainty than FFP—but more demanding than the application standard for cost-reimbursement contracts, which permit award when "uncertainties involved in contract performance do not permit costs to be estimated with sufficient accuracy to use any type of fixed-price contract" (FAR 16.301-2(a)(2)).

DoD share-ratio guidance: 120% ceiling, 50/50 share as the point of departure

DFARS 216.403-1(a)(2) overlays a DoD-specific instruction: "The contracting officer shall pay particular attention to share lines and ceiling prices for fixed-price incentive (firm target) contracts, with a 120 percent ceiling and a 50/50 share ratio as the point of departure for establishing the incentive arrangement." This is not a mandate—the DFARS uses "point of departure," not "requirement"—but it is a strong norm. A 120% ceiling means the ceiling price is 120% of target cost. A 50/50 share ratio means the government and contractor split cost variance equally. If the contracting officer proposes a different share ratio (e.g., 70/30 government-favorable or 60/40 contractor-favorable) or a tighter or looser ceiling (110% or 130%), the contract file should document the rationale—why the default does not fit the risk profile of this acquisition.

The 50/50 default reflects DoD's judgment that equal cost-risk sharing provides a strong cost-control incentive (the contractor absorbs half of every overrun dollar) while keeping risk exposure within commercially reasonable bounds. A more government-favorable share ratio (e.g., 80/20) reduces the contractor's profit sensitivity to cost performance, which may weaken the incentive; a more contractor-unfavorable ratio (e.g., 40/60, contractor absorbs 60%) increases the contractor's exposure and typically triggers a demand for higher target profit. Civilian agencies are not bound by the DFARS default, but agency guides and contracting practice often reference the 120% / 50/50 point of departure as a reasonable baseline when program-specific data are lacking.

Mandatory D&F signed by the head of the contracting activity

FAR 16.401(d) imposes a categorical documentation requirement for all incentive contracts, including FPIF: "A determination and finding, signed by the head of the contracting activity, shall be completed for all incentive- and award-fee contracts justifying that the use of this type of contract is in the best interest of the Government." The D&F must be "documented in the contract file." This is a pre-award gate—the contracting officer may not execute the contract until the HCA (or authorized designee) has signed the D&F. For DoD FPIF contracts, DFARS 216.401(d)(ii) permits the D&F for incentive-fee contracts (as distinguished from award-fee contracts, which require HCA or one-level-below signature per DFARS 216.401(d)(i)) to be signed "one level above the contracting officer"—a lower threshold than the FAR's "head of the contracting activity," reflecting DoD's policy preference for objective incentive contracts over subjective award-fee contracts.

The D&F must explain why the FPIF contract type is in the government's best interest—typically, why a firm-fixed-price contract is not suitable (cost uncertainty too high, no adequate price competition or price history) and why a cost-reimbursement contract is not preferred (target cost is realistic enough to set a firm target, and shifting cost risk to the contractor via the share ratio will yield better cost control). The D&F is not lengthy—one to three pages is typical in practice—but it must affirmatively address the contract-type selection rationale and be signed at the required level before award.

Billing prices and interim payments under FAR 16.403(c)

Because final price is not established until after performance, FPIF contracts use billing prices as an interim payment mechanism. FAR 16.403(c) states that "billing prices are established as an interim basis for payment" and "may be adjusted, within the ceiling limits, upon request of either party to the contract, when it becomes apparent that final negotiated cost will be substantially different from the target cost." Billing prices are typically set at or near target cost during negotiation and incorporated into the contract schedule. The contractor submits invoices against the billing prices; the government pays promptly under the Prompt Payment Act. After final cost is negotiated and final price is calculated via the formula, the parties perform a price reconciliation: if the contractor was overpaid (final price < cumulative billing-price payments), the contractor refunds the difference or the government offsets it; if underpaid (final price > cumulative payments), the government pays the delta. The billing-price mechanism eliminates the voucher-by-voucher cost scrutiny that slows payment on cost-reimbursement contracts.

Fixed-price family: default remedies, not "best efforts"

Although the FPIF contract reimburses allowable incurred costs (like a cost-reimbursement contract) and adjusts profit by formula (unlike a pure FFP contract), it remains a fixed-price contract under FAR Part 16. This classification has a critical consequence: the contractor must deliver on time and in conformance with specifications, or be subject to termination for default under FAR Part 49, even if total costs exceed the ceiling price. On cost-reimbursement contracts, the contractor's obligation is to use "best efforts" to perform within the estimated cost (see FAR 52.232-20, Limitation of Cost, for cost contracts, and FAR 52.232-22, Limitation of Funds, for incrementally funded cost contracts). If a cost-reimbursement contractor is performing diligently but runs out of money, the government must either provide additional funding or accept the work as-is; termination for default is generally not appropriate when the contractor's "best efforts" defense applies. No such protection exists on FPIF contracts. If the contractor fails to deliver, the government may terminate for default under FAR 52.249-8 (the fixed-price default clause) and assess excess-reprocurement costs—even if the contractor's cost overrun was the cause of non-delivery. This fixed-price default exposure is one reason contractors seek higher target profit on FPIF contracts than on cost-reimbursement contracts: they are assuming not just cost risk via the share ratio, but performance risk as well.

The use case: production with learning-curve uncertainty, development with cost history

FPIF contracts are commonly used in two scenarios. First, production contracts with learning-curve or rate-uncertainty—the government is buying multiple units, the contractor has built prototypes, cost-per-unit history exists, but economies of scale, process improvements, or yield uncertainty make a locked-in FFP unit price speculative. An FPIF contract sets a target cost based on projected learning, negotiates a share ratio that rewards the contractor for beating the curve, and caps the government's exposure at the ceiling if learning does not materialize. Second, development contracts that have matured past the pure-research phase—the requirement is defined well enough to permit a target cost (so FAR 16.301-2's "cannot define requirements" prong is not met), cost data from earlier phases are available, but technical risk remains (integration challenges, first-article unknowns, test variability). An FPIF contract gives the contractor a profit incentive to control costs (unlike cost-plus-fixed-fee, where fee is invariant with cost performance) while protecting the government with a ceiling and a cost-audit right (unlike FFP, where the government pays the contract price regardless of actual cost).

The FPIF contract is not appropriate when cost uncertainty is low enough to support a firm-fixed-price contract (use FFP instead—lower administrative burden, stronger cost-control incentive from full contractor risk), nor when cost uncertainty is so high that realistic targets cannot be set (use cost-reimbursement or successive-targets FPIF under FAR 16.403-2 instead). It is the tool of choice for the middle ground under FAR Subpart 16.4: enough cost visibility to negotiate a target, enough uncertainty to justify a formula, and enough government concern about cost growth to demand a share of any overrun and a hard ceiling.

Source: FAR 16.403-1 Source: FAR 16.403 Source: FAR 16.401 Source: DFARS 216.403-1 Source: 90 FR 41872 (FAR inflation adjustment, effective October 1, 2025)

The fixed-price contract with economic price adjustment (FP-EPA) is the second fixed-price contract type enumerated in FAR Subpart 16.2 and one of only two contract types permitted in sealed-bid procurements and commercial-item acquisitions under restrictive policy rules. Unlike a firm-fixed-price contract, where the price is locked at award and may not be adjusted based on the contractor's cost experience, an FP-EPA contract "provides for upward and downward revision of the stated contract price upon the occurrence of specified contingencies" (FAR 16.203-1(a)). The contract establishes a base price and an adjustment mechanism triggered by external market events—changes in published catalog prices, actual labor or material costs incurred by the contractor, or movements in specified cost indexes—rather than by the contractor's efficiency or cost-control performance. This structure allows both parties to shift the risk of cost volatility outside either party's control (commodity-price swings, industry-wide wage increases, inflation-driven index movements) into a formulaic adjustment clause, reducing the need for the contractor to embed large contingency premiums into the initial bid price and reducing the government's exposure to contractor default when markets turn sharply against the contractor mid-performance.

The three adjustment types under FAR 16.203-1(a)

FAR 16.203-1(a) enumerates three general categories of economic price adjustment, each tied to a distinct triggering event and corresponding FAR clause prescription in FAR 16.203-4.

Adjustments based on established prices (FAR 16.203-1(a)(1)). These adjustments key off "increases or decreases from an agreed-upon level in published or otherwise established prices of specific items or the contract end items." The canonical use case is acquisition of commercial supplies—standard catalog items, off-the-shelf products, semistandard supplies customized only for packaging or preservation—for which the contractor maintains and publishes a price list to commercial customers. When the contractor raises (or lowers) its commercial catalog price during the performance period, the contract price adjusts in parallel by the percentage change, subject to ceiling and notice requirements in the clause. FAR 52.216-2 (Economic Price Adjustment—Standard Supplies) applies when the contract is for standard commercial items sold from an established catalog or market price; FAR 52.216-3 (Economic Price Adjustment—Semistandard Supplies) applies when the requirement is for semistandard supplies whose prices can be reasonably related to the prices of nearly equivalent standard supplies with an established catalog or market price. Both clauses impose a default cap: "The aggregate of the increases in any contract unit price under this clause shall not exceed 10 percent of the original contract unit price" (FAR 52.216-2(d)(1) and FAR 52.216-3(c)(1)). The contracting officer may modify the clause to increase this limit upon approval by the chief of the contracting office (FAR 16.203-4(a)(4) and (b)(6)). There is no percentage limitation on decreases—if the contractor's commercial price falls, the government receives the full benefit.

Adjustments based on actual costs of labor or material (FAR 16.203-1(a)(2)). These adjustments are "based on increases or decreases in specified costs of labor or material that the contractor actually experiences during contract performance." This type requires the contractor to disclose baseline labor rates (including fringe benefits) and material unit prices in the contract schedule; when those rates or prices change during performance—a negotiated wage increase, a shift in health-insurance premiums, a supplier's price hike on a key raw material—the contractor notifies the contracting officer and the parties negotiate an adjustment to the contract unit price to reflect the cost change. FAR 52.216-4 (Economic Price Adjustment—Labor and Material) is the standard clause. The clause imposes three significant limitations. First, adjustments are permitted only for changes in the specific labor rates and material unit prices shown in the contract schedule—"There shall be no adjustment for … changes in rates or unit prices other than those shown in the Schedule" (FAR 52.216-4(c)(2)). Second, "There shall be no adjustment for any change in rates of pay for labor (including fringe benefits) or unit prices for material which would not result in a net change of at least 3 percent of the then-current total contract price" (FAR 52.216-4(c)(3))—this materiality floor prevents administrative churn over minor cost fluctuations. Third, "The aggregate of the increases in any contract unit price made under this clause shall not exceed 10 percent of the original unit price" (FAR 52.216-4(c)(4)), with no limit on decreases. The contracting officer may modify the clause to increase the 10% cap upon approval by the chief of the contracting office (FAR 16.203-4(c)(5)). The contractor must notify the contracting officer within 60 days of the cost increase or decrease (or within an additional period the contracting officer approves in writing), but not later than the date of final payment (FAR 52.216-4(a)).

Adjustments based on cost indexes of labor or material (FAR 16.203-1(a)(3)). These adjustments use "increases or decreases in labor or material cost standards or indexes that are specifically identified in the contract"—for example, the Bureau of Labor Statistics Producer Price Index for a particular commodity or industry, a published steel-price index, or a regional construction wage index. The contracting officer and contractor agree at award on the index to be used, the baseline index value, the formula for translating index movement into price adjustment, and the frequency of adjustment (quarterly, semiannually, or upon a threshold percentage movement). FAR 16.203-4(d) does not prescribe a standard clause for index-based adjustments; instead, it instructs the contracting officer to insert "an appropriate clause, constructed as similarly as possible" to the labor-and-material clause at FAR 52.216-4. Index-based EPA clauses are less common than the other two types but are appropriate when (i) the contract involves an extended period of performance with significant costs to be incurred beyond one year after performance begins; (ii) the contract amount subject to adjustment is substantial; and (iii) the economic variables for labor and materials are too unstable to permit a reasonable division of risk between the government and the contractor without this type of clause (FAR 16.203-4(d)(1)). Use of an index-based EPA clause requires approval one level above the contracting officer (FAR 16.203-4(d)(2)). The index-based variant is typically tailored with explicit ceiling and floor percentages, minimum-adjustment thresholds, and retrospective or prospective effective-date rules to match the program's cost profile and the parties' tolerance for price volatility.

The two-prong application standard under FAR 16.203-2

FAR 16.203-2 establishes when an FP-EPA contract may be used. The regulation states that "a fixed-price contract with economic price adjustment may be used when (i) there is serious doubt concerning the stability of market or labor conditions that will exist during an extended period of contract performance, and (ii) contingencies that would otherwise be included in the contract price can be identified and covered separately in the contract." Both prongs must be met. The first prong requires genuine cost uncertainty tied to external market forces—not contractor inefficiency or technical risk—over a contract performance period long enough that pricing those uncertainties into a firm-fixed-price bid would either deter offerors or force the government to pay prohibitively large contingency premiums. A multi-year production contract for steel-intensive equipment during a period of volatile commodity pricing, a construction contract spanning two or more years in a region with rapidly escalating labor rates, or a long-lead-time supply contract for items dependent on imported materials subject to tariff or exchange-rate fluctuation would satisfy the "serious doubt" prong. The second prong requires that the cost drivers subject to volatility be identifiable and separable—the parties must be able to agree on which labor categories, which material line items, or which published indexes will trigger adjustment, and specify them in the contract schedule or an exhibit. If cost risk is diffuse, unquantifiable, or intertwined with the contractor's own cost-control decisions, the FP-EPA vehicle is not suitable and the contracting officer must either use a firm-fixed-price contract (accepting that the contractor will embed a risk premium in its bid) or a cost-reimbursement or incentive contract under the standards in FAR 16.301-2 or FAR 16.403-1.

FAR 16.203-2 adds two policy constraints on the scope of adjustments. "Price adjustments based on established prices should normally be restricted to industry-wide contingencies"—the regulation presumes that contractor-specific pricing decisions (a single supplier's strategic price cut to capture market share, for example) should not flow through to the government's contract price; only market-wide price movements that affect all similarly situated suppliers justify adjustment. "Price adjustments based on labor and material costs should be limited to contingencies beyond the contractor's control"—wage increases imposed by a union collective-bargaining agreement, statutory minimum-wage hikes, or tariff-driven import-cost increases are beyond the contractor's control and appropriately covered by an EPA clause; internal management decisions on overtime policy, workforce mix, or supplier selection are not. These are "should" standards, not absolute bars, but they frame the contracting officer's analysis of whether a proposed EPA clause structure aligns with FAR Part 16's risk-allocation philosophy.

FAR 16.203-2(a) imposes a baseline-setting discipline: "In establishing the base level from which adjustment will be made, the contracting officer shall ensure that contingency allowances are not duplicated by inclusion in both the base price and the adjustment requested by the contractor under economic price adjustment clause." If the contractor's proposed price already includes a contingency for anticipated steel-price increases and the contract also includes an EPA clause keyed to a steel-price index, the government would pay twice for the same risk—once embedded in the base price, once through the adjustment. The contracting officer must verify that the base price reflects current costs (or costs as of a specified baseline date) without built-in escalation assumptions that overlap the EPA mechanism. FAR 16.203-2(b) reinforces this obligation for contracts that do not require certified cost or pricing data (acquisitions below the Truth in Negotiations Act threshold at FAR 15.403-4, currently $2.5 million for most procurements as of October 1, 2024): "the contracting officer shall obtain adequate data to establish the base level from which adjustment will be made and may require verification of data submitted." The contracting officer may demand current commercial price lists, recent invoices from the contractor's suppliers for the specified materials, wage-rate certifications, or index values as of the baseline date to confirm that the starting point is accurate and not padded.

The mandatory threshold determination under FAR 16.203-3

FAR 16.203-3 establishes a categorical gate: "A fixed-price contract with economic price adjustment shall not be used unless the contracting officer determines that it is necessary either to protect the contractor and the Government against significant fluctuations in labor or material costs or to provide for contract price adjustment in the event of changes in the contractor's established prices." This is an affirmative determination—"shall not be used unless"—that the contracting officer must make and document in the contract file before including an EPA clause in the solicitation or contract. The regulation identifies two alternative grounds, each sufficient on its own. The first ground—"necessary … to protect … against significant fluctuations in labor or material costs"—applies when the market or economic conditions satisfy the FAR 16.203-2 application test (serious doubt about stability, identifiable contingencies) and neither party can reasonably absorb the cost-volatility risk. This ground typically supports labor-and-material or index-based EPA clauses in long-duration contracts where locking in a firm fixed price at award would expose the contractor to ruinous losses (and thus deter responsible bidders) or would induce the contractor to pad the bid price with a contingency so large that the government's expected total cost exceeds what it would pay under an FP-EPA structure with adjustment limits. The second ground—"necessary … to provide for contract price adjustment in the event of changes in the contractor's established prices"—applies to commercial-item acquisitions where the standard clause at FAR 52.216-2 or FAR 52.216-3 permits the contract price to track the contractor's catalog price. This ground reflects the commercial-marketplace principle: if the government is buying at a contractor's standard commercial price, and that price changes for all customers during the contract period, the contract price should adjust in parallel (subject to the 10% upward cap) rather than locking the government into a stale price that no longer reflects market conditions.

The determination is not separately documented in a formal determination and findings (D&F) under FAR 1.7—unlike time-and-materials contracts (FAR 16.601(d)(1)), cost-reimbursement contracts (FAR 16.301-3(a)), and incentive contracts (FAR 16.401(d))—but it must be explicit. The best practice is to address the FAR 16.203-3 determination in the written acquisition plan required under FAR 7.105 when the EPA clause is a significant feature of the contract structure, or at minimum to include a brief rationale in the contract file (price-negotiation memorandum, business-clearance memo, or contract-award documentation) explaining which of the two grounds applies and why a firm-fixed-price contract without an EPA clause is not suitable. When the determination is not made and documented, inclusion of an EPA clause in the solicitation is improper and may be challenged in a pre-award bid protest as an arbitrary contract-type decision inconsistent with the FAR Subpart 16.2 framework.

Permitted use in sealed bidding and commercial-item acquisition

FAR 16.102(a) mandates that "contracts resulting from sealed bidding shall be firm-fixed-price contracts or fixed-price contracts with economic price adjustment." No other contract type may be used under FAR Part 14 sealed-bid procedures. The FP-EPA vehicle is therefore the only mechanism available in sealed bidding to address cost uncertainty over an extended delivery period—a multi-year Indefinite-Delivery Contract (IDC) for standard supplies, for example, where the contractor's catalog price is expected to change annually. The evaluation remains strictly on price (FAR 14.201-8), but the bid price may include an EPA clause permitting adjustment per the schedule; the contracting officer awards to the low responsive, responsible bidder whose total evaluated price (including projected adjustments under the EPA clause, if the solicitation instructs bidders to project them for evaluation purposes) is lowest. FAR 14.408-4 governs use of EPA clauses in sealed bidding and requires the contracting officer to (a) include the adjustment clause in the invitation for bids (IFB), (b) provide sufficient information in the IFB to enable bidders to estimate the magnitude and frequency of adjustments, and (c) evaluate bids on a common basis, either by assuming no adjustment will occur or by applying a standard projection methodology to all bids.

For negotiated acquisitions of commercial products or commercial services, FAR 16.201(c) similarly constrains contract-type selection: "The contracting officer shall use firm-fixed-price or fixed-price with economic price adjustment contracts when acquiring commercial products and commercial services, except as provided in 12.207(b)." (The exception at FAR 12.207(b) permits time-and-materials or labor-hour contracts for commercial services under narrow conditions—competitive procedures plus a D&F that no other contract type is suitable.) The commercial-item presumption is that market pricing is inherently fair and reasonable, and that cost-reimbursement contracting (with its attendant cost-accounting-system requirements, FAR Part 31 allowability analysis, and government audit of incurred costs) is both unnecessary and inconsistent with commercial practice. When a commercial supplier's pricing fluctuates during the contract period—annual catalog updates, price adjustments tied to raw-material costs published in trade indexes, or contract terms that reference external benchmarks—an FP-EPA clause at FAR 52.216-2 or FAR 52.216-3 aligns the government contract with the supplier's standard commercial terms. The 10% upward-adjustment cap built into those clauses (which may be raised by the chief of the contracting office, per FAR 16.203-4(a)(4) and (b)(6)) provides the government with price predictability while still permitting the contractor to recover catalog-price increases within the capped range.

Compatibility with award-fee and performance incentives

FAR 16.203-1(b) expressly permits layering: "The contracting officer may use a fixed-price contract with economic price adjustment in conjunction with an award-fee incentive (see 16.404) and performance or delivery incentives (see 16.402-2 and 16.402-3) when the award fee or incentive is based solely on factors other than cost." When so combined, "the contract type remains fixed-price with economic price adjustment." This rule clarifies that an EPA clause addresses external cost volatility (market-driven changes in labor, material, or catalog prices), while award fees and performance incentives address contractor behavior (quality, schedule, technical performance). A production contract with an EPA clause keyed to a commodity-price index may simultaneously include a delivery-incentive clause under FAR 52.216-5 that reduces the contract price if the contractor delivers early or increases it if the contractor delivers late, or an award-fee plan that adjusts fee based on defect rates or customer-satisfaction scores. The EPA adjustment and the incentive adjustment are independent—the former is formulaic and triggered by external indices, the latter is evaluative and tied to the contractor's performance—and both operate on the contract price (or fee) without converting the contract into a cost-reimbursement or incentive-fee type under FAR Subpart 16.3 or 16.4.

The base-price and adjustment-frequency mechanics

An FP-EPA contract establishes a base price (or base unit price, if the contract is for multiple deliveries or units) as of a specified baseline date. For established-price clauses (FAR 52.216-2 and -3), the base price is the contractor's catalog or market price as of the contract date (or as of the date of the contractor's price list identified in the contract). For labor-and-material clauses (FAR 52.216-4), the contract schedule lists the specific labor categories with applicable hourly rates (including fringe benefits) and the material items with unit prices, all as of the contract date or as of a negotiated baseline date shortly before award. For index-based clauses, the contract identifies the index (by name, series number, and publication source) and the index value as of the baseline date. The clause then prescribes when and how adjustments are made. Established-price clauses typically permit adjustment upon the contractor's written request after the contractor has changed its commercial price, with the increase effective retroactively to the date of the commercial price change if the contracting officer receives notice within a specified period (10 days under FAR 52.216-2(c)(2) and FAR 52.216-3(c)(2)), or prospectively from the date of the request if notice is late. Labor-and-material clauses require the contractor to notify the contracting officer within 60 days of the cost change (FAR 52.216-4(a)), triggering negotiations; the contracting officer may defer negotiations until changes accumulate to at least the 3% materiality threshold (FAR 52.216-4(b)). Index-based clauses typically specify a fixed adjustment schedule (quarterly, semiannually, or annually) or a threshold index movement (e.g., 5% change from baseline) that triggers adjustment, with the effective date set prospectively from the date the threshold is met or the adjustment period begins.

Ceiling-price discipline and downward-adjustment symmetry

The standard FAR clauses at 52.216-2, -3, and -4 all impose a 10% aggregate cap on upward adjustments to any contract unit price. This ceiling is cumulative across all adjustments during the contract period—once the sum of all percentage increases reaches 10% of the original unit price, no further upward adjustments are permitted (though downward adjustments remain available). The 10% cap may be increased "upon approval by the chief of the contracting office" (FAR 16.203-4(a)(4), (b)(6), and (c)(5))—a one-level-above-the-contracting-officer gate that ensures institutional review before exposing the government to larger price growth. The cap does not apply to decreases: "There is no percentage limitation on the amount of decreases that may be made under this clause" (FAR 52.216-2(d)(1), FAR 52.216-3(c)(1), FAR 52.216-4(c)(4)). This asymmetry reflects the FAR's policy preference for capturing the full benefit of cost reductions for the government while limiting the government's exposure to cost growth. If the contractor's catalog price falls by 20% mid-performance, the contract price adjusts downward by the full 20%; if it rises by 20%, the contract price adjusts upward by only 10% (absent chief-of-contracting-office approval to raise the cap). For index-based EPA clauses, which are agency-prescribed rather than standard FAR clauses, the contracting officer typically negotiates a symmetric ceiling and floor (e.g., ±15%) to balance the parties' risk, but may impose an asymmetric structure (10% upward, unlimited downward) if the government's bargaining position or the market conditions warrant it.

Risk allocation compared to other FAR Part 16 types

The FP-EPA contract occupies a distinct niche in the FAR Part 16 risk continuum. It is less rigid than a firm-fixed-price contract—cost volatility tied to specified external triggers shifts to a formulaic adjustment rather than being absorbed entirely by the contractor—but it remains a fixed-price contract for all other cost risks. The contractor still bears the risk of its own inefficiency, technical performance failures, schedule slippage (absent excusable delay), and cost growth in labor or material categories not covered by the EPA clause. Unlike a cost-reimbursement contract (where the government reimburses allowable, allocable, and reasonable costs under FAR Part 31 and audits incurred costs), the FP-EPA contract requires no government audit of the contractor's books except to verify the baseline data or the triggering event (e.g., confirming that the contractor's published catalog price actually increased by the percentage claimed, or that the contractor actually paid the new wage rate shown in a collective-bargaining agreement). Unlike an FPIF contract (where final price is determined by a share-ratio formula applied to final negotiated cost), the FP-EPA contract's adjustment is not tied to total cost performance; it is mechanical and triggered solely by the specified contingency. The FP-EPA contract is therefore the vehicle of choice when cost uncertainty is externalized (market-driven, not contractor-driven), identifiable (specific labor rates, material items, or indexes), and limited in magnitude (the 10% default cap and the materiality thresholds in the standard clauses keep total price growth within a predictable band), but the requirement and technical performance are stable enough to support a fixed-price vehicle. When cost uncertainty is pervasive or intertwined with technical risk, the contracting officer must instead use a cost-reimbursement or incentive contract; when cost uncertainty is manageable or the contractor can price it into a contingency without deterring competition, a firm-fixed-price contract is preferable.

Source: FAR 16.203-1 Source: FAR 16.203-2 Source: FAR 16.203-3 Source: FAR 16.203-4 Source: FAR 16.201 Source: FAR 16.102

The cost-plus-award-fee (CPAF) contract is one of the five cost-reimbursement contract types enumerated in FAR Subpart 16.3 and is governed by the detailed rules for award-fee contracts in FAR 16.401(e). CPAF contracts are widely used in federal services acquisition—systems engineering and technical assistance (SETA), long-duration development programs, IT services, and any acquisition where performance quality depends on subjective judgments rather than objective metrics. The defining feature is a two-part fee structure: a base fee fixed at inception (which may be zero, at the contracting officer's discretion) plus an award-fee pool that the contractor may earn—in whole, in part, or not at all—based on periodic evaluations by a designated government official applying criteria stated in an award-fee plan. Unlike formulaic incentive contracts (CPIF under FAR 16.405-1 or FPIF under FAR 16.403-1), where fee adjusts mechanically based on cost or performance targets, the CPAF contract vests fee determination authority solely in the government's unilateral, subjective judgment of the contractor's overall performance in cost control, schedule adherence, and technical execution.

The two-element fee structure under FAR 16.405-2 and FAR 16.305

FAR 16.405-2 (cross-referenced by FAR 16.305) defines a cost-plus-award-fee contract as "a cost-reimbursement contract that provides for a fee consisting of (1) a base amount fixed at inception of the contract, if applicable and at the discretion of the contracting officer, and (2) an award amount that the contractor may earn in whole or in part during performance and that is sufficient to provide motivation for excellence in the areas of cost, schedule, and technical performance." The base fee is negotiated before award and is paid regardless of the contractor's performance, subject only to the contractor's delivery of at least minimum acceptable performance and compliance with contract terms. Many CPAF contracts set the base fee at zero, reserving the entire fee opportunity for the award-fee pool; when a base fee is included, it is typically small (DFARS 215.404-4(c)(4)(i) caps DoD base fees at three percent of estimated cost, exclusive of fee, for CPAF contracts) and functions as a floor to keep the contractor financially engaged even if award-fee evaluations are poor. The award fee is the variable component. It is not guaranteed. The contractor begins each evaluation period with zero percent of the available award fee and must earn it through performance (DFARS PGI 216.405-2, reflected in agency practice). The total award-fee pool—the sum of award-fee amounts available across all evaluation periods for the life of the contract—is established at award, but the contractor receives award-fee payments only after the Fee-Determining Official (FDO) evaluates performance for a completed evaluation period and determines how much of that period's allocated award fee the contractor has earned.

The three-prong suitability test under FAR 16.401(e)(1)

FAR 16.401(e)(1) establishes that an award-fee contract (whether cost-plus-award-fee or fixed-price-award-fee under FAR 16.404) is suitable for use only when three cumulative conditions are met. These are threshold requirements, not factors; if any prong is unsatisfied, the award-fee vehicle is not appropriate.

(i) Objective incentive targets are not feasible or effective. The work must be "such that it is neither feasible nor effective to devise predetermined objective incentive targets applicable to cost, schedule, and technical performance." This prong presumes that the contracting officer has considered whether a formulaic incentive contract—CPIF (with a target cost, fee-adjustment formula, and minimum/maximum fee) or FPIF (with a target cost, share ratio, and ceiling price)—could be structured to motivate the desired performance. If realistic targets can be set and cost or performance can be measured objectively at the end of performance, those contract types are preferred because they provide clearer contractor expectations and reduce the administrative burden of subjective periodic evaluations. Award-fee contracts are appropriate when the nature of the work makes objective target-setting impractical: service contracts whose quality turns on responsiveness, initiative, problem-solving, or customer satisfaction (dimensions that resist quantification); R&D contracts at the frontier of knowledge, where technical milestones are aspirational rather than firm; or system-integration contracts where success depends on coordination, communication, and adapting to evolving requirements. The key is that performance cannot be reduced to pass/fail deliverables or numeric cost/schedule targets without losing the evaluative nuance the government needs to distinguish exceptional, satisfactory, and unsatisfactory contractor effort.

(ii) Enhanced likelihood of meeting acquisition objectives. The second prong asks whether "the likelihood of meeting acquisition objectives will be enhanced by using a contract that effectively motivates the contractor toward exceptional performance and provides the Government with the flexibility to evaluate both actual performance and the conditions under which it was achieved." This prong recognizes that award-fee contracts impose a higher administrative burden than other contract types—periodic evaluations, Award-Fee Board meetings, Fee-Determining Official determinations, written feedback to the contractor—and that burden is justified only when the motivational upside and evaluative flexibility outweigh the cost. The contracting officer must determine that the prospect of earning additional fee through superior performance (or losing fee through mediocre performance) will drive contractor behavior in ways that a CPFF contract (where fee is fixed regardless of performance quality) or a pure fixed-price contract (where profit depends solely on cost control, not on quality or responsiveness) cannot. The "conditions under which performance was achieved" language permits the FDO to credit a contractor for overcoming obstacles beyond its control (supply-chain disruptions, customer-caused delays, poorly defined requirements) or to penalize a contractor for poor performance even when the end product meets minimum technical specifications.

(iii) Cost-benefit justification for administrative effort. The third prong mandates that "any additional administrative effort and cost required to monitor and evaluate performance are justified by the expected benefits as documented by a risk and cost benefit analysis to be included in the Determination and Findings referenced in 16.401(e)(5)(iii)." This is a formal documentation requirement (discussed below), but it also reflects a substantive policy constraint: award-fee contracts are resource-intensive. The government must staff an Award-Fee Board (typically composed of the contracting officer's representative, technical leads, cost analysts, and program-office personnel), convene the board at the end of each evaluation period (quarterly, semiannually, or annually per the award-fee plan), prepare detailed performance assessments against each award-fee criterion, present findings to the Fee-Determining Official, and provide feedback to the contractor. The contracting officer must determine—before award—that the expected benefits (better cost control, higher quality, improved schedule adherence, more proactive contractor engagement) justify these ongoing costs. For small-dollar contracts, short performance periods, or low-risk acquisitions, the administrative burden typically outweighs the incentive value, and a simpler contract type is appropriate.

Award-fee amount tied to overall cost, schedule, and technical performance under FAR 16.401(e)(2)

FAR 16.401(e)(2) establishes two cardinal rules for award-fee determination. First, "the amount of award fee earned shall be commensurate with the contractor's overall cost, schedule, and technical performance as measured against contract requirements in accordance with the criteria stated in the award-fee plan." The fee earned must track actual performance across all three dimensions—cost control, schedule adherence, and technical quality—not just one. A contractor that delivers excellent technical work but incurs cost overruns or misses interim milestones may earn reduced award fee; conversely, a contractor that controls cost and meets schedule but delivers marginal technical quality is not entitled to high award-fee scores. The phrase "in accordance with the criteria stated in the award-fee plan" ties the FDO's discretion to the plan incorporated into the contract at award; the FDO may not invent new criteria mid-performance or penalize the contractor for factors not identified in the plan.

Second, "award fee shall not be earned if the contractor's overall cost, schedule, and technical performance in the aggregate is below satisfactory." This is an absolute floor: unsatisfactory aggregate performance yields zero award fee for that evaluation period, regardless of strengths in individual areas. The FAR does not define "satisfactory," leaving agencies to calibrate the standard in their award-fee plans, but the typical formulation is that satisfactory performance meets contract requirements with no significant deficiencies and no contractor-caused cost or schedule impacts. FAR 16.401(e)(2) also requires that "the basis for all award-fee determinations shall be documented in the contract file to include, at a minimum, a determination that overall cost, schedule and technical performance in the aggregate is or is not at a satisfactory level." This documentation serves two purposes: it provides the contractor with substantive feedback (required for continuous improvement) and it creates a record for potential disputes or protests (though award-fee determinations are generally not protestable under the "subjective evaluation" doctrine, the administrative record must still demonstrate that the evaluation followed the plan's methodology). The regulation closes with the unilateral-discretion principle: "This determination and the methodology for determining the award fee are unilateral decisions made solely at the discretion of the Government." The contractor has no right to negotiate fee after performance; the FDO's determination is final, subject only to the requirement that it be consistent with the award-fee plan criteria.

The seven mandatory award-fee plan elements under FAR 16.401(e)(3)

FAR 16.401(e)(3) mandates that "all contracts providing for award fees shall be supported by an award-fee plan that establishes the procedures for evaluating award fee and an Award-Fee Board for conducting the award-fee evaluation." The plan is incorporated into the contract (by attachment or reference in the special contract requirements) and binds both parties. The regulation enumerates seven required elements; omitting any one renders the plan non-compliant and jeopardizes the award-fee contract's validity.

(i) Fee-Determining Official approval. Award-fee plans "shall be approved by the FDO unless otherwise authorized by agency procedures." The Fee-Determining Official is the government official designated to make the final award-fee determination for each evaluation period; typically, this is the program manager, the contracting officer's technical representative (if senior enough), or an official one or two levels above the program office. The FDO's pre-award approval of the plan ensures that the official who will make the fee decisions endorses the criteria, the rating scale, and the administrative process.

(ii) Link award-fee criteria to acquisition objectives. The plan must "identify the award-fee evaluation criteria and how they are linked to acquisition objectives which shall be defined in terms of contract cost, schedule, and technical performance." The criteria are the performance dimensions on which the contractor will be evaluated—examples include quality of deliverables, responsiveness to government direction, effectiveness of cost management, adherence to interim milestones, technical innovation, risk identification and mitigation, and customer satisfaction. Each criterion must map to one or more of the three statutory performance areas (cost, schedule, technical) and must be tied to the program's acquisition objectives as documented in the acquisition plan under FAR 7.105. The regulation adds a caution: "Criteria should motivate the contractor to enhance performance in the areas rated, but not at the expense of at least minimum acceptable performance in all other areas." This warns against constructing a plan that rewards gaming—e.g., incentivizing schedule acceleration so aggressively that the contractor cuts corners on quality, or rewarding cost underruns so heavily that the contractor defers necessary work to a follow-on contract.

(iii) Measurement against criteria. The plan must "describe how the contractor's performance will be measured against the award-fee evaluation criteria." This element requires the plan to specify the evidentiary basis for evaluation: what data sources the Award-Fee Board will review (progress reports, cost-performance reports, customer feedback surveys, inspection results, earned-value metrics), what standards define satisfactory versus excellent performance for each criterion, and how subjective assessments (e.g., "responsiveness to government direction") will be anchored in observable contractor actions. The description need not be exhaustive, but it must provide enough structure that the contractor understands what performance the government will examine and how that performance translates into an award-fee score.

(iv) Adjectival ratings, descriptions, and percentage bands per Table 16-1. The plan must "utilize the adjectival rating and associated description as well as the award-fee pool earned percentages shown below in Table 16-1." FAR 16.401(e)(3) reproduces a mandatory five-tier rating scale (the table is not reproduced here but is codified in the regulation): Excellent (generally 91–100% of available award fee for that period), Very Good (generally 76–90%), Satisfactory (generally 51–75%), Marginal (generally 0–50%, with a note that performance is minimally acceptable but significant improvement is needed), and Unsatisfactory (0%, with performance below minimum acceptable standards). The word "generally" signals that agencies may tailor the percentage bands within a narrow range, but the five-tier structure and the general percentage distribution are mandatory unless a statute or agency-head determination authorizes a deviation. The scale ensures consistency across CPAF contracts government-wide and anchors the FDO's subjective judgment to defined performance levels.

(v) Evaluation period frequency. The plan must "establish the frequency of evaluations (e.g., quarterly, semiannually, annually)." Evaluation periods are the intervals at which the Award-Fee Board assesses performance and the FDO determines the amount of award fee earned for that period. Shorter evaluation periods (quarterly or semiannual) provide more frequent feedback to the contractor and allow the government to adjust course if performance is slipping, but they impose higher administrative burden (more board meetings, more documentation). Longer periods (annual or at major milestones) reduce burden but delay feedback. The plan must specify the period length, the start and end dates for each period, and whether the final evaluation period covers performance through contract completion or only through the end of the last scheduled period. FAR 16.401(e)(3)(v) also cross-references the evaluation-timing and payment rules: for DoD CPAF contracts, DFARS 216.405-2(a)(2) prohibits interim award-fee payments except those tied to the evaluation at the end of an award-fee period, and requires the FDO's rating to be provided to the contractor within 45 calendar days of the period's end.

(vi) Composition and operation of the Award-Fee Board. The plan must "address the composition of the Award-Fee Board and the board's operational procedures." The board is the body that conducts the detailed performance assessment, applies the award-fee criteria, and recommends a rating and fee amount to the FDO. Typical board membership includes the contracting officer's representative (often the chair), government technical leads in relevant disciplines (engineering, IT, logistics), a cost or price analyst, and program-office representation. The plan should specify how the board will be appointed, the quorum requirements, whether the board's recommendation is by majority vote or consensus, and the format and content of the board's written recommendation to the FDO. The FDO is not bound by the board's recommendation—the FDO may adjust the rating or fee amount upward or downward—but agency practice (documented in DFARS PGI 216.401(e) and civilian-agency award-fee guides) generally expects the FDO to provide written rationale if departing significantly from the board's findings.

(vii) Award-fee pool allocation across evaluation periods. The plan must "define the total award-fee pool amount and how this amount is allocated across each evaluation period." The total pool is the sum of award fee available over the life of the contract; it is negotiated as part of fee analysis under FAR 15.404-4 and fixed at award. The allocation determines how much of the total pool is at stake in each evaluation period. An even allocation (e.g., $400,000 pool over four annual periods = $100,000 per period) treats all performance equally. A weighted allocation (e.g., 10% / 20% / 30% / 40% over four periods) front-loads or back-loads the incentive. DFARS 216.405-2(a)(1) imposes a DoD-specific rule: "The contracting officer shall perform an analysis of appropriate fee distribution to ensure at least 40 per cent of the award fee is available for the final evaluation so that the award fee is appropriately distributed over all evaluation periods to incentivize the contractor throughout performance of the contract." This back-loading rule reflects DoD's judgment that contractors often focus disproportionately on early-period performance when fee is front-loaded, then allow quality or cost control to slip in later periods; reserving at least 40% of the pool for the final evaluation sustains the incentive through contract closeout. The 40% floor may be reduced only if the contracting officer documents the rationale and the head of the contracting activity (HCA) approves; HCA approval may not be delegated (DFARS 216.405-2(a)(1)).

Rollover prohibition under FAR 16.401(e)(4)

FAR 16.401(e)(4) flatly prohibits the practice of "rollover of unearned award fee"—defined in FAR 16.001 as "the process of transferring unearned award fee, which the contractor had an opportunity to earn, from one evaluation period to a subsequent evaluation period, thus allowing the contractor an additional opportunity to earn that previously unearned award fee." If a contractor earns 60% of the available award fee in Period 1, the remaining 40% is lost; it does not carry forward to Period 2. The rationale is accountability: permitting rollover dilutes the incentive structure by allowing a contractor to recover from poor performance in one period by excelling in a later period, which undermines the prompt-feedback and continuous-improvement purposes of the award-fee mechanism. The prohibition applies to all CPAF contracts, with no exceptions. (Note that the base fee, if any, is paid in installments under the contract's payment clause and is not subject to the rollover concept—only the award-fee portion is at risk each period.)

The three mandatory limitations under FAR 16.401(e)(5)

FAR 16.401(e)(5) imposes three cumulative prerequisites that must be satisfied before any award-fee contract may be awarded. These limitations apply to both cost-plus-award-fee and fixed-price-award-fee contracts.

(i) Compliance with cost-reimbursement limitations (for CPAF only). "All of the limitations in 16.301-3, that are applicable to cost-reimbursement contracts only, are complied with." For cost-plus-award-fee contracts, this incorporates the full suite of cost-reimbursement prerequisites: the contracting officer must determine that circumstances do not allow the agency to define requirements sufficiently for a fixed-price contract, or that uncertainties in cost estimation do not permit use of a fixed-price contract (FAR 16.301-2); the acquisition plan must document the contract-type rationale and be approved one level above the contracting officer (FAR 16.301-2(b)); the contractor's accounting system must be adequate for determining costs (FAR 16.301-3(a)(3)); and adequate government resources must be available to manage the contract, including designation of at least one qualified COR before award (FAR 16.301-3(a)(4)). CPAF contracts are also categorically prohibited for acquisition of commercial products and commercial services under FAR 16.301-3(b) and FAR 12.207.

(ii) Award-fee plan completed per 16.401(e)(3). "An award-fee plan is completed in accordance with the requirements in 16.401(e)(3)." This reiterates that the seven-element award-fee plan is not optional; it must be finished, approved by the FDO, and incorporated into the solicitation and contract documents before award. If the plan is incomplete or non-compliant, the award-fee contract may not be executed.

(iii) Determination and findings addressing suitability. "A determination and finding is completed in accordance with 16.401(d) addressing all of the suitability items in 16.401(e)(1)." FAR 16.401(d) mandates that "a determination and finding, signed by the head of the contracting activity, shall be completed for all incentive- and award-fee contracts justifying that the use of this type of contract is in the best interest of the Government." For award-fee contracts specifically, the D&F must address all three suitability prongs in FAR 16.401(e)(1): the infeasibility or ineffectiveness of objective targets, the enhanced likelihood of meeting acquisition objectives, and the cost-benefit justification for the administrative effort. The D&F must also incorporate the risk and cost benefit analysis mentioned in prong (iii). For DoD CPAF contracts, DFARS 216.401(d)(i) permits the D&F to be signed by the head of the contracting activity or a designee no lower than one level below the HCA; for civilian agencies, the FAR default is HCA signature, though agency supplements may authorize one-level-below delegation. The D&F is a pre-award gate—the contracting officer may not execute the contract until it is signed and in the file.

DoD-specific constraints under DFARS 216.405-2

DFARS 216.405-2 overlays several additional rules for DoD cost-plus-award-fee contracts. First, base fees are capped at three percent of estimated cost exclusive of fee (DFARS 215.404-4(c)(4)(i)). Second, the weighted-guidelines profit-analysis method in FAR 15.404-4(d) may not be applied to CPAF contracts for either the base fee or the award fee (DFARS 215.404-4(c)(4)(ii))—DoD contracting officers must use alternative fee-analysis approaches documented in DFARS PGI 215.404-4. Third, award-fee payments other than those resulting from evaluation at the end of a period are prohibited (DFARS 216.405-2(a)(2))—no "interim" or "provisional" award-fee advances are permitted. Fourth, the FDO's rating must be provided to the contractor within 45 calendar days of the period's end (DFARS 216.405-2(a)(2)). Fifth, at least 40% of the award-fee pool must be allocated to the final evaluation unless the HCA approves a lower percentage (DFARS 216.405-2(a)(1)). These rules do not apply to civilian-agency CPAF contracts unless the agency has adopted parallel limitations in its acquisition regulation supplement.

The use case: services and R&D when objective metrics are unavailable

Cost-plus-award-fee contracts are the contract type of choice—and often the only viable option—when three conditions converge. First, the work is cost-reimbursement in character under the FAR 16.301-2 application test (requirements or cost uncertainty precludes fixed-price contracting). Second, performance quality depends on dimensions that resist objective measurement—responsiveness, initiative, customer satisfaction, problem anticipation, technical judgment, communication effectiveness. Third, the government is willing to commit the resources (Award-Fee Board, periodic evaluations, FDO time) to conduct and document subjective assessments. Typical applications include systems engineering and technical assistance (SETA) contracts, where the contractor provides advisory support and the quality of that advice cannot be reduced to pass/fail deliverables; long-duration software development or system integration, where technical performance turns on architecture decisions, code quality, and collaboration rather than on whether the system boots; base operations and maintenance services, where performance is measured by facility readiness, tenant satisfaction, and proactive problem-solving; R&D contracts where the frontier of knowledge makes objective technical milestones speculative; and program-management support contracts, where success depends on the contractor's ability to keep complex programs on track through coordination, risk management, and stakeholder engagement. In each scenario, a CPFF contract would provide no performance incentive beyond the fixed fee, a CPIF contract cannot be structured because realistic cost targets are unavailable, and a fixed-price contract (even with award-fee overlay under FAR 16.404) is unsuitable because cost risk cannot be meaningfully shifted to the contractor. The CPAF contract fills that gap by tying fee to the government's ongoing, holistic assessment of contractor performance—an administratively demanding but often indispensable mechanism for motivating excellence when the work resists formulaic incentives.

Source: FAR 16.305 Source: FAR 16.401 Source: FAR 16.405-2 Source: FAR 16.301-3 Source: DFARS 216.405-2

The cost-plus-fixed-fee (CPFF) contract is the most widely used cost-reimbursement contract type in federal acquisition when the government requires work that cannot be defined with sufficient specificity or cost certainty to permit fixed-price contracting, yet the parties can negotiate a reasonable fixed fee at the outset. FAR 16.306(a) defines a CPFF contract as "a cost-reimbursement contract that provides for payment to the contractor of a negotiated fee that is fixed at the inception of the contract." The fixed fee does not vary with actual cost—whether the contractor incurs 80% or 120% of the estimated cost, the fee remains the same—but the fee may be adjusted as a result of changes in the work to be performed under the contract. This invariance is both the contract type's defining feature and its central policy tension: "This contract type permits contracting for efforts that might otherwise present too great a risk to contractors, but it provides the contractor only a minimum incentive to control costs" (FAR 16.306(a)). The government accepts cost risk (reimbursing all allowable, allocable, and reasonable costs subject to the estimated-cost ceiling) in exchange for the contractor's willingness to undertake high-uncertainty work; the contractor accepts a fixed fee (rather than the potential for higher profit through cost underruns, as in CPIF or FPIF contracts) in exchange for freedom from cost overrun exposure (beyond the best-efforts obligation discussed below).

The two-prong suitability standard under FAR 16.306(b)

FAR 16.306(b)(1) establishes when a CPFF contract is suitable: "when the conditions of 16.301-2 are present"—meaning the contracting officer has determined under FAR 16.301-2(a) that either (i) circumstances do not allow the agency to define its requirements sufficiently to allow for a fixed-price contract, or (ii) uncertainties in contract performance do not permit costs to be estimated with sufficient accuracy to use any type of fixed-price contract—"and, for example," one of two scenarios applies. The word "example" signals that the two scenarios are illustrative, not exhaustive, but they define the core use case for CPFF contracts.

The first scenario is research or early-stage exploration where the level of effort is unknown: "(i) The contract is for the performance of research or preliminary exploration or study, and the level of effort required is unknown" (FAR 16.306(b)(1)(i)). This prong covers basic research, feasibility studies, proof-of-concept work, and preliminary investigations where the government seeks an answer to a question but cannot predict in advance how many labor hours, iterations, or approaches will be necessary to reach a conclusion. The contractor commits to apply effort diligently (the "best efforts" standard under the limitation-of-cost clause at FAR 52.232-20 or limitation-of-funds clause at FAR 52.232-22), but the government cannot define success as delivery of a specific end product on a fixed schedule—only as pursuit of the research objective within the estimated cost.

The second scenario is development and test work that has not yet matured to the point where a cost-incentive contract is feasible: "(ii) The contract is for development and test and the contractor is required to explore an unreduced number of approaches and furnish findings without conclusions or recommendations" (FAR 16.306(b)(1)(ii)). This prong applies when the government needs the contractor to examine multiple technical solutions, conduct comparative testing, or generate data that the government will analyze internally to inform later acquisition decisions. The work is more structured than pure research—there is a test plan, a set of approaches to explore—but the government has not yet narrowed the field to a single preferred solution or established firm performance targets, so a CPIF contract (which requires a realistic target cost and a fee-adjustment formula tied to cost performance) is not practical.

FAR 16.306(b)(2) imposes a critical constraint that appears nowhere else in FAR Subpart 16.3's enumeration of cost-reimbursement types: "A cost-plus-fixed-fee contract normally should not be used in development of major systems (see part 34) once preliminary exploration, studies, and risk reduction have indicated a high degree of probability that the development is achievable and the Government has established reasonably firm performance objectives and schedules." This is a maturation gate. Once a major-system program has progressed from the preliminary-exploration phase (where CPFF is appropriate) to a point where technical feasibility is demonstrated, cost history is available, and performance objectives are firm, the contracting officer must transition to a contract type that provides stronger cost-control incentives—typically CPIF (if cost targets can be set but cost uncertainty remains significant) or FPIF (if cost estimation is mature enough to support a firm target cost, share ratio, and ceiling price). The "normally should not" phrasing leaves the contracting officer narrow discretion to use CPFF in later development phases when exceptional circumstances justify the minimum-incentive structure, but the default policy is clear: CPFF is a tool for the uncertain, early stages of a program, not for production or mature development.

The completion form: delivery obligation and fee conditionality under FAR 16.306(d)(1)

FAR 16.306(c) divides CPFF contracts into two forms: completion and term. The distinction turns on the nature of the contractor's obligation and the conditions for payment of the fixed fee. FAR 16.306(d)(1) describes the completion form: "The completion form describes the scope of work in terms of a definite goal or target and specifies an end product or result in terms of reliability or other objective criteria (e.g., a final report of research accomplishing the goal or target)." Under this form, "the contractor is required to complete and deliver the specified end product (e.g., a final report of research accomplishing the goal or target) within the estimated cost, if possible, as a condition for payment of the entire fixed fee."

The completion form imposes a delivery obligation—the contractor must furnish the specified end product. If the work cannot be completed within the estimated cost, FAR 16.306(d)(1) grants the government a unilateral right: "However, in the event the work cannot be completed within the estimated cost, the Government may require more effort without increase in fee, provided the Government increases the estimated cost." The government may add funding and compel continued performance at the same fixed fee, even if the contractor has already expended the original estimated cost. This right is not unlimited—it is subject to the "best efforts" standard embedded in the limitation-of-cost clause (FAR 52.232-20 for fully funded CPFF contracts) or the limitation-of-funds clause (FAR 52.232-22 for incrementally funded CPFF contracts), which obligates the contractor to notify the contracting officer when costs will reach a percentage threshold (typically 75% or 85%) of the estimated cost and relieves the contractor of further performance obligation if the government does not increase funding. But within the scope of that funding discipline, the completion form's fee conditionality shifts completion risk to the contractor: if the contractor fails to deliver the specified end product and the government has provided adequate funding, the contractor is not entitled to the full fee—partial fee payment may be negotiated, or the government may withhold fee entirely under the fixed-fee clause at FAR 52.216-8.

The completion form is appropriate when the contracting officer can define the end product or goal with enough specificity to permit the contractor to estimate the effort required to complete the work, even if cost uncertainty or technical risk precludes a fixed-price contract. A research contract calling for a final technical report documenting findings, a prototype development contract requiring delivery of a functioning breadboard unit, or a systems engineering study requiring a trade-off analysis and recommended solution architecture would typically use the completion form. The contractor's obligation is to deliver the defined result; the government's obligation is to reimburse allowable costs (subject to the estimated-cost ceiling) and pay the fixed fee upon successful delivery.

The term form: level-of-effort obligation and time-based fee payment under FAR 16.306(d)(2)

FAR 16.306(d)(2) describes the term form: "The term form describes the scope of work in general terms and obligates the contractor to devote a specified level of effort for a stated time period." Under this form, success is measured not by delivery of an end product but by expenditure of the agreed level of effort over the contract period. "Under this form, if the performance is considered satisfactory by the Government, the fixed fee is payable at the expiration of the agreed-upon period, upon contractor statement that the level of effort specified in the contract has been expended in performing the contract work." The contractor earns the fee by performing diligently for the required duration—typically expressed as a number of labor hours per month, or full-time-equivalent staff over a stated period—not by completing a deliverable. The government evaluates whether performance was "satisfactory" (meeting the general scope of work and quality standards in the contract), but the fee does not turn on successful completion of a defined goal.

FAR 16.306(d)(2) clarifies that term contracts are not evergreen arrangements: "Renewal for further periods of performance is a new acquisition that involves new cost and fee arrangements." Each successive period requires a new contract or modification negotiating fresh cost estimates and fee; the term form does not automatically extend beyond its stated period.

The mandatory preference for completion over term under FAR 16.306(d)(3)

FAR 16.306(d)(3) establishes an explicit hierarchy: "Because of the differences in obligation assumed by the contractor, the completion form is preferred over the term form whenever the work, or specific milestones for the work, can be defined well enough to permit development of estimates within which the contractor can be expected to complete the work." This is a "preferred" standard—stronger than a suggestion, weaker than a prohibition. The policy rationale is straightforward: the completion form imposes a delivery obligation, which aligns the contractor's incentive (earn the fee by delivering the product) with the government's interest (obtain the result) more tightly than the term form, under which the contractor earns the fee simply by expending hours. When the contracting officer can articulate a sufficiently clear goal or milestone—even if the path to that goal is uncertain and costs are difficult to estimate—the completion form should be used. The term form is appropriate only when the work genuinely cannot be scoped beyond a general level-of-effort commitment: advisory services where the contractor provides on-call expertise, systems engineering and technical assistance (SETA) support where the contractor augments government staff without producing discrete deliverables, or exploratory research where the government seeks sustained investigation over a period without committing to a specific finding or outcome.

FAR 16.306(d)(4) reinforces the constraint: "The term form shall not be used unless the contractor is obligated by the contract to provide a specific level of effort within a definite time period." A contract that obligates the contractor merely to "perform services as requested" or "provide support" without specifying the labor hours, staff positions, or level of effort is not a valid term-form CPFF contract—it lacks the definiteness necessary to make the contract binding and to permit the government to evaluate whether the contractor has satisfied the fee-payment condition.

Fee adjustment for scope changes but not cost performance

FAR 16.306(a) states that the fixed fee "does not vary with actual cost, but may be adjusted as a result of changes in the work to be performed under the contract." This is the key distinction between CPFF and the two cost-reimbursement incentive types (CPIF at FAR 16.405-1 and CPAF at FAR 16.305/16.405-2). On a CPIF contract, the fee adjusts according to a formula as actual costs underrun or overrun the target cost; on a CPAF contract, the award fee varies based on the government's subjective evaluation of performance. On a CPFF contract, the fee is invariant with cost performance—cost underruns do not increase fee, cost overruns (within the estimated-cost ceiling) do not decrease fee—but the fee may be adjusted upward or downward through bilateral modification when the government changes the scope of work. If the government adds tasks, increases deliverables, or extends the period of performance beyond the original scope, the contracting officer negotiates an equitable adjustment to both the estimated cost and the fixed fee under the Changes clause (FAR 52.243-2 for cost-reimbursement contracts). Conversely, if the government descopes work—deletes deliverables, narrows the research objective, or reduces the level of effort on a term contract—the fee is reduced in proportion to the scope reduction. The adjustment is not automatic; it requires a negotiated modification. Absent a scope change, the fee remains fixed regardless of the contractor's actual cost experience.

Compliance with cost-reimbursement limitations under FAR 16.301-3

FAR 16.306(c) cross-references FAR 16.301-3 for limitations: "See 16.301-3 for limitations" on use of CPFF contracts. This incorporation by reference means that all four prerequisites in FAR 16.301-3(a) must be satisfied before a CPFF contract may be awarded: (1) the contracting officer must determine that requirements cannot be sufficiently defined for a fixed-price contract, or that cost uncertainties preclude fixed-price contracting (FAR 16.301-2); (2) the acquisition plan must document the contract-type rationale and be approved one level above the contracting officer (FAR 16.301-2(b) and 16.301-3(a)(2)); (3) the contractor's accounting system must be adequate for determining costs applicable to the contract (FAR 16.301-3(a)(3)); and (4) adequate government resources must be available to manage the contract, including designation of at least one qualified COR before award (FAR 16.301-3(a)(4)). CPFF contracts are also categorically prohibited for acquisition of commercial products or commercial services under FAR 16.301-3(b) and FAR 12.207(a)—if the supplies or services meet the commercial-item definition in FAR 2.101, the contracting officer must use firm-fixed-price or fixed-price with economic price adjustment, or (for commercial services only, under the narrow exception in FAR 12.207(b)) time-and-materials or labor-hour contracts following competitive procedures and execution of a D&F.

The minimum-incentive trade-off and when to use CPFF instead of CPIF or CPAF

The central tension in CPFF contracting is the "minimum incentive to control costs" acknowledged in FAR 16.306(a). Because the contractor's fee is fixed regardless of cost performance, the contractor has no financial incentive to underrun the estimated cost—doing so does not increase profit. The contractor's obligation is to perform the work diligently and within the estimated cost if possible, but cost efficiency does not translate to reward. This stands in sharp contrast to CPIF contracts, where the contractor earns a share of cost savings (and absorbs a share of cost overruns) through the fee-adjustment formula, and to CPAF contracts, where cost control is one of the evaluation criteria for award-fee determination. The government accepts this minimum-incentive structure when the nature of the work makes objective cost targets (necessary for CPIF) or subjective periodic evaluations (necessary for CPAF) impractical or administratively burdensome.

CPFF is appropriate when the work is genuinely exploratory—the contractor cannot predict in advance how many iterations, tests, or approaches will be required—and when the government values delivery of the research findings or exploration results more than it values cost efficiency. It is also appropriate when the contract is relatively small in dollar value or short in duration, such that the administrative overhead of a CPIF share-ratio negotiation and final-cost reconciliation, or the Award-Fee Board meetings and fee-determination memoranda required for CPAF, would exceed the expected benefit of the cost-control incentive. For large-dollar, long-duration cost-reimbursement contracts where cost control is a significant government concern, the contracting officer should use CPIF (if realistic cost targets can be negotiated) or CPAF (if cost or performance cannot be reduced to objective metrics but subjective evaluation is feasible) rather than defaulting to CPFF. FAR 16.306(b)(2)'s admonition against using CPFF in later-stage major-system development reflects this policy: once a program matures, the government should demand stronger cost incentives than the fixed fee provides.

Contract clauses: fixed fee, limitation of cost, and allowable cost

FAR 16.307 prescribes the clauses for cost-reimbursement contracts. For CPFF contracts, the contracting officer must include FAR 52.216-8 (Fixed Fee), which specifies the amount of the fixed fee, the payment schedule (typically in installments as costs are incurred, with a percentage withheld until contract completion or acceptance), and the conditions under which the fee becomes payable. For fully funded CPFF contracts, the contracting officer includes FAR 52.232-20 (Limitation of Cost), which establishes the estimated cost, requires the contractor to notify the contracting officer when costs will reach a specified percentage of the estimate (usually 75%), and relieves the contractor of further performance obligation if the government does not increase the estimated cost before it is reached. For incrementally funded CPFF contracts, FAR 52.232-22 (Limitation of Funds) serves a parallel function, capping the contractor's reimbursement at the currently allotted amount and requiring notice before that amount is reached. FAR 52.216-7 (Allowable Cost and Payment) governs cost reimbursement, specifying that the government will reimburse the contractor for allowable costs determined in accordance with FAR Part 31 and the contract's cost principles, and establishing the invoice and payment procedures.

For completion-form CPFF contracts, the fixed-fee clause conditions payment of the fee on delivery of the specified end product; for term-form CPFF contracts, the clause conditions payment on satisfactory expenditure of the specified level of effort over the stated period. The distinction is operationalized in the clause's fee-payment paragraph, which the contracting officer tailors to match the contract form selected.

The use case: research, early-stage development, and level-of-effort services

CPFF contracts are the workhorse of federal R&D contracting and the contract type of choice—often the only viable option—for three scenarios. First, basic and applied research where the level of effort cannot be predicted in advance: university research grants (though often structured as grants rather than procurement contracts, when they do take contract form they are typically CPFF completion contracts), exploratory studies for new technologies, and preliminary feasibility analyses all fit this pattern. The government wants the research findings, but cannot define in advance how many experiments, simulations, or iterations will be required to reach a scientifically supportable conclusion. Second, early-stage development and test where multiple technical approaches must be explored and requirements have not yet crystallized: proof-of-concept prototypes, trade-off studies examining alternative architectures, and risk-reduction efforts in advance of a major acquisition decision typically use CPFF completion contracts to deliver findings without locking in a single solution prematurely. Third, level-of-effort services where the contractor provides sustained expertise or support over a period without producing discrete deliverables: SETA contracts supporting government program offices, advisory and assistance services in specialized technical disciplines, and on-call engineering support often use CPFF term contracts to secure the contractor's commitment of qualified staff for a defined period.

In each scenario, the government cannot—at the time of award—define the work tightly enough to support a fixed-price contract, or estimate costs accurately enough to set a realistic CPIF target, or structure objective evaluation criteria for a CPAF award-fee plan. The CPFF contract bridges that gap by shifting cost risk to the government (reimbursing all allowable costs within the estimated-cost ceiling) and fixing the fee at a level sufficient to induce the contractor to perform, while accepting that the contractor's profit will not vary with cost performance. The administrative price is ongoing cost oversight (DCAA audits, COR surveillance, voucher review under FAR Part 31 cost principles), the same burden the government bears on all cost-reimbursement contracts. The policy trade-off is that the government obtains access to contractor capability for high-uncertainty work that the contractor would refuse to undertake on a fixed-price or high-risk-share incentive basis, at the cost of accepting minimal contractor incentive to control costs once the contract is awarded.

Source: FAR 16.306 Source: FAR 16.301-2 Source: FAR 16.301-3

A letter contract is a high-stakes, time-limited contract vehicle reserved for acquisitions where the government's operational needs demand immediate contractor performance but negotiating a definitive contract in time is not possible. FAR 16.603-1 defines a letter contract as "a written preliminary contractual instrument that authorizes the contractor to begin immediately manufacturing supplies or performing services." The letter contract is binding on both parties—the contractor incurs cost risk (subject to a government-liability ceiling), the government commits to definitize or determine price and terms within a statutory window—but it is explicitly preliminary, a bridge to a definitive contract, not an end state. Letter contracts carry mandatory institutional approvals, strict limitations on use, and aggressive conversion deadlines that distinguish them from other undefinitized vehicles (such as unpriced orders under FAR 13.302-2 or basic ordering agreements under FAR 16.703). They appear most often in urgent operational scenarios—prototype or production acceleration to meet theater demand, emergency repair or logistics surge, rapid technology insertion when delay would jeopardize mission success—but their use is tightly regulated to prevent them from becoming a default workaround for poor acquisition planning.

The two-prong application standard under FAR 16.603-2(a)

FAR 16.603-2(a) establishes the threshold conditions: "A letter contract may be used when (1) the Government's interests demand that the contractor be given a binding commitment so that work can start immediately and (2) negotiating a definitive contract is not possible in sufficient time to meet the requirement." Both prongs must be satisfied; if either is not met, the letter contract is unavailable and the contracting officer must use another vehicle or delay the requirement. The first prong—government's interests demand immediate start—requires genuine urgency tied to mission need, not administrative convenience or acquisition-office workload. Examples that satisfy this prong include operational imperatives (theater commanders need equipment or services on compressed timelines that do not permit the months-long FAR Part 15 negotiated-procurement cycle), technology windows (an emerging threat requires fielding a countermeasure before the adversary adapts, and delay for full definitization would close the opportunity), and supply-chain or production-line risks (a critical supplier will shut down a production line or reallocate capacity unless the government commits immediately). The urgency must be documented; FAR 16.603-3's mandatory determination by the head of the contracting activity (discussed below) requires the contracting officer to explain why the requirement cannot wait.

The second prong—negotiating a definitive contract is not possible in sufficient time—presumes the contracting officer has made reasonable efforts to structure a definitive contract (firm-fixed-price, cost-reimbursement, or one of the other FAR Part 16 types) and concluded that the time required to negotiate terms, establish price or cost, verify cost or pricing data under FAR 15.403-4, conduct a pre-award accounting-system review (if cost-reimbursement is contemplated), or complete technical discussions would cause unacceptable delay. This is not a license to skip negotiation because it is hard; it is recognition that mission tempo or external constraints make pre-award definitization genuinely infeasible. The regulation adds a completeness discipline: "However, a letter contract should be as complete and definite as feasible under the circumstances" (FAR 16.603-2(a)). Even under urgency, the contracting officer must define the scope of work, specify deliverables or performance standards, identify the type of definitive contract contemplated (FFP, CPFF, T&M, etc.), and include the clauses that will govern the definitized contract—the only elements left undefinitized are price (or estimated cost and fee) and any terms that turn on price negotiation (such as cost-accounting-system adequacy findings for cost-reimbursement). A letter contract that authorizes the contractor to "perform services as directed" with no statement of work, no ceiling price, and no definitization schedule is not merely incomplete—it is likely unenforceable and certainly noncompliant with FAR 16.603-2(a).

Mandatory determination by the head of the contracting activity under FAR 16.603-3

FAR 16.603-3 imposes a categorical gate: "A letter contract may be used only after the head of the contracting activity or a designee determines in writing that no other contract is suitable." This is a pre-award requirement—the determination must be signed and in the contract file before the contracting officer executes the letter contract. The "head of the contracting activity" is defined by agency supplements; for DoD, it is typically the senior contracting official at the military-department or defense-agency level (not the program contracting officer). The determination may be delegated under agency procedures, but the level of delegation is constrained—most agencies permit delegation no lower than one level below the HCA, reflecting the policy judgment that letter-contract authority requires senior institutional oversight. The determination is not a formality; it must address why the two application prongs in FAR 16.603-2(a) are met and why other contract types—firm-fixed-price based on competition or price history, cost-reimbursement with a realistic estimated cost, time-and-materials under FAR 16.601, or an incrementally funded definitive contract—are not suitable for this requirement. The contracting officer prepares the request and supporting rationale (often as part of a business-clearance memorandum); the HCA (or designee) reviews and approves. Without the signed determination, the letter contract may not be awarded.

The 180-day definitization deadline under FAR 16.603-2(c)

FAR 16.603-2(c) establishes the central time discipline for letter contracts: "Each letter contract shall, as required by the clause at 52.216-25, Contract Definitization, contain a negotiated definitization schedule including (1) dates for submission of the contractor's price proposal, required certified cost or pricing data and data other than certified cost or pricing data; and, if required, make-or-buy and subcontracting plans, (2) a date for the start of negotiations, and (3) a target date for definitization, which shall be the earliest practicable date for definitization." The schedule is not aspirational—it is contractually binding and must be incorporated into every letter contract via the FAR 52.216-25 clause. The regulation then imposes a statutory ceiling: "The schedule will provide for definitization of the contract within 180 days after the date of the letter contract or before completion of 40 percent of the work to be performed, whichever occurs first." This is a hard deadline with narrow exceptions. If the letter contract cannot be definitized within 180 days or before 40% work completion (measured by the government-liability ceiling or the estimated total contract value), the contracting officer must either (i) not use a letter contract, or (ii) obtain approval for an extension "in extreme cases and according to agency procedures" (FAR 16.603-2(c)).

The "extreme cases" language sets a high bar—not merely inconvenient or complex negotiations, but circumstances where definitization within 180 days is genuinely impossible despite diligent effort by both parties. Examples include major programs with novel pricing structures, R&D contracts where technical performance during the undefinitized period will inform the cost estimate, or acquisitions where the contractor's cost-accounting system must be corrected before final cost can be negotiated. Extensions require approval at a level specified by agency procedures (typically the HCA or higher for DoD, per DFARS Subpart 217.74 overlay rules). The 40% work-completion gate operates as an additional constraint: even if 180 days have not elapsed, if the contractor will complete 40% of the work before definitization can occur, the letter contract is not the right vehicle unless the contracting officer can accelerate the definitization schedule or the government adjusts the scope to stay below the 40% threshold during the undefinitized period.

Failure-to-agree mechanism under FAR 16.603-2(c) and FAR 52.216-25

FAR 16.603-2(c) anticipates that the parties may reach an impasse: "If, after exhausting all reasonable efforts, the contracting officer and the contractor cannot negotiate a definitive contract because of failure to reach agreement as to price or fee, the clause at 52.216-25 requires the contractor to proceed with the work and provides that the contracting officer may, with the approval of the head of the contracting activity, determine a reasonable price or fee in accordance with subpart 15.4 and part 31, subject to appeal as provided in the Disputes clause." This is a unilateral-determination mechanism that distinguishes letter contracts from other preliminary instruments. If the contractor submits a qualifying proposal (one containing sufficient cost or pricing data to permit government analysis), the parties negotiate in good faith per the definitization schedule, and agreement still cannot be reached, the contractor does not walk away—the letter contract obligates the contractor to continue performance, and the government retains the right to determine price or fee unilaterally. The contracting officer applies the price-analysis and cost-analysis tools in FAR Subpart 15.4, the cost principles in FAR Part 31 (if the definitive contract will be cost-reimbursement), and the profit/fee guidelines in FAR 15.404-4, then issues a unilateral modification establishing the definitive contract price or estimated cost and fee. The contractor may dispute the determination under the Disputes clause (FAR 52.233-1), invoking the Contract Disputes Act process (claims to the contracting officer, appeal to the agency board of contract appeals or the Court of Federal Claims under FAR Subpart 33.2). This mechanism ensures that failure to agree on price does not leave the government without the supplies or services it authorized under the letter contract, but it also exposes the contractor to cost risk if the government's unilateral determination is lower than the contractor's final proposal—a risk the contractor accepts by entering into the letter contract in the first place.

Ceiling price and government-liability limitation under FAR 16.603-2(b) and (d)

FAR 16.603-2(b) imposes a special requirement for competitively awarded letter contracts: "When a letter contract award is based on price competition, the contracting officer shall include an overall price ceiling in the letter contract." This rule prevents the government from undermining competition by awarding on the basis of competing bids and then allowing the price to float during definitization. The ceiling locks in the competitive price discipline at award; the definitive price may be lower (if negotiations yield savings) but may not exceed the ceiling without a scope change. For letter contracts awarded without price competition (sole-source or limited-competition under FAR Part 6), FAR 16.603-2(d) establishes a different constraint tied to government funding exposure: "The maximum liability of the Government inserted in the clause at 52.216-24, Limitation of Government Liability, shall be the estimated amount necessary to cover the contractor's requirements for funds before definitization." This ceiling operates like the limitation-of-cost clause in cost-reimbursement contracts—the contractor may incur costs up to the stated ceiling, but the government's payment obligation does not exceed that amount unless the contracting officer raises the ceiling through a bilateral modification. The government-liability ceiling is not the estimated price of the definitive contract; it is the portion of that estimated price the contractor will need to incur before definitization occurs. If the letter contract is expected to definitize in 90 days and the contractor will incur 30% of total costs during that period, the government-liability ceiling should be set at roughly 30% of the estimated total contract value, not 100%. Setting the ceiling too high exposes the government to cost growth if definitization is delayed or the contractor front-loads expenditures; setting it too low may force the contractor to stop work if the ceiling is reached before definitization, triggering the same mission-delay risk the letter contract was meant to avoid. The contracting officer must estimate the undefinitized-period funding requirement realistically and document the basis in the contract file.

Three categorical limitations under FAR 16.603-3

Beyond the mandatory HCA determination, FAR 16.603-3 imposes three absolute prohibitions on letter-contract use. These are "shall not" rules—no exceptions, no waivers. First, letter contracts "shall not commit the Government to a definitive contract in excess of the funds available at the time the letter contract is executed." The letter contract may obligate only the amount covered by a valid funding document (commitment, obligation, or apportionment under the Antideficiency Act, 31 U.S.C. § 1341). If the anticipated definitive contract will cost $50 million but only $20 million is currently available, the letter contract's government-liability ceiling may not exceed $20 million, and the definitization schedule must contemplate either incremental funding or receipt of additional appropriations before the ceiling is reached. This rule aligns letter contracts with the general FAR prohibition on committing the government beyond available appropriations (FAR 1.602-1(b) and FAR 32.703-2).

Second, letter contracts "shall not be entered into without competition when competition is required by part 6." If the acquisition meets the dollar threshold for full and open competition under FAR Part 6, the contracting officer must conduct competition (sealed bidding under FAR Part 14 or negotiated procurement under FAR Part 15) before awarding the letter contract, or execute a justification and approval (J&A) under FAR 6.303 for sole-source or limited competition. The urgency that justifies using a letter contract does not excuse noncompliance with statutory competition requirements. In practice, this means letter contracts are often awarded as the result of a competitive negotiated procurement under FAR Part 15—the contracting officer conducts discussions, selects the awardee on the basis of initial proposals or best-and-final offers, and then awards a letter contract (rather than a definitive contract) because price and certain other terms cannot be finalized before the government needs the contractor to start work. Alternatively, the contracting officer prepares a J&A citing unusual and compelling urgency under FAR 6.302-2 (one of the seven exceptions to full and open competition) and awards the letter contract sole-source. Either path is permissible; awarding a letter contract without competition when FAR Part 6 requires it is not.

Third, letter contracts "shall not be amended to satisfy a new requirement unless that requirement is inseparable from the existing letter contract. Any such amendment is subject to the same requirements and limitations as a new letter contract" (FAR 16.603-3(c)). This rule prevents the government from using letter-contract amendments as a vehicle for adding unrelated work that would otherwise require a new competitive procurement. If the government wants to add a new requirement—supplies or services not contemplated in the original statement of work—the contracting officer must treat the amendment as a new letter contract, meaning the HCA (or designee) must execute a fresh determination that no other contract is suitable, the amendment must comply with FAR Part 6 competition requirements, and the definitization clock starts anew. The "inseparable" exception is narrow—it covers changes in quantity or delivery schedule for supplies already on contract, or additional phases of work that are integral to the original technical objective and were contemplated (even if not formally scoped) at the time of the original letter-contract award. Adding a different product line, a separate service category, or work for a different program or end user is a new requirement and cannot be folded into an existing letter contract via amendment.

DoD overlay: undefinitized contract actions under DFARS Subpart 217.74

For Department of Defense procurements, letter contracts are a subset of undefinitized contract actions (UCAs) governed by DFARS Subpart 217.74, which implements 10 U.S.C. § 3371 et seq. DFARS 217.7401 defines a UCA as "any contract action for which the contract terms, specifications, or price are not agreed upon before performance is begun under the action," and includes letter contracts, orders under basic ordering agreements, and provisioned-item orders as examples. DFARS 217.74 overlays several additional limitations. First, the head of the contracting activity must approve the UCA (which includes the FAR 16.603-3 determination plus additional DFARS-specific findings) per DFARS 217.7404-1. Second, the contracting officer may not obligate more than 50 percent of the not-to-exceed price under the letter contract before definitization, unless the contractor submits a qualifying proposal (defined in DFARS 217.7401 as a proposal containing sufficient information to enable DoD to conduct meaningful analyses and audits) before 50% is obligated, in which case the limitation increases to 75 percent (DFARS 217.7404-4). This funding gate is stricter than the FAR's government-liability-ceiling discipline and is designed to prevent the contractor from completing most of the work before price is established, which would give the contractor negotiating leverage ("you've already paid for most of it; pay our price or waste the expenditure"). Third, when the final price is negotiated after a substantial portion of performance is complete, the head of the contracting activity must ensure that the profit or fee reflects the contractor's reduced cost risk for costs already incurred—the contractor did not bear cost uncertainty for work already done and invoiced, so the profit analysis under FAR 15.404-4 should assign lower risk weight to those incurred costs than to prospective costs (DFARS 217.7405(a)).

DFARS PGI 217.7404 prescribes a detailed approval package that the contracting officer must submit to the HCA, including (i) documentation of why a UCA is required, (ii) a detailed explanation of the need to begin performance before definitization, (iii) an assessment of the adverse impact on agency requirements if performance is delayed, (iv) identification of the risk of using a UCA and the government's risk-mitigation strategy, (v) justification of the specific contractual instrument (letter contract versus another UCA type), (vi) limitations on obligation of funds, and (vii) the definitization schedule. This package goes beyond the FAR's "no other contract is suitable" standard and reflects DoD's institutional concern—reinforced by recurring DoD Inspector General audits—that letter contracts and other UCAs are sometimes used as substitutes for disciplined acquisition planning. Civilian agencies are not subject to DFARS Subpart 217.74, but many have adopted parallel limitations in agency acquisition regulation supplements or internal policy memoranda.

Mandatory clauses under FAR 16.603-4

FAR 16.603-4(a) requires the contracting officer to include in each letter contract "the clauses required by this regulation for the type of definitive contract contemplated and any additional clauses known to be appropriate for it." If the letter contract will definitize as a cost-plus-fixed-fee contract, the contracting officer must include the cost-reimbursement clauses prescribed in FAR Subpart 16.3 and FAR Part 31 (allowable-cost and payment, limitation of cost or limitation of funds, fixed fee, etc.); if it will definitize as firm-fixed-price, the fixed-price clauses in FAR Subpart 16.2 and FAR Part 52. This ensures that the rights and obligations governing performance during the undefinitized period match those that will govern after definitization—the contractor knows which cost principles apply, whether the government will audit incurred costs, and what payment and invoice procedures are in effect.

FAR 16.603-4(b) prescribes three letter-contract-specific clauses that must be included in every letter contract. First, FAR 52.216-24, Limitation of Government Liability, with dollar amounts completed per FAR 16.603-2(d). This clause establishes the government-liability ceiling and obligates the contractor to notify the contracting officer when costs will reach 75% of the ceiling, paralleling the limitation-of-cost discipline in cost-reimbursement contracts. Second, FAR 52.216-25, Contract Definitization, with paragraph (b) completed per FAR 16.603-2(c). This clause incorporates the definitization schedule (proposal submission date, negotiation start, definitization target) and the failure-to-agree mechanism (contractor proceeds with work, contracting officer may determine reasonable price or fee unilaterally with HCA approval). If the letter contract is based on price competition, the contracting officer uses Alternate I of FAR 52.216-25, which adds language reinforcing the price-ceiling requirement in FAR 16.603-2(b). Third, when the letter contract will require submission of certified cost or pricing data at definitization, paragraph (a) of FAR 52.216-25 must reference FAR 15.408, Table 15-1; if the definitization will be based on adequate price competition or another exception to the Truth in Negotiations Act (TINA) under FAR 15.403-1, the contracting officer may delete the certified-data reference from the clause. Additionally, FAR 16.603-4(c) requires inclusion of FAR 52.216-26, Payments of Allowable Costs Before Definitization, in solicitations and letter contracts when a cost-reimbursement definitive contract is contemplated and the letter contract will authorize interim payments based on incurred costs (rather than fixed billing prices).

The use case: operational urgency with definitization-timing risk

Letter contracts are the contract type of last resort when two conditions converge: the government cannot wait for a definitive contract, and the parties cannot finalize price or terms before performance must begin. Typical scenarios include (1) urgent operational needs in support of combat or contingency operations—theater commanders identify a critical capability gap, industry can deliver rapidly, but contract negotiations (especially for novel items with no price history) cannot keep pace with the operational timeline; (2) production-line preservation—a contractor notifies the government that a critical production line will shut down unless the government commits within weeks, and the time required to negotiate a multi-year production contract (with economic-price-adjustment clauses, cost or pricing data submission, and subcontracting-plan approvals) exceeds the window; (3) technology insertion under schedule pressure—a program office identifies an urgent need to integrate a new technology (cybersecurity countermeasure, sensor upgrade, software patch) into fielded systems, the development and integration work must start immediately to meet an operational deadline, but the cost of the work cannot be estimated until the contractor completes preliminary design; (4) disaster response or emergency repair—a natural disaster, enemy action, or equipment failure creates an immediate need for repair or replacement of government property, and the contractor must mobilize resources before the government can scope the work or negotiate price. In each case, the letter contract provides a legally binding vehicle—procurement authority under the FAR, not an other-transaction authority or a grant—that permits the contractor to incur costs and invoice the government while definitization proceeds.

The administrative price is significant: the HCA determination, the definitization-schedule discipline, the government-liability-ceiling management, and (for DoD) the funding and profit-adjustment constraints in DFARS Subpart 217.74 all impose overhead that a definitive contract does not carry. But when the alternative is mission failure or lost opportunity, the letter contract is the mechanism the FAR provides. The key practitioner discipline is recognizing that letter contracts are preliminary, not perpetual—the 180-day / 40%-work-completion clock is not negotiable, extensions require senior approval and "extreme" justification, and failure to definitize on time exposes both parties to disputes over the unilateral price-determination mechanism in FAR 52.216-25. Programs that treat letter contracts as open-ended authorizations to proceed without price agreement inevitably trigger contractor claims, DoD IG audits, and GAO protests alleging that the letter contract was used to circumvent competition or definitization disciplines. The regulation tolerates urgency; it does not tolerate indefinite undefinitization.

Source: FAR 16.603-1 Source: FAR 16.603-2 Source: FAR 16.603-3 Source: FAR 16.603-4 Source: DFARS Subpart 217.74

The cost-plus-incentive-fee (CPIF) contract is the cost-reimbursement analog to the fixed-price incentive (firm target) contract, sitting at the intersection of cost reimbursement and performance incentives within the FAR Part 16 framework. Where a cost-plus-fixed-fee contract provides only minimal cost-control incentive (the fee is invariant with cost performance under FAR 16.306(a)) and a cost-plus-award-fee contract ties fee to subjective government evaluation (FAR 16.305 and 16.405-2), the CPIF contract motivates the contractor through an objective, formulaic fee-adjustment mechanism tied to the relationship between total allowable costs and a negotiated target cost. FAR 16.405-1(a) defines a CPIF contract as "a cost-reimbursement contract that provides for the initially negotiated fee to be adjusted later by a formula based on the relationship of total allowable costs to total target costs." The contract specifies a target cost, a target fee, minimum and maximum fees, and a fee adjustment formula; after performance, the fee payable is determined by applying the formula to final allowable cost. This structure gives the government the cost-audit rights and cost-ceiling discipline of cost reimbursement while layering on a contractor profit incentive to underrun the target cost—stronger than CPFF, more objective than CPAF, but without the price-ceiling feature that defines fixed-price incentive contracts under FAR 16.403-1.

The five negotiated elements under FAR 16.405-1(a)

FAR 16.405-1(a) enumerates the five elements that distinguish a CPIF contract from other cost-reimbursement types and that must be negotiated and fixed at contract award. First, target cost is the parties' best estimate at the time of award of what performance will cost, negotiated using cost or pricing data under FAR 15.403-4 when the contract exceeds the Truth in Negotiations Act threshold (currently $2.5 million for most acquisitions as of October 1, 2025) or cost information sufficient to determine price reasonableness when TINA does not apply. Target cost is not a ceiling—the government reimburses all allowable costs under FAR Part 31, subject to any estimated-cost limitation in the contract's limitation-of-cost or limitation-of-funds clause (FAR 52.232-20 or 52.232-22)—but it is the baseline against which cost performance is measured for purposes of fee adjustment.

Second, target fee is the fee (profit) the contractor will earn if final allowable cost exactly equals target cost. Target fee is typically expressed as a dollar amount and is negotiated using the profit or fee analysis methodology in FAR 15.404-4 (the weighted-guidelines method for DoD and NASA contracts exceeding the cost-or-pricing-data threshold, or a structured approach for other contracts). The target fee should reflect the contractor's cost risk under the fee-adjustment formula (discussed below); FAR 16.401(c) states that incentive contracts are most effective when "it is usually to the Government's advantage for the contractor to assume substantial cost responsibility and an appropriate share of the cost risk," so the target fee must be calibrated to induce the contractor to accept the share ratio embedded in the formula.

Third and fourth, minimum fee and maximum fee establish the lower and upper bounds of the fee the contractor may earn. The minimum fee may be zero or a positive amount; a zero minimum fee is common and reflects the policy judgment that if cost performance is sufficiently poor, the contractor earns no profit, only reimbursement of allowable costs. The minimum fee may not be negative—the CPIF contract remains a cost-reimbursement contract, so the contractor does not incur net losses (the government pays total allowable costs plus at least the minimum fee, even if the fee-adjustment formula would otherwise yield a negative result). The maximum fee reflects the government's willingness to reward exceptional cost performance; it is typically set at 1.5× to 2× the target fee, though the multiple is negotiated based on the range of reasonably foreseeable cost variance and the government's budget constraints. The spread between minimum and maximum fee defines the fee range within which the formula operates. FAR 16.405-1(a) clarifies the boundary conditions: "When total allowable cost is greater than or less than the range of costs within which the fee-adjustment formula operates, the contractor is paid total allowable costs, plus the minimum or maximum fee." If final cost is so high that the formula would drive fee below the minimum, the contractor receives the minimum; if final cost is so low that the formula would drive fee above the maximum, the contractor receives the maximum.

Fifth, the fee adjustment formula is the mechanism that translates cost performance into fee earned. The formula is expressed as a share ratio—a percentage split of cost variance (underruns or overruns relative to target cost) between the government and the contractor. Common share ratios are 80/20 (government retains 80% of savings or absorbs 80% of overruns; contractor earns 20% of savings or gives back 20% of overruns), 70/30, or 60/40. Unlike the fixed-price incentive contract under FAR 16.403-1, where the share ratio adjusts price (within a ceiling price), the CPIF share ratio adjusts only fee—the government reimburses total allowable costs regardless of whether those costs are above or below target. If the contractor underruns target cost by $1 million under an 80/20 formula, the contractor's final fee equals target fee plus 20% of $1 million ($200,000), and the government pays total allowable costs (which are $1 million less than target) plus the increased fee; the government's net savings is $1 million − $200,000 = $800,000 (80% of the underrun). If the contractor overruns target cost by $1 million, the contractor's final fee equals target fee minus $200,000 (20% of the overrun), and the government pays total allowable costs (which are $1 million more than target) plus the reduced fee; the government's net cost increase is $1 million − $200,000 = $800,000 (still 80% of the variance, now an overrun). The formula incentivizes cost control—underruns increase contractor profit, overruns erode it—but the contractor does not absorb cost risk dollar-for-dollar as in a fixed-price contract; the government always pays total allowable costs, and the fee adjustment is a profit incentive layered on top of that cost reimbursement.

Fee-adjustment mechanics: the formula in operation

The fee-adjustment formula operates within the band defined by minimum and maximum fee. FAR 16.405-1(a) states that "the formula provides, within limits, for increases in fee above target fee when total allowable costs are less than target costs, and decreases in fee below target fee when total allowable costs exceed target costs." The phrase "within limits" signals that the minimum and maximum fees act as guardrails. To illustrate: assume a CPIF contract with target cost $10 million, target fee $800,000, minimum fee $0, maximum fee $1.4 million, and a 75/25 share ratio (government 75%, contractor 25%). If final allowable cost is $9 million (a $1 million underrun), the contractor's fee increases by 25% × $1 million = $250,000, so final fee = $800,000 + $250,000 = $1.05 million. The government pays $9 million (costs) + $1.05 million (fee) = $10.05 million total, versus the target price of $10.8 million (target cost + target fee), a government savings of $750,000 (75% of the $1 million underrun). If final allowable cost is $11 million (a $1 million overrun), the contractor's fee decreases by 25% × $1 million = $250,000, so final fee = $800,000 − $250,000 = $550,000. The government pays $11 million + $550,000 = $11.55 million total, versus the target price of $10.8 million, a government cost increase of $750,000 (75% of the $1 million overrun, with the contractor absorbing the remaining 25% via reduced fee).

When cost variance is so large that the fee-adjustment formula would drive fee outside the minimum/maximum range, the fee is capped at the boundary. If final allowable cost in the example above is $6.8 million (a $3.2 million underrun), the formula would yield final fee = $800,000 + (25% × $3.2M) = $1.6 million, which exceeds the $1.4 million maximum. The contractor receives only the maximum fee of $1.4 million, and the government pays $6.8M + $1.4M = $8.2 million total—the government captures the full underrun beyond the point where the formula hits the maximum-fee ceiling. Conversely, if final allowable cost is $14 million (a $4 million overrun), the formula would yield final fee = $800,000 − (25% × $4M) = −$200,000, a negative number. The contractor receives the minimum fee of $0, and the government pays $14 million + $0 = $14 million total. The contractor has absorbed $800,000 of profit (the full target fee) through the formula's operation, but absorbs no additional loss beyond that point because the minimum fee is zero—this is the key distinction between CPIF and fixed-price contracts, where cost overruns can impose net losses on the contractor.

The contracting officer and contractor negotiate final allowable cost after contract performance using the allowable-cost principles in FAR Part 31 and the incurred-cost-audit procedures administered by the Defense Contract Audit Agency (DCAA) for DoD contracts or the cognizant civilian-agency auditor. The process parallels the final-cost negotiation on a fixed-price incentive contract under FAR 52.216-16, except that there is no price ceiling on a CPIF contract—the government's cost obligation runs to total allowable costs (subject to the estimated-cost limitation in the contract's limitation-of-cost or limitation-of-funds clause, which the contracting officer may increase through bilateral modification if performance is not yet complete). Once final allowable cost is determined and documented in a modification or contracting-officer determination, the fee-adjustment formula is applied to calculate final fee, and the contractor invoices (or the government adjusts prior payments to reflect) the final cost-plus-fee total.

The two-prong application standard under FAR 16.405-1(b)(1)

FAR 16.405-1(b)(1) establishes when a CPIF contract is appropriate: "for services or development and test programs when—(i) A cost-reimbursement contract is necessary (see 16.301-2); and (ii) A target cost and a fee adjustment formula can be negotiated that are likely to motivate the contractor to manage effectively." Both prongs must be satisfied. The first prong incorporates by reference the cost-reimbursement application standard in FAR 16.301-2(a), which permits cost-reimbursement contracts only when (i) circumstances do not allow the agency to define its requirements sufficiently to allow for a fixed-price contract, or (ii) uncertainties involved in contract performance do not permit costs to be estimated with sufficient accuracy to use any type of fixed-price contract. If a fixed-price contract is feasible—either a firm-fixed-price contract under FAR 16.202-2 or a fixed-price incentive contract under FAR 16.403-1—the contracting officer must use that type instead, because it places greater cost responsibility on the contractor and reduces the government's audit and surveillance burden. The first prong of FAR 16.405-1(b)(1) thus presumes that the work is exploratory, developmental, or otherwise characterized by cost or requirement uncertainty that makes fixed-price contracting unsuitable.

The second prong requires that "a target cost and a fee adjustment formula can be negotiated that are likely to motivate the contractor to manage effectively." This is the dividing line between CPIF and the other cost-reimbursement types. A CPIF contract is appropriate when the parties can agree on a realistic target cost before award—even if that target is less certain than the cost estimates that support a fixed-price incentive contract—and when a share ratio can be devised that will incentivize the contractor to control costs without demanding a risk premium so large that the government would be better off using a cost-plus-fixed-fee contract (where the fee does not vary with cost performance) or accepting the administrative burden of a cost-plus-award-fee contract (where fee is tied to subjective evaluation rather than a formulaic cost metric). FAR 16.405-1(b)(3) reinforces the formula-design discipline: "The fee adjustment formula should provide an incentive that will be effective over the full range of reasonably foreseeable variations from target cost." If cost uncertainty is so high that the target cost is essentially a guess and the formula's effectiveness depends on cost outcomes far outside the negotiated fee range (minimum to maximum), the CPIF vehicle is not suitable—the contracting officer should use CPFF (if no meaningful cost targets can be set) or CPAF (if subjective performance dimensions beyond cost control are critical to program success).

FAR 16.405-1(b)(2) permits layering of technical performance incentives onto a CPIF contract "when it is highly probable that the required development of a major system is feasible and the Government has established its performance objectives, at least in general terms." When both cost and technical performance can be incentivized through objective formulas, "the most appropriate contract type is a multiple-incentive contract containing both objective incentives" rather than a pure CPIF or a hybrid CPIF/CPAF structure. FAR 16.405-1(b)(2) adds that "this approach also may apply to other acquisitions, if the use of both cost and technical performance incentives is desirable and administratively practical." Multiple-incentive contracts are complex—they require negotiation of separate formulas for cost and technical performance, weighting of the relative importance of cost versus performance, and administrative systems to measure and document performance against each target—but they can provide stronger contractor motivation than cost-only or performance-only incentives when the program's success depends on achieving both cost discipline and technical milestones. DFARS 216.401(e)(2) expresses DoD's policy preference for such structures: "When objective criteria exist but the contracting officer determines that it is in the best interest of the Government also to incentivize subjective elements of performance, the most appropriate contract type is a multiple-incentive contract containing both objective incentives and subjective award-fee criteria (i.e., cost-plus-incentive-fee/award-fee or fixed-price-incentive/award-fee)."

Compliance with cost-reimbursement limitations under FAR 16.405-1(c)

FAR 16.405-1(c) imposes a categorical gate: "No cost-plus-incentive-fee contract shall be awarded unless all limitations in 16.301-3 are complied with." This incorporation by reference means that the CPIF contract is subject to the full suite of cost-reimbursement prerequisites enumerated in FAR 16.301-3. First, the contracting officer must affirmatively determine that one of the two cost-reimbursement application tests in FAR 16.301-2(a) is met—either requirements cannot be defined sufficiently for a fixed-price contract, or cost uncertainties preclude fixed-price contracting. Second, the acquisition plan must document the contract-type rationale and be approved one level above the contracting officer per FAR 16.301-2(b) and FAR 16.301-3(a)(2). Third, the contractor's accounting system must be adequate for determining costs applicable to the contract (FAR 16.301-3(a)(3))—a threshold requirement enforced through pre-award accounting-system audits by DCAA or the cognizant civilian-agency auditor. If the contractor's system has a significant deficiency or is not compliant with the Cost Accounting Standards (for contractors subject to CAS under FAR Part 30), the accounting system is not adequate and the CPIF contract may not be awarded until the deficiency is corrected or the contracting officer accepts the risk and documents the rationale in the contract file. Fourth, adequate government resources must be available to manage the contract, including designation of at least one qualified contracting officer's representative (COR) before award (FAR 16.301-3(a)(4)). The government must commit to cost surveillance, invoice review under FAR Part 31 cost principles, and performance monitoring sufficient to provide "reasonable assurance that efficient methods and effective cost controls are used." If DCAA audit coverage is unavailable, if no qualified COR can be assigned, or if the contracting office lacks capacity for ongoing cost-reimbursement oversight, this limitation is not satisfied and the CPIF contract may not be awarded.

FAR 16.301-3(b) categorically prohibits cost-reimbursement contracts—including CPIF—for acquisition of commercial products or commercial services: "The use of cost-reimbursement contracts is prohibited for the acquisition of commercial products and commercial services (see parts 2 and 12)." If the supplies or services meet the commercial-item definition in FAR 2.101, the contracting officer must use a firm-fixed-price or fixed-price with economic price adjustment contract under FAR 12.207(a), or (for commercial services only, under the narrow exception in FAR 12.207(b)) a time-and-materials or labor-hour contract following competitive procedures and execution of a determination and findings that no other contract type is suitable. The commercial-item prohibition applies even when the contractor is willing to accept cost-reimbursement terms; the FAR presumes that commercial pricing is market-driven and that the cost-accounting-system requirements, FAR Part 31 cost audits, and government surveillance obligations of cost-reimbursement contracting are inconsistent with commercial practices.

Mandatory determination and findings under FAR 16.401(d)

FAR 16.401(d) imposes a pre-award documentation requirement for all incentive and award-fee contracts, including CPIF: "A determination and finding, signed by the head of the contracting activity, shall be completed for all incentive- and award-fee contracts justifying that the use of this type of contract is in the best interest of the Government. This determination shall be documented in the contract file." The D&F is not a suggestion or a best practice—it is a mandatory gate. The contracting officer may not execute a CPIF contract until the determination is signed by the head of the contracting activity (HCA) or an authorized designee and filed. The "head of the contracting activity" is defined by agency supplements; for DoD, it is typically the senior contracting official at the military-department or defense-agency level.

For DoD CPIF contracts, DFARS 216.401(d)(ii) permits delegation of the determination to "one level above the contracting officer for incentive-fee contracts," a lower signature threshold than the FAR's default "head of the contracting activity." This DFARS overlay reflects DoD's policy preference for objective incentive contracts (CPIF and FPIF) over subjective award-fee contracts (CPAF), where the determination must be signed by the HCA or a designee no lower than one level below the HCA per DFARS 216.401(d)(i). Civilian agencies are not bound by the DFARS delegation rule unless the agency's acquisition regulation supplement adopts a parallel provision; absent such a supplement, the FAR default is HCA signature, though most agencies have issued class deviations or internal policy memoranda permitting one- or two-level-below delegation for CPIF determinations.

The content of the D&F must "justif[y] that the use of this type of contract is in the best interest of the Government." The determination is not a formality—it must address why the CPIF contract type is appropriate for this acquisition, why a firm-fixed-price or fixed-price incentive contract is not suitable (cost or requirement uncertainty under FAR 16.301-2), why a cost-plus-fixed-fee contract would not provide adequate cost-control incentive, and why a cost-plus-award-fee contract is not preferable (objective cost targets can be set, so formulaic incentives are more effective and less administratively burdensome than subjective award-fee evaluations). The determination should also document that the target cost is realistic, that the fee-adjustment formula will be effective over the range of reasonably foreseeable cost variance, and that the minimum and maximum fees are appropriately calibrated to the contractor's cost risk under the share ratio. The D&F is typically one to three pages and is prepared by the contracting officer as part of the business-clearance or pre-award approval package, then routed to the HCA (or designee) for signature. Without the signed D&F in the contract file before award, the CPIF contract is procedurally deficient and may be vulnerable to bid protest or post-award contractor claim alleging improper contract-type selection.

Distinction from CPFF and CPAF: when to use CPIF instead

The CPIF contract occupies a specific niche within the cost-reimbursement family. It is appropriate when the conditions for cost-reimbursement contracting under FAR 16.301-2 are met (requirement or cost uncertainty precludes fixed-price), when the parties can negotiate a realistic target cost and a fee-adjustment formula likely to motivate effective cost management, and when the government values the cost-control incentive enough to accept the administrative overhead of final-cost negotiation and fee-formula application. The CPIF contract is not appropriate in three scenarios. First, when cost uncertainty is low enough that a fixed-price incentive contract under FAR 16.403-1 is feasible—if target cost can be estimated with the accuracy required to support an FPIF contract (which adds a ceiling price and shifts cost risk above the ceiling to the contractor), the FPIF type is preferred because it provides stronger cost discipline. Second, when cost uncertainty is so high that a realistic target cost cannot be negotiated—if the target is essentially a placeholder and the fee-adjustment formula will not operate within the fee range for any reasonably foreseeable cost outcome, a cost-plus-fixed-fee contract under FAR 16.306 is more appropriate; the CPFF contract accepts that the fee will not vary with cost performance and focuses the contractor's obligation on diligent effort within an estimated-cost ceiling. Third, when performance quality depends on subjective dimensions (responsiveness, innovation, customer satisfaction) that cannot be reduced to cost or technical performance metrics—if the government needs the flexibility to evaluate "both actual performance and the conditions under which it was achieved" per FAR 16.401(e)(1)(ii), a cost-plus-award-fee contract under FAR 16.305 and 16.405-2 is more appropriate despite the higher administrative burden of Award-Fee Boards, fee-determining-official evaluations, and award-fee-plan documentation.

The CPIF contract is the workhorse of DoD development contracting when programs have matured past the pure-research phase (where CPFF is typical) but have not yet achieved the cost-history density and requirement stability that would support fixed-price incentive contracting. Typical applications include engineering and manufacturing development (EMD) contracts for major defense programs after preliminary design review, system-integration contracts where the technical approach is defined but cost drivers (labor mix, subcontractor performance, yield rates) remain variable, and service contracts (systems engineering and technical assistance, logistics support) where the level of effort is negotiable and a cost target can be set but the government wants a formulaic fee incentive to reward cost efficiency. The CPIF contract is less common in civilian-agency acquisition but appears in R&D contracts, IT development, and large-scale services contracts when the program office can articulate a defensible target cost and the fee-adjustment formula can be structured to operate within the expected cost-variance band.

Contract clause and final-fee determination under FAR 16.406(d)

FAR 16.406(d) prescribes the contract clause for CPIF contracts: "The contracting officer shall insert the clause at 52.216-10, Incentive Fee, in solicitations and contracts when a cost-plus-incentive-fee contract is contemplated." The clause incorporates the target cost, target fee, minimum fee, maximum fee, and fee-adjustment formula into the contract and establishes the procedure for final-fee determination. After performance, the contractor submits a proposal for final cost (an incurred-cost submission under FAR 42.703-2, containing the contractor's claimed allowable costs for the contract, organized by cost element and supported by accounting records). The contracting officer (with DCAA or cognizant-auditor support) reviews the submission, conducts cost negotiations if necessary, and determines final allowable cost in accordance with the cost principles in FAR Part 31. The fee-adjustment formula is then applied to the difference between final allowable cost and target cost, yielding final fee (subject to the minimum and maximum fee constraints). The contracting officer documents the final-cost and final-fee determination in a bilateral contract modification or, if the parties cannot agree, in a unilateral contracting-officer determination subject to the disputes process under FAR 52.233-1 and FAR Subpart 33.2. The contractor may dispute the final-cost determination (challenging cost allowability, allocability, or reasonableness under FAR Part 31) or the fee calculation (alleging mathematical error in applying the formula), but the contractor may not dispute the formula itself—the formula was negotiated and fixed at contract award and is not subject to post-performance renegotiation absent a bilateral contract modification adding or changing scope.

The government's cost obligation on a CPIF contract is total allowable costs, subject to the estimated-cost limitation in the contract's limitation-of-cost clause (FAR 52.232-20 for fully funded contracts) or limitation-of-funds clause (FAR 52.232-22 for incrementally funded contracts). These clauses obligate the contractor to notify the contracting officer when costs will reach a percentage threshold (typically 75% or 85%) of the estimated cost, and they cap the government's reimbursement at the estimated cost unless the contracting officer increases the estimate through a bilateral modification before the ceiling is reached. This cost-ceiling mechanism is independent of the fee-adjustment formula—the formula adjusts fee based on the relationship between final allowable cost and target cost, but it does not alter the government's obligation to reimburse allowable costs within the estimated-cost ceiling. If the contractor incurs allowable costs beyond the estimated-cost ceiling and the contracting officer has not raised the ceiling, the contractor absorbs those excess costs as a loss (the "best efforts" obligation under FAR 52.232-20 or 52.232-22 relieves the contractor of further performance obligation once the ceiling is reached unless the government provides additional funding). This is the only scenario in which a CPIF contractor incurs a net loss—not from the fee-adjustment formula (which floors at the minimum fee, typically zero), but from performance beyond the estimated-cost ceiling without government authorization.

The use case: development and test with cost-target maturity

CPIF contracts are appropriate for the middle ground in the cost-risk spectrum: work that is too uncertain to support fixed-price contracting but mature enough that a realistic target cost and a motivating fee formula can be negotiated. The canonical applications are development and test programs (FAR 16.405-1(b)(1) expressly names "development and test" as the primary use case) and services contracts where the level of effort is definable but cost drivers are variable. A development program that has completed preliminary design, established a technical baseline, and generated cost estimates from prototype or early-phase work—but has not yet reached the production-readiness level where an FPIF contract with a ceiling price is appropriate—fits the CPIF profile. The government wants the contractor to control costs and deliver within a target, but recognizes that integration risks, test outcomes, and design maturation may drive costs above the target; the CPIF formula rewards the contractor for beating the target (via increased fee) and penalizes cost overruns (via reduced fee) without exposing the contractor to the full dollar-for-dollar cost risk (and potential net loss) of a fixed-price contract. Services contracts—systems engineering and technical assistance (SETA), logistics support, IT operations and maintenance—use CPIF when the government can estimate a target level of effort (labor hours, travel, materials) but wants a cost-control incentive stronger than the invariant fee of a CPFF contract and more objective than the subjective award-fee evaluations of a CPAF contract. The CPIF contract's administrative price is ongoing cost audit, final-cost negotiation, and fee-formula application—overhead the government accepts when the cost-control incentive justifies it and when the target cost is realistic enough that the formula will operate within the fee range for likely cost outcomes.

Source: FAR 16.405-1 Source: FAR 16.401 Source: FAR 16.301-2 Source: FAR 16.301-3 Source: DFARS 216.401 Source: 90 FR 41872 (FAR inflation adjustment, effective October 1, 2025)

The fixed-price-award-fee (FPAF) contract is a hybrid vehicle that marries the cost-certainty and risk-allocation profile of a firm-fixed-price contract with the subjective performance-evaluation framework of a cost-plus-award-fee contract. FAR 16.404 defines the type in economical terms: "Award-fee provisions may be used in fixed-price contracts when the Government wishes to motivate a contractor and other incentives cannot be used because contractor performance cannot be measured objectively. Such contracts shall establish a fixed price (including normal profit) for the effort." The fixed price covers the contractor's anticipated costs plus normal profit and is paid for satisfactory performance, full stop—no cost reimbursement, no audit of incurred costs under FAR Part 31, no adjustment for cost overruns or underruns. The award fee (if any) is earned through periodic subjective evaluations of the contractor's performance in schedule, technical quality, responsiveness, and other dimensions beyond mere delivery of the minimum contractual requirements, and is paid in addition to the fixed price. This structure permits the government to obtain the administrative simplicity and cost discipline of fixed-price contracting while retaining the motivational leverage—and evaluative flexibility—that award-fee mechanisms provide when objective performance metrics cannot capture the nuances of contractor performance that matter to mission success.

The two-element payment structure under FAR 16.404

FAR 16.404 establishes the core architecture in two sentences. First, the contract "shall establish a fixed price (including normal profit) for the effort." This price is negotiated at award using the price-reasonableness and cost-analysis tools in FAR Subpart 15.4, applying the profit or fee analysis in FAR 15.404-4 to determine the profit component embedded in the fixed price. The fixed price is not a base fee analogous to the optional base fee in cost-plus-award-fee contracts under FAR 16.305 and FAR 16.405-2—it is the entire contract price for satisfactory performance. The FAR states explicitly: "This price will be paid for satisfactory contract performance." If the contractor delivers on time and meets the minimum technical and quality requirements in the statement of work, the government pays the fixed price; no performance beyond "satisfactory" is required to earn that payment, and unsatisfactory performance triggers not fee withholding but instead the remedies available under fixed-price contracts (cure notice, show-cause, termination for default under FAR 52.249-8, or withholding of payment under the inspection clause at FAR 52.246-2 until defects are corrected).

Second, "award fee earned (if any) will be paid in addition to that fixed price." The award fee is a separate payment pool negotiated at contract inception, structured and administered under the award-fee plan required by FAR 16.401(e)(3). The contractor earns award fee—in whole, in part, or not at all—through periodic subjective evaluations by a government Award-Fee Board and a Fee-Determining Official applying the criteria in the award-fee plan. The phrase "if any" underscores that the award fee is not guaranteed; the contractor may earn zero award fee in a given evaluation period (or cumulatively over the life of the contract) if performance does not exceed satisfactory, yet still receive the full fixed price for satisfactory delivery of the required supplies or services. The award fee is an incentive, not a component of the contract price—FPAF is a fixed-price contract under the FAR Part 16 taxonomy, not a cost-reimbursement contract (FAR 16.401(c) groups award-fee contracts into "fixed-price incentive contracts" under FAR 16.403 and 16.404, and "cost-reimbursement incentive contracts" under FAR 16.405, confirming that FPAF belongs to the fixed-price family).

Suitability: objective targets infeasible, but price can be fixed

FPAF contracts occupy a narrow suitability band. On one side sits the firm-fixed-price contract with objective performance or delivery incentives under FAR 16.402-2 and 16.402-3—appropriate when the government can devise formulaic incentives tied to measurable performance dimensions (on-time delivery, defect rates below a threshold, fuel efficiency above a target). On the other side sits the cost-plus-award-fee contract under FAR 16.305—appropriate when cost or requirement uncertainty precludes fixed-price contracting under FAR 16.301-2 and performance quality turns on subjective evaluation. The FPAF contract bridges the gap: the government can establish a fair and reasonable fixed price at the outset (the requirement is defined well enough, and cost history or competition exists, to satisfy the firm-fixed-price suitability standard in FAR 16.202-2), but the performance dimensions that the government wishes to incentivize cannot be reduced to objective, predetermined targets—responsiveness to changing mission needs, innovation in solving technical problems, quality of collaboration with government personnel, proactive risk identification, customer satisfaction. FAR 16.401(e)(1) enumerates the three-prong suitability test for all award-fee contracts, and all three must be met for an FPAF contract just as for a CPAF contract. First, "the work to be performed is such that it is neither feasible nor effective to devise predetermined objective incentive targets applicable to cost, schedule, and technical performance." For an FPAF contract, this prong focuses on schedule and technical performance—cost is already fixed, so the contractor has no opportunity to earn additional profit by underrunning cost (unlike a fixed-price incentive contract under FAR 16.403-1, where underruns increase profit via the share ratio). If schedule adherence can be measured objectively (delivery by date X, with incentive payments for early delivery under FAR 52.216-5) and technical performance can be assessed against pass/fail acceptance criteria (the supplies meet the specification in the contract), a pure firm-fixed-price contract with delivery or performance incentives under FAR 16.402-2 or 16.402-3 is preferable—simpler to administer, clearer contractor expectations. The FPAF contract is suitable when the government values performance dimensions that resist formulaic expression: "extent of contractor initiative," "effectiveness of problem-solving," "quality of integration," "degree of collaboration."

Second, "the likelihood of meeting acquisition objectives will be enhanced by using a contract that effectively motivates the contractor toward exceptional performance and provides the Government with the flexibility to evaluate both actual performance and the conditions under which it was achieved." This prong asks whether the award-fee incentive—the prospect of earning additional profit beyond the fixed price—will drive contractor behavior in ways that a pure fixed-price contract will not, and whether the government needs the discretion to evaluate not just outcomes but context (did the contractor excel despite obstacles beyond its control, or did it meet minimum requirements only because conditions were favorable?). For production contracts, this flexibility matters when the program office anticipates design changes, engineering change proposals, or evolving government requirements during performance—the award-fee evaluation can credit a contractor that accommodates changes responsibly, or penalize one that resists changes the contract permits. For long-duration service contracts, the flexibility matters when performance quality turns on intangible but mission-critical factors—customer satisfaction, responsiveness to urgent requests, continuous-improvement initiatives—that cannot be reduced to service-level agreements with liquidated-damages clauses.

Third, "any additional administrative effort and cost required to monitor and evaluate performance are justified by the expected benefits as documented by a risk and cost benefit analysis to be included in the Determination and Findings referenced in 16.401(e)(5)(iii)." FPAF contracts impose the full award-fee administrative machinery—Award-Fee Board meetings, periodic evaluations, Fee-Determining Official determinations, written feedback to the contractor, documentation in the contract file per FAR 16.401(e)(2)—on top of the inspection and acceptance procedures already required for fixed-price contracts under FAR Part 46. The government must commit resources (board members' time, COR effort, FDO bandwidth) to conduct evaluations at quarterly, semiannual, or annual intervals throughout the contract period. For short-duration or low-dollar contracts, this overhead often outweighs the motivational benefit; for major production programs, large-scale integration contracts, or multi-year service efforts where contractor performance quality has direct mission impact, the trade-off is favorable. The risk and cost benefit analysis (required to be documented in the D&F discussed below) should quantify the government's expected performance improvement—fewer defects, faster problem resolution, better collaboration—and compare it to the administrative cost and the award-fee pool itself.

Compliance with all award-fee requirements in FAR 16.401(e)

FAR 16.404's second sentence states that contracting officers must "See 16.401(e) for the requirements relative to utilizing this contract type." This is a blanket incorporation—every rule in FAR 16.401(e) for award-fee contracts applies equally to FPAF and CPAF, with one critical distinction: for FPAF contracts, the cost-reimbursement prerequisites in FAR 16.401(e)(5)(i) do not apply because the contract is fixed-price, not cost-reimbursement. The seven-element award-fee plan in FAR 16.401(e)(3) is mandatory. The plan must (i) be approved by the Fee-Determining Official unless otherwise authorized by agency procedures; (ii) identify the award-fee evaluation criteria and link them to acquisition objectives defined in terms of contract cost, schedule, and technical performance (for FPAF contracts, the cost dimension typically drops out or is limited to cost impacts on the government, such as the contractor's responsiveness in minimizing the cost of government-furnished property or avoiding schedule delays that drive up government program-office costs); (iii) describe how performance will be measured against the criteria; (iv) utilize the mandatory five-tier adjectival rating scale in FAR 16.401(e)(3)(iv) Table 16-1 (Excellent / Very Good / Satisfactory / Marginal / Unsatisfactory) with associated award-fee percentages (generally 91–100% / 76–90% / 51–75% / 0–50% / 0%); (v) establish the frequency of evaluations (quarterly, semiannual, annual, or at milestones); (vi) address the composition and operational procedures of the Award-Fee Board; and (vii) define the total award-fee pool and its allocation across evaluation periods.

FAR 16.401(e)(2) governs the award-fee amount. "The amount of award fee earned shall be commensurate with the contractor's overall cost, schedule, and technical performance as measured against contract requirements in accordance with the criteria stated in the award-fee plan." For FPAF contracts, "cost" performance typically means schedule adherence (which affects government program cost) and avoidance of changes or rework that impose cost on the government, not the contractor's internal cost control (the government does not see the contractor's costs on a fixed-price contract and has no basis to evaluate them). "Award fee shall not be earned if the contractor's overall cost, schedule, and technical performance in the aggregate is below satisfactory." This is a hard floor—unsatisfactory aggregate performance yields zero award fee for that period. FAR 16.401(e)(2) also mandates documentation: "The basis for all award-fee determinations shall be documented in the contract file to include, at a minimum, a determination that overall cost, schedule and technical performance in the aggregate is or is not at a satisfactory level. This determination and the methodology for determining the award fee are unilateral decisions made solely at the discretion of the Government." The contractor has no right to negotiate the award-fee score or the methodology mid-performance; both are locked in by the award-fee plan at contract inception (subject to bilateral modification if both parties agree, but the government retains unilateral discretion to apply the plan as written).

FAR 16.401(e)(4) prohibits rollover of unearned award fee, defined in FAR 16.001 as "the process of transferring unearned award fee, which the contractor had an opportunity to earn, from one evaluation period to a subsequent evaluation period." If the contractor earns 60% of available award fee in Period 1, the remaining 40% is forfeited—it does not carry forward to Period 2. This rule applies equally to FPAF and CPAF contracts.

FAR 16.401(e)(5) enumerates three limitations that must be satisfied before any award-fee contract may be awarded. For FPAF contracts, prong (i)—"all of the limitations in 16.301-3, that are applicable to cost-reimbursement contracts only, are complied with"—is inapplicable by its own terms; FAR 16.301-3 limitations (adequate contractor accounting system, adequate government resources for cost surveillance, prohibition on commercial-item acquisition) govern only cost-reimbursement contracts, and an FPAF contract is fixed-price. Prong (ii)—"an award-fee plan is completed in accordance with the requirements in 16.401(e)(3)"—is mandatory and discussed above. Prong (iii)—"a determination and findings is completed in accordance with 16.401(d) addressing all of the suitability items in 16.401(e)(1)"—is also mandatory and discussed below.

Mandatory determination and findings under FAR 16.401(d)

FAR 16.401(d) imposes a pre-award gate for all incentive and award-fee contracts, including FPAF: "A determination and finding, signed by the head of the contracting activity, shall be completed for all incentive- and award-fee contracts justifying that the use of this type of contract is in the best interest of the Government. This determination shall be documented in the contract file and, for award-fee contracts, shall address all of the suitability items in 16.401(e)(1)." The D&F is not a suggestion; the contracting officer may not execute the contract until it is signed and in the file. For DoD FPAF contracts, DFARS 216.401(d)(i) permits the D&F to be signed by the head of the contracting activity or "a designee no lower than one level below the head of the contracting activity for award-fee contracts," a level reflecting DoD's concern (reinforced by recurring DoD IG audits) that award-fee contracts impose administrative burden and subjective evaluation risk that warrant senior oversight. Civilian agencies may adopt parallel delegation rules in agency supplements, but absent such a supplement the FAR default is HCA signature.

The content requirement is specified in FAR 16.401(d): for award-fee contracts, the D&F must "address all of the suitability items in 16.401(e)(1)." This means the determination must explain (i) why predetermined objective incentive targets are neither feasible nor effective for cost, schedule, and technical performance; (ii) why an award-fee contract will enhance the likelihood of meeting acquisition objectives and why the government needs flexibility to evaluate both performance and the conditions under which it was achieved; and (iii) that the administrative effort and cost of the award-fee mechanism are justified by expected benefits, supported by a risk and cost benefit analysis. The determination should also explain why alternative contract types—firm-fixed-price with objective performance or delivery incentives under FAR 16.402-2 or 16.402-3, or cost-plus-award-fee under FAR 16.305 if cost uncertainty would otherwise preclude fixed-price contracting—are not suitable. The D&F is typically one to three pages, prepared by the contracting officer as part of the business-clearance or pre-award approval package, and routed to the HCA (or authorized designee) for signature before contract execution.

No base fee; the fixed price is not disaggregated

A critical distinction between FPAF and CPAF contracts is the absence of a base-fee option. On a CPAF contract under FAR 16.305 and FAR 16.405-2, the fee structure has two components: "(1) a base amount fixed at inception of the contract, if applicable and at the discretion of the contracting officer, and (2) an award amount that the contractor may earn in whole or in part during performance." The base fee (which may be zero, and often is) is paid for satisfactory performance regardless of the contractor's award-fee score. On an FPAF contract, there is no base fee—there is a fixed price that includes normal profit. That fixed price is paid for satisfactory contract performance, full stop; it is not broken into a "guaranteed" component and an "at-risk" component the way a CPAF contract's base fee and award fee are. The award-fee pool on an FPAF contract is a separate incentive payment, entirely at risk—the contractor earns it (in whole or part) only through above-satisfactory performance as evaluated by the FDO. This structural difference matters for profit analysis under FAR 15.404-4. On a CPAF contract, the contracting officer negotiates the base fee and the award-fee pool separately, applying the weighted-guidelines method (for DoD and NASA contracts exceeding the cost-or-pricing-data threshold) or a structured approach (for other contracts) to each component. On an FPAF contract, the contracting officer negotiates the fixed price (applying cost analysis, price analysis, or both under FAR 15.404-1) and the award-fee pool; the profit embedded in the fixed price is determined using the same FAR 15.404-4 methodology the contracting officer would apply to a firm-fixed-price contract, and the award-fee pool is then added on top as an additional profit opportunity. The fixed price already compensates the contractor for normal business risk, technical risk, and cost risk (because it is a fixed-price contract, the contractor absorbs cost overruns and retains cost savings); the award fee compensates the contractor for exceptional performance beyond the contractual baseline.

For DoD FPAF contracts, DFARS 215.404-4(c)(4)(i) (which caps the base fee on CPAF contracts at three percent of estimated cost, exclusive of fee) does not apply—there is no base fee on an FPAF contract. Similarly, DFARS 215.404-4(c)(4)(ii) (which prohibits application of the weighted-guidelines method to CPAF base fees or award fees) does not prohibit use of weighted guidelines for the profit component of the fixed price on an FPAF contract—the fixed price is analyzed as a fixed-price contract, and weighted guidelines (for DoD and NASA) or the structured approach (for civilian agencies) apply normally.

Award-fee pool allocation and the 40% final-evaluation rule for DoD

FAR 16.401(e)(3)(vii) requires the award-fee plan to "define the total award-fee pool amount and how this amount is allocated across each evaluation period." The total pool is negotiated at contract inception and is fixed (subject to adjustment only if the scope of work changes via bilateral modification, in which case both the fixed price and the award-fee pool may be adjusted equitably). The allocation determines how much of the pool is available to be earned in each evaluation period. An even allocation (e.g., $500,000 pool over five annual periods = $100,000 per period) treats all periods equally. A weighted allocation (e.g., 10% / 15% / 20% / 25% / 30%) back-loads the incentive to sustain contractor performance through contract closeout.

For DoD FPAF contracts, DFARS 216.405-2(a)(1) imposes a back-loading mandate that applies equally to CPAF and FPAF: "The contracting officer shall perform an analysis of appropriate fee distribution to ensure at least 40 per cent of the award fee is available for the final evaluation so that the award fee is appropriately distributed over all evaluation periods to incentivize the contractor throughout performance of the contract." This 40% floor may be reduced only if "the contracting officer determines that a lower percentage is appropriate, and this determination is approved by the head of the contracting activity (HCA). The HCA may not delegate this approval authority." The policy rationale is straightforward: contractors tend to focus effort on early evaluation periods when award fee is front-loaded, then allow performance quality to slip in later periods after the bulk of the fee has been earned or lost. Reserving at least 40% for the final evaluation sustains the incentive through delivery and ensures the government retains leverage to reward (or withhold payment for) performance quality at contract completion, when defects or delays have the greatest mission impact. Civilian agencies are not bound by the DFARS 40% rule unless the agency supplement adopts it, but many have parallel guidance in internal award-fee policy memoranda.

Award-fee evaluation timing and the 45-day rating requirement for DoD

DFARS 216.405-2(a)(2) imposes two timing constraints on DoD award-fee contracts (both CPAF and FPAF). First, "award-fee payments other than payments resulting from the evaluation at the end of an award-fee period are prohibited." No interim or provisional award-fee payments are permitted; the contractor receives award-fee payment only after the FDO has evaluated the completed period and determined the amount earned. This rule prevents the government from advancing award fee based on anticipated performance or contractor requests for early payment, which would undermine the incentive structure. Second, "the fee-determining official's rating for award-fee evaluations will be provided to the contractor within 45 calendar days of the end of the period being evaluated." This deadline ensures timely feedback—the contractor needs to know its performance score promptly to adjust effort in subsequent periods, and program offices need the discipline of a hard deadline to prevent evaluations from languishing indefinitely. The 45-day clock starts at the end of the evaluation period (the last day of the quarter, semester, or year, or the milestone date specified in the award-fee plan), not at the date the Award-Fee Board convenes or the date the contractor submits a self-assessment (if the plan requires one). Civilian agencies are not subject to the DFARS 45-day rule unless adopted in an agency supplement.

Permitted layering with other incentives under FAR 16.202-1(b) and FAR 16.203-1(b)

FAR 16.202-1(b) explicitly permits the contracting officer to "use a firm-fixed-price contract in conjunction with an award-fee incentive (see 16.404) and performance or delivery incentives (see 16.402-2 and 16.402-3) when the award fee or incentive is based solely on factors other than cost." When so layered, "the contract type remains firm-fixed-price." This rule confirms that a firm-fixed-price contract can carry both an FPAF overlay (subjective evaluation of quality, responsiveness, collaboration) and objective performance or delivery incentives (formula-driven payments for early delivery under FAR 52.216-5, or for exceeding technical performance targets under a negotiated incentive clause)—provided the award fee and the objective incentives address different performance dimensions. If both mechanisms incentivize the same dimension (e.g., on-time delivery), the layering is inefficient and risks double-payment; the contracting officer should choose one or the other.

FAR 16.203-1(b) similarly permits use of "a fixed-price contract with economic price adjustment in conjunction with an award-fee incentive (see 16.404) and performance or delivery incentives (see 16.402-2 and 16.402-3) when the award fee or incentive is based solely on factors other than cost." When combined, "the contract type remains fixed-price with economic price adjustment." A multi-year production contract with an EPA clause keyed to a steel-price index (to manage commodity-cost volatility under FAR 16.203-2) may also include an FPAF overlay to incentivize production quality, manufacturing process improvements, or collaboration with government quality assurance representatives. The EPA adjustment is formulaic and tied to external market indices; the award fee is subjective and tied to contractor performance; both operate independently on the contract price and fee.

The use case: production and long-term services when quality exceeds mere delivery

FPAF contracts are appropriate for two canonical scenarios. First, production contracts where the requirement is mature enough to permit a fixed price (cost history exists, the design is stable, competition or cost analysis yields a fair and reasonable price) but the government values performance dimensions beyond on-time delivery of conforming supplies—production quality that exceeds the minimum acceptance standard, proactive identification and correction of design or manufacturing issues, responsiveness to engineering change proposals, effective collaboration with government program-office and quality-assurance personnel, continuous process improvement that enhances product reliability or reduces life-cycle cost. A multi-year production contract for a major defense system (aircraft, vehicles, shipboard systems) often uses FPAF when the government wants to incentivize the contractor to maintain manufacturing discipline, invest in quality over the contract period, and treat the government as a collaborative partner rather than an adversarial customer—none of which can be reduced to pass/fail acceptance criteria or formulaic delivery incentives. The fixed price provides cost certainty and shifts cost risk to the contractor; the award fee provides a profit upside (beyond the profit embedded in the fixed price) for contractors that excel.

Second, long-duration service contracts where the level of effort or deliverables can be defined well enough to support a fixed price (fixed-price level-of-effort under FAR 16.207, or a firm-fixed-price contract with a detailed performance work statement) but service quality depends on responsiveness, initiative, customer satisfaction, or other subjective dimensions that resist objective measurement. Base operations and maintenance contracts, facilities management, IT operations and maintenance, and program-management support contracts use FPAF when the government can specify the required staffing levels, labor categories, or recurring deliverables (monthly reports, help-desk response within specified hours) in a fixed-price statement of work, yet the success of the contract turns on contractor behaviors that go beyond minimum compliance—anticipating problems before they escalate, proposing innovative solutions, maintaining high morale among contractor staff, earning positive feedback from government end users. The FPAF structure locks in the service price (avoiding the ongoing cost-audit burden and invoice-review complexity of cost-reimbursement or time-and-materials contracts) while preserving the government's ability to reward contractors that deliver exceptional service quality through periodic award-fee evaluations.

FPAF contracts are not appropriate when performance can be measured objectively—if the government can define on-time delivery windows and attach formula-driven incentive payments for early delivery or disincentives for late delivery (FAR 52.216-5), or can specify quantitative technical performance targets (system availability above X%, defect rates below Y per thousand units) and tie profit or fee to achievement via a fixed-price incentive or performance-incentive clause, those objective mechanisms are simpler to administer and provide clearer contractor expectations than a subjective award-fee plan. FPAF is also not appropriate when cost or requirement uncertainty precludes fixed-price contracting—if the contracting officer cannot establish a fair and reasonable price at the outset because requirements are ill-defined or cost history is absent, the contract must be cost-reimbursement (CPFF under FAR 16.306, CPIF under FAR 16.405-1, or CPAF under FAR 16.305), not FPAF. The FPAF sweet spot is mature requirements, stable costs, but performance quality that depends on contractor behaviors the government values but cannot prescribe in objective contract clauses.

Administrative burden: fixed-price discipline plus award-fee machinery

The FPAF contract imposes a dual administrative load. On the fixed-price side, the contracting officer must apply the full FAR Part 15 price-analysis and cost-analysis discipline (adequate price competition under FAR 15.403-1, cost or pricing data under FAR 15.403-4 if the contract exceeds the TINA threshold and no exception applies, profit analysis under FAR 15.404-4), negotiate a fair and reasonable fixed price, and include the standard fixed-price contract clauses (FAR 52.212-4 for commercial items, or the fixed-price clauses in FAR Part 52 Subpart 52.2 for non-commercial supplies and services). During performance, the government inspects and accepts supplies or services under FAR Part 46 (FAR 52.246-2 for fixed-price supply contracts, FAR 52.246-4 for fixed-price service contracts), but does not audit the contractor's incurred costs under FAR Part 31—the contractor's internal cost performance is irrelevant to the government's payment obligation, which is the fixed price for conforming supplies or satisfactory services. On the award-fee side, the contracting officer must develop a compliant seven-element award-fee plan under FAR 16.401(e)(3), incorporate it into the contract at award, staff and convene an Award-Fee Board at the end of each evaluation period, prepare performance assessments against each criterion in the plan, present findings to the Fee-Determining Official, obtain the FDO's determination (applying the mandatory five-tier adjectival scale in Table 16-1), document the determination in the contract file with a satisfactory/unsatisfactory aggregate-performance finding, provide written feedback to the contractor (within 45 days for DoD contracts), and process the award-fee payment (if any) earned for that period. This machinery operates throughout the contract period—quarterly, semiannually, or annually per the plan—until the final evaluation. The administrative cost is substantially higher than for a pure firm-fixed-price contract (which requires only inspection and acceptance, no periodic performance evaluations) but lower than for a CPAF contract (which adds the cost-audit and voucher-review burden of cost reimbursement on top of the award-fee evaluations). The government accepts this overhead when the performance improvement expected from the award-fee incentive—fewer defects, faster problem resolution, higher customer satisfaction, better contractor collaboration—justifies the resource commitment, as documented in the risk and cost benefit analysis required by FAR 16.401(e)(1)(iii) and incorporated into the D&F under FAR 16.401(d).

Source: FAR 16.404 Source: FAR 16.401 Source: FAR 16.202-1 Source: DFARS 216.401 Source: DFARS 216.405-2

The requirements contract is the second of three indefinite-delivery contract types enumerated in FAR Subpart 16.5, sitting between the definite-quantity contract (where the government commits to a firm quantity at award) and the indefinite-quantity contract (where the government commits only to a stated minimum and may order up to a stated maximum). FAR 16.503(a) defines a requirements contract as one that "provides for filling all actual purchase requirements of designated Government activities for supplies or services during a specified contract period (from one contractor), with deliveries or performance to be scheduled by placing orders with the contractor." The defining feature—and the principal risk allocation mechanism—is the exclusivity obligation: the government agrees to obtain all of its actual requirements for the specified supplies or services from the single awardee, and the contractor agrees to furnish those requirements when ordered, within limits stated in the contract. This structure shifts demand risk from the contractor (who does not know in advance how much the government will order, but knows it will receive all orders if demand materializes) to the government (who cannot easily shift to another source mid-contract if the contractor's pricing becomes uncompetitive or if requirements change), making the requirements contract appropriate for recurring needs when the government can reliably predict that it will have requirements during the contract period but cannot fix the precise quantities at award.

The exclusivity obligation and "all actual purchase requirements"

The core of the requirements contract is the government's commitment to source all of its actual requirements for the designated supplies or services from the contractor during the contract period. FAR 16.503(a) states that the contract "provides for filling all actual purchase requirements of designated Government activities" (emphasis added). "Designated Government activities" are specified in the contract—typically a particular installation, command, program office, or agency component. The government may not place orders for the same supplies or services covered by the requirements contract with another contractor during the contract period unless the requirements contract itself authorizes such purchases (through a contract clause permitting orders from other sources under specified circumstances, or by defining the scope narrowly enough that other sources provide non-covered items). This exclusivity is binding on the government even if another source offers a lower price mid-performance, absent a termination for convenience or a scope limitation in the contract.

The contractor's reciprocal obligation is to fill all orders the government places, subject to the maximum stated in the contract (discussed below). The contractor does not guarantee that the government will have requirements—demand may be higher or lower than estimated, or may evaporate entirely if the designated activities' mission changes—but the contractor commits to supply whatever the government actually orders. This asymmetry distinguishes requirements contracts from definite-quantity contracts (where both quantity and price are fixed at award, and the government must take delivery) and from indefinite-quantity contracts (where the government commits only to order a stated minimum quantity but is not obligated to source all requirements from the IDIQ contractor and may compete individual orders or maintain multiple awards).

Realistic estimated quantity — informational, not binding

FAR 16.503(b)(1) mandates that "for the information of offerors and contractors, the contracting officer shall state a realistic estimated total quantity in the solicitation and resulting contract." This estimate serves a critical function during the competitive procurement: it permits offerors to understand the scale of the requirement, assess whether their production or service-delivery capacity can meet anticipated demand, and price their proposals accordingly. The estimate is the basis for price evaluation (the contracting officer typically evaluates unit prices by extending them against the estimated quantity to determine total evaluated price for award purposes), and it informs the profit or fee analysis under FAR 15.404-4 when cost or pricing data are required.

But the estimate is explicitly non-binding. FAR 16.503(b)(1) states: "This estimate is not a representation to an offeror or contractor that the estimated quantity will be required or ordered, or that conditions affecting requirements will be stable or normal." If the government's actual requirements during the contract period are 50% or 200% of the estimate, the contractor has no right to an equitable adjustment based on the variance—the contractor assumed the risk of demand fluctuation when it bid on a requirements contract rather than a definite-quantity contract. The government's only obligation is to order its actual requirements (whatever those turn out to be) from the requirements-contract holder, subject to the contract's stated maximum limit.

FAR 16.503(b)(1) instructs the contracting officer to obtain the estimate "from records of previous requirements and consumption, or by other means, and should base the estimate on the most current information available." Historical data—prior fiscal-year purchases, consumption rates, program-of-record projections—are the typical sources. The estimate should be realistic (a good-faith projection based on available data), not artificially inflated to attract more bidders or deflated to fit within a budget threshold. An unrealistic estimate undermines the competitive process (offerors cannot price responsibly if the estimate is divorced from likely actual demand) and may expose the government to a bid-protest challenge alleging that the estimate was arbitrary or misleading.

Maximum limits on contractor obligation and government authority

FAR 16.503(b)(2) establishes the boundary discipline: "The contract shall state, if feasible, the maximum limit of the contractor's obligation to deliver and the Government's obligation to order." This maximum operates as a ceiling. If the government's actual requirements during the contract period exceed the stated maximum, the contractor is not obligated to fill orders beyond that limit (though the contractor may agree to do so via bilateral modification, or the government may exercise an option period if one was negotiated at award). Conversely, the government is not obligated to order beyond the maximum even if actual requirements exceed it—the government may compete a separate procurement for the excess, issue orders under a separate contract, or reduce consumption.

The "if feasible" qualifier acknowledges that in some requirements contracts—particularly those for services with highly variable demand, or for supplies whose consumption depends on operational tempo that cannot be predicted—the contracting officer may not be able to establish a realistic maximum at award. When a maximum is not feasible, the contract operates as an open-ended requirements contract: the government orders all actual requirements (however large), and the contractor must deliver. This structure is riskier for the contractor (unlimited upside exposure if demand surges and the contractor's capacity or supply chain cannot scale) and administratively awkward for the government (funding and fiscal-law complications if requirements exceed the amount initially obligated). Best practice is to state a maximum whenever reasonably possible.

FAR 16.503(b)(2) adds that "the contract may also specify maximum or minimum quantities that the Government may order under each individual order and the maximum that it may order during a specified period of time." These sub-limits—per-order caps, monthly or quarterly ceilings—provide additional predictability for both parties. A contractor may need to know that no single order will exceed its production capacity in a given month; the government may want to smooth demand across the fiscal year to avoid end-of-year surge purchases. These limits are negotiated at award and incorporated into the ordering procedures in the contract.

The suitability test under FAR 16.503(b)(1)

FAR 16.503(b)(1) establishes when a requirements contract is appropriate: "A requirements contract may be appropriate for acquiring any supplies or services when the Government anticipates recurring requirements but cannot predetermine the precise quantities of supplies or services that designated Government activities will need during a definite period." This is a two-prong threshold. First, the government must anticipate recurring requirements—not a one-time buy or a requirement limited to a single delivery. Recurring requirements are those that arise repeatedly over the contract period: monthly orders for office supplies, quarterly janitorial services, annual maintenance on equipment, or on-demand repair services as equipment fails. If the requirement is for a single defined quantity with a single delivery date, the appropriate vehicle is a definite-quantity contract under FAR 16.502, not a requirements contract.

Second, the government must be unable to predetermine the precise quantities. If the contracting officer can determine at the time of solicitation that the government will require (for example) exactly 1,000 units delivered in four quarterly shipments of 250 units each, the appropriate vehicle is a definite-quantity contract—the government should commit to the firm quantity, obtain the pricing certainty that comes with that commitment, and avoid the administrative overhead of indefinite-delivery ordering procedures. The requirements contract is suitable when demand will fluctuate based on variables the government cannot control or predict precisely at award: operational tempo, equipment failure rates, user consumption patterns, mission changes, or budget execution. The government can estimate the total quantity (and must, per FAR 16.503(b)(1)), but cannot commit to a firm number because actual need will vary with circumstances during performance.

The $150 million single-source limitation under FAR 16.503(b)(2)

FAR 16.503(b)(2) imposes a statutory gate on large single-award requirements contracts: "No requirements contract in an amount estimated to exceed $150 million (including all options) may be awarded to a single source unless a determination is executed in accordance with 16.504(c)(1)(ii)(D)." This limitation is a subset of the broader indefinite-delivery single-award limitation in FAR 16.504(c)(1)(ii)(D), which applies to both requirements contracts and indefinite-quantity contracts. The $150 million threshold is cumulative—it includes the base period and all option periods. If a requirements contract has an estimated value (based on the estimated quantity stated in FAR 16.503(b)(1) multiplied by the unit prices, plus any other costs) of $150 million or more over its life, the contracting officer may not award it to a single source unless the head of the agency (or authorized designee under agency procedures, typically no lower than one level below the head of the agency) executes a written determination that one of four conditions applies.

FAR 16.504(c)(1)(ii)(D)(1) enumerates the four permissible grounds for a single award over $150 million. First, the head of the agency may determine that "the task or delivery orders expected under the contract are so integrally related that only a single source can reasonably perform the work." This ground applies when the supplies or services are interdependent—perhaps because they must be sourced from a single manufacturer to ensure interoperability, or because the service provider must have access to classified or proprietary information that cannot be shared with multiple contractors without jeopardizing security or intellectual-property protections. Second, the head of the agency may determine that "the contract provides only for firm-fixed-price task or delivery orders for (A) products for which unit prices are established in the contract; or (B) services for which prices are established in the contract for the specific tasks to be performed." This ground permits single-source requirements contracts when pricing is fully determined at award and the government is not exposed to cost growth risk—the rationale being that the price certainty of FFP orders mitigates the competition concern that ordinarily favors multiple awards. Third, the head of the agency may determine that "only one source is qualified and capable of performing the work at a reasonable price to the Government." This is the sole-source rationale familiar from FAR 6.302-1, applied to the indefinite-delivery context. Fourth, the head of the agency may determine that "it is necessary in the public interest to award the contract to a single source due to exceptional circumstances," in which case the agency must notify Congress within 30 days after the determination (FAR 16.504(c)(1)(ii)(D)(2)).

If none of the four grounds applies, the contracting officer may not award a single requirements contract estimated to exceed $150 million—the contracting officer must either structure the requirement to permit multiple awards (transitioning to an indefinite-quantity multiple-award vehicle under FAR 16.504, where fair-opportunity procedures under FAR 16.505(b) apply), reduce the estimated value or scope to stay below $150 million, or proceed without the head-of-agency determination (which would render the award procedurally deficient and vulnerable to bid protest). The determination is in addition to any justification and approval required under FAR Part 6 if the single award is sole-source or otherwise uses other than full and open competition. FAR 16.504(c)(1)(ii)(D)(3)(i) makes this clear: "The requirement for a determination for a single-award contract greater than $150 million is in addition to any applicable requirements of subpart 6.3."

The advisory-and-assistance-services limitation under FAR 16.503(d)

FAR 16.503(d) imposes a separate restriction on requirements contracts for advisory and assistance services. Paragraph (d)(1) provides: "Except as provided in paragraph (d)(2) of this section, no solicitation for a requirements contract for advisory and assistance services in excess of three years and $20 million (including all options) may be issued unless the contracting officer or other official designated by the head of the agency determines in writing that the services required are so unique or highly specialized that it is not practicable to make multiple awards using the procedures in 16.504." This is a lower threshold than the $150 million limit in FAR 16.503(b)(2)—$20 million and three years—and it applies specifically to advisory and assistance services as defined in FAR 2.101 (services in support of program management, analysis, studies, engineering support, and similar professional-services categories that inform government decision-making but do not involve direct performance of an inherently governmental function).

The policy rationale is that advisory and assistance services are usually amenable to multiple-award IDIQ structures under FAR 16.504, where the government can maintain several contractors and compete individual task orders to ensure fresh ideas, avoid contractor lock-in, and sustain a competitive marketplace. A single-award requirements contract for advisory services creates entrenchment risk—the contractor becomes the sole source of advice to a program office or agency component, and the government loses the competitive tension and diverse perspectives that multiple advisors would provide. The determination that services are "so unique or highly specialized that it is not practicable to make multiple awards" must be fact-specific: the services depend on access to proprietary data or systems that cannot be shared, the contractor holds unique technical expertise that no other firm possesses, or the advisory role requires such deep integration with the government client that switching or sharing among multiple contractors would be infeasible. Generic management consulting, program-management support, or systems-engineering services do not typically meet the "unique or highly specialized" standard—those services are widely available in the marketplace and are the canonical use case for multiple-award IDIQ contracts.

FAR 16.503(d)(2) provides a carve-out: "The limitation in paragraph (d)(1) of this section is not applicable to an acquisition of supplies or services that includes the acquisition of advisory and assistance services, if the contracting officer or other official designated by the head of the agency determines that the advisory and assistance services are necessarily incident to, and not a significant component of, the contract." If the primary purpose of the requirements contract is acquisition of supplies or other services, and advisory services are merely incidental (for example, a requirements contract for IT hardware that includes vendor technical support and configuration advice as a minor add-on), the $20 million / three-year limitation does not apply. The determination that advisory services are incident and not significant is a judgment call; the contracting officer should document the rationale in the contract file, addressing the relative dollar value and importance of the advisory component versus the primary supplies or services.

Government property furnished for repair under FAR 16.503(c)

FAR 16.503(c) addresses a narrow but operationally significant scenario: "When a requirements contract is used to acquire work (e.g., repair, modification, or overhaul) on existing items of Government property, the contracting officer shall specify in the Schedule that failure of the Government to furnish such items in the amounts or quantities described in the Schedule as 'estimated' or 'maximum' will not entitle the contractor to any equitable adjustment in price under the Government Property clause of the contract." This rule prevents a mismatch between the requirements-contract structure (where the government's ordering obligation is limited to actual requirements) and the government-property clause at FAR 52.245-1 (which normally provides for equitable adjustment if the government fails to furnish property as required by the contract).

The scenario: the government awards a requirements contract for depot-level maintenance on aircraft engines, estimating 50 engines per year. The contract states that the government will furnish engines to the contractor for overhaul. If the government furnishes only 30 engines in a given year (because the fleet flew fewer hours than projected, or because funding was reduced), the contractor might argue that the failure to furnish the estimated 50 engines is a breach of the government-property clause and seek an equitable adjustment for unabsorbed overhead or lost profit. FAR 16.503(c) forecloses that claim by requiring the contracting officer to specify in the Schedule that the estimate is not a guarantee and that variance from the estimate does not trigger the equitable-adjustment mechanism. The contractor's remedy is limited to the requirements-contract structure itself: the government must furnish (and pay for repair of) all engines that actually require overhaul during the contract period, but the contractor has no claim if the actual number is less than estimated.

Advantages and risk trade-offs under FAR 16.501(b)(4)

FAR 16.501(b)(4) identifies the principal operational advantage of requirements contracts: "Requirements contracts may permit faster deliveries when production lead time is involved, because contractors are usually willing to maintain limited stocks when the Government will obtain all of its actual purchase requirements from the contractor." The exclusivity commitment allows the contractor to invest in inventory, production capacity, or service-delivery infrastructure in advance of actual orders, knowing that all government demand will flow through the requirements contract. A contractor holding a requirements contract for spare parts may pre-position stock at a regional warehouse, reducing lead time from weeks to days. A janitorial-services contractor with a requirements contract covering a military installation may hire and train staff in advance of the government's peak-demand periods, ensuring responsiveness. This advantage is unavailable under indefinite-quantity contracts (where the contractor competes for each order and cannot assume it will win all orders) and is unnecessary under definite-quantity contracts (where the government has already committed to a firm quantity and the contractor can plan production accordingly).

The trade-off is reduced flexibility for the government. Once a requirements contract is awarded, the government is locked in—it cannot easily shift to another source if the market price falls, if a competitor offers better terms, or if the contractor's performance deteriorates (absent termination for default or convenience, which triggers claims and administrative burden). The requirements contract also shifts demand risk to the government in a way that indefinite-quantity contracts do not: if actual requirements fall far below the estimate, the government pays only for what it orders (no take-or-pay obligation), but the contractor may seek to recover its unabsorbed costs or lost profit through a claim alleging that the government's failure to generate requirements was a breach of the implied covenant of good faith and fair dealing. Courts have generally rejected such claims when the government's requirements genuinely decreased for legitimate programmatic or budgetary reasons, but the risk exists and should inform the contracting officer's decision whether to use a requirements contract versus an indefinite-quantity contract with a realistic minimum guarantee.

Contract type compatibility under FAR 16.501(c)

FAR 16.501(c) clarifies that "indefinite-delivery contracts may provide for any appropriate cost or pricing arrangement under part 16." A requirements contract may be firm-fixed-price (the contractor quotes unit prices, and each order is placed at those prices), fixed-price with economic price adjustment (unit prices adjust based on specified indices or market conditions under FAR Subpart 16.2), time-and-materials or labor-hour (for service requirements where extent and duration cannot be estimated, subject to the limitations in FAR 16.601), or even cost-reimbursement (though cost-reimbursement is rare for requirements contracts because the indefinite-quantity nature of the requirement usually precludes the realistic cost estimation required under FAR 16.301-2). The most common pairing is firm-fixed-price requirements contracts for recurring supply needs or for services with well-defined labor categories and rates.

The use case: recurring supply or service needs with variable demand

Requirements contracts are the vehicle of choice—often the only administratively practical option—when the government can reliably predict that it will have recurring requirements for specific supplies or services during a contract period, but cannot commit to firm quantities because demand depends on variables beyond the government's control. Typical applications include base-supply contracts for consumables (office supplies, janitorial supplies, vehicle fuel, food service for a dining facility), maintenance and repair services for equipment or facilities where the volume of work depends on failure rates or usage intensity, transportation or logistics services where shipment volumes fluctuate with operational tempo, and IT support or help-desk services where demand varies with the size and activity level of the user base. In each scenario, the government wants the certainty of a pre-competed contract with a committed supplier (avoiding the administrative burden of repeated competitions for each recurring need), the contractor wants the exclusivity commitment that justifies maintaining capacity, and both parties accept that actual order quantities will vary from the estimate. The requirements contract formalizes that mutual understanding in a binding vehicle—government commits to single-source all actual requirements, contractor commits to deliver, and the estimate provides the pricing and evaluation baseline without creating a quantity guarantee. When the government cannot make the exclusivity commitment (because it anticipates needing to maintain multiple sources, or because the dollar value or duration exceeds the statutory single-award limits in FAR 16.503(b)(2) or (d)(1) without a qualifying determination), the contracting officer must instead use a multiple-award indefinite-quantity contract under FAR 16.504, accepting the fair-opportunity ordering procedures and administrative complexity that vehicle entails.

Source: FAR 16.503 Source: FAR 16.501 Source: FAR 16.504(c)(1)(ii)(D)

The definite-quantity contract is the simplest and most straightforward of the three indefinite-delivery contract types enumerated in FAR Subpart 16.5, and it is the foundational vehicle for understanding the indefinite-delivery family. FAR 16.502(a) defines a definite-quantity contract as one that "provides for delivery of a definite quantity of specific supplies or services for a fixed period, with deliveries or performance to be scheduled at designated locations upon order." The contract establishes at award a firm total quantity that the government commits to purchase and the contractor commits to deliver—no estimates, no contingencies, no quantity risk. What remains indefinite is when deliveries or performance will occur and where they will be made—those are determined by individual delivery orders or task orders issued by the government during the contract period. This combination of quantity certainty and scheduling flexibility makes the definite-quantity contract the vehicle of choice when the government knows exactly how much it will need over a contract period but cannot fix delivery dates or locations at the time of award, or when spreading deliveries across multiple orders simplifies contract administration, payment processing, or logistics compared to a single-delivery fixed-quantity contract.

The two-prong application standard under FAR 16.502(b)

FAR 16.502(b) establishes when a definite-quantity contract is appropriate: "A definite-quantity contract may be used when it can be determined in advance that—(1) A definite quantity of supplies or services will be required during the contract period; and (2) The supplies or services are regularly available or will be available after a short lead time." Both prongs must be satisfied. The first prong—a definite quantity will be required—is the threshold that distinguishes definite-quantity contracts from the other two indefinite-delivery types. If the contracting officer can determine at the time of solicitation and award that the government will need (for example) exactly 10,000 units of a supply item, or exactly 2,000 labor hours of a particular service, during the contract period, and that quantity is certain (not an estimate subject to variation based on operational tempo, budget changes, or demand fluctuations), the definite-quantity vehicle is appropriate. The government's commitment is firm: the contract obligates the government to order the full quantity stated in the schedule, and the contractor is entitled to payment for that quantity when delivered in accordance with the contract terms. This is not a requirements contract, where the government orders only its actual requirements (which may be more or less than estimated), nor an indefinite-quantity contract, where the government commits only to a minimum quantity and may order up to a stated maximum. The definite-quantity contract locks in the total—the government cannot reduce the quantity without a bilateral modification (which the contractor is not obligated to accept) or a termination for convenience under FAR Part 49, which triggers termination costs and settlement.

The second prong—supplies or services are regularly available or will be available after a short lead time—ensures that the indefinite-delivery structure is administratively appropriate. If the contractor can deliver promptly upon order (either from stock, from a production line with short lead time, or from an on-call workforce for services), the government can issue delivery orders or task orders as needs crystallize without locking in delivery dates at award. "Regularly available" includes commercial off-the-shelf items, standard catalog supplies, or services the contractor routinely provides to commercial or government customers. "Short lead time" is a relative term—the FAR does not define a threshold—but it generally means lead times measured in days or weeks, not months. If the supplies require long lead-time procurement of raw materials, custom manufacturing with extended production cycles, or services that depend on hiring and training specialized personnel, the government should either structure the contract with firm delivery schedules at award (a traditional fixed-quantity contract under FAR Part 12 or FAR Subpart 16.2, not an indefinite-delivery vehicle) or use a requirements or indefinite-quantity contract that accounts for the lead-time uncertainty in the ordering procedures. The second prong thus screens out acquisitions where the indefinite-delivery ordering mechanism would create unacceptable delivery risk or force the contractor to maintain expensive excess capacity.

Government obligation to order the full quantity under FAR 52.216-20

FAR 16.506(c) prescribes the mandatory contract clause for definite-quantity contracts: "Insert the clause at 52.216-20, Definite Quantity, in solicitations and contracts when a definite-quantity contract is contemplated." FAR 52.216-20 makes the government's obligation explicit. Paragraph (a) of the clause states: "This is a definite-quantity, indefinite-delivery contract for the supplies or services specified, and effective for the period stated, in the Schedule." Paragraph (b) imposes the ordering obligation: "The Government shall order the quantity of supplies or services specified in the Schedule, and the Contractor shall furnish them when ordered." The word "shall" is mandatory—the government is contractually bound to order the full quantity during the contract period, and the contractor is bound to deliver when orders are placed. If the government fails to order the full quantity before the contract period expires, the contractor has a breach-of-contract claim for the unordered portion, seeking recovery of lost profit and unabsorbed overhead (though the contractor must mitigate damages by attempting to sell the unordered supplies or services to other customers if commercially reasonable). Conversely, if the contractor refuses or is unable to deliver the quantity ordered, the government may pursue remedies for default—cure notice, show cause, termination for default under FAR 52.249-8 (for fixed-price supply contracts) or FAR 52.249-10 (for fixed-price service contracts)—and may seek to recover excess reprocurement costs.

The clause's reciprocal obligations distinguish the definite-quantity contract sharply from the requirements contract (where the government orders only actual requirements, which may fall short of estimates, and the contractor has no claim if demand does not materialize) and the indefinite-quantity contract (where the government commits only to a stated minimum quantity, and the contractor's entitlement runs only to that minimum, not to the estimated or maximum quantities stated in the contract). On a definite-quantity contract, both parties assume quantity risk at award: the government risks ordering supplies or services it ultimately does not need (and must pay for them anyway, or terminate for convenience and reimburse settlement costs), and the contractor risks committing capacity to fulfill the government's order when market conditions or other customer demand might have been more profitable.

Scheduling and location flexibility under FAR 52.216-20(b) and (c)

The "indefinite" element of a definite-quantity contract is the timing and location of deliveries or performance. FAR 52.216-20(b) provides that "delivery or performance shall be at locations designated in orders issued in accordance with the Ordering clause and the Schedule." The government issues individual delivery orders or task orders specifying when and where the contractor shall deliver each portion of the total quantity. The schedule in the contract typically establishes broad parameters—perhaps a minimum advance notice the government must provide (e.g., 10 days' notice for delivery orders), a maximum quantity per order, or a delivery window during which orders must be placed—but the government retains discretion within those parameters to issue orders as mission needs, budget execution, or operational tempo dictate. FAR 52.216-20(c) reinforces this flexibility: "Except for any limitations on quantities in the Order Limitations clause or in the Schedule, there is no limit on the number of orders that may be issued. The Government may issue orders requiring delivery to multiple destinations or performance at multiple locations." The government may issue one large order, ten medium orders, or a hundred small orders over the contract period, so long as the cumulative quantity matches the total quantity specified in the schedule. The government may direct deliveries to different installations, ships, or program offices, or may direct service performance at geographically dispersed sites, without amending the contract—the individual orders, not the base contract, specify the delivery or performance locations.

This ordering flexibility offers significant administrative and operational advantages. For supply contracts, it permits the government to synchronize deliveries with warehouse capacity, budget-execution schedules, or downstream production needs, avoiding the cost and risk of taking delivery of the entire quantity at contract award and storing it until needed. For service contracts, it allows the government to schedule performance in phases, align task orders with the availability of government-furnished property or information, or shift performance locations as mission requirements evolve. The contractor, in turn, can plan production or staffing to the firm total quantity (reducing unit cost through economies of scale or stable workforce planning) while accommodating the government's delivery or performance-timing needs through the order-issuance process. The trade-off is that the contractor must maintain readiness to respond to orders throughout the contract period, which may require holding inventory, retaining trained personnel, or reserving production-line slots—costs the contractor prices into its unit rates or service prices at the time of proposal.

Orders issued during the contract period but completed afterward

FAR 52.216-20(d) addresses a common timing scenario: "Any order issued during the effective period of this contract and not completed within that time shall be completed by the Contractor within the time specified in the order." If the government issues a delivery order or task order before the contract's expiration date, but the delivery date or performance period extends beyond that expiration, the contractor remains obligated to complete the order. The clause continues: "The contract shall govern the Contractor's and Government's rights and obligations with respect to that order to the same extent as if the order were completed during the contract's effective period; provided, that the Contractor shall not be required to make any deliveries under this contract after __ [Contracting Officer inserts date]." The first part of the provision ensures continuity—the terms, clauses, pricing, and remedies in the base contract continue to apply to the order even though performance spills past the contract's nominal end date. The second part (the fill-in-the-blank cutoff date) permits the contracting officer to establish an outside limit on deliveries, protecting the contractor from indefinite extension and ensuring that the government does not use late-issued orders to extend performance far beyond the contemplated contract period. The cutoff date is typically set at a reasonable margin beyond the contract period (for example, if the contract period is one year and typical lead time is 30 days, the cutoff might be set 60 or 90 days after contract expiration) to accommodate orders issued near the end of the period.

Relationship to the other indefinite-delivery types

FAR 16.501-2(a) establishes the taxonomy: "There are three types of indefinite-delivery contracts: definite-quantity contracts, requirements contracts, and indefinite-quantity contracts." The three types form a spectrum of quantity commitment and risk allocation. At one end sits the definite-quantity contract, where quantity is certain and both parties commit at award—government risk is that it might not need the full quantity, contractor risk is that production or performance costs might exceed estimates. In the middle sits the requirements contract under FAR 16.503, where the government commits to order all of its actual requirements from the contractor during the contract period, but actual demand may be more or less than estimated—government risk is largely eliminated (it pays only for what it actually needs), contractor risk is demand variability. At the other end sits the indefinite-quantity contract (IDIQ) under FAR 16.504, where the government commits only to a stated minimum quantity and may order up to a stated maximum—government obligation is capped at the minimum, contractor certainty is limited to that minimum, and quantities above the minimum are at the government's discretion (and may be competed among multiple awardees if the IDIQ is a multiple-award vehicle). The definite-quantity contract offers the highest government commitment and the greatest contractor certainty of the three types, which typically translates to the most competitive unit pricing (the contractor does not need to embed a risk premium for demand uncertainty) and the strongest contractor incentive to perform efficiently (the contractor knows it will deliver the full quantity and can optimize production or service delivery accordingly).

FAR 16.501-2(b) enumerates the advantages of indefinite-delivery contracts generally, but does not separately list advantages specific to definite-quantity contracts—the advantages are implicit in the firm-quantity commitment. By comparison, FAR 16.501-2(b)(4) states that "requirements contracts may permit faster deliveries when production lead time is involved, because contractors are usually willing to maintain limited stocks when the Government will obtain all of its actual purchase requirements from the contractor." Definite-quantity contracts offer the same advantage (contractors will stock or schedule production for a known quantity) and eliminate the demand-variance risk that exists under requirements contracts (where actual requirements might fall well below estimates, leaving the contractor with excess inventory or underutilized capacity).

Common contract-type pairings and clause prescription

FAR 16.501-2(c) permits indefinite-delivery contracts to use "any appropriate cost or pricing arrangement under part 16." In practice, definite-quantity contracts are most commonly structured as firm-fixed-price contracts—the schedule specifies a unit price for each supply item or a labor-hour rate or fixed price per task for services, and the total contract value is the unit price or rate multiplied by the definite quantity. This FFP pairing provides maximum cost certainty for both parties: the government knows its total obligation (quantity × unit price), and the contractor knows the revenue it will earn if it performs efficiently. Definite-quantity contracts may also be structured as fixed-price with economic price adjustment under FAR Subpart 16.2 when the contract period is long enough that commodity-price volatility, wage inflation, or other market-driven cost changes warrant formulaic adjustment clauses, or as time-and-materials or labor-hour contracts under FAR Subpart 16.6 when the nature of the services makes fixed pricing impractical (though T&M and LH are less common for definite-quantity vehicles because the "definite quantity" concept presumes the government can quantify the requirement, which usually supports fixed pricing). Cost-reimbursement definite-quantity contracts are rare—the firm-quantity commitment typically implies enough requirement definition and cost certainty to support a fixed-price vehicle under the FAR 16.301-2 application test.

FAR 16.506 prescribes three categories of clauses for indefinite-delivery contracts. First, the ordering clause at FAR 52.216-18, Ordering, which establishes the procedures for issuing delivery orders or task orders, is mandatory for all three indefinite-delivery types (definite-quantity, requirements, and IDIQ) per FAR 16.506(a). Second, the order-limitations clause at FAR 52.216-19, Order Limitations, which the contracting officer tailors to specify minimum or maximum quantities per order and minimum advance-notice requirements, is prescribed by FAR 16.506(b) for use "when a definite-quantity contract, a requirements contract, or an indefinite-quantity contract is contemplated." Third, the definite-quantity clause at FAR 52.216-20, discussed above, is unique to definite-quantity contracts and prescribed by FAR 16.506(c). The requirements-contract clause (FAR 52.216-21) and the indefinite-quantity clause (FAR 52.216-22) are mutually exclusive with FAR 52.216-20—the contracting officer includes only the clause corresponding to the type selected.

Comparison to single-delivery fixed-quantity contracts

Practitioners sometimes ask when to use a definite-quantity contract versus a traditional fixed-quantity contract without the indefinite-delivery overlay (a firm-fixed-price contract under FAR Subpart 16.2 with a single delivery schedule specified in the contract at award, or a commercial-item contract under FAR Part 12 with delivery terms in the schedule). The answer turns on whether scheduling or location flexibility justifies the administrative overhead of an ordering mechanism. If the government knows at award not only the total quantity but also when and where each delivery or performance event will occur, a single-delivery or multi-delivery fixed-quantity contract is simpler—one contract award, one (or a few) pre-scheduled deliveries, one acceptance, one payment voucher (or a small number tied to milestones or deliveries). The indefinite-delivery structure under FAR Subpart 16.5 adds complexity: the contract is awarded, then individual orders are issued (each order is a separate obligation document, each may trigger a separate delivery and acceptance, each generates a separate payment voucher), and the contracting officer must ensure that the cumulative quantity of all orders equals the total quantity stated in the schedule. That overhead is worth incurring when the government cannot fix delivery timing or locations at award—perhaps because budget execution is uncertain, because the designated receiving activities have fluctuating warehouse capacity, because the supplies will support multiple programs with uncoordinated schedules, or because service performance must align with government-furnished equipment availability that cannot be predicted months in advance. When those conditions do not apply—when the government can specify "deliver 10,000 units to Building 123, Fort XYZ, by June 30" at the time of solicitation—the simpler fixed-quantity contract is preferable.

The use case: known total quantity, variable timing or locations

Definite-quantity contracts are appropriate for three canonical scenarios. First, recurring supply purchases where the government knows its annual or multi-year requirement but wants to spread deliveries across the fiscal year to match consumption, manage storage costs, or synchronize with budget availability—office supplies, vehicle parts, subsistence items, or IT hardware delivered in quarterly or monthly increments rather than in a single bulk shipment. The government commits to the total quantity (avoiding the demand-uncertainty risk of a requirements contract) but retains the flexibility to call off deliveries as warehouse space opens or as subordinate activities submit requisitions. Second, production contracts where the government is procuring a known quantity of end items but the delivery schedule depends on downstream integration, testing, or fielding plans that cannot be finalized at contract award—aircraft, vehicles, weapons systems, or major subsystems delivered in lots as the program office designates delivery dates and destinations (depots, test facilities, or operational units). The firm quantity supports the contractor's production planning and permits economies of scale; the ordering mechanism accommodates the government's schedule uncertainty. Third, service contracts for a known total level of effort—for example, a contract for 2,000 hours of specialized technical support services, with individual task orders issued to assign specific tasks, set performance periods, and designate work locations as requirements arise during the contract period. The government commits to purchasing the full 2,000 hours (giving the contractor certainty to retain qualified personnel), but retains discretion to allocate those hours among tasks and sites as mission needs evolve. In each scenario, the definite-quantity contract bridges the gap between the full commitment of a fixed-quantity contract (appropriate when timing and location are also known at award) and the contingent commitment of a requirements or IDIQ contract (appropriate when quantity itself is uncertain).

Source: FAR 16.502 Source: FAR 52.216-20 Source: FAR 16.501-2 Source: FAR 16.506

A basic ordering agreement (BOA) is one of the most frequently misunderstood instruments in federal acquisition. It is not a contract. FAR 16.703(a) defines a BOA as "a written instrument of understanding, negotiated between an agency, contracting activity, or contracting office and a contractor, that contains (1) terms and clauses applying to future contracts (orders) between the parties during its term, (2) a description, as specific as practicable, of supplies or services to be provided, and (3) methods for pricing, issuing, and delivering future orders under the basic ordering agreement." The regulation then states flatly: "A basic ordering agreement is not a contract." This is not a technicality—it is the foundational legal characteristic that distinguishes BOAs from indefinite-delivery contracts under FAR Subpart 16.5 (definite-quantity, requirements, and indefinite-quantity contracts) and determines how BOAs may be used, when orders become binding, and what obligations (if any) the parties assume when a BOA is executed.

The bright-line distinction: BOA versus IDIQ

The most common practitioner mistake is conflating a basic ordering agreement with an indefinite-quantity contract. Both are preliminary instruments that contemplate future orders, both establish pricing methodology and ordering procedures, and both permit multiple orders over a contract period—but the legal effect at the time of execution is categorically different. An indefinite-quantity contract under FAR 16.504 is a binding contract at award. It obligates the government to order—and the contractor to furnish—at least a stated minimum quantity of supplies or services (FAR 16.504(a)(1)), and it commits the government to appropriated funds in the amount of the guaranteed minimum at the time the contract is executed (the government incurs a recordable legal obligation for the minimum quantity; see GAO decisions B-308969 and B-302358, which confirm that IDIQ contracts require a bona fide need for the guaranteed minimum and that the minimum must be more than nominal to ensure the contract is binding). A BOA, by contrast, obligates neither party to anything when it is executed. FAR 16.703(c) mandates that "a basic ordering agreement shall not state or imply any agreement by the Government to place future contracts or orders with the contractor or be used in any manner to restrict competition." The government is free to place zero orders under a BOA, to compete each requirement outside the BOA, or to terminate the BOA without cause or cost. The contractor assumes no performance obligation and earns no revenue unless and until an individual order is issued and becomes binding under the procedures specified in the BOA itself.

The application standard under FAR 16.703(b)

FAR 16.703(b) establishes when a BOA may be used: "A basic ordering agreement may be used to expedite contracting for uncertain requirements for supplies or services when specific items, quantities, and prices are not known at the time the agreement is executed, but a substantial number of requirements for the type of supplies or services covered by the agreement are anticipated to be purchased from the contractor." This application test has three elements. First, uncertain requirements—if items, quantities, and prices are known or can be reasonably estimated at the time of negotiation, the contracting officer should use a definitive contract (firm-fixed-price, definite-quantity, requirements, or IDIQ) rather than a BOA. The BOA is appropriate when the government anticipates recurring needs but cannot define them tightly enough at the outset to commit to quantities or pricing structures. Second, substantial number of requirements anticipated—the BOA is not designed for one-off or occasional purchases; it is a streamlining tool for situations where the government expects multiple orders over the BOA's term. If the government anticipates only a handful of orders, the administrative overhead of negotiating and maintaining a BOA (annual review, compliance with updated FAR provisions) may outweigh the benefit. Third, anticipated to be purchased from the contractor—the regulation uses "anticipated," not "committed" or "guaranteed." The government expects to place orders with the BOA holder, but that expectation does not create an obligation. If circumstances change—mission requirements shift, budget constraints intervene, or competitive conditions evolve—the government may place orders elsewhere or not at all, without breaching the BOA.

FAR 16.703(b) also identifies the operational advantages: "Under proper circumstances, the use of these procedures can result in economies in ordering parts for equipment support by reducing administrative lead-time, inventory investment, and inventory obsolescence due to design changes." The BOA's value proposition is speed and flexibility. Once the BOA is in place—terms, clauses, pricing methodology, and delivery procedures all negotiated and agreed—individual orders can be issued rapidly, often on a single-page Optional Form 347 (Order for Supplies or Services) that incorporates the BOA by reference. The government avoids the need to conduct a full FAR Part 15 negotiated procurement or FAR Part 14 sealed-bid competition for each recurring requirement (though competition at the order level may still be required, as discussed below). The contractor benefits from pre-positioned status: the BOA establishes the contractor as a known, pre-qualified source, reducing the contractor's proposal costs for individual orders and providing visibility into the government's anticipated requirements even though no commitment exists.

Mandatory contents under FAR 16.703(d)(1)

FAR 16.703(d)(1) enumerates six elements that each BOA must contain. These are not optional; omission of any element renders the BOA non-compliant and potentially unenforceable when orders are issued. First, (i) describe the method for determining prices to be paid to the contractor for the supplies or services. This is the pricing methodology—not firm prices themselves (if firm prices could be established, the vehicle should be a definitive contract), but the process by which prices will be determined when orders are placed. Common methodologies include: catalog or market pricing (the contractor's published commercial price list, possibly with a negotiated discount); cost-plus-fixed-fee or cost-plus-percentage pricing for services where cost estimation is speculative; labor-hour or time-and-materials rates with negotiated hourly billing for specified labor categories; or a formula tied to indices or raw-material costs. The BOA must specify which methodology applies and provide enough detail that the contracting officer and contractor can determine price for an order without re-negotiating the methodology each time.

Second, (ii) include delivery terms and conditions or specify how they will be determined. Delivery terms—FOB point, delivery schedule, packaging, transportation responsibility—may be stated in the BOA if they are standard for all anticipated orders, or the BOA may specify that delivery terms will be negotiated or stated in each individual order. The key is that the BOA must address delivery, either by fixing it or by establishing the process for determining it.

Third, (iii) list one or more Government activities authorized to issue orders under the agreement. The BOA must identify which contracting officers or contracting activities have authority to place orders. This may be a single contracting office, multiple offices within an agency, or (with appropriate inter-agency agreement authority) offices across agencies. Any government activity not listed in the BOA lacks authority to issue orders, and any order issued by an unauthorized office is void. This provision ensures accountability and prevents unauthorized commitments.

Fourth, (iv) specify the point at which each order becomes a binding contract (e.g., issuance of the order, acceptance of the order in a specified manner, or failure to reject the order within a specified number of days). This is the binding-contract trigger and the most legally consequential element of the BOA. The BOA itself is not a contract, but each order issued under the BOA becomes a contract when the specified event occurs. The FAR offers three common formulations: the order becomes binding upon issuance by the government (the contractor is obligated to perform once the order is issued, without need for separate acceptance); the order becomes binding upon acceptance by the contractor in a specified manner (the contractor must sign and return the order, or acknowledge it in writing, before the obligation arises); or the order becomes binding upon the contractor's failure to reject the order within a specified number of days (a deemed-acceptance mechanism, where silence after a defined period constitutes acceptance). The choice among these formulations turns on the parties' risk tolerance and the nature of the supplies or services. Binding-on-issuance gives the government maximum assurance of performance but exposes the contractor to orders it may not have capacity to fulfill; binding-on-acceptance protects the contractor's right to decline orders but introduces delay and uncertainty for the government; deemed-acceptance via failure-to-reject splits the difference, permitting the contractor a narrow window to object while defaulting to acceptance if the contractor does not act. Whichever trigger the BOA selects, it must be explicit—ambiguity about when the order becomes binding creates dispute risk and may render the order unenforceable.

Fifth, (v) provide that failure to reach agreement on price for any order issued before its price is established (see paragraph (d)(3) of this section) is a dispute under the Disputes clause included in the basic ordering agreement. This dispute-resolution provision addresses the scenario where the contracting officer issues an order before price is finalized (permitted under limited circumstances in FAR 16.703(d)(3), discussed below). If the parties cannot agree on price after the order has been issued and performance is underway or complete, the disagreement is treated as a dispute under the Contract Disputes Act and the Disputes clause (FAR 52.233-1), giving the contractor the right to submit a claim, obtain a contracting-officer decision, and appeal to the agency board of contract appeals or the Court of Federal Claims if the decision is adverse. This provision ensures that pricing disputes are resolved through the established disputes process rather than left in limbo.

Sixth, (vi) if fast payment procedures will apply to orders, include the special data required by 13.403. Fast payment procedures under FAR 13.403 permit payment based on the contractor's submission of an invoice without waiting for government inspection and acceptance (used for low-dollar purchases of commercial items where the administrative cost of inspection exceeds the risk of nonconformance). If the BOA contemplates use of fast payment for some or all orders, the BOA must include the data elements FAR 13.403 prescribes (the contracting officer's determination that the conditions for fast payment are met, the dollar threshold below which fast payment will apply, and notice to the contractor of the fast-payment obligation).

Annual review requirement under FAR 16.703(d)(2)

FAR 16.703(d)(2) imposes a continuing maintenance obligation: "Each basic ordering agreement shall be reviewed annually before the anniversary of its effective date and revised as necessary to conform to the requirements of this regulation. Basic ordering agreements may need to be revised before the annual review due to mandatory statutory requirements." This annual-review rule ensures that BOAs remain compliant with the current FAR. When the FAR Council publishes a new FAR rule—particularly one affecting clauses, socioeconomic requirements, or competition procedures—the contracting officer must review all active BOAs and modify them to incorporate the updated provisions before the next order is issued (or before the next annual anniversary if no orders are imminent). FAR 16.703(c)(2) states: "A basic ordering agreement shall be changed only by modifying the agreement itself and not by individual orders issued under it. Modifying a basic ordering agreement shall not retroactively affect orders previously issued under it." This means the contracting officer cannot use an individual order to change the terms of the BOA (if a clause change is needed, the BOA must be formally modified via bilateral amendment), and any modification to the BOA applies only to orders issued after the modification—orders already issued and accepted remain governed by the version of the BOA in effect at the time they were placed.

Order-issuance procedures and competition requirements under FAR 16.703(d)

The fact that a BOA is in place does not eliminate competition requirements. FAR 16.703(d)(1) states the baseline rule: "Before issuing an order under a basic ordering agreement, the contracting officer shall—" and enumerates three threshold gates. First, (i) follow the policies in subpart 6.3 (Other Than Full and Open Competition) if the order is to be placed without providing for full and open competition. This cross-reference to FAR Part 6 means that if the contracting officer intends to place an order under the BOA without competing the requirement, the contracting officer must execute a justification and approval (J&A) under FAR 6.303 citing one of the seven exceptions to full and open competition in FAR 6.302 (only one source, unusual and compelling urgency, industrial mobilization, international agreement, authorized by statute, national security, or public interest). The existence of the BOA does not satisfy FAR Part 6—the contracting officer must independently justify why this particular order cannot be competed. Second, (ii) if the order is being placed after competition, ensure that use of the basic ordering agreement is not prejudicial to other offerors. If the contracting officer competes the order (solicits proposals from the BOA holder and one or more other sources), the fact that one offeror holds a BOA must not create an unfair advantage. The contracting officer must ensure that non-BOA offerors have access to the same information, terms, and evaluation criteria, and that the evaluation is conducted on an equal footing. If the BOA holder's pricing methodology or pre-negotiated terms give it a structural advantage that other offerors cannot match, the use of the BOA in that competition may be improper and vulnerable to protest. Third, (iii) sign or obtain any applicable justifications and approvals, and any determination and findings, and comply with other requirements in accordance with 1.602-1(b), as if the order were a contract awarded independently of a basic ordering agreement. This is the heart of the competition discipline: every order under a BOA must comply with the same statutory and regulatory requirements—synopsis, competition, J&A, small-business set-aside analysis, price reasonableness determination, funding certification—as if the BOA did not exist. The BOA streamlines the ordering process by pre-negotiating terms and pricing methodology, but it does not exempt the government from FAR Part 5 (publicizing the requirement if it exceeds $25,000), FAR Part 6 (competition), FAR Part 19 (small-business considerations), or FAR Part 15 (source selection and price reasonableness). The contracting officer treats each order as a standalone contract action for purposes of those requirements.

FAR 16.703(d)(2) prescribes the ordering instrument: "The contracting officer shall—(i) issue orders under basic ordering agreements on Optional Form (OF) 347, Order for Supplies or Services, or on any other appropriate contractual instrument; (ii) incorporate by reference the provisions of the basic ordering agreement; (iii) if applicable, cite the authority under 6.302 in each order; and (iv) comply with 5.203 when synopsis is required by 5.201." The OF 347 is a one-page standard form; the contracting officer completes it with the order-specific details (quantity, delivery date, destination, price if known), incorporates the BOA by reference (citing the BOA number and effective date), and—if the order is sole-source—cites the FAR 6.302 exception that justifies non-competitive placement. If the order exceeds the synopsis threshold ($25,000 for most supplies and services, or the simplified-acquisition threshold for certain commercial items), the contracting officer must synopsis the order in the Federal government's contract opportunities system (SAM.gov) under FAR 5.203, just as the contracting officer would for any standalone contract award.

The pricing-before-performance rule and its narrow exceptions under FAR 16.703(d)(3)

FAR 16.703(d)(3) establishes a critical discipline: "The contracting officer shall neither make any final commitment nor authorize the contractor to begin work on an order under a basic ordering agreement until prices have been established, unless the order establishes a ceiling price limiting the Government's obligation and either—(i) the basic ordering agreement provides adequate procedures for timely pricing of the order early in its performance period; or (ii) the need for the supplies or services is compelling and unusually urgent (i.e., when the Government would be seriously injured, financially or otherwise, if the requirement is not met sooner than would be possible if prices were established before the work began)." This is a two-part gate. The default rule is no work without price—the contracting officer may not issue a binding order or direct the contractor to begin performance until the order price is established. This rule implements fiscal-law principles (the government may not incur an obligation without knowing the amount to be obligated, per 31 U.S.C. § 1501) and protects both parties from open-ended cost exposure. The government avoids committing to an unknown price; the contractor avoids performing work at unknown compensation.

The regulation permits two narrow exceptions, both conditioned on the order establishing a ceiling price that caps the government's obligation. First, the BOA may include adequate procedures for timely pricing early in the performance period—for example, a methodology for provisional billing at estimated rates, coupled with a commitment to finalize pricing within 30 or 60 days after work begins, or a cost-reimbursement structure with a ceiling and a fee to be negotiated based on incurred costs. If the BOA contains such procedures, the contracting officer may issue the order with a ceiling and authorize work to start before final price is determined. Second, if the need is compelling and unusually urgent—a standard that parallels the unusual-and-compelling-urgency exception to competition in FAR 6.302-2—the contracting officer may authorize work before pricing is complete, provided a ceiling is established. "Compelling and unusually urgent" means the government would be seriously injured, financially or otherwise, if performance is delayed to permit pre-work pricing—operational emergencies, mission-critical failures, or theater demands that cannot wait. The regulation adds a follow-on obligation: "The contracting officer shall proceed with pricing as soon as practical. In no event shall an entire order be priced retroactively." Even when work starts before pricing is final, the contracting officer must finalize price promptly (while performance is ongoing or shortly after completion), and the entire order may not be priced retroactively after the fact—some portion of the pricing must be established before or during performance to anchor the parties' expectations.

Limitations: no commitment, no competition restriction

FAR 16.703(c) imposes two categorical prohibitions that enforce the BOA's non-contract status. "A basic ordering agreement shall not state or imply any agreement by the Government to place future contracts or orders with the contractor or be used in any manner to restrict competition." The first prohibition—no commitment—means the BOA may not contain language suggesting the government will place a minimum number or dollar value of orders, will obtain its requirements exclusively from the BOA contractor, or will give the contractor any preference when placing orders. Such language would convert the BOA into a requirements contract or indefinite-quantity contract, triggering the obligation and funding disciplines of FAR Subpart 16.5 and potentially violating fiscal law if the government has not obligated funds for the stated minimum. The second prohibition—no competition restriction—means the BOA may not be used to steer orders to the BOA holder or to deter competition from other sources. Each order must be competed (or justified as sole-source under FAR Part 6) on its own merits, and the BOA may not create a structural barrier to other offerors. GAO decisions (e.g., B-190663, B-211891) have enforced this limitation, holding that informal competition for orders placed under BOAs must comply with procurement principles and that BOAs may not be used to prequalify a single source in a manner that forecloses meaningful competition.

Distinction from blanket purchase agreements and basic agreements

Practitioners sometimes confuse basic ordering agreements with blanket purchase agreements (BPAs) under FAR 13.303 or basic agreements under FAR 16.702. A blanket purchase agreement is a simplified acquisition tool for filling anticipated repetitive needs for supplies or services by establishing charge accounts with qualified contractors (FAR 13.303(a)). BPAs are used for purchases at or below the simplified acquisition threshold (currently $250,000) and streamline ordering for commercial items and simple services. Like BOAs, BPAs are not contracts—they become binding only when individual orders (calls) are placed—but BPAs operate under the simplified-acquisition procedures of FAR Part 13, not the FAR Part 16 contract-type framework. BPAs are also used extensively as ordering mechanisms under GSA Federal Supply Schedules and other government-wide acquisition contracts (GWACs), where they permit individual agencies to establish pre-negotiated pricing and ordering procedures with schedule contractors (FAR 8.405-3). A basic agreement under FAR 16.702 is "a written instrument of understanding, negotiated between an agency or contracting activity and a contractor, that (1) contains contract clauses applying to future contracts between the parties during its term and (2) contemplates separate future contracts that will incorporate by reference or attachment the required and applicable clauses agreed upon in the basic agreement" (FAR 16.702(a)). Like BOAs, basic agreements are not contracts—"A basic agreement is not a contract" (FAR 16.702(a))—but basic agreements are used to pre-negotiate standard clauses and terms for future definitive contracts, not to establish ordering procedures for recurring requirements. Basic agreements are common in R&D contracting with universities and nonprofit organizations (FAR 35.015(b) specifically addresses basic agreements with educational institutions) and in situations where an agency anticipates awarding multiple separate contracts to the same contractor over time and wants to avoid re-negotiating standard terms for each contract. The basic agreement is incorporated by reference into each subsequent contract (FAR 16.702(d)), but each contract is a separate, fully competed, and fully documented procurement—there is no streamlined ordering process as with BOAs.

The use case: recurring requirements with uncertain scope, rapid ordering imperative

Basic ordering agreements are appropriate in three canonical scenarios. First, equipment parts and repair services where the government owns or operates complex equipment (aircraft, vehicles, IT systems), anticipates recurring part-replacement or maintenance needs, but cannot predict at the outset which parts will fail or what quantities will be required over the BOA term. The BOA establishes the contractor as a qualified source, negotiates catalog pricing or cost-plus-fee methodology for parts and labor, and permits the government to place rapid orders as equipment failures occur—avoiding the delay of conducting a FAR Part 15 negotiated procurement or FAR Part 14 sealed bid every time a component needs replacement. Second, surge or contingency support services where the government expects to need additional labor, logistics, or technical support on short notice but cannot define quantities or timing in advance. A BOA with a services contractor establishes labor rates, travel reimbursement policies, and ordering procedures; when the government's mission tempo increases or a crisis emerges, the contracting officer can issue a ceiling-price order under the BOA within hours or days, authorizing the contractor to deploy personnel while price is finalized under the BOA's pricing procedures. Third, commercial items with fluctuating requirements where the government buys from a contractor's catalog or established product line and wants streamlined ordering but cannot commit to firm quantities. The BOA incorporates the contractor's current catalog pricing (or a negotiated discount), defines delivery and acceptance terms, and permits individual contracting officers to issue orders as requirements arise—similar to a GSA schedule but tailored to a specific agency's anticipated needs and negotiated directly with the contractor rather than through the GSA schedules program.

Basic ordering agreements are not appropriate when the government can define its requirements tightly enough to commit to a minimum quantity (use an indefinite-quantity contract under FAR 16.504 instead, which provides the contractor greater certainty and the government a binding vehicle), when the government's requirements are exclusive to one contractor (use a requirements contract under FAR 16.503, which obligates the government to order all actual requirements from the contractor and eliminates competition for individual orders), or when the government's requirements are firm and known at the outset (use a definite-quantity contract under FAR 16.502 or a traditional fixed-quantity contract, both of which commit the government to the total quantity and permit more aggressive contractor pricing because quantity risk is eliminated). The BOA occupies the space where requirements are genuinely uncertain, where flexibility and speed are worth the cost of not committing the government or the contractor, and where the administrative overhead of maintaining the BOA (annual reviews, order-by-order competition or justification, synopsis compliance) is justified by the volume and frequency of anticipated orders.

Source: FAR 16.703 Source: FAR 16.702 Source: FAR 13.303

Section 1804(c) of the National Defense Authorization Act for Fiscal Year 2026 (P.L. 119-60, enacted December 18, 2025) raises the threshold for mandatory submission of certified cost or pricing data under the Truthful Cost or Pricing Data Act (formerly the Truth in Negotiations Act, commonly called TINA) from $2 million to $10 million for Department of Defense contracts entered into after June 30, 2026. The provision amends 10 U.S.C. § 3702(a) directly; it does not amend the parallel civilian-agency statute at 41 U.S.C. § 3502, nor does it amend the Federal Acquisition Regulation. This is the first statutory increase to the DoD TINA threshold in decades and represents a fivefold jump from the $2 million baseline (which had been inflation-adjusted to $2.5 million under FAR 1.109 as of 2024).

The June 30, 2026 effective date and DoD contract-award timing

For DoD procurements, the $10 million threshold applies to contracts entered into after June 30, 2026. Section 1804(c) preserves the prior threshold—$2 million as stated in the pre-amendment version of 10 U.S.C. § 3702(a), or $2.5 million as adjusted for inflation in the FAR—for contracts entered into on or before June 30, 2026. "Entered into" means the date the contract is executed by the government, not the date of solicitation, proposal submission, or final negotiations. A DoD contract signed on June 30, 2026, is governed by the $2.5 million threshold (or the then-current FAR inflation adjustment); a contract signed on July 1, 2026, is governed by the $10 million threshold by force of statute.

For subcontracts under DoD prime contracts, Section 1804(c) establishes a split rule. For prime contracts entered into after June 30, 2026, the subcontract TINA threshold is $10 million. For prime contracts entered into on or before June 30, 2026, the subcontract threshold remains at the level in effect when the prime was entered into—$2 million per the pre-amendment statute, adjusted for inflation to $2.5 million per FAR 1.109 as of 2024—even if the subcontract itself is awarded after June 30, 2026. This date-of-prime-contract rule preserves the TINA obligations that flowed down to the prime contractor at the time of prime-contract award.

Automatic application to modifications of existing contracts: the June 2020 FAR clause mechanism

Whether the $10 million threshold applies automatically to modifications of DoD contracts entered into on or before June 30, 2026 depends on which version of the FAR TINA clauses the contract incorporates. In June 2020, the FAR Council revised FAR 52.215-10 (Price Reduction for Defective Certified Cost or Pricing Data), FAR 52.215-11 (Price Reduction for Defective Certified Cost or Pricing Data—Modifications), FAR 52.215-12 (Subcontractor Certified Cost or Pricing Data), and FAR 52.215-13 (Subcontractor Certified Cost or Pricing Data—Modifications) to include automatic threshold-adjustment language tied to FAR 1.109 inflation adjustments. The current (post-June-2020) versions of FAR 52.215-12 and FAR 52.215-13 state: "If the threshold for submission of certified cost or pricing data specified in FAR 15.403-4(a)(1) is adjusted for inflation as set forth in FAR 1.109(a), then pursuant to FAR 1.109(d) the changed threshold applies throughout the remaining term of the contract, unless there is a subsequent threshold adjustment."

Additionally, the June 2020 revisions to FAR 52.215-11 (for prime-contract modifications) and FAR 52.215-13 (for subcontract modifications) added the phrase "on the date of execution of the modification" to the operative trigger in paragraph (a)(1). FAR 52.215-11(a)(1), as revised, now states: "This clause shall become operative only for any modification to this contract involving a pricing adjustment expected to exceed the threshold for submission of certified cost or pricing data in Federal Acquisition Regulation (FAR) 15.403-4(a)(1) on the date of execution of the modification." FAR 52.215-13(a)(1) contains parallel language. This temporal hook means the threshold applicable to a modification is determined by the threshold in effect at the time the modification is executed, not the threshold in effect when the base contract was awarded.

For DoD contracts that include the June 2020 or later versions of these clauses, the $10 million threshold will likely apply automatically to modifications executed after June 30, 2026, if and when FAR 15.403-4(a)(1) is amended to reflect the new statutory threshold. The clause's cross-reference to FAR 15.403-4(a)(1) is dynamic—it points to whatever threshold FAR 15.403-4(a)(1) specifies at the relevant time. Section 1804 directs implementing regulations to be issued within 180 days of enactment (by approximately June 16, 2026), but if the FAR Council has not yet amended FAR 15.403-4 by June 30, 2026, the regulatory text will still reference the $2.5 million threshold even though the statute (10 U.S.C. § 3702(a)) will mandate $10 million for new DoD contracts. In that scenario, whether the clause's FAR 15.403-4(a)(1) cross-reference picks up the statutory change without a published FAR amendment is an open question—the clause text itself does not resolve whether "the threshold… specified in FAR 15.403-4(a)(1)" means the text currently printed in the FAR or the threshold that must be applied under governing statute. Practitioners should assume that once the FAR is amended (whether by interim rule, final rule, or class deviation), contracts with the June 2020 clauses will apply the $10 million threshold to modifications executed thereafter without further contract modification. Until the FAR is amended, contracting officers and contractors negotiating modifications in the July–August 2026 window should document in writing which threshold will apply to avoid disputes.

For contracts that include older clause versions—those awarded before June 2020 and not subsequently updated—the automatic-adjustment language is absent. Pre-June-2020 versions of FAR 52.215-11, for example, stated simply: "This clause shall become operative only for any modification to this contract involving a pricing adjustment expected to exceed the threshold for submission of certified cost or pricing data at FAR 15.403-4," without the "on the date of execution of the modification" temporal reference and without the FAR 1.109 automatic-adjustment provision. Defense Contract Audit Agency guidance historically interpreted these older clauses to mean that threshold adjustments (whether inflation-driven or statutory) do not automatically apply to modifications of existing contracts; the contracting officer must issue a bilateral modification to update the threshold if the parties wish the new threshold to govern future modifications. Contractors holding DoD contracts with pre-June-2020 clauses should request that the contracting officer modify the contract to incorporate the current clause versions. FAR 15.408 prescription notes indicate such modifications are executed "without requiring consideration" (they are administrative updates benefiting both parties by reducing compliance burden), though the contracting officer retains discretion to decline if administrative workload or program-office policy disfavors mass clause updates.

Civilian-agency contracts: no statutory change, FAR rulemaking required

Section 1804(c) does not amend 41 U.S.C. § 3502, the statute governing TINA for civilian-agency contracts. That statute continues to specify a $2 million threshold (inflation-adjusted to $2.5 million under FAR 1.109). Legislative history and post-enactment agency statements suggest Congress expects the FAR Council to amend FAR Part 15 to harmonize the TINA threshold at $10 million government-wide, consistent with longstanding policy of maintaining identical thresholds for defense and civilian procurement. However, until the FAR is amended, civilian agencies remain bound by 41 U.S.C. § 3502 and the current FAR 15.403-4 threshold. Civilian-agency contractors should not assume the $10 million threshold applies to non-DoD contracts entered into after June 30, 2026, unless and until (i) the FAR Council publishes an interim or final rule amending FAR 15.403-4, or (ii) the contracting agency issues a class deviation under FAR 1.404 authorizing application of the higher threshold to its contracts. The FAR rulemaking process typically takes months; if the FAR Council meets the 180-day deadline in Section 1804, a final or interim rule would be published by mid-June 2026, permitting the $10 million threshold to apply to civilian-agency contracts entered into after June 30, 2026. If rulemaking is delayed past June 30, civilian agencies will face a split regime—DoD contracts at $10 million by statute, civilian contracts at $2.5 million by regulation—until the FAR catches up. Contractors with pending civilian-agency proposals or contract modifications should monitor the Federal Register and coordinate with contracting officers to confirm which threshold will apply.

Practical effect and compliance planning

The threshold increase substantially narrows the population of DoD contracts and modifications subject to TINA's certified-cost-or-pricing-data requirement and defective-pricing liability. Negotiated contracts, sole-source awards, and modifications without adequate price competition in the $2.5 million to $10 million range will no longer require submission of Table 15-2 cost or pricing data (unless an exception under FAR 15.403-1 applies or the item is not a commercial product or service and no other exception is available). This aligns with the broader FY 2026 NDAA acquisition-reform objectives: reducing compliance burden for established contractors and lowering barriers to entry for nontraditional defense contractors.

Contractors should undertake three actions. First, inventory existing DoD contracts to identify which will remain active after June 30, 2026, and determine which FAR clause versions they incorporate—contracts awarded June 2020 or later likely have the automatic-adjustment clauses; contracts awarded before June 2020 likely do not. Second, for contracts with the June 2020 clauses, coordinate with contracting officers to confirm the government's interpretation of how the $10 million threshold will apply to modifications executed after June 30, 2026, especially if the FAR has not yet been amended by that date. Document this understanding in writing (e.g., in negotiation memoranda or modification cover sheets) to avoid disputes when the first post-June-30 modification is priced. Third, for contracts with pre-June-2020 clauses, request bilateral modifications to replace the outdated TINA clauses with current versions—such updates are typically executed without consideration per FAR prescription, and agencies are likely to accommodate because the updates reduce the government's TINA-review workload.

The $10 million threshold does not apply retroactively to contracts or modifications executed on or before June 30, 2026. A modification executed on June 29, 2026, is subject to the $2.5 million threshold even if performance extends past June 30. Contractors negotiating awards in late June 2026 may request that the contracting officer defer execution until July 1 to obtain the benefit of the higher threshold, though the government has no obligation to accommodate such requests.

Source: National Defense Authorization Act for Fiscal Year 2026, Pub. L. No. 119-60, § 1804(c) (2025) Source: FAR 52.215-11, Price Reduction for Defective Certified Cost or Pricing Data—Modifications Source: FAR 52.215-12, Subcontractor Certified Cost or Pricing Data Source: FAR 52.215-13, Subcontractor Certified Cost or Pricing Data—Modifications