Contract Vehicles in GovCon: IDIQ, GWAC, GSA Schedule Strategy

1792 words GovCon ProposalEngine

You won a seat on an IDIQ. Eighteen months later, your pipeline is empty because you never learned how the orders actually get competed. Or the reverse: you spent six weeks and a lot of money on IDIQ proposal writing for a vehicle where you had no realistic path to a single task order. Both failures are common, and both come from treating the contract vehicle as the prize instead of the starting line.

A vehicle gets you into a pool. Revenue comes from task orders, and task orders are won with a different skill set, a different timeline and a different set of documents than the vehicle proposal itself. This guide covers what each vehicle type is, how to decide which ones deserve a bid, how to write the vehicle proposal, and how to compete once you hold a seat.

How Contract Vehicles Change the Competition

On a standalone contract, you compete against everyone who can credibly do the work. On a multiple-award vehicle, you compete only against the other holders, and the government must give each holder a fair opportunity to be considered for each order under FAR 16.505. That is a smaller field and a more predictable one. You can name your competitors, read their public task order wins, and position against them before the solicitation drops.

The trade is that winning the seat guarantees almost nothing. Vehicles usually carry a minimum guarantee that is small. The real money lives in the orders, and those orders arrive on short notice with tight page limits. A team that is built for one large proposal a quarter will struggle with a vehicle that generates three task order responses a month.

Vehicles also change how agencies buy. A contracting officer with a Schedule contract in hand can order under FAR Subpart 8.4 without running a full and open competition. A program office with an IDIQ can issue a task order in weeks instead of months. That speed is the reason agencies push work onto vehicles, and it is the reason your capture clock starts earlier than the solicitation date.

IDIQ, GWAC, MAS and BPA: What Each One Is

These terms get used loosely. The distinctions matter because they determine which FAR rules apply, who can order, and how protests work.

IDIQ

Indefinite delivery, indefinite quantity contracts are governed by FAR Subpart 16.5. The government commits to a minimum and can order up to a stated maximum over the ordering period. Multiple-award IDIQs create the fair opportunity requirement under FAR 16.505. Single-award IDIQs do not, which is why a single-award vehicle is closer to a standalone contract in how you compete for the work.

GWAC

A governmentwide acquisition contract is an IT-focused multiple-award IDIQ run by an agency that OMB has designated as an executive agent. Examples include GSA Alliant 2, GSA 8(a) STARS III, GSA VETS 2, NASA SEWP and NIH NITAAC CIO-SP3. GSA OASIS+ covers professional services, but it is a multi-agency contract, not a GWAC. If a solicitation calls itself a GWAC, check who runs it and what OMB designation backs it.

MAS

The GSA Multiple Award Schedule is ordered under FAR Subpart 8.4. A MAS contract has a 5-year base and three 5-year options, up to 20 years. Pricing is negotiated by labor category and published, and agencies order against it directly. MAS is not an IDIQ in the FAR 16.5 sense, but it functions like one from a buyer's point of view.

BPA

A Blanket Purchase Agreement is an ordering instrument, not a contract vehicle in itself. Agencies can set up BPAs against the Schedule, and a BPA can be the real competition even after you hold a Schedule contract. A single-agency BPA against MAS is often where the actual revenue sits.

VehicleGoverning FARWho can orderProtests at GAO
Multiple-award IDIQFAR Subpart 16.5Agencies named in the vehicleLimited by dollar threshold and scope
GWACFAR Subpart 16.5GovernmentwideLimited by dollar threshold and scope
MASFAR Subpart 8.4GovernmentwideAvailable for Schedule orders
BPADepends on the parent vehicleAgencies that established itDepends on the parent vehicle

Deciding Which Vehicles Are Worth the Bid

Not every vehicle deserves a response. A vehicle proposal can consume as much effort as a standalone contract, and the payoff is a seat, not revenue. Score each opportunity against the following before you commit.

  • Ordering agencies. Which agencies can actually buy off this vehicle, and do you already sell to them? A GWAC open governmentwide is worth less to you than a single-agency IDIQ where you have three program offices.
  • Scope fit. Can your existing past performance carry the self-scoring? If the vehicle scores relevant projects and you have none in that domain, you will lose points you cannot recover.
  • Competitor density. How many holders will there be, and how many of them already own the work? A pool of 200 holders with 20 active competitors is a different bet than a pool of 30.
  • Cost to bid. Estimate the labor hours for the vehicle proposal and divide by the realistic task order value you can win in the first two years. If the ratio is bad, walk.
  • On-ramp timing. If you miss this window, when is the next one? Some vehicles on-ramp regularly; others do not.

