About the data

Where the documents come from

• The city's agenda center (Revize), from August 2025: every meeting with its agenda items, attachments and packet, harvested daily. Upcoming meetings appear here as soon as the city posts them.
• The city website's document center: minutes from 2020 on, harvested daily.
• SharePoint packet folders, 2021 to 2026: imported once.
• The Laserfiche archive: imaged minutes from 1962, and the signed ordinances and resolutions, with a daily check of the current year.
• The City Code of Ordinances: every chapter, harvested daily with every changed version kept.

Harvesting is polite (at most one request a second to each host). Every document keeps its provenance: where it was found, when, and under which name. The same file found in two places is stored once.

How the text is read

Documents with a text layer are read directly. Scanned pages are read by OCR (Tesseract), and most scanned pages are read a second time by a vision model running on the archive's own hardware; a quality gate compares the two and keeps the vision text only where it is plausibly better. Old scans (the 1960s to the early 2000s especially) still contain misreadings. The document pages show which method produced the text, and the original PDF is always one click away.

How votes are known

Motions, movers, seconders, results and votes are read from the minutes by rules written for each era of the city's minutes, then matched to the roster of council members by name (with date-scoped fuzzy matching for misspellings). A vote is either named in the record (a roll call, a vote list, or the signed ordinance or resolution) or implied: when the minutes say only "All ayes" or "carried unanimously", the ayes are credited to the members the minutes list as present. Every vote shows its basis on the member's page. Meetings without minutes in the archive have no votes here; that is a gap in the archive, not a record that nothing happened.

Money: "as printed" and "derived"

Figures marked As printed are copied from a document as the city printed it (a payables list's total, a Treasurer's report balance, a disclosure statement's debt). Figures marked Derived are computed from printed figures (a sum of lines, a share of the debt limit), and an Estimate adds borrowing a statement does not yet include. Where two documents disagree, both are shown. Spending covers the bills on the council's payables lists only, so payroll is not included; fiscal years run July to June and are named by the year they end. None of this is official accounting.

Projects

Each project or initiative gathers its agenda items, motions, contracts, pay applications, change orders, payments and documents into one timeline. Statuses are derived from those events unless set by hand from a cited document. "Completed vs contract" is the completed and stored work over the contract sum on the newest pay application.

How to take part in a meeting

City Council meetings are open to the public and take public comment; agendas are posted by the city before each meeting (see Coming up). For how to comment, speak at a public hearing or contact the council, use the city's own channels: this archive is not affiliated with the city and cannot pass messages on.

Following new records

Subscribe in any feed reader: new meetings and agendas, adopted resolutions and ordinances and split votes, and each project page has its own feed. The data is also available as JSON under /api/ (every page links its own).

Report an error

Found a misread vote, a wrong date, a mismatched name or a figure that does not match its source? Please send feedback from the page where you saw it: the form records which page you were on, so a short note is enough. Corrections are made in the archive's review queue and applied by the next rebuild.