Why Local Procurement Data is Difficult to Aggregate
Data methodology
June 2026
State and local procurement records span thousands of agencies, systems, document formats, and records processes. Building a usable dataset requires collection, normalization, and source traceability.
State and local governments publish procurement records to support public accountability. These records include solicitations, contract awards, purchase orders, vendor lists, budget documents, and board materials.
The data is distributed across thousands of agencies. States, cities, counties, school districts, higher-education institutions, and special districts each use their own procurement systems and records processes.
A researcher studying a public-sector market may need to review hundreds of individual sources to understand a single category or vendor. Each source contributes a small part of the larger view of vendor activity and procurement patterns.
Many systems and document formats
Procurement records appear in a range of formats. Some agencies publish structured data through an open-data portal. Others use procurement platforms with searchable notices and attachments. Many records are published as PDFs, scanned documents, meeting packets, or spreadsheets.
The level of detail also varies by agency: one city may publish purchase order histories with vendor names and dollar amounts; another may publish a contract award notice with limited information. A school district may discuss a major procurement in a board agenda or meeting minutes. Each source requires its own collection process. The records then need to be converted into a consistent structure.
Vendor names require normalization
A single vendor can appear under several names across public-sector records. Legal entities, subsidiaries, acquired companies, abbreviations, and spelling differences can all create separate entries for the same business. For example, a software company may appear under its corporate legal name in one contract, its product brand in a purchase order, and a reseller’s name in a school district record.
Vendor names need to be reviewed and connected to the correct company. This process supports a clearer view of customer activity, spend, and competitive position.
Each document represents a different part of the buying process
A government procurement process can generate several documents: a solicitation describes an agency’s requirements and the vendors that may respond. A contract award identifies the selected vendor. A purchase order can show an individual transaction. A contract amendment may show an extension or change in scope.
Each record provides useful context. Together, they can show how an agency evaluated a purchase, which vendors were involved, and how the relationship developed over time.
Public records requests fill gaps
Many useful records are available online, although the sources are fragmented. Public records requests can provide access to additional purchase order data, invoices, vendor lists, contract documents, and communications.
The public-record request process varies by jurisdiction. States have different public-records laws, fee structures, response timelines, and exemptions. Local agencies also manage requests in different ways. Public records workflows can add detail to existing records and expand the available data for agencies that publish less information online.