Denver's City Council introduced 4.37 resolutions for every bill in 2025 — and read across all 1,654 legislative items, nearly two-thirds carried contract, agreement, or amendment language in their titles

The Granicus Legistar InSite API exposes the full legislative record of the City and County of Denver — every matter the City Council introduces, with its file number, type (Bill, Resolution, Proclamation, and so on), title, introduction date, and final status — with no key or login. Pulled this run (retrieved 2026-08-10) for a fixed window, matters with an introduction date from January 1 through December 31, 2025, the record is as follows. The full window returns more than the API's 1,000-row page cap, so the pull was paged in three requests ordered by matter ID and de-duplicated to 2,020 unique matters. Of those 2,020 matters, 1,346 are resolutions and 308 are bills. The remaining 366 are not legislative instruments the council votes into law: 175 presentations, 115 proclamations, 50 sets of approved minutes, 19 amendments, 4 communications, 2 nominations, and 1 executive-session notice. Setting those aside leaves 1,654 bills-or-resolutions — the instruments the council actually adopts or passes. Among them resolutions outnumber bills 1,346 to 308, 81.4% to 18.6%, a ratio of 4.37 to 1. In Denver's charter a bill becomes an ordinance — the city's law — while a resolution is the lighter instrument used chiefly to approve contracts, intergovernmental agreements, and appointments. Classifying each 2025 instrument by a case-insensitive whole-word keyword match on its title ^mmodeled, 968 of the 1,346 resolutions (71.9%) name a contract, agreement, amendatory agreement, intergovernmental agreement, grant, loan, lease, or purchase order; 153 (11.4%) are appointments or nominations to boards; and 225 (16.7%) are other approvals, mostly expenditure authorizations and subdivision plats ^mmodeled. The bills are not purely lawmaking either: of the 308, 154 (50.0%) are general ordinances, 86 (27.9%) approve a contract or agreement, 35 (11.4%) are appropriations or budget measures, and 33 (10.7%) are rezonings ^mmodeled. Combining both types, 1,054 of the 1,654 instruments — 63.7% — carry contract, agreement, or purchase-order language in their title ^mmodeled. Separately, 818 of the 1,346 resolution titles (60.8%) contain an explicit dollar figure. The instruments almost always pass. Of the 1,346 resolutions, 1,290 were adopted (95.8%) and 13 failed (1.0%); of the 308 bills, 283 passed (91.9%) and 10 failed (3.2%). Across both types, 23 of 1,654 instruments — 1.39% — carry a Failed status; the rest that were not adopted or passed were tabled, filed, or still in committee review at pull time. Every count above is re-pullable: file 25-0013 is a rezoning bill (Passed), 25-0030 a rezoning bill (Failed), 25-0011 a contract resolution (Adopted), 25-0007 an appointment resolution (Adopted), and 25-0009 a contract resolution (Failed).

The following is analysis, not fact. Nothing here assigns a motive to the council or a judgment to any single vote; the finding is one of composition, and composition is legible only when the whole year's docket is read at once. A city council is, by name and by civics-class reputation, a legislature — a body that makes law. Denver's 2025 record, read by instrument type, is dominated not by ordinances but by resolutions. Four of every five instruments it introduced were resolutions, and once contract language in the bills is added in, roughly two in three of everything it took up — 1,054 of 1,654 — carried contract, agreement, or amendment language in the title. Bills were 308 of the 1,654 instruments, 18.6%; but the general ordinance — the actual act of lawmaking, as distinct from a bill that ratifies a contract or sets the budget — was just 154 items, 9.3% of the docket, fewer than one in ten. Rezonings, the land-use decisions that draw neighbors to the microphone, were 33 bills by our keyword match, about 2%. The dollar detail sharpens the composition: 61% of resolution titles name a figure, because the resolution is the vehicle through which the city's spending — a Kaiser Foundation health contract, a third or fourth amendatory agreement extending a vendor, an intergovernmental deal with the Regional Transportation District or the Denver Housing Authority — passes through the elected body on its way to execution. By instrument count, the calendar is heavy with the city's spending items given a public reading and a recorded vote. The recorded outcomes rarely differ from adoption. Adoption ran at 95.8% for resolutions and 91.9% for bills; 23 of 1,654 instruments carry a Failed status for the year. What that near-unanimity means is not settled by these fields. The status and the title tell us what an instrument is called and how its final vote was recorded; they do not tell us how much was negotiated, amended, or contested in committee before the floor vote, nor how consequential each item was. As an inference only ^sspeculative, a docket that is four-fifths resolutions, heavy with contract titles, and adopted at 96% is consistent with a body acting largely as the public checkpoint on an administrative pipeline — though equally consistent with a body that does its contesting upstream of the recorded vote. The statuses and keyword titles counted here cannot distinguish the two.

