Not one of the 283 ordinances Denver's council passed in 2025 moved in under 20 days — while 88% of its 1,301 resolutions were adopted the same day they reached the floor

The Denver City Council posts its legislative record to Granicus Legistar, whose public API returns, free and without a key, every measure the council handles and, for each, the dates it was introduced, first reached the council floor, and received final passage. We pulled every matter the council introduced in calendar year 2025 — 2,020 records (retrieved 2026-08-11). By legal form, those 2,020 matters were 1,346 resolutions, 308 bills (the council's term for a proposed ordinance), 175 presentations, 115 proclamations, 50 sets of approved minutes, and a scattering of amendments, nominations, and communications. This piece times the two forms that make binding law: the 1,301 resolutions and 283 ordinances that carried both an introduction date and a final-passage date in the pull — 1,584 enacted measures in one year. Every one of the 283 ordinances took at least 20 days from introduction to final passage; the median was 34. Not one moved faster than 20 days. That floor is the council's own rule operating: under Denver's Rules of Procedure a bill must pass on two separate readings, a first reading and a final reading, typically a week apart. The data shows the gap. Measured from the day a bill first reached the council floor (its first reading) to the day it received final passage, the median ordinance sat 9 days, and 218 of the 283 — 77% — fell in a 7-to-13-day window. Resolutions, which the same rules let the council adopt in a single reading, show the mirror pattern. Of the 1,301, 1,149 — 88% — were adopted the same day they reached the council floor; only 8 sat 7 days or longer between reaching the floor and being adopted. Just 3 of the 1,301 were adopted the same day they were introduced. The difference is entirely on the floor, not before it. Both forms spend about the same time in committee first: from introduction to first floor appearance, the median resolution waited 21 days and the median ordinance 24. What separates them is what happens after: a resolution is adopted the day it arrives; an ordinance is read, published, and returned a week or more later for a second, final vote.

The following is analysis, not fact. A resident watching a Denver council session sees two things that look the same: a resolution adopted in seconds by voice on the consent block, and an ordinance passed on final reading by the same near-unanimous vote. On the floor, in the room, they are indistinguishable — a quick, lopsided yes. The record shows they are not the same at all. One had a zero-day life on the floor; the other had a mandated week-plus between its two readings, and never less than 20 days from the moment it was introduced. What the enumeration surfaces is that the deliberation window a Denver measure gets is set almost entirely by its legal form, not by its stakes. A routine plat approval and a consequential rezoning, if both drafted as resolutions, each get one reading and are adopted the day they hit the floor. A minor code cleanup and a major spending agreement, if both drafted as bills, each get two readings a week apart. The form is chosen upstream, often as a matter of what state and charter law require of the subject; the pace follows the form automatically. Nothing in the 2025 record shows the council lengthening the window for a weighty item or shortening it for a trivial one within a form. The two-reading floor held for all 283 ordinances without exception. This is why the two-track structure is invisible from the final vote and visible only across the whole year's dates. The vote tally cannot distinguish a measure the public had one day to notice from one it had a week of published notice on, because both pass by the same margin. Only the introduction-to-passage clock, read across all 1,584 enacted measures at once, separates the track that gives residents a second look from the track that does not — and shows that which track a measure rides is decided by its form long before anyone votes.

The strongest objection is that "deliberation window" is the wrong label for these dates. The clock this piece measures — introduction to final passage — captures process time, not scrutiny. A resolution adopted the day it reaches the floor may have been negotiated for months in a committee, in a land-use hearing, or in the mayor's office before it was ever introduced; its zero-day floor life understates the attention it got. Conversely, an ordinance's mandated two readings can be a formality run twice on an item no one contests. The dates bound how long a measure was formally pending; they do not measure how hard anyone looked at it. Second, the two forms are not substitutes a council freely chooses between. Colorado law and Denver's charter dictate that certain actions — appropriations, code changes, franchises — take the form of an ordinance, while others are properly resolutions. So the finding that "form sets the pace" is partly the finding that "the law sets the form." We report the pace each form runs at; we do not claim the council could have put any given item on the faster track. Third, the date fields carry the usual caveats. A handful of records showed a final-passage date a day before or after the floor date — signing and recording artifacts — which is why the resolution floor window is reported at its median of zero rather than as a strict count of same-day pairs. We restricted the timing analysis to the 1,301 resolutions and 283 ordinances that carried all three dates; matters still pending, withdrawn, tabled, or filed are excluded, and their absence means this describes measures that passed, not the ones that died. Finally, this is one council and one year. Whether a 20-day floor and a two-reading window is fast, slow, or ordinary for a large US city is not something a single-city pull can answer; it is a baseline, not a benchmark.

From the vantage of a resident deciding when to weigh in, the split is the whole point. On an ordinance, the record gives a predictable opening: it is read once, ordered published, and not voted to final passage for a week or more — a median of 9 days of formal notice, and never fewer than the 20-day floor from introduction. On a resolution, there is essentially no such window; 88% were adopted the day they reached the floor. The chance to be heard before a Denver measure becomes law is not evenly distributed across measures — it is distributed across forms, and a resident who does not know which form their issue takes cannot know how much warning they will get. From the vantage of the record itself: any single measure's timeline is a few clicks away on the council's portal. The shape of all 1,584 at once — that ordinances never move in under 20 days and resolutions almost always clear the floor in one — exists only if someone times every measure the council passed in a year, which is exactly the reading a weekly beat covering the loudest item cannot perform.

A beat reporter covers the measure that matters this week: the rezoning, the spending agreement, the ordinance that draws a crowd. Each story is accurate and each is, by construction, a single point on a clock no one reads end to end. Timed across the whole year, the thing no single-vote story can show is that the pace of Denver lawmaking is set before any vote is cast, by a choice of legal form: all 283 ordinances the council passed in 2025 took at least 20 days and a median of 34, moving through two readings a median of 9 days apart, while 88% of its 1,301 resolutions were adopted the same day they reached the floor. The final tally looks the same for both — a quick, near-unanimous yes — which is exactly why the two tracks are invisible from the vote and visible only from the dates. The resident who gets a week of published notice and the resident who gets none are separated not by how important their issue is, but by which form it happened to take.