If you already went through the C-type RFP training, you know how to build Sections L and M, pick a source selection method, and align your evaluation factors with your instructions. An IDIQ RFP uses all of the same tools. The UCF is the same. The FAR Part 15 evaluation process is the same. What changes is the set of decisions you need to make before you start writing, because an IDIQ is not buying a defined deliverable. It is establishing a vehicle that will generate orders for years.

A quick orientation: the base IDIQ contract itself carries a D in position nine of its PIID (FAR 4.1603(a)(3)). That covers IDIQs, Requirements contracts, Federal Supply Schedules, GWACs, and multi-agency contracts. The individual task orders, delivery orders, and BPA calls placed against that vehicle carry an F. The D is the vehicle you build once. The F is every order that flows from it.

This training is about the decisions you face when building the D. Specifically: how do you set the guaranteed minimum, should you evaluate price at the base contract level, how should you weigh your evaluation factors, how many contracts should you award, and how do you structure a vehicle that might run for a decade? Each of these questions has a different answer depending on what you are buying, and getting them wrong creates problems that persist for the life of the contract.

Every IDIQ must state a minimum quantity or dollar value the government is obligated to order (FAR 16.504(a)(1)). This is a binding commitment per awardee. If you award five contracts with a $500,000 minimum each, the government just committed to $2.5M in total minimum orders before a single task order is written. Courts and boards have sustained contractor claims when the government failed to meet the minimum, so this is not a theoretical number.

The FAR says the minimum must "exceed a nominal quantity" but must "not exceed the amount the Government is fairly certain to order." That gives you a range, and where you land in that range depends on the vehicle.

How the Minimum Gets Satisfied

The minimum guarantee can be satisfied in two ways, and which one you plan for matters:

Guaranteed work is almost always what you want. But on a multiple-award vehicle with 8 or 10 awardees, the reality is that some contractors get outbid every time. Maybe their rates are slightly higher, or maybe their proposals at the order level are consistently weaker. If one awardee has not received a single order halfway through the ordering period, you have a minimum guarantee problem coming.

You have a few options when that happens. You can sole-source an order to the contractor under the FAR 16.505 exception to fair opportunity to satisfy the minimum. That is not a bad solution. You just need a requirement on hand to tie it to, and you need to do it in the fiscal year that you award the contract because that is when the minimum guarantee obligation must be satisfied.

Setting the Right Number

On a C-type definitive contract, you evaluate price because that is the only competition. On a multiple-award IDIQ, you have a second opportunity to evaluate price: fair opportunity at the order level. That changes the calculus.

For a single-award IDIQ, you should evaluate price at the base contract level. There is no order-level competition. The rates you accept at award are the rates you live with for the life of the contract. Price evaluation is essential.

For a multiple-award IDIQ, the question is more nuanced. You will be competing price again at every task order, so the base contract rates are not the final word on what the government will pay. Some agencies still evaluate price at the base contract to ensure proposed rates are realistic and to establish rate ceilings. Others focus the base contract evaluation entirely on technical capability and past performance, deferring price competition to the order level where it is more meaningful because it is tied to specific work.

On a C-type contract, the factor weighting question is usually about technical vs. price vs. past performance. On an IDIQ, you have additional tools and different tradeoffs because of what you are actually trying to learn about the offeror.

Past performance may matter more than technical approach. On a C-type, the technical proposal describes exactly what the contractor will do on your specific contract. On an IDIQ, the technical proposal sometimes describes what the contractor can do in the abstract, because the specific work may not be fully defined yet. A construction IDIQ covers a variety of future projects. An IT services IDIQ covers whatever task orders come through. In those cases, past performance tells you what the contractor actually did on similar vehicles, which may be more revealing than a general capability narrative. A contractor's track record managing task orders, meeting schedules, and handling the ordering process on similar IDIQ contracts is concrete. Weighting past performance heavily, or even making it the most important factor, is defensible and sometimes the right call. (When you do have defined work, like a seed project, the technical response to that specific requirement is a different story.)

Seed projects can be the real discriminator. A seed project is an actual requirement that will be awarded to the winning contractor upon award of the IDIQ itself. Rather than asking offerors to describe their general approach to work that does not exist yet, you give them a real task order and have them respond to it as part of their proposal. This tests what matters: can they develop a responsive technical approach, staff it correctly, price it realistically, and deliver it on schedule? It also has a practical benefit: awarding the seed project satisfies the guaranteed minimum for that contractor. The downside on a multiple-award IDIQ is that you only have one seed project, so you only satisfy one awardee's minimum. The rest of the pool still needs work through the normal ordering process or a flat payment guarantee. For many IDIQs, the seed project response is the most useful thing in the entire evaluation.

You may not need a heavy technical evaluation. Consider what a technical approach volume actually tells you on an IDIQ. If the work is well-defined (construction, facility maintenance, commodity IT), two qualified contractors will write virtually identical technical narratives about how they plan to do the work. Past performance and a sample task may give you better differentiation than 30 pages of boilerplate about quality management systems.

FAR 16.504(c)(1)(ii)(A) says the contracting officer must, to the maximum extent practicable, give preference to multiple awards. A single-award IDIQ requires a written determination under FAR 16.504(c)(1)(ii)(D). So the default expectation is multiple awards. The question is how many.

