Government-wide Acquisition Contracts: The IT Vehicle That Belongs to Everyone and No One in Particular
There is a peculiar category of federal contract whose entire reason for existing is that buying things in the federal government turned out to be harder than expected. The Government-wide Acquisition Contract, or GWAC, is one of those structures that seems strange until the alternative is described, at which point it begins to seem almost reasonable. It is a contract that one agency competes and signs, and that any other federal agency is then permitted to use, provided certain things are true.
The shape of the thing
A GWAC is, in formal terms, a pre-competed, indefinite-delivery indefinite-quantity (IDIQ) contract vehicle for information technology, established by one agency on behalf of the entire federal government. The General Services Administration runs most of the major ones. Once GSA has held the underlying competition and put a pool of qualified contract holders under contract, agencies issue task orders against that pool rather than running a fresh source-selection from scratch.
The mechanism rests on a designation. Under the Clinger-Cohen Act and subsequent guidance from the Office of Management and Budget, certain agencies are formally named as Executive Agents authorized to operate GWACs for IT. GSA is one. NASA is another, which is why SEWP — Solutions for Enterprise-Wide Procurement, run out of Goddard Space Flight Center — exists as a parallel and slightly different creature. The Department of the Interior used to operate one as well. The list is short on purpose.
A buying agency that wants to use a GWAC pays a small fee, issues a task order, and proceeds. The contracting officer at the buying agency still has to follow the Federal Acquisition Regulation, still has to compete the task order among the contract holders in most circumstances, and still has to document the file. What the contracting officer does not have to do is run a full FAR Part 15 source selection from a blank piece of paper. That is the entire point.
How a GWAC differs from the Multiple Award Schedule
A reasonable question, and one that confuses people for years before they sort it out: if GSA already runs the Multiple Award Schedule program, which any agency can also use to buy IT, why does a separate category called GWACs exist?
The answer turns out to be partly legal and partly cultural.
The MAS program, described by GSA on its overview pages, is a continuously open Federal Supply Schedule. A vendor applies, GSA negotiates pricing, and the vendor is added. The Schedule never closes. It covers an enormous range of products and services well beyond IT — furniture, professional services, security equipment, language interpretation. Agencies place orders against pre-negotiated prices, often without further competition for smaller buys, under the streamlined ordering procedures of FAR Subpart 8.4.
A GWAC is a different animal. It is a single, finite competition with a fixed pool of awardees, a defined ceiling, and a defined period of performance. When the period ends, the vehicle ends, and a follow-on must be competed. Task orders against a GWAC are issued under FAR Subpart 16.505, which has its own rules about fair opportunity, protests, and documentation. The competition was held once, at the front end, for the right to be one of the holders. After that, the work is distributed among holders by task order.
In practice, the cultural difference matters as much as the legal one. The Schedule is broad and shallow. A GWAC is narrow and deep. A GWAC is built around a specific community of practice — large IT integrators, small disadvantaged businesses, service-disabled veteran-owned firms, professional services providers — and the holders know each other, compete against each other repeatedly, and develop institutional knowledge of how the vehicle is run. There is a paddock quality to it.
The GSA-managed GWACs, in rough order of size and seriousness
Alliant 2 is the flagship for large, complex, full-scope IT solutions. It is unrestricted, meaning the holders are mostly large businesses, and the work runs to systems integration, cybersecurity, software development, and the large entangled programs that federal agencies tend to acquire when they are trying to modernize something. The ceiling is measured in tens of billions of dollars over the life of the vehicle.
8(a) STARS III is reserved for firms participating in the Small Business Administration's 8(a) Business Development Program, which serves socially and economically disadvantaged small businesses. The scope is similar to Alliant in technical breadth but the holders are exclusively 8(a) firms, and orders placed against STARS III count toward an agency's small business and 8(a) goals. It is a useful instrument for a contracting officer who has been told, with some firmness, to find more 8(a) work.
VETS 2 plays the same role for service-disabled veteran-owned small businesses (SDVOSBs). The technical scope covers IT services broadly, and the holders are a curated pool of SDVOSB primes.
OASIS+ is the slightly anomalous member of the group. OASIS, and its successor OASIS+, is technically classed by GSA as a Best-in-Class contract for professional services rather than a pure IT GWAC. It covers management consulting, engineering, scientific, financial, logistics, and technical services, with several different pools including unrestricted, small business, 8(a), HUBZone, WOSB, and SDVOSB. It is included in any honest survey of the GWAC landscape because it functions much the same way operationally, even if the regulatory pedigree is slightly different.
GSA's own page on Government-wide Acquisition Contracts lays out the current roster and the scopes; the agency keeps it current because the vehicles age out and get replaced on a roughly decade-long rhythm.
The non-GSA cousins
SEWP V, run by NASA, is the most prominent GWAC not operated by GSA. It is a product-heavy vehicle — hardware, software licenses, cloud, audiovisual — with a reputation for fast order processing and modest fees. Agencies use it heavily for commodity IT. SEWP VI is in development as of this writing and will replace V on the usual rolling schedule.
ITES-3, operated by the Army's Computer Hardware, Enterprise Software and Solutions (CHESS) office, is technically an Army contract but is available government-wide for IT services (ITES-3S) and hardware (ITES-3H). It is not a GWAC in the strict OMB sense — the Army is not designated as an Executive Agent — but it functions as a government-wide vehicle through interagency agreement mechanics, and contracting officers across the federal government use it.
The taxonomy here is fussier than it looks. A vehicle can be government-wide in the practical sense, meaning anyone can order from it, without being a GWAC in the technical OMB-designated sense. The distinction matters mostly to the lawyers and to the people who write congressional reports, but it occasionally matters to a contracting officer trying to figure out which authority cite belongs in the file.
Why the structure exists at all
It is worth stepping back to notice what problem this is solving. Federal procurement is governed by the Federal Acquisition Regulation, available in full at acquisition.gov, which is not a short document. A contracting officer running a competitive procurement from scratch for an IT services contract worth, say, fifty million dollars, will spend somewhere between nine and eighteen months on it, will write a source selection plan, will field questions from vendors, will evaluate proposals against published criteria, will document a tradeoff decision, and will then defend all of that against the protests that follow. The transaction cost is substantial, and most of it is borne by an agency that is trying to do something else for a living, like run the National Park Service or process veterans' benefits.
A pre-competed vehicle absorbs most of that work once, at the front end, and amortizes it across however many task orders get issued during the vehicle's life. The agencies issuing task orders still compete among the holders — fair opportunity is a requirement, with limited exceptions — but the competition is faster, the pool is known, and the contractual terms are settled. The trade-off is that the buyer is restricted to the holders. If the right firm for the job is not on the vehicle, the buyer either uses a different vehicle or runs a stand-alone procurement.
40 U.S.C. and 41 U.S.C., the relevant titles of the U.S. Code covering public property and public contracts, provide the underlying authorities. The FAR provides the operating rules. OMB designates the Executive Agents. GSA, NASA, and the others run the actual vehicles. The whole apparatus is, on close inspection, a slightly absurd pile of definitions invented by humans, but it functions, and the alternative — every agency running every IT procurement from scratch — is worse.
Task orders and how the work actually flows
The point at which a GWAC becomes real, for an agency, is the task order. The buying agency's contracting officer prepares a statement of work, decides on an evaluation approach, and issues a request for task order proposals to the holders in the relevant pool. Under FAR 16.505, task orders above the simplified acquisition threshold generally require fair opportunity to be considered, with documented exceptions for things like urgency, sole-source logical follow-ons, or minimum guarantees.
The holders respond, the contracting officer evaluates, and a task order is awarded. The award itself is generally not protestable at the Government Accountability Office for orders under certain dollar thresholds — the rules vary between civilian and defense agencies and have shifted over time — which is one of the operational reasons agencies prefer task orders to stand-alone contracts. The protest exposure is lower.
Each GWAC charges a small Contract Access Fee, typically a fraction of a percent of the order value, which funds the program office that runs the vehicle. The fees are visible, published, and predictable.
A few honest oddities
The vehicles overlap. An agency wanting to buy IT services from a small disadvantaged business could, depending on the specifics, use 8(a) STARS III, the small business pool of OASIS+, the small business reserve of MAS IT, or a direct 8(a) sole-source award. The choice among these is a matter of judgment, file documentation, and sometimes which program office returns calls faster.
The naming conventions are inconsistent. Alliant 2 follows Alliant 1. STARS III follows STARS II. OASIS+ follows OASIS. SEWP V follows SEWP IV. VETS 2 follows VETS. There is no master nomenclature; each program office names its own successors, and the result is a graveyard of expired vehicles whose names persist in old contract files for years afterward.
The boundary between a GWAC and an agency-specific contract used government-wide is genuinely blurry. ITES-3 is the obvious case, but there are others. A contracting officer trying to be precise will distinguish between OMB-designated GWACs, Best-in-Class contracts, and other government-wide vehicles. Most working documents do not bother.