March 5, 2026

One of the most common—and most misunderstood—questions about APFIT is deceptively simple: what contract vehicles can actually be used to execute APFIT funding?
The short answer is encouraging: almost any viable contract vehicle can be used to capture APFIT funding, provided it meets a few critical conditions around ceiling, scope, and prime status.
APFIT does not prescribe a single “approved” contract vehicle. Instead, the program places responsibility on the service or component executing the funds to select and shape a vehicle that can legally and practically absorb a $10M–$50M procurement award.
What matters most is whether the vehicle:
If either of those conditions is not met, execution risk increases—often significantly.
Standalone contracts or Phase III purchase orders can be used in theory, but in practice they often introduce friction. As discussed in the transcript, a standalone Phase III purchase order capped at, for example, $15M may technically qualify, but scaling it up to support a larger APFIT award would likely require a scope and/or ceiling modification. That modification can be challenging, time‑consuming, or unattractive to a contracting officer—especially when procurement dollars are involved.
In other words, while standalone vehicles are not prohibited, they are often the least flexible option for APFIT execution.
Indefinite Delivery/Indefinite Quantity (IDIQ) contracts—particularly PhaseIII IDIQs with available ceiling—are frequently cited as strong candidates for APFIT. If the ceiling is already high enough and the scope aligns, the government can issue task orders or modifications without having to fundamentally restructure the contract.
Other Transaction Authority (OTA) agreements can also be used for APFIT, according to both transcript discussion and internal materials. OTAs are attractive because of their structural flexibility, particularly when transitioning from prior prototype efforts into procurement‑like execution.
That said, OTAs still must support a clear procurement deliverable, as APFIT funds are procurement dollars—not R&D. APFIT is about fielding and acquisition, not continued development.
FAR‑based contracts are often where teams can be the most strategic. If a company does not already have a suitable vehicle in place, APFIT funding can beleveraged—through a government champion—to justify standing up a new, flexible FAR‑based contract with a large ceiling.
In practice, this can look like:
Even GSA Schedule contracts may be viable in some APFIT scenarios. While not traditionally associated with large defense procurement transitions, they can be considered if they meet ceiling, scope, and execution requirements.The key takeaway is that APFIT does not artificially narrow the universe of options—it expands them, provided the fundamentals are sound.
One constraint is absolute: the APFIT recipient must be the prime contractor. You cannot route APFIT funding through a subcontractor position or “squeeze it through” a relationship with a large prime.
APFIT is intentionally contract‑agnostic. IDIQs, Phase III vehicles,OTAs, FAR‑based contracts, GSA schedules, and other structures can all work.The determining factors are not the label on the vehicle, but whether it:
Teams that think strategically about contract structure early—often before submission—are far better positioned to execute APFIT quickly and to leverage it into sustained, out‑year production funding.