Requirements Contract

A Requirements contract obligates the government to purchase all its actual requirements for specified supplies or services exclusively from the contractor during the contract period, guaranteeing the contractor exclusivity but not a minimum dollar amount.

What is a Requirements Contract?

A Requirements contract is defined in FAR 16.503 as an indefinite delivery contract in which the government agrees to purchase all of its actual requirements for specified supplies or services from the contractor during the contract period. Unlike an IDIQ contract, which has a stated minimum and maximum, a Requirements contract has no quantity minimum, the government commits only to exclusivity, not to a specific purchase level.

Key characteristics:

• Exclusivity commitment: the government agrees not to purchase the specified items from any other source during the contract period (the government must order all of its requirements from this contractor)
• No guaranteed minimum: the contractor is guaranteed exclusivity, not quantity. If the government has no requirements in a period, no orders are placed and the contractor receives nothing
• Actual requirements only: the government can only order quantities it actually needs. It cannot order more than actual requirements to give the contractor higher revenue, and it cannot withhold actual requirements to punish the contractor
• Delivery orders: individual requirements are placed as delivery orders as needs arise

Requirements contracts are appropriate when:

• The agency cannot estimate total quantity needs with certainty
• Demand is variable but the government will definitely have some requirements
• A single supplier is preferable for consistency, compatibility, or administrative efficiency

Common uses: fuel supply contracts, food service at fixed installations, medical supply contracts at single facilities, and recurring support services.

Why Requirements contracts matter for government contractors

A Requirements contract provides exclusivity without quantity certainty, the ultimate market position in a defined government market, but with revenue uncertainty. If the agency's actual requirements are high, the contractor benefits from the exclusive relationship. If requirements drop (due to downsizing, program changes, or competition from new sources), the contractor bears the revenue shortfall. When bidding on Requirements contracts, contractors must research the agency's historical consumption carefully, the contract's revenue potential is entirely dependent on actual usage patterns. Requirements contracts are also more commonly seen in supply-side contracting (fuel, food, parts) than in professional services.

Example

The Army issues a Requirements contract to a fuel supplier for all diesel fuel needed at a specific installation for 12 months. The installation's historical fuel consumption averages 2 million gallons per year, but actual requirements vary based on operational tempo. The contractor sets its per-gallon price based on cost modeling at 2 million gallons. During a high-operational period, the Army orders 2.8 million gallons, the contractor must supply all of it. During a reduced-activity quarter, orders drop to 300,000 gallons. The contractor cannot refuse to supply at the contracted price even at high volumes, and the Army cannot buy fuel from a competing supplier even when a better spot price is available.

Frequently Asked Questions

What happens if the agency tries to buy the contract items from another vendor during the Requirements contract period?

The agency would be in breach of contract. The contractor can file a claim for damages equal to the lost profits on the diverted purchases. The exclusivity commitment is legally binding on the government. This is why Requirements contracts are taken seriously by contracting officers, they limit the government's procurement flexibility in a meaningful way.

Can a Requirements contract have a minimum quantity?

FAR 16.503 allows including an estimated amount that creates a binding minimum: "The Government agrees to purchase... not less than a stated minimum amount." This hybrid gives the contractor some revenue floor while maintaining the exclusivity structure. In practice, most Requirements contracts do not guarantee a minimum.

What is the difference between a Requirements contract and a Blanket Purchase Agreement?

A Blanket Purchase Agreement (BPA) is not a contract, it is a simplified acquisition vehicle that sets terms and pricing for future purchases. A Requirements contract is a binding contract with the exclusivity commitment. BPAs are easier to establish and terminate; Requirements contracts provide more legal protection for both parties.

How does a Requirements contract affect competition law?

Requirements contracts are not anti-competitive under the Sherman Act because the government has sovereign immunity and the contract is awarded through a competitive process. The exclusivity is a contract right won in competition, not an anti-competitive restraint. Future competitions for the next contract period maintain competitive pressure on the exclusive contractor.