St Paul's City Council introduced 62 ordinances in 2025 — and 603 property-case matters. One in three items on its 2025 docket wasn't a law; it was a code or tax-assessment hearing.

The Granicus Legistar InSite API exposes Saint Paul's full legislative record — every governing body, every matter — with no key required. Pulled this run (retrieved 2026-08-11), filtered to matters with a MatterIntroDate in the 2025 calendar year and scoped to the City Council body, it returns 1,790 matters. Their introduction dates are spread across all twelve months (a low of 111 in September to a high of 193 in January), so this is a full-year record, not a data artifact. Sorted by matter type, the council's 2025 record breaks down as follows. Ordinances — the city's binding local laws — number 62. Plain Resolutions number 768, and a further 236 are "Resolution-Public Hearing". Administrative Orders number 75. The largest block after routine resolutions is neither laws nor policy. It is 603 "Legislative Hearing" resolutions — a distinct set of matter types the council uses for individual code-enforcement and assessment cases. Broken out: 320 Tax Assessment Appeals, 95 Assessment Roll ratifications, 67 Summary Abatement Orders, 32 Substantial Abatement Orders, 25 Vacant Building Registrations, 22 Vacate Orders, 20 Fire Certificate-of-Occupancy or Correction Orders, 11 Rent Stabilization Appeals, and 11 Code Correction Orders (320 + 95 + 67 + 32 + 25 + 22 + 20 + 11 + 11 = 603). Together these 603 items are 33.7% of the council's 1,790 matters — one in three. Against the 62 ordinances, that is a ratio of 9.7 Legislative Hearing resolutions to every ordinance. Property-assessment matters alone — the 320 appeals plus 95 rolls — total 415, or 23.2% of the council's year. These are not rubber-stamps. Of the 320 tax-assessment appeals introduced in 2025, the council's own titles record 177 as "Ratifying" the appealed assessment, 105 as "Deleting" it, and 38 as "Amending" it — a changed outcome on 143 of 320, or 44.7%. These figures count matters by their 2025 introduction date and read each disposition from the matter's title verb; the date of the final council vote, which can fall after the year a matter is introduced, is not tracked here. This piece reports these matters only in aggregate; each individual case names a private property and, in the abatement files, a private appellant, and none is named here.

The following is analysis, not fact. The phrase "legislative record" sets an expectation — laws, budgets, policy — that the record itself does not meet. Read end to end, a third of the Saint Paul City Council's 2025 docket was not legislation. It was quasi-judicial: a homeowner's appeal of a special tax assessment, a bill for boarding up a vacant building, a nuisance-abatement charge confirmed or cancelled, case by individual case. The council introduced 62 ordinances and 603 such matters. The quasi-judicial docket is a third of the record and outnumbers the ordinances roughly ten to one, yet it is invisible in any account of the council that counts only its laws. This routing is a structural choice, not an accident: Minnesota law channels special assessments and many code charges through the governing body for ratification, and the council runs them through a Legislative Hearing Officer before a public-hearing vote. What is legible here is the whole shape: because Saint Paul publishes a structured, machine-readable feed, the 603 hearing matters can be counted against the 62 ordinances in a way that a PDF agenda or a single meeting never reveals ^mmodeled. The number a resident would guess — that a city council mostly makes laws — is off by an order of magnitude for the part of its work that touches individual properties directly. The 44.7% change rate on tax appeals is the detail that resists the easy read. If this docket were ceremonial, the titles would show near-uniform ratification; instead the titles record 105 assessments as deleted and 38 as amended. Whatever else it is, this is a live appeals docket whose recorded outcomes are far from uniform — consequential for the individual residents who appear before it, and easily overlooked, because it arrives 320 times as near-identical line items rarely read in full.

The strongest counter is that this is due process working exactly as designed, and reads as dysfunction only if you expected a legislature and found an administrative court. Minnesota's special-assessment framework (Chapter 429) requires the governing body to adopt and hear appeals on assessment rolls; abatement and vacant-building charges follow parallel appeal paths. The 603 hearing matters are not the council failing to legislate — they are the council performing a statutory adjudicative duty that has to live somewhere. The count reframes what the body does; it does not indict it. A second caution is that an ordinance count understates legislative weight. Sixty-two ordinances is not a do-nothing year: a single ordinance can rewrite a zoning code or a budget, while a Legislative Hearing resolution disposes of one property. And the 768 plain Resolutions and 236 public-hearing resolutions include substantive policy, contracts and appropriations, not filler — the "law vs. hearing" split is a matter-type distinction, not a measure of importance. We report the full type breakdown so a reader can weight it differently. Finally, the vintage and scope caveats. These are matters introduced in 2025 and scoped to the City Council body in this specific API; a small number may not have reached a final vote, and any matter the city did not publish to Legistar is not counted. The tax-appeal outcome split (177/105/38) is read from each matter's own title verb and is exact for the 320 titles as published, but it captures the recorded disposition, not any later reconsideration.

The vantage this offers is less about Saint Paul than about legibility. Where a council's full record exists only as PDF agendas, a composition like this one — a third of the year in individual property adjudication — would be effectively uncountable. Saint Paul's structured, machine-readable feed is what makes it countable at all. Whether other cities' records look similar, this pull cannot say; the finding is about what the label "city council" can hide wherever the record isn't published this way ^mmodeled.