Understanding Contract Types: FFP, CPFF, T&M, and More

Intermediate

contract-types pricing risk acquisition

Contract Type Selection: The Tactical Art of Risk Allocation

Stop treating contract type selection like checking a box on a form. In my twenty-five years inside Air Force acquisition—ranging from depot modernization to rapid capabilities development—I’ve watched more programs stumble at this starting block than at any other. The contract type you choose isn’t just paperwork; it’s a strategic declaration about who owns the risk, how much innovation you’re willing to buy, and whether you’re acquiring a partner or merely purchasing a product.

Let me be direct: pick the wrong contract vehicle, and you’ve either handicapped your contractor before they start or written the government a blank check for mediocrity. Here’s how to think, lead, and execute this decision correctly.


Strategic Foundations (Think): Risk Algebra and Relationship Posture

Before you touch Standard Form 1449 or craft that Section B clause, understand the strategic calculus at play. Contract type selection is fundamentally about risk allocation. In the Department of Defense, we talk about “cost risk” like it’s an abstraction—it isn’t. It’s taxpayer money, mission readiness, and often, warfighter safety.

Strategic patience demands you match the contract type to your requirement maturity. If you’re trying to buy something that’s never been built before—say, a new autonomous refueling algorithm or a hypersonic thermal protection system—but you slap a Firm Fixed Price (FFP) requirement on it because “that’s what contracting prefers,” you’ve committed strategic malpractice. You’ve transferred all technical risk to a contractor who will either price in massive contingency (wasting appropriated funds) or cut corners to survive (endangering the mission).

Conversely, using Cost Plus Fixed Fee (CPFF) for established commercial laptops is equally foolish—you’re paying for surveillance overhead you don’t need while removing the contractor’s incentive for efficiency.

Remember our principle: Partners, not products. Cost-type contracts (CPFF, CPIF, T&M) signal partnership—you’re buying expertise and collaboration through uncertainty. Fixed-price contracts signal transaction—you’re buying defined outcomes. Choose your signal wisely.


Operational Leadership (Lead): Aligning Stakeholders and Intent

In Air Force acquisition, I learned that the Contracting Officer (KO) isn’t the only voice in this room, but they are the authority. Your job as a program manager or requirements lead is to bring them the context they need to bless the right vehicle.

Leadership means managing the tension between:

  • Finance: Wants budget certainty (pushes FFP)
  • Technical: Wants flexibility to iterate (pushes Cost-type)
  • Legal: Wants minimal surveillance burden (pushes FFP)
  • End User: Wants capability fast (pushes T&M)

Your operational task is building consensus around which risk matters most. Are you more afraid of cost overruns (go FFP) or fielding the wrong capability (go CPFF)? Are you trading innovation within constraints or just buying commodity?

Critical insight from the buyer’s side: When I sat on source selection boards at Wright-Patterson and the Pentagon, the contract type told me how much the program office trusted their own requirements. FFP with vague specs screamed, “We don’t know what we want, but we want someone else to pay for our ignorance.” CPFF with precise specs said, “We can’t control the unknowns, but we can manage the relationship.”

Values-based decision making enters here: If you choose CPFF or T&M, you are morally obligated to provide rigorous government surveillance. You’re asking taxpayers to fund uncertainty; they deserve oversight in return. If you choose FFP, you are ethically bound to provide rock-solid requirements. Asking a contractor to shoulder risk for your ambiguity is cowardly contracting.


Tactical Execution (Do): The Contract Types Decoded

Here’s your field manual. Intermediate practitioners need to know not just what these vehicles are, but when they live and die in the Air Force context.

Firm Fixed Price (FFP): The Accountability Standard

Use when: Requirements are stable,技术成熟 (technology is mature), and market prices are ascertainable. Think sustainment of existing systems, commercial off-the-shelf (COTS) integration, or production runs of proven hardware.

The Reality: The contractor owns 100% of cost risk. They exceed their cost estimate? Their problem. Material costs spike? Their problem. This creates powerful incentives for efficiency—but only if your specs are surgically precise.

Air Force Buyer’s Perspective: We love FFP for budget stability. Congress loves FFP for predictability. But here’s what kills programs: using FFP for development. I saw a major command try to FFP a next-generation radar interface that didn’t exist yet. The vendor low-balled to win, hit technical hurdles, and spent the next three years in claims litigation instead of coding. Innovation within constraints requires breathing room; FFP suffocates invention when requirements are fluid.

Tactical Watchout: FFP with economic price adjustment (EPA) clauses for multi-year buys. In today’s inflationary environment, don’t force contractors to price 2026 aluminum at 2024 rates unless you enjoy sole-source renegotiations or bad performance.

Cost Plus Fixed Fee (CPFF): The Partnership Platform

