Legistar File Numbers, Explained
What file numbers like 882-2026 actually mean, how matter types differ, and why Cleveland runs two Legistar backends whose IDs disagree.
Updated
Every piece of Cleveland City Council business gets a file number the moment it is introduced, and that number is the single most reliable way to track it through committee, a vote, and beyond. It is also, underneath the simple sequence-and-year format, hiding a real technical gotcha: Cleveland's Legistar system is actually two separate backends that assign two different internal IDs to the same file, and if you build a link using the wrong one, you end up on the wrong record. This guide explains both — the numbering scheme you see, and the plumbing underneath it that you do not.
The format: sequence, dash, year
A Cleveland file number looks like 882-2026 — a sequence number, a dash, and the year the item was introduced. The sequence number resets each year and simply counts up as items are introduced, so 882-2026 was roughly the 882nd item introduced to council in 2026. It does not encode a ward, a committee, or a matter type; it is purely a running count.
That means file numbers are not comparable across years in any meaningful way — 200-2025 and 200-2026 are unrelated files that happen to share a sequence position — and a low number does not mean "minor" or "early in the process." It just means it was introduced early in that calendar year.
Matter type: what kind of file it is
Separate from the file number, Legistar tags every record with a matter type. The main ones you will run into on Cleveland City Council records are Ordinance, Emergency Ordinance, Resolution, and Communication.
- Ordinance — a piece of binding legislation. Once passed and signed, it typically becomes effective 30 days later, which allows time for a referendum petition.
- Emergency Ordinance — the same kind of binding legislation, but passed with the required emergency findings so it can take effect immediately on passage and signature instead of waiting out the standard period. File 882-2026, the Slavic Village home repair ordinance covered in the companion guide on reading a Cleveland ordinance, is an example.
- Resolution — typically used for council's own procedural actions, positions, or non-binding statements, rather than enacting new binding law.
- Communication — correspondence into the legislative record, such as a report or notice from an administration department, rather than a proposal council is voting on.
Status: where the file stands right now
Alongside the file number and matter type, Legistar records a status — Introduced, referred to committee, reported, passed, and so on. Status is a snapshot, not a history; to see how a file moved through committee and floor votes over time, you generally need to look at the file's action or history log rather than the status field alone. A "Passed" status, like on file 882-2026, tells you the outcome, but the committee-of-referral field and the action history are what tell you the path it took to get there.
The gotcha: two Legistar backends, two IDs
Here is the part that trips people up, including anyone trying to build their own tools on top of Cleveland's legislative data: Cleveland runs two separate Legistar systems under the hood, and they do not share the same internal identifiers for the same file.
The public website — the one at cityofcleveland.legistar.com that a human browses, where a specific record's URL looks like LegislationDetail.aspx?ID=... — assigns its own internal ID to each matter. Separately, Legistar's public API, hosted at webapi.legistar.com/v1/cityofcleveland/, returns records with a different internal identifier, called MatterId, for what is logically the same file. These two ID spaces are not the same numbering system, and there is no simple arithmetic conversion between them.
That distinction matters the moment you try to go from "I have a file number, I want a working link" to actually building that link programmatically. The file number itself (882-2026) and the human-readable title are consistent across both systems; the internal database IDs are not.
Publiusly resolves this by treating the file number, not either internal ID, as the durable key, and by explicitly reconciling the API's MatterId against the correct public-site ID before it ever links out to Legistar. That reconciliation logic lives in the ingestion pipeline specifically because getting it wrong silently sends readers to the wrong ordinance — a failure mode that is easy to miss in testing because the link still resolves, just to the wrong page.
The file number itself and the human-readable title are consistent across both systems; the internal database IDs are not.
Practical implications for anyone using file numbers
If you are a resident just trying to look something up, the safest approach is almost always to search Legistar's public site directly by the file number itself (for example, searching "882-2026") rather than trying to construct a URL by hand from an ID you found somewhere else. The search will resolve to the correct public-site record regardless of which internal ID is attached to it.
If you are trying to reference a Cleveland legislative file in your own notes, an email to a council office, or a public comment, cite the file number and matter type together — "Emergency Ordinance 882-2026" — rather than any internal ID. That is the identifier council staff, the clerk's office, and Legistar's own search all use consistently, and it is the one that will still make sense a year from now.
How Publiusly uses file numbers
Every Publiusly article about a piece of Cleveland legislation carries the file number in its receipts panel, alongside the matter type, status, and committee, plus a "View on Legistar" link that has already been resolved to the correct public-site record. If you want to verify a claim in an article, the file number is the fastest way to jump from what Publiusly published to the underlying record — see the companion guide on using Publiusly to verify civic claims for the step-by-step version of that process.