City of Chicago IT Procurement Types, 2026
Chapters
Disclosure: this site is owned and operated by XL.net, a Chicago MSP that is itself ranked here. How we handle that conflict.
What do the City's IT procurement types look like on the record?
Two types hold most of the City's IT records: joint purchase with 114 original records and master agreement with 33, on our read of the City of Chicago Contracts dataset on 2026-10-14. Request for Proposals (RFP) and sole source follow at 4 records each, the smaller types hold 2 or fewer each, and 28 records carry no procurement type at all.
Our window runs from 2021-01-01 to 2026-10-14, by the date the City approved each record. We count an original record (revision zero) once and treat later revisions as modifications. The original records name 41 distinct awardees, which we count but never name. The table below gives each type as the City records it, next to the number of records held by that type's single largest awardee. Source: City of Chicago Contracts, dataset rsxa-ify5, rows updated 2026-10-13, read 2026-10-14.
A record is what the portal says and nothing more. We checked no contract, and a record enters our count only when its own description uses one of our listed terms or the City's own contract type marks it as Software, Hardware or Telecommunications. The counts are therefore a floor, not a census of City IT buying.
| Procurement type (as the City records it) | IT original records | Of them, held by the type's single largest awardee (never named) |
|---|---|---|
| JOINT PURCHASE | 114 | 110 |
| MASTER AGREEMENT | 33 | 3 |
| RFP | 4 | 1 |
| SOLE SOURCE | 4 | 1 |
| CONTRACT ASSIGNMENT/TRANS | 2 | 1 |
| REFERENCE CONTRACT | 2 | 1 |
| BID | 1 | 1 |
| CONTRACT ASSIGNMENT/TRANSFER | 1 | 1 |
| All other procurement types (1) | 1 | not counted |
| Not recorded | 28 | not counted |
TL;DR
The City of Chicago IT procurement types on the City's contracts portal (read 2026-10-14) are led by joint purchase at 114 original records and master agreement at 33. The joint-purchase count is almost entirely one awardee's line items, 110 of 114, so it describes a pattern in the records and not how widely the City uses a method. Master agreements show a much more even spread, with the largest awardee holding 3, and a recorded amount is not a price per user.
- Joint purchase: 114 IT original records, 110 held by the type's single largest awardee (read 2026-10-14).
- Master agreement: 33 records, largest awardee holds 3, a far more even spread (read 2026-10-14).
- Sole source and request-for-proposals records are 4 each, so a small count says nothing alone about competition versus direct award.
- Recorded amounts are often ceilings or blanket agreements; never divide them by users or set them beside a managed IT price.
Why is a joint-purchase count of 114 not the City's practice?
Because 110 of those 114 records are held by a single awardee, the row reads as one awardee's line items, not as a City-wide habit. In the City of Chicago Contracts dataset read on 2026-10-14, 110 of 114 joint-purchase IT original records belong to the type's largest awardee.
The same concentration shows up across the whole read. Of all 190 original IT records counted on 2026-10-14, 134 are held by one unnamed awardee. We report the type-level figure and the all-records figure separately and do not claim they describe the same firm. Either way, the lesson for a reader is the same: a count of records is a count of rows in a table, not a measure of how widely the City uses a method, a term or a department.
We also never divide records by awardees. With 41 distinct awardees on the original records, an average would suggest an even spread that the largest-awardee column plainly contradicts.
For anyone citing these figures, the practical check is simple: before repeating a procurement-type count, find the largest-awardee column for that same row. If one awardee holds most of the row, describe the row as concentrated, and do not describe it as a City preference.
How do master agreements differ from joint purchases?
Master agreements show a much more even spread, because the largest awardee holds only 3 of 33 original IT records on the 2026-10-14 read. The City of Chicago Contracts dataset, read on 2026-10-14, records 33 master-agreement IT original records, of which the largest awardee holds 3.
Set the two rows side by side and the point is clear: joint purchase has the larger count, master agreement the smaller, and the smaller count is the more evenly spread. Two types with large counts can mean very different things, and the count alone cannot tell you which.
Amounts need the same care. On the portal's recording, an amount can belong to a master agreement shared by several firms (read 2026-10-14), so it is not one firm's price. We do not add amounts together, and we do not compare amounts between types.
We also do not read these rows as a ranking of methods. Nothing in the records we read explains why the City used one type for one purchase and another type for the next, and we will not guess at a reason.
What does a small count say about sole source and RFP records?
On its own, nothing. The City of Chicago Contracts dataset, read on 2026-10-14, lists 4 sole-source and 4 request-for-proposals IT original records, each type's largest awardee holding 1.
That is a very small base. Four records cannot show how the City weighs competition against direct award, and our read does not describe how the City chooses between methods. The other small types are no larger: contract assignment or transfer records are 2 and 1, reference contracts are 2, and bid is 1. Another 28 records have no recorded procurement type on the 2026-10-14 read, so the type column is blank for them.
If you want a sense of how a public body buys, these counts are a starting prompt for questions, not an answer. For a private buyer weighing a competitive process of its own, our IT provider RFP guide for Chicago SMBs covers what a request for proposals should contain. The City's record does not tell you how often a method is used or whether it was the right one.
Is a recorded amount on these records a price per user?
No. An amount on a City IT record is the figure the portal records for a contract or for a change to one. It is often a multi-year ceiling, a blanket agreement drawn on as needed, or a master agreement shared by several firms. The City's own notes in the Contracts dataset, read 2026-10-14, say a blanket contract recorded at zero dollars has no guaranteed amount.
That is why we hold, as part of our Price Comparison position, that per-user figures without scope context mislead. Never divide a City amount by users, staff, devices or years. Never add amounts together, and never set an amount beside a managed IT price. A managed IT price only means something alongside what each tier includes, and a ceiling or blanket amount on a public record is a different kind of figure.
For scale only: the 2023 row of our year table shows 23 original IT records of $10 million or more on the 2026-10-14 read, against 50 IT original records that year. Those are recorded amounts, not spend, and the table says nothing about users. Our guide to comparing managed IT costs in Chicago shows how to put proposals on the same scope footing before comparing anything.
How should a Chicago IT buyer use this read?
Use it as a map of what the portal lists, then ask your own questions. Our reading of the City of Chicago Contracts dataset on 2026-10-14 counts records, not projects or money spent, so a count is a floor.
The length data carries the same warning. Of the 190 original records on the 2026-10-14 read, 36 run three to under five years, 5 run five years or more, 5 run under one year, and 138 have no start or end date recorded. The City notes that only blanket contracts carry an end date in this dataset. A length here is what a public body recorded, not advice for a private buyer, and our Contract Length position stands: shorter agreements are generally better for the buyer.
Three habits keep the read honest. First, quote the read date, 2026-10-14, beside any figure. Second, pair every count with its largest-awardee figure. Third, keep City amounts out of any price comparison. Nothing in this record is a reason to choose or avoid any IT provider. For the County side, see our piece on Cook County IT contract amendments and new awards.
Frequently asked questions
Does 114 joint-purchase records mean the City mainly buys IT that way?
No. On the 2026-10-14 read, 110 of the 114 joint-purchase IT original records are held by one awardee, so the row reflects one awardee's line items. A count of records is not a measure of how widely the City uses a method.
Can I divide a City contract amount by users to get a per-user price?
No. A recorded amount is often a ceiling, a blanket agreement or a master agreement shared by several firms, and it is not a price per user. Never divide it by users, staff, devices or years, and never set it beside a managed IT price.
Is this a complete list of City IT purchasing?
No. It is a floor. A record counts only when its description uses a listed term or the City's own contract type marks it, and the portal does not list every purchase. Chicago Public Schools and State of Illinois BidBuy are not covered.
Why do you not name the awardees?
We read counts of records, not firms. Naming an awardee would turn a record pattern into a claim about a company, which our read cannot support.