Use when: Requirements cannot be fully defined, or you’re in prototype/development territory. R&D contracts, new software development, integration of emerging tech.

The Reality: Government bears cost risk. Contractor gets reimbursed for allowable costs plus a fixed fee (profit). This enables strategic patience—you can discover the solution as you go without bankrupting the vendor.

Critical Tactical Element: You must resource robust Contracting Officer Representative (COR) surveillance. CPFF without granular insight into actual costs is a license for waste. The Air Force learned this painfully during the KC-46 and F-35 early days—insufficient oversight on complex cost-type vehicles leads to “cost growth” that makes headlines.

Values-Based Execution: Transparency is non-negotiable. If a contractor balks at open-book accounting on CPFF, find another contractor. You’re entering a partnership; secrecy has no place here.

Cost Plus Incentive Fee (CPIF): The Alignment Mechanism

Use when: You can define success criteria (technical performance, cost targets, schedule) but not necessarily how to get there.

The Reality: Share the risk based on performance. If the contractor beats the cost target, they keep a percentage of the savings; if they miss, they absorb a percentage of overruns. This creates partnership dynamics where you’re both pulling toward efficiency.

Tactical Application: Excellent for sustainment modernization where you know the end-state (reduce mean-time-to-repair by 40%) but not the exact engineering path. Better than CPFF for motivating efficiency, safer than FFP for immature solutions.

Time & Materials (T&M): The Bridge, Not the Destination

Use when: Urgent requirement, cannot define scope of work, typically used for quick-turn engineering support, emergency repairs, or transition periods.

The Reality: You pay for labor hours (negotiated rates) and materials (actual cost). This is dangerous territory—it’s essentially cost-reimbursement without the rigorous justification.

Air Force Context: We use T&M for rapid capabilities cells and urgent operational needs (UONs). But here’s the rule: T&M is for urgent prototypes, not production. Using T&M to buy 1,000 units of anything violates every efficiency principle I know. The contractor has zero incentive to finish quickly or cheaply—you’re paying for their time, not their solution.

Tactical Safeguard: Always negotiate a “Not-to-Exceed” (NTE) ceiling. Always. And convert to FFP or IDIQ as soon as the requirement stabilizes.

Indefinite Delivery/Indefinite Quantity (IDIQ): The Modern Workhorse

Multiple Award IDIQs (like SEWP, CHESS, or AF’s own NETCENTS) dominate contemporary acquisition.

The Reality: You compete for the contract vehicle (the “hunting license”), then compete task orders for actual work. This gives you strategic flexibility—you can pivot between vendors based on specific task order requirements.

Tactical Execution: Don’t treat IDIQ selection as “getting the contract.” The real work is Task Order competition strategy. Using single-source task orders under a multi-award IDIQ without justification is abuse of the vehicle.

Innovation Within Constraints: IDIQs enable rapid prototyping by letting you test small bets ($50K prototypes) with multiple vendors before committing to full FFP production. This is how the Air Force Rapid Sustainment Office (RSO) and AFWERX operate—small, fast buys under flexible vehicles.

Blanket Purchase Agreements (BPA) and Simplified Acquisition

For requirements under the simplified acquisition threshold (SAT) or commercial items, BPAs provide call-order efficiency.

Tactical Note: Perfect for partners, not products relationships with service providers or commodity suppliers. But remember: even simplified acquisition requires market research and basis for award documentation.


Strategic Takeaways

  1. Risk Follows Clarity: If you can’t write down exactly what you want, don’t expect someone else to price it. No clarity means cost-type; high clarity means FFP. Anything else is gambling with appropriated funds.

  2. Contract Type is Relationship Posture: Every CPFF contract requires partnership discipline; every FFP contract requires specification precision. Choose the relationship you need, not the administration you prefer.

  3. Surveillance is Proportional: The more risk the government assumes (cost-type), the more oversight resources you must apply. Underserved CPFF contracts become boondoggles; overstaffed FFP contracts waste surveillance dollars.

  4. Innovation Requires Appropriate Risk Sharing: You cannot outsource invention on a fixed-price basis. If you’re buying innovation—AI integration, additive manufacturing, digital engineering—you need cost-type flexibility or incentive structures that reward discovery.

  5. Values-Based Contracting: Whether FFP or CPFF, transparency in pricing and performance is non-negotiable. The taxpayer isn’t your adversary, and the contractor isn’t your enemy. Both deserve honesty about what the requirement actually costs.

Master these contract types not as bureaucratic categories, but as strategic tools for mission outcomes. The Air Force doesn’t buy products; we acquire capability through relationships. Choose your contract vehicle accordingly.

Execute with precision. Lead with context. Think before you sign.

Dr. Jesse W. Johnson Craftsman Leadership