Cook County IT Contract Amendments, 2026

Do Cook County IT contract amendments outnumber new awards?

Yes, as lines in the record. In Cook County's procurement dataset, read by us on 2026-10-14, the IT records include 63 new contracts and 131 amendments. We read the Procurement - Awarded Contracts & Amendments dataset, whose rows the publisher last updated on 2026-10-08. The window runs from 2021-01-01 to 2026-10-14 by the date the County released each record, and it holds 194 IT records in all.

The County's own notes say an amendment can be an extension, renewal, increase, decrease or scope change, and that its amount may be blank when it only extends a contract. We do not split the 131 by type here. Cook County IT procurement records also carry amounts, but an amount is often a multi-year ceiling or a shared master agreement, so we never divide one by users or years and never add them together. In the table below, the amount columns describe the new contracts only. The amendments column is a separate count of lines and carries no amount breakdown.

Read the 131 as lines, not as a rate at which new contracts get amended. The table counts new contracts and amendments by release date, and we have not matched any amendment to the contract it amends, so we make no claim about which contracts were amended. Amendments run from 21 to 29 a year across the 2021 to 2025 rows, and 10 in 2026 to date. The new contracts are held by 55 distinct awardees by recorded vendor name, and the largest awardee holds 3 of 63. We name no firm.

How many Cook County IT contracts needed Board of Commissioners approval?

Of the 63 IT new contracts, the County records 34 as requiring approval by its Board of Commissioners and 29 as not requiring it, with none left unrecorded. Cook County's records, read by us on 2026-10-14, mark 34 of 63 IT new contracts as requiring Board of Commissioners approval.

We report that as a record of County process, not a measure of contract size or quality. We infer no threshold or reason from the flag, and a contract recorded as not requiring Board approval is not thereby small, cheap or minor. The flag sits on the new contracts. We make no statement about approval of the 131 amendments.

For a private buyer the comparable question is internal: who in your organization must sign off on a new agreement, and who on a renewal, an increase or a scope change? If a provider's paperwork lets a renewal or price change take effect without a decision from you, ask where that sits in the agreement. Our auto-renewal clause guide covers what to look for.

What contract lengths did Cook County record for IT new contracts?

The County recorded all four length bands: 2 under one year, 30 from one to under three years, 18 from three to under five years, and 13 of five years or more. No new contract lacks a start or end date, and none has an end date before its start date. The bands cover the 63 new contracts only, and the 131 amendments are separate lines.

Cook County's records, read by us on 2026-10-14, list 63 IT new contracts, 13 of them five years or more in length.

These lengths are what a public body recorded, not advice for a private buyer. The argument usually made for multi-year terms is stability. The records cannot test it, because they hold dates, not outcomes, and a longer recorded length says nothing about how the work went or whether either side wanted out.

We hold that shorter agreements are generally better for the buyer, because long lock-ins mainly benefit the vendor. A public body's multi-year lengths are therefore not evidence that multi-year terms are a neutral or positive default for a Chicago small or midsize business. Ask whether your own situation shares the rules, review steps and budget cycles a public body buys under; most private buyers will find it does not. Our contract length explainer sets out the private-buyer side.

How do the City of Chicago's modifications differ from County amendments?

They are counted on different definitions, so we set them side by side and never merge them. The City of Chicago's contracts dataset, read by us on 2026-10-14, holds 190 IT original records and 173 modifications. The City's modification is a later revision of a record, while the County's amendment is an extension, renewal, increase, decrease or scope change.

We read the City's Contracts dataset, rows updated by the publisher on 2026-10-13, for records approved from 2021-01-01 to 2026-10-14: 363 records in all. The City's notes add two cautions. A negative modification removes scope and money, and a revision-zero record can be the transfer or re-issue of an earlier contract.

One caution on the counts: the 190 original records sit with 41 distinct awardees by the City's vendor ID, and the single largest holds 134 of them. By procurement type, JOINT PURCHASE accounts for 114 originals, 110 of them with that type's largest awardee. Where one awardee is most of a row, that row is one awardee's line items, not the City's practice, and we do not describe any count as how widely the City uses a method.

Lengths are thin too. Only blanket contracts, meaning repeated purchases, carry an end date in this dataset, so 138 of the 190 originals have no start or end date recorded. The rest run 5 under one year, 6 from one to under three years, 36 from three to under five years and 5 of five years or more. If you want to compare lengths, treat the County's bands as the fuller set and the City's as a partial one.

Is a count of records a census of public IT buying?

No. Cook County and City of Chicago portal records, counted by us on 2026-10-14, form a floor, not a census, of public IT buying. A record counts only when its description uses one of our listed terms or the body's own classification marks it. A description term says what a record mentions, not what was delivered, and we checked no contract.

The classification route does much of the work. In the County, 40 IT new contracts match no description term and were counted only because of the County's commodity type, while 16 mention software and 5 mention hosting, data centres, or managed or outsourced IT. In the City, 58 originals were counted only because of the City's contract type, and 79 mention software. Lead departments appear in the records too, such as Enterprise Technology with 14 County new contracts. We read these as how records are labelled, not as how heavily a department buys.

Some buying is absent by design. The sheet does not cover State of Illinois BidBuy, which has no machine-readable feed, or Chicago Public Schools, which has no contracts dataset in the open-data catalogs, or any purchase the two portals do not list. A contract line is also not a price per user, and we never set an amount beside a managed IT price. For how we treat providers that cite public-sector work, see our government vertical claims article.

What should a private Chicago buyer take from these records?

Take the questions, not the terms. IT Support Chicago's Contract Length position holds that shorter agreements are generally better for the buyer.

The case for a longer term is usually predictability of cost and staffing, and it deserves a fair hearing. If a provider offers a better rate for a longer commitment, ask what you give up for it: exit rights, price-increase clauses, renewal mechanics. Then price the same scope month to month or for a year. Ask what each tier includes before comparing any per-user rate, because a lower figure with narrower scope is not the cheaper offer.

A Service Level Agreement (SLA) earns its place mainly in longer, multi-year agreements, as a way to share pain with the provider. Under a year, or where the agreement allows termination for convenience, the better recourse is usually to terminate. Our comparison of SLAs and termination rights covers the trade-off.

Provider size is no shortcut either. The records say nothing about whether a larger firm served any public body better, and right-sizing to your own scope matters more than headcount.