Multi-Source Agreements: What They Are and Which Dates to Track

Procurement teams managing multi-source agreements often track option periods and renewal windows in a shared spreadsheet. That works until a base period quietly closes without a bridge contract in place, or an option gets exercised two weeks after the exercise window already shut. At that point you're either paying to re-compete the contract from scratch or negotiating a sole-source bridge that nobody wanted - and both cost far more than a missed calendar alert.

What is a multi-source agreement?

The term "multi-source agreement" is commonly used in government and defense procurement to describe what the Federal Acquisition Regulation formally calls a multiple-award indefinite-delivery/indefinite-quantity contract - written as a multiple-award IDIQ or MAC (multiple award contract).

The structure works in two levels. First, the government runs a competition, qualifies a pool of vendors, and awards slots on the contract to several of them. Each awardee is "on the vehicle" but gets no guarantee of actual work - they get the right to compete for individual task orders or delivery orders as requirements arise. This is governed by FAR 16.504(c), which establishes a preference for multiple-award vehicles over single-award contracts when volume is large enough to support competition at the order level.

Major government-wide vehicles like GSA's OASIS+ (professional services) and NASA SEWP (IT products) follow this model. So do thousands of agency-specific IDIQs across defence, healthcare, and infrastructure. When people outside federal procurement use "multi-source agreement," they almost always mean this type of vehicle, regardless of whether they use the FAR terminology.

Most multiple-award IDIQs follow a standard time structure: a base period of one to five years, followed by option periods - typically four one-year options - giving a total ordering life of up to five years for civilian agencies, and up to ten years for DoD vehicles under DFARS 217.204(e). The base period and each option period must be formally exercised. Nothing carries forward automatically.

Key dates and periods inside a multi-source agreement

A single IDIQ doesn't just have one expiry date. It carries several, operating at different levels - and each one has real consequences if missed.

Base period end date. When the initial contract period closes. If the contracting officer doesn't exercise the first option before this date, the contract lapses. Re-competing the whole vehicle is the usual result.

Option period end dates. Each option period has its own end date. On a five-year vehicle with a one-year base and four one-year options, that's five distinct period-end dates, each requiring a separate exercise decision.

Option exercise deadlines. This is the date by which the contracting officer must send written notice that the next option is being exercised. Under FAR 17.207(a), that written notice must be sent "within the time period specified in the contract" - meaning the exercise window is set in the contract terms, typically 30 to 60 days before the current period ends (FAR 17.207, acquisition.gov). Miss the notice deadline and you've missed the option, even if the period itself hasn't technically closed yet.

Ordering period close. The date after which no new task orders or delivery orders can be placed against the master contract. Existing orders can still run, but no new work can be initiated once this date passes.

Individual task and delivery order expiry dates. Each order placed against the master contract has its own period of performance. A task order issued in year four of a five-year IDIQ might carry an 18-month performance period, running well past the ordering period close. These dates need tracking separately from the parent contract.

Key reporting and invoicing deadlines. Many orders carry progress reporting milestones, invoice submission cutoffs, and close-out dates. Missing these affects payment processing and past-performance ratings.

Why these dates are hard to track

A multiple-award IDIQ that's been running for three years generates a lot of dates. Start with the parent contract's five period-end dates, multiply by the number of awardees (often five to twenty vendors), add the task orders each has received, and each of those orders has its own performance period, reporting milestones, and invoicing cutoffs.

The decision that matters most - whether to exercise the next option - also needs to happen well before the exercise deadline. A contracting officer needs time to assess past performance, confirm funding availability, and prepare the formal determination and finding that FAR 17.207(c) requires before the notice goes out. In practice, option decisions often need to start two to three months before the written notice is legally due.

That creates three distinct dates for every option: the internal decision point, the written notice deadline, and the period-end date. Three dates per option period, across multiple vehicles, with different notice windows in each contract. A spreadsheet that records only one expiry date per contract misses all of this.

How to track them

Manually. For a small team managing one or two vehicles with a handful of awardees, a well-maintained spreadsheet works. Record the base period end date, each option period end date, and the notice deadline for each option (typically 30-60 days before the period end, per contract terms). Add calendar reminders at 90, 60, and 30 days before each option exercise deadline. Assign one named person as owner for each vehicle.

The system breaks down when the vehicle count grows, when task order expiry dates need tracking alongside parent contract dates, or when ownership changes and no formal handover happens.

With Lapsewise. Add each period of a multi-source agreement as a separate record in the Contracts module: base period as one record, each option period as another. Set the notice period on each record to match the option exercise deadline in the contract terms. Lapsewise sends reminders before each date in the assigned owner's timezone, so the contracting officer gets flagged when the internal decision window opens - not the day before the notice is legally due.

For task and delivery orders, add each active order as its own record with its period of performance end date and any reporting milestones. One dashboard shows all dates across all levels, sorted by what's due soonest. The contract management software page covers what the Contracts module tracks, including notice periods, document storage, and status views.

Common mistakes

Tracking only the master contract end date. A team that records just the five-year vehicle expiry misses every option exercise deadline along the way. The contract doesn't send reminders - that's the contracting officer's job, and it only happens if there's something surfacing those dates proactively.

Starting the option decision process too late. The written notice requirement has a fixed deadline, but the internal steps (past-performance review, D&F documentation, funding confirmation) take time. Starting the decision process 30 days out when you need 45 days of internal review creates a problem. The action date needs to be earlier than the notice deadline. Why Renewal Reminders Fail covers this failure pattern in detail.

Letting a base period expire without a bridge. If an option can't be exercised because of a funding delay, a bridge contract provides continuity while the situation resolves. But bridge contracts require their own procurement action and take time. Without early warning, you're negotiating a bridge under pressure, often at unfavorable terms.

Forgetting task order performance periods. When a vehicle's ordering period closes, active task orders continue running. Each has its own expiry and close-out requirements. They don't disappear when the parent contract's ordering period ends.

Single-person ownership. When one person manages all the option-period tracking in their head or their inbox, the dates travel with them when they move on. See Contract Renewal Reminders: Stop Missing Deadlines for how to build a tracking system that survives personnel changes.

Frequently asked questions

How many option years does a typical federal IDIQ have?

The most common structure is one base year plus four one-year option periods, for a five-year total. DoD vehicles can go to ten years (often a five-year base with one or more option periods) under DFARS 217.204(e). Government-wide vehicles like the GSA Multiple Award Schedule operate on a different model and don't follow the same base-plus-options structure.

What happens if an option period isn't exercised in time?

If the written notice isn't sent before the deadline in the contract, the contracting officer has generally lost the right to exercise that option. Continuing performance past the period end without a formal exercise creates a constructive contract modification and potential Anti-Deficiency Act issues. The practical outcome is either a bridge contract (a new procurement action under time pressure) or a full re-competition of the requirement.

Can Lapsewise track multiple contracts under one umbrella?

Yes. You can create individual records for each period of a single vehicle (base period plus each option year), plus separate records for active task and delivery orders. All of them appear in the same Contracts dashboard, sorted by upcoming dates. See Expiry Tracking 101 for how to structure a tracking system that covers multiple layers of dates across a contract portfolio.

Is a multi-source agreement the same as a blanket purchase agreement (BPA)?

No. A BPA is a simplified ordering arrangement established against a GSA Schedule, typically with one vendor, requiring no separate competition. A multiple-award IDIQ involves a full competitive procurement, a formal contract award to multiple vendors, and a structured ordering period with guaranteed minimums. The FAR provisions, option period rules, and compliance requirements are different. When "multi-source agreement" is used informally in procurement, it almost always means a multiple-award IDIQ or MAC, not a BPA.