The sweet spot is usually 4 to 6 awardees. That gives you enough contractors for meaningful order-level competition, enough backup if one underperforms, and enough diversity of capability to handle different types of work. It also keeps the awardee pool manageable for the ordering offices that have to run fair opportunity competitions.

But every vehicle is different. Some considerations:

IDIQs are flexible on duration. Because the base IDIQ does not obligate funds (except the minimum guarantee), you do not need option years in the same way a definitive contract does. You have several structural choices, and each one changes how the vehicle operates.

Straight ordering period, no options. You can write a 5-year IDIQ with a single 5-year ordering period and no option years at all. The government can place orders at any time during the 5 years. Each order has its own period of performance. There is nothing to exercise because there are no options. This is the simplest structure and it works well when the government is confident in the workload for the full period.

Base period plus option years. A 1-year base with 4 one-year options gives the government an off-ramp every year. If workload drops or the contractor pool is underperforming, you can decline to exercise the option and no new orders can be placed. If you include options, the RFP must include FAR 52.217-9 (Option to Extend the Term). Offerors price each period separately, which gives you visibility into rate escalation.

Extended vehicles with on-ramps. For large enterprise vehicles, you can structure a 5-year base ordering period with 5 one-year options, giving you up to 10 years. Under the RFO (FAR 16.504-4 and 16.504-5(h)(3)), any vehicle with an ordering period exceeding five years must include on-ramp and off-ramp provisions unless you document that on-ramps are not in the government's best interest. This is a powerful structure because you do not have to terminate poorly performing contractors; you just do not exercise their option and on-ramp a replacement.

IDIQs are useful in part because of this structural flexibility. You do not necessarily have to terminate a poor performer (which is a complex, contested process). You can just decline to exercise the next option period and on-ramp a better contractor. The government retains control without the adversarial process of a termination for cause.

The IDIQ RFP uses the same Uniform Contract Format as a C-type, but three sections look fundamentally different.

Section B defines the pricing structure for all future orders, not a single deliverable. For services, this is usually a labor category rate table. For supplies, it may be a catalog. Section B must state the minimum and maximum quantities or dollar values (FAR 16.504(a)(2)). Remember: the minimum is per awardee on a MA-IDIQ.

Section H is where the ordering procedures live. The ordering procedures should be included in the solicitation so offerors understand how the vehicle will operate before they decide to bid. They should also be incorporated into the PWS so the terms are part of the contract's performance framework. The ordering procedures need to describe the fair opportunity process at each tier, evaluation criteria for order competitions, response timeframes, exceptions, and (for vehicles over 5 years) on-ramp/off-ramp procedures.

Sections L and M evaluate whether the offeror belongs in the pool, not whether they can perform one specific job. The seed project is the most IDIQ-specific element: a real requirement the offeror responds to as part of their proposal, which will be awarded to the winner upon contract award. This tests their ability to develop a technical approach, staff it, and price it against actual work.

IDIQ contracts create protest exposure at two levels: the base contract award and the individual orders. Understanding both is important because it affects how you write the RFP.

Base contract protests follow the same rules as any FAR Part 15 competition. Offerors can protest the award decision to GAO or the Court of Federal Claims. The standard issues apply: evaluation consistency, unstated criteria, unequal treatment, cost/technical tradeoff documentation.

Order-level protests are more restricted. Under FAR Subpart 33.1, protests of task and delivery orders are generally limited to orders that increase the contract scope, period, or maximum value. However, there are dollar thresholds above which order-level protests are permitted: $10 million for non-DoD agencies, $25 million for DoD, NASA, and the Coast Guard. Contractors use these thresholds, and agencies awarding large orders under MA-IDIQs need to treat fair opportunity with the same rigor they would apply to a full-and-open competition.

Agencies must also designate a task-order ombudsman (FAR 16.507-2(b)), a senior official independent of the contracting officer, to review contractor complaints about fair opportunity. The base contract should identify or reference this role.

Before you start writing, answer these questions. If you cannot answer them confidently, you are not ready to write the RFP.

Single or multiple award? If multiple, you need a documented acquisition strategy. If single, you need a written determination under FAR 16.504(c)(1)(ii)(D) explaining why multiple awards are not practicable.

How many awardees? Match the pool size to your expected workload and the ordering offices' administrative capacity. 4 to 6 is a common sweet spot, but construction and facilities IDIQs sometimes go higher.

What is the minimum guarantee per awardee? Do the math: awardee count times per-awardee minimum equals your total guaranteed commitment. Can you realistically reach that number?

Are you evaluating price at the base contract? For single-award, yes. For MA-IDIQs, decide whether base-contract price evaluation adds value given that you will compete price at every order.

What are your evaluation factors and how are they weighted? Past performance may matter more than technical. A sample task or seed project may be more useful than a general capability narrative. Match your factors to what actually differentiates qualified offerors for this specific vehicle.

What is your ordering period structure? Straight 5-year with no options? Base plus options? Longer with on-ramps? If over 5 years, you need on-ramp/off-ramp provisions per FAR 16.504-4.

Have you written your ordering procedures? Fair opportunity tiers, evaluation criteria, response timeframes, exceptions, ombudsman identification. These belong in the solicitation (so offerors know what they are signing up for), in Section H (as part of the contract), and in the PWS (so the ordering procedures are part of the performance framework). Write this before you write L and M.

Where do on-ramps and off-ramps live? Both the solicitation (Section H or L) and the PWS. The solicitation covers the contracting process. The PWS covers the operational transition of work.