GWACs: Government-Wide Acquisition Contracts Overview

Government-Wide Acquisition Contracts (GWACs) are pre-competed, multiple-award contract vehicles that allow federal agencies to procure information technology products and services without conducting separate, full-length acquisitions. Authorized under 40 U.S.C. § 11302, GWACs occupy a distinct category within the broader landscape of indefinite-delivery/indefinite-quantity contracts, offering both buyers and vendors a streamlined path to the federal marketplace. Understanding how GWACs operate, when they apply, and how they compare to similar vehicles is essential for any contractor pursuing federal IT and technology government contracting work.

Definition and scope

A GWAC is a task-order or delivery-order contract for information technology that has been designated by the Office of Management and Budget (OMB) for use across the entire federal government — not just the issuing agency. The designation is granted under authority vested in OMB through the Clinger-Cohen Act, codified at 40 U.S.C. § 11302, which requires OMB approval before any executive agency can establish a new GWAC.

Only a small number of agencies hold GWAC authority. As of the most recent OMB-approved list, 4 agencies operate designated GWACs:

1. GSA (General Services Administration) — operates Alliant 2, OASIS, and 8(a) STARS III
2. NIH (National Institutes of Health) — operates CIO-SP3 and CIO-SP3 Small Business through the NIH Information Technology Acquisition and Assessment Center (NITAAC)
3. NASA — operates SEWP (Solutions for Enterprise-Wide Procurement)
4. Department of Homeland Security — historically operated EAGLE, now largely succeeded by other vehicles

GWAC scope is restricted to IT-related acquisitions as defined in 40 U.S.C. § 11101, which covers hardware, software, services, and support. Non-IT professional services, construction, and research and development fall outside GWAC authority, though hybrid task orders may include incidental non-IT components. Contractors seeking a broader overview of federal vehicle types can consult the types of government contracts reference for full context.

How it works

GWACs function as umbrella contracts. An agency holding GWAC authority — called the Executive Agent — conducts a single, large-scale competitive solicitation, awards contracts to a pool of qualified vendors, and then makes that pool available to all federal agencies through a task-order process.

The mechanics operate in two phases:

Phase 1 — On-ramping (Becoming a Contract Holder)
Vendors respond to the Executive Agent's base solicitation, which typically evaluates technical capability, past performance, and price. Award confers a contract number, approved NAICS codes, and eligibility to compete for task orders. Most GWACs are multiple-award vehicles, meaning 50 or more vendors may hold a single GWAC simultaneously.

Phase 2 — Task Order Competition
Any federal agency (the "ordering agency") can issue a task order against the GWAC after obtaining an Interagency Agreement or Economy Act determination. The ordering agency conducts a streamlined competition among GWAC holders — not the full federal marketplace — using the contracting officer on their side and often a dedicated GWAC program office on the Executive Agent's side.

The ordering agency pays a program access fee to the Executive Agent. For NASA SEWP, that fee is capped at 0.75% of the task order value (NASA SEWP Program Office). NIH NITAAC charges a fee of up to 0.75% as well (NITAAC Fee Structure). These fees fund vehicle administration and are typically embedded in contractor pricing.

Task orders issued under GWACs are subject to the same regulatory framework as direct contracts — including DFARS compliance for defense orders, cybersecurity maturity model certification thresholds, and standard Federal Acquisition Regulation clauses.

Common scenarios

GWACs appear in three recurring procurement patterns across the federal government:

Enterprise IT Refresh — An agency needs to replace aging hardware across 40 field offices. Rather than issuing a full competitive solicitation, the agency's contracting officer places a task order against NASA SEWP, which already holds negotiated, pre-competed pricing from hardware resellers and OEM partners.

Cybersecurity Services — A civilian agency needs to procure a managed security operations center. The agency uses NIH CIO-SP3, which explicitly covers cybersecurity services under its technology domain scope, and runs a streamlined best-value competition among the existing pool of holders.

Small Business Set-Aside Delivery — An agency must meet small-business contracting goals. The 8a-business-development-program STARS III vehicle, operated by GSA, restricts competition to certified 8(a) firms, allowing the agency to fulfill both the procurement need and the set-aside requirement in a single action. Similar set-aside structures exist for other socioeconomic categories addressed in small business set-asides.

Agencies visiting governmentcontractorauthority.com will find that GWACs account for a substantial share of federal IT spend — GSA reported GWAC obligations exceeding $15 billion in fiscal year 2022 (GSA Data and Reports).

Decision boundaries

Not every IT procurement belongs on a GWAC. Contracting officers and vendors both benefit from understanding when a GWAC is the right vehicle and when an alternative applies.

GWAC vs. GSA Schedule (MAS)
The GSA Multiple Award Schedule (GSA Schedules Explained) is not a GWAC — it lacks formal OMB GWAC designation. The MAS covers a broader range of products and services beyond IT, and its competitive procedures differ. For pure IT requirements, GWACs typically offer more pre-vetted, IT-specialist vendors; the MAS offers broader product and service categories with more vendors overall.

GWAC vs. Agency-Specific IDIQ
An agency-specific IDIQ is restricted to the issuing agency; other agencies cannot order from it without a separate interagency agreement. A GWAC is explicitly government-wide from the point of award. If the requirement will be shared across multiple agencies, a GWAC eliminates duplicative competitive effort.

GWAC vs. Blanket Purchase Agreement
A blanket purchase agreement (BPA) is an ordering arrangement set up against an existing contract — including a GWAC. BPAs do not replace GWACs; they can be layered on top of them for recurring, defined-scope buys.

Key decision factors when evaluating GWAC applicability:

1. IT scope — Does the requirement fall within the statutory IT definition at 40 U.S.C. § 11101? Non-IT work requires a different vehicle.
2. Cross-agency use — Is more than one agency funding or using the deliverable? GWACs reduce duplicative solicitation overhead in shared-services models.
3. Set-aside goals — Does the requirement support a socioeconomic set-aside? Several GWACs restrict award pools by small-business category.
4. Existing holder status — Is the vendor already on the GWAC? Vendors not yet on the vehicle cannot compete for task orders without first pursuing an on-ramp.
5. Fee tolerance — Does the task order budget accommodate the Executive Agent's program access fee (typically 0.75%)?

Contractors without existing GWAC presence should monitor on-ramp solicitations posted on beta.SAM.gov, where Executive Agents periodically open new competition windows for additional contract holders.