GSA History and Major Milestones
The General Services Administration began life as a tidying-up operation. By the late 1940s the federal government had accumulated, in the way governments do, a remarkable collection of overlapping agencies: one to handle public works, another to buy supplies, a third to dispose of the leftovers from a finished war, and a fourth to look after the paper records of all of it. Someone, eventually, was going to have to put these into the same building and ask them to share a coffee pot.
That someone was the 81st Congress, which in 1949 passed the Federal Property and Administrative Services Act and, in the process, invented an agency whose entire purpose was to make the rest of the government slightly less chaotic about its furniture, its filing cabinets, and its real estate.
The 1949 consolidation
The Federal Property and Administrative Services Act of 1949 folded four organizations into one. The Federal Works Agency, which had grown up around New Deal public construction, brought buildings. The Bureau of Federal Supply brought procurement of goods. The War Assets Administration brought the considerable problem of what to do with surplus materiel from the Second World War — jeeps, typewriters, hangars, the contents of entire bases — once peacetime arrived and the government found itself with too much of everything. The National Archives and Records Service brought the records.
These were, on paper, four entirely different jobs. Building a courthouse, buying pencils, selling off a surplus airfield, and preserving the original of the Emancipation Proclamation are not obviously the same activity. The 1949 Act treated them as variations on a single theme: the federal government's relationship with its physical and administrative stuff. GSA was given the mandate to provide that stuff, manage it, and eventually get rid of it, on behalf of every other agency.
The statutory framework that emerged from this consolidation now lives in two large stretches of the U.S. Code. Title 40 covers public buildings, property, and works; Title 41 covers public contracts. Both are dense, both have been amended many times, and both still bear the imprint of that postwar tidying-up impulse. The official text is published by the Office of the Law Revision Counsel.
The National Archives, it should be said, did not stay put. In 1985 it was spun back out as the independent National Archives and Records Administration, on the reasonable theory that the people preserving the founding documents of the republic ought not to report to the same office that decides whether the federal government needs more swivel chairs. The other three functions, broadly speaking, are still the core of what GSA does.
The Brooks Act of 1965
By the early 1960s the federal government had discovered computers, which is to say it had begun buying them in large quantities without quite knowing how to do so. Each agency negotiated its own deals, often with the same handful of vendors, and the results were uneven in the way one might expect when several hundred independent buyers approach a small market with public money and limited expertise.
The Brooks Automatic Data Processing Act of 1965, named for Representative Jack Brooks of Texas, gave GSA central authority over federal procurement of automatic data processing equipment. The theory was straightforward: a single buyer, equipped with consolidated demand and full-time specialists, would get better terms than two hundred buyers acting separately. The practice was more complicated, as practice usually is, and the Brooks Act regime accumulated its own bureaucracy over the following decades. But the principle — that information technology procurement is a distinct discipline that benefits from centralization — has shaped federal IT buying ever since.
It is worth pausing on this, because the Brooks Act set GSA up to be, among other things, the federal government's technology buyer. That role would later expand into the Multiple Award Schedule program for IT, the Government-wide Acquisition Contracts (GWACs), and eventually the digital service organizations of the 2010s. None of that was visible in 1965. What was visible in 1965 was an IBM mainframe and a question of who, exactly, ought to sign the purchase order.
The Federal Acquisition Regulation
The Federal Acquisition Regulation, or FAR, did not arrive with GSA's founding. It was issued in 1984, jointly by GSA, the Department of Defense, and NASA, to consolidate what had previously been a sprawl of agency-specific procurement rules into a single uniform code. The FAR is now the primary rulebook for civilian federal procurement, and GSA is one of its three custodians. The current text is maintained at acquisition.gov.
The FAR is large. Reading it cover to cover is the kind of activity that career contracting officers undertake reluctantly, in pieces, and with strong coffee. But its existence — the fact that there is a single document, with section numbers, that governs how the federal government buys things — is itself a milestone. Before 1984, contracting officers had to know which agency's regulations applied to which transaction. After 1984, there was, at least in principle, one book.
The Clinger-Cohen Act of 1996
The Information Technology Management Reform Act of 1996, known in nearly all conversation as the Clinger-Cohen Act after its sponsors, did two things at once. It repealed most of the Brooks Act's central-buying authority over IT, on the grounds that the world had changed and centralized mainframe procurement made less sense in an era of distributed computing. And it created the role of agency Chief Information Officer, requiring each major federal agency to have one.
The shift was philosophical as much as procedural. Brooks-era IT procurement assumed that computers were rare, expensive, and best bought by specialists in a central office. Clinger-Cohen assumed that computers were everywhere, that every agency had its own technology strategy, and that what was needed was not a single buyer but a network of accountable executives. GSA's role shifted accordingly — from gatekeeper to provider of vehicles that agencies could use, or not, as they chose.
This is the period in which the Multiple Award Schedule program, the GWACs, and the various assisted-acquisition services began to look recognizably like their modern forms. GSA stopped trying to be the only door and started trying to be a useful door.
The digital services era
By the early 2010s a different problem had become visible. The federal government's public-facing websites, taken collectively, were not impressive. Some were excellent; many were not; the experience of interacting with the government online ranged from pleasant to distinctly Kafkaesque. In 2014, in the wake of the troubled launch of HealthCare.gov, GSA stood up 18F as an internal digital consultancy, modeled loosely on the United Kingdom's Government Digital Service.
18F was joined, over the following years, by a small ecosystem of other digital services: cloud.gov, a platform-as-a-service offering tailored to federal compliance requirements; login.gov, a shared identity service so that citizens did not have to invent a new username for every agency they encountered; and the longstanding usa.gov, the public front door to federal information. These were eventually grouped under Technology Transformation Services within the Federal Acquisition Service.
The digital services era is, in a sense, the third act of the Brooks Act story. Brooks centralized hardware procurement. Clinger-Cohen decentralized it. The 2010s reorganization centralized something different — shared platforms and standards — while leaving individual agencies to build their own applications on top.
The 2019 MAS consolidation
For most of its existence, the Multiple Award Schedule program was not, strictly speaking, a program. It was twenty-four programs. Each Schedule covered a different category — IT, professional services, office supplies, scientific equipment, law enforcement gear, and so on — and each had its own solicitation, its own terms, and its own institutional culture. A vendor selling both IT services and office furniture might hold contracts under two entirely separate Schedules and submit two entirely separate proposals.
In 2019 GSA consolidated all twenty-four Schedules into a single Multiple Award Schedule, with a single solicitation and a single set of terms. The category structure remained — vendors still proposed under specific Large Categories and Special Item Numbers — but the underlying contract was unified. The MAS Vendor Roadmap walks new contractors through the process as it now stands.
This was, in administrative terms, a substantial undertaking. Tens of thousands of existing contracts had to be migrated. Vendors had to consolidate their offerings. The internal GSA workforce had to be retrained. The consolidation took several years to fully execute, and the seams are still occasionally visible in the documentation. But the result is a procurement vehicle that more closely matches the way commercial sellers actually do business, which is to say, without rigid product-category boundaries.
The current shape of GSA
The agency that emerged from these milestones operates along three main lines. The Public Buildings Service owns or leases roughly the federal civilian real estate portfolio, applies the P100 Facilities Standards to its construction, and disposes of properties no longer needed through disposal.gsa.gov and gsaauctions.gov. The Federal Acquisition Service runs the MAS, the GWACs, GSA Advantage, GSA eBuy, the Reverse Auctions platform, the SmartPay charge card program, the City Pair air travel program, the Federal Fleet, and per diem rate-setting. Staff offices handle policy, including the parts of 41 CFR that govern federal property management, and coordinate with SAM.gov, the unified entity registration system.
The agency's organizational chart is published, along with the GSA Strategic Plan, on its website. Both documents are useful reading for anyone trying to understand how the various pieces fit together, because the pieces themselves do not always make obvious sense from the outside. There is a reason for that. GSA's structure reflects seventy-five years of accumulated decisions, each rational in its moment, layered on top of a 1949 consolidation that was itself a compromise.
A note on what GSA is not
GSA is sometimes confused with the Office of Management and Budget, which sets government-wide policy from inside the Executive Office of the President; with the Office of Personnel Management, which handles the federal workforce; and with the Government Accountability Office, which audits the rest of the executive branch on behalf of Congress. GSA does none of those things. It buys, it builds, it leases, it disposes, and it operates shared services. That is the whole job, more or less, and it has been the whole job since 1949.
The job has grown. The 1949 agency would not recognize cloud.gov, and the 1965 agency would have struggled to explain a category management strategy. But the underlying premise — that the federal government's administrative infrastructure benefits from being run by people who think about it full-time — has held up reasonably well across three quarters of a century, which is more than can be said for most postwar reorganizations.