For a deeper view of how to weigh these factors against your capture resources, see the win strategy and capture management guide.

Writing the Vehicle Proposal

Vehicle proposals are often self-scoring. The offeror claims points for relevant projects, certifications and systems, and must prove each claim with documents. That changes the writing job. You are not telling a story about why you are the best partner; you are building an evidence file that a evaluator can score line by line.

Build the scorecard first

Before you write a sentence, build a spreadsheet that mirrors the evaluation criteria exactly. Every row is a claim, a point value, the evidence you will attach, and the name of the person who owns it. If a claim has no evidence, it does not go in the proposal. This is the same discipline described in the proposal compliance guide, applied to a scoring rubric instead of Section L and M.

Write to the evidence, not the narrative

Most vehicle proposals fail on documentation, not prose. A project reference without a signed letter, a certification without the certificate number, a system description without a policy document: each of these loses points. Assign one person to chase documents and give that person a deadline two weeks before submission.

Keep the technical volume thin and exact

Vehicle proposals rarely reward long technical narratives. They reward clean cross-references between the claim, the evidence and the criterion. Use tables. Use the evaluator's language. Keep every section to the length the solicitation allows and no longer. For structure conventions that hold up under review, see the federal proposal structure guide.

Plan for the price volume

Many vehicles require ceiling rates or labor category pricing that will govern every task order you win. Do not set rates you cannot live with for five years. Model them against your actual loaded costs, your escalation assumptions and the discounts you expect to offer on task orders.

Winning Task Orders After Award

Task order responses are short-turn: commonly a few days to a few weeks, with tight page limits. The team that wins is the team that already has the boilerplate, the past performance library and the pricing model ready before the order drops.

  • Track the forecast. Read agency procurement forecasts and the vehicle's order history. Know which program offices buy what, and when.
  • Do the pre-work. Meet the program office before the order is issued. Understand the requirement, the incumbent and the evaluation criteria.
  • Maintain a reusable library. Keep cleared past performance write-ups, resumes, quality plans and pricing templates tagged by scope area so a response can start on day one.
  • Staff the response team in advance. Name a task order lead, a pricing lead and a compliance reviewer before you need them.
  • Read the order's evaluation criteria. Fair opportunity does not mean every order is scored the same way. Some are best value, some are lowest price technically acceptable.

If your team is drowning in short-turn responses, the guide to AI and RFP automation covers where automation actually helps and where it creates review risk.

Protests, On-Ramps and Staying on the Vehicle

Task order protests at GAO are generally limited to orders above $10 million for civilian agencies and $25 million for DoD, NASA and Coast Guard, or to claims that the order increases the scope, period or maximum value of the contract. Check the current text before you rely on a threshold, because these numbers change and the FAR is being rewritten under the Revolutionary FAR Overhaul. Confirm current section numbers rather than citing from memory.

On-ramps add new holders during the ordering period. Off-ramps remove inactive or non-compliant holders. Both are routine, and both mean your seat is not permanent. Treat the vehicle as a relationship you maintain, not a credential you earn once.

  • Submit required reports on time. Late or missing reports are a common off-ramp trigger.
  • Keep your SAM registration, certifications and insurance current.
  • Respond to every fair opportunity you can credibly win. Silence looks like disengagement.
  • Track your order volume against the vehicle's expectations and be ready to explain gaps.
  • Watch for on-ramp announcements and decide early whether to bid.

A 90-Day Plan for a New Vehicle Holder

The first 90 days after award set the pattern for the whole ordering period. Use them to build the machinery that makes task order responses fast.

  1. Days 1 to 15: Confirm your contract data in the agency's systems. Brief your delivery leads on the vehicle scope and the ordering agencies.
  2. Days 16 to 30: Pull the vehicle's order history and agency forecasts. Build a target list of program offices and requirements.
  3. Days 31 to 45: Assemble the reusable library: past performance write-ups, resumes, quality and management plans, pricing templates.
  4. Days 46 to 60: Meet program offices on your target list. Ask what they plan to buy and how they intend to compete it.
  5. Days 61 to 75: Run a dry-run task order response against a real or realistic order. Time it. Find the bottlenecks.
  6. Days 76 to 90: Set the operating rhythm: who watches the forecast, who owns pricing, who reviews compliance, and how fast you can turn a response.

For a broader view of how vehicles fit into an IT services strategy, see the federal IT contracting guide. When a task order lands, GovCon ProposalEngine reads the solicitation, builds the compliance matrix and drafts sections from your own library so a short response window is enough.

Managing active bids? GovCon ProposalEngine uses AI to extract every compliance requirement, match your institutional knowledge base, and produce section-by-section proposal drafts in minutes.

Start Free Trial