The strongest counter is that volume is not importance, and a count of instruments flattens the one measure that matters most — consequence. A single bill — the annual budget ordinance, a zoning-code overhaul, a bond authorization — can outweigh a thousand routine contract resolutions in dollars, precedent, and effect on residents' lives. By instrument count the council looks like a procurement desk; by hours of debate, public testimony, or downstream impact it may look nothing of the sort, and this piece measures the former, not the latter. A reader should not read "64% contract-titled" as "64% of what the council did that mattered." A second, related caution: the charter assigns contract and agreement approval above a threshold to the council by design. That the elected body signs off on the city's larger deals is not a drift into administration but the separation of powers working as written — the legislature holding the purse. On that reading the composition reported here is a feature, not a finding, and the only novel thing is the tally. Finally, the classification is approximate. The contract, appointment, and rezoning buckets are a keyword match on each title, not Denver's official taxonomy; a resolution that approves a contract without using any of the matched words is undercounted, and a title that uses "agreement" loosely is over-counted. The type split itself — 1,346 resolutions, 308 bills, 2,020 matters — is exact from the API's own fields; the contract share, 63.7%, is a reproducible estimate, and is reported as ^mmodeled, not.

From outside Denver, this is less a Denver finding than a property of the Legistar record. Granicus runs the same InSite platform, exposing the same fields — matter type, title, introduction date, status — for hundreds of US local governments, and the same two queries against any participating city return the same computable object: the resolution-to-bill ratio, and the share of a year's instruments that are contracts rather than ordinances. Denver is legible here only because its clerk enters the full matter record into the feed; a city that files fewer of its transactions through the council, or types them into a system we never queried, would show a leaner, more legislative-looking docket while moving the same money by other means. The un-copyable move is not reading one council's year — it is that the same pull runs across every Legistar city at once, and no single-town desk sees its own council as one row in that distribution.

A resident who follows Denver's City Council through the news sees the exceptions: the contested rezoning that drew a crowd, the one contract that failed, the ordinance that made a headline. What no single matter shows is the shape of the whole. Read across all 2,020 matters Denver introduced in 2025, three facts appear that no meeting-goer carries home. First, the council is, by volume, a resolution body: 1,346 resolutions to 308 bills, 4.37 to one. Second, most of what it handles carries transactional language — 1,054 of 1,654 instruments, 64%, carried contract, agreement, or amendment language in their titles, and 61% of resolution titles named a dollar amount; the general ordinance — actual lawmaking, as distinct from bills that ratify contracts — was 154 items, 9.3% of the instrument docket, fewer than one in ten. Third, the recorded outcomes rarely differ from adoption: 96% of resolutions adopted, 92% of bills passed, 23 Failed statuses in 1,654 votes. What that composition means for how the council deliberates is not something the type, title, and status fields can settle — they record what each instrument is called and how its final vote landed, not how contested it was on the way there. The counts are the finding; the interpretation is left open, a shape invisible from any one agenda and legible only across a year of them.