What AI means to municipal procurement

Illinois municipalities purchase a wide range of goods and services to carry out their day-to-day responsibilities. Vehicles, software, insurance, road salt and engineering services are just a few examples. The statutes governing how those purchases happen have not changed much in a generation. The tools available to carry them out have changed considerably in the last two years.

That gap is worth a few minutes of your attention, and this article is an attempt to explain it plainly.

Start with what state law already permits

Cooperative purchasing is not new and it is not a shortcut around competitive bidding. It is competitive bidding conducted once, by one governmental unit, and then made available to others.

Three provisions matter here. The Governmental Joint Purchasing Act (30 ILCS 525/2 to 3) authorizes joint purchasing among governmental units. The Intergovernmental Cooperation Act (5 ILCS 220/3) permits units of local government to contract with one another to exercise their powers jointly and 44 Ill. Admin. Code 1.5420 addresses the administrative mechanics.

Taken together, these give Illinois municipalities considerable latitude to purchase through a contract another public entity has already competitively awarded.

The authority is not the constraint. Visibility is. There are thousands of cooperative contracts in circulation nationally. A village clerk in Illinois has no practical way of knowing which contract covers the service they need to buy next month. So they run their own solicitation instead.

What that costs

Running your own solicitation is not free.

A traditional local government solicitation takes six to nine months from identifying a need to executing a contract, and costs between $1,500 and $17,000 in staff time and direct expenses depending on complexity.

For a municipality with one purchasing agent, or with purchasing handled by a finance director who has four other jobs, that is not a rounding error. It is a meaningful share of the year.

Purchasing through an existing cooperative contract does not eliminate that work. It reduces it. Our experience across cooperative programs is that the timeline for drafting solicitations, obtaining approvals and conducting negotiations shrinks by more than half, and by as much as 60% for negotiated contracts.

Where the technology fits

Artificial intelligence (AI) is not going to purchase anything on your behalf, and any vendor suggesting otherwise should be treated with suspicion. It addresses four specific bottlenecks:

Finding the contract

Searching national, state and regional cooperative contracts at once, so a need can be matched to a competitively bid vehicle in minutes rather than weeks. This is the direct answer to the visibility problem described above.

Reading the documents

Reviewing lengthy solicitations and contracts in seconds and flagging missing clauses, inconsistent terms and gaps that are easy to miss on a manual read.

Checking compliance as you go

Running checks while a purchase moves rather than at the end, so the file stays audit ready instead of being reconstructed afterward.

Making sense of spend

Turning scattered purchasing records into an analysis that a finance officer can use, including comparisons from similar jurisdictions.

These tools can also apply scoring criteria consistently across submissions and document how each score was reached. That is genuinely useful. It is worth being precise about what it is, though: consistency and a clear record, not the elimination of bias. Any vendor who tells you their system is unbiased has told you something about the vendor.

This does not replace professional judgment. A procurement officer still has to confirm that the underlying solicitation met its own rules and that the scope and pricing actually fit. The point is not to skip diligence. It is to stop repeating work someone else has already done.

What Illinois expects of AI vendors

In July 2026, Governor JB Pritzker signed the Artificial Intelligence Safety Measures Act (SB 315). The Act, which comes into force in stages from January 1, 2027, regulates large AI developers through requirements including third-party audits, with civil penalties for non-compliance.

The Act does not impose obligations on municipalities as purchasers. It establishes a state expectation that AI systems are auditable and their developers will be held accountable. Municipalities should apply the same standard to what they purchase.

There is a practical local resource for doing that. In May 2025, the Illinois State Association of Counties (ISACo) published Generative AI Use by Local Governments (available at https://www.isacoil.org/generative-ai/). It was written for county officials but applies equally to municipal officials. Among its recommendations: require AI vendors to disclose how their systems work, what data they use, how they mitigate bias, how their tools can be audited and write those requirements into the contract.

That translates into four questions for any procurement platform.

1. Is compliance continuous or is it a final check? These are not the same product.
2. Does it surface cooperative contracts you can actually use? The value is in finding valid vehicles outside your current awareness.
3. Can it tell you what comparable jurisdictions paid? This is where spend analysis earns its place.
4. Can the vendor explain how the system works and how it is audited? If not, ISACo suggests caution.