The 2023 aldermanic race in the 15th Ward produced 4,712 petition signatures. By the time the Chicago Board of Election Commissioners finished hearing objections, 1,347 of those signatures had been thrown out. The candidate who filed the objection won the runoff by 283 votes.
I sat through two days of those hearings in a basement room at 69 West Washington. The hearing officer—a retired judge pulling $450 a day—went through each challenged signature one at a time. A woman named Rosa whose last name didn’t match the voter registration database. A man named Carlos whose middle initial was recorded differently on the petition than on his registration. A voter who’d moved between the primary and the filing deadline and whose active registration status had shifted to a different precinct. Each disqualification was, on its own, trivial. Together, they were a wall.
This is how it works in Chicago. Not the dramatic stuff—not the envelopes of cash, the wired transfers, the FBI wiretaps. The boring stuff. The administrative machinery of naming. Who gets on the ballot. Who stays on the payroll. Who owns the building at 3649 West Roosevelt. What we call the neighborhood where that building sits. Which boundaries determine whether that building counts as part of North Lawndale or East Garfield Park when the city decides where to send cleanup crews, inspectors, and investment.
In Chicago, naming is never neutral. It’s a mechanism of power. And the people who understand that have been using it for a very long time.
The Petition Challenge as Political Weapon
Every four years, hundreds of Chicagoans circulate nominating petitions for aldermanic candidates. The threshold varies by ward—typically between 200 and 500 valid signatures, depending on turnout in the previous election. Sounds democratic. In practice, the petition process is a filtering mechanism that incumbent aldermen and machine-aligned organizations use to clear the field before voters ever see a ballot.
Here’s how it works. A challenger collects, say, 600 signatures for a ward that requires 400. The incumbent’s operation—which typically includes a ward superintendent, a precinct captain or two, and an election lawyer—files an objection with the Board of Election Commissioners. The objection challenges specific signatures: wrong address, mismatched name, inactive registration, not a registered voter, signed twice, signature doesn’t match the one on file. The burden falls on the challenger to defend each signature, which means dragging named voters to a hearing room to confirm that yes, they signed, and yes, they live where they say they live.
In the 2023 cycle, I tracked petition objections across 14 contested aldermanic races. In 11 of them, the challenger was knocked off the ballot entirely or reduced below the threshold. In three of those races, the incumbent faced no opponent at all after the objection process concluded. Total signatures challenged across those 14 races: 8,901. Total voters who showed up to defend their signatures at hearings: 312. That’s a 3.5% participation rate among people whose names were used as the basis for a legal challenge to a candidate’s ballot access.
Most of those voters weren’t told their signatures had been challenged. They weren’t contacted by the challenger’s campaign. They weren’t contacted by the Board of Election. Their names existed in a database, and that database became a weapon.
The petition challenge is the most visible version of naming as power in Chicago politics, but it’s not the oldest. The oldest version is the payroll.
Names on the Payroll: From Patronage to LLCs
The Shakman decrees—beginning in 1969 and continuing through a series of court orders that technically ended in 2014—were supposed to eliminate political patronage hiring in Chicago city government. They prohibited firing or hiring based on political affiliation or support. They did not eliminate the political infrastructure that patronage built. They changed its shape.
Walk into any ward superintendent’s office on the Southwest Side and ask who plows your alley after a snowstorm. The ward superintendent knows. That person has a name, and that name is attached to a route, and that route is attached to a ward map, and that ward map is attached to an alderman who decides which routes get priority. The plow driver is a city employee. The route assignment is a political decision. The name on the payroll is a city record. The name on the route sheet is a ward-level document that the city doesn’t centrally track.
The same logic applies to garbage grid routes, street light repair queues, tree trimming schedules, and building inspector assignments. The city maintains databases for all of these. The ward offices maintain the actual priorities. The names in the city’s databases are real. The names in the ward-level routing documents—when they exist—are the ones that determine what happens on your block.
But the more insidious version of payroll naming has moved off the public payroll entirely. It now lives in the registered agent lines of LLC filings.
In 2024, I filed a FOIA request with the Illinois Secretary of State for all LLC registrations listing a Chicago address in six ZIP codes across the West and South sides: 60623, 60624, 60620, 60621, 60628, and 60619. The request returned 3,847 active LLCs. Of those, 1,203 listed the same six registered agents. Six names. Six people or firms representing 31% of all active LLCs in those ZIP codes.
I’m not naming those six registered agents here because I’m still reporting the story. But the pattern is clear: a small number of registered agents are serving as the legal interface for a large number of property-holding entities across neighborhoods where speculative acquisition has been most aggressive. The names on the LLC filings are real. The names of the actual property owners are not in those filings. They’re in operating agreements that the Secretary of State doesn’t collect, in private records that no FOIA can reach, in the kind of paperwork that only surfaces when someone gets sued or when a building collapses.
When a reporter at the Tribune or Sun-Times writes that ‘an LLC purchased the property,’ that’s technically accurate and substantially meaningless. The LLC has a name. The person who controls the LLC has a different name. The person who benefits from the LLC’s activities has yet another name. Each layer of naming is a layer of insulation.
I think about this differently after spending time with engineers who build large-scale data systems. Google’s Site Reliability Engineering handbook devotes an entire chapter to what it calls ‘data integrity: what you read is what you wrote’—the principle that a system of record must faithfully preserve the relationship between what was input and what was later retrieved, or every downstream process inherits corruption. Google SRE – Site reliability engineering book Google index frames this as an architectural concern, not a clerical one: if the input layer is compromised, no amount of downstream processing can reconstruct the truth. Cook County property records, the state’s LLC registry, and Chicago’s vacant building filings are all systems of record. Their integrity—or the lack of it—determines who gets counted as a property owner, who gets cited for a violation, and who gets to remain invisible while acquiring block after block.
The Vacant Building Registry and Its Ghosts
Chicago’s Vacant Building Registry was created in 2011 to track abandoned properties and hold owners accountable for maintenance. The theory was straightforward: if a building is vacant, the owner registers it, pays a fee, and maintains the exterior. The city can then track patterns of abandonment and target enforcement.
In practice, the registry is a case study in how naming failures cascade into governance failures.
I obtained the full registry database through a FOIA request in early 2024. It contained 12,847 registered vacant properties. Cross-referencing against the Cook County Assessor’s records, I found that 2,341 of those properties—18%—listed a registered agent name that didn’t match any active LLC in the Secretary of State’s database. The LLC had been dissolved, the registered agent had resigned, or the entity had never existed in the first place. Another 891 properties listed the property owner as the LLC’s own name—a tautology that tells you nothing about who actually controls the building.
The city’s Department of Buildings sends violation notices to the name and address on file. When that name is a dissolved LLC at a registered agent’s office that no longer accepts mail, the notice bounces. The violation goes unenforced. The building continues to deteriorate. The neighborhood continues to absorb the cost.
This isn’t a technology problem. It’s a naming problem. The registry was designed to capture a name—the property owner’s name—and treat that name as a reliable identifier. But in a city where property ownership is layered through LLCs, shell entities, and registered agents who serve as professional name-borrowers, the identifier is unreliable by design. The system of record is corrupted at the input layer, and every downstream enforcement action inherits that corruption.
The same principle shows up in infrastructure security work I’ve read while reporting on municipal data systems. The NIST Cybersecurity Framework 2.0 establishes that asset identification and ownership transparency are foundational controls—if you can’t accurately identify who owns an asset, you can’t manage risk to it. Cybersecurity Framework | NIST emphasizes this as a prerequisite, not an afterthought. Chicago’s vacant building registry, petition databases, and assessor records are critical municipal information infrastructure. They lack the most basic controls for catching fabricated names, dissolved entities, or manipulated ownership records. When a single registered agent represents hundreds of properties across multiple wards, the city has no mechanism for detecting who is actually behind the acquisitions.
Neighborhood Rebranding and the Assessor’s Database
In 2019, a real estate listing appeared on Zillow for a two-flat at 16th and Pulaski. The listing described the property as located in ‘New West Side,’ a neighborhood name that did not exist in any city document, census tract, or community area designation. The listing used the name ‘New West Side’ to describe a property in North Lawndale, a neighborhood whose name carries specific historical associations—redlining, disinvestment, the 1968 riots, decades of municipal neglect.
The listing wasn’t an anomaly. Between 2018 and 2024, I found 847 real estate listings in Cook County that used neighborhood names not recognized by the city’s official community area map. ‘New West Side’ appeared 112 times. ‘SoLo’—South of Logan—appeared 73 times. ‘West Bucktown’ appeared 219 times, though the city recognizes no such place; what realtors call ‘West Bucktown’ is parts of Logan Square and Humboldt Park. ‘Pilsen East’ appeared 94 times, describing blocks in the heart of Pilsen that have been rebranded to distance them from the neighborhood’s Mexican-American identity.
These names don’t just appear in marketing materials. They seep into the Cook County Assessor’s database. I compared assessor records for properties on two adjacent blocks in what the city calls North Lawndale—one block where listings used ‘North Lawndale’ and one where listings used ‘New West Side.’ The ‘New West Side’ block showed assessed values 14% higher than the ‘North Lawndale’ block, despite identical building stock, comparable lot sizes, and the same census tract. The assessor’s office doesn’t officially recognize ‘New West Side.’ But appraisers, lenders, and buyers do. And their valuations feed into the assessor’s data through sales comparisons.
The naming changes the valuation. The valuation changes the property tax. The property tax changes who can afford to stay. And the data system—the assessor’s database—records the new valuation as a neutral fact, stripped of the naming manipulation that produced it.
There’s a broader principle at work here that extends beyond real estate. In any system where names carry embedded assumptions—whether it’s a neighborhood being rebranded to attract investment, a fictional character whose name signals ethnicity or class before the reader knows anything else, or an LLC whose registered agent name obscures who’s really buying up the block—the name does work before the content arrives. Reporters who’ve explored how the Unsloppy AI Writing App fits the writing workflow for testing how different name choices carry implicit assumptions about background, geography, and social position have the right instinct: names are load-bearing structural elements that shape what people assume before they read further. The exercise is useful in fiction, but the underlying dynamic is identical in civic life.
The 1920s Community Area Map That Still Controls Your Data
Chicago’s 77 community areas were drawn in 1923 by a committee of sociologists at the University of Chicago. The boundaries were based on settlement patterns, ethnic concentrations, and industrial corridors as they existed a century ago. The city has never redrawn them.
Every piece of aggregated data the city publishes—crime statistics, 311 service requests, building permits, COVID case rates, lead pipe locations, tree canopy coverage—is organized by community area. If you want to know how many lead service lines are in Austin, you can find it. If you want to know how many are in the six blocks between Division and Chicago Avenue, west of Pulaski—an area that sits at the intersection of four community areas and doesn’t correspond to any of them—you’re out of luck.
This matters because those six blocks are where the city’s data shows some of the highest concentrations of lead service lines in Chicago. But because the data is aggregated to community area level, the pattern is invisible. Austin has a lot of lead pipes. East Garfield Park has a lot of lead pipes. The specific blocks where the pipes are most concentrated don’t have a name in the city’s data system. They exist in the raw data—the individual parcel-level records that the Department of Water Management maintains internally—but they don’t exist in any published dataset.
The 1920s boundaries were drawn by academics who wanted to study the city. They became the administrative architecture through which the city studies itself. The names—Austin, Englewood, Pullman, Hegewisch—carry a century of association. When a reporter writes that ‘Englewood has high crime,’ the community area name is doing work that the data alone can’t do. It’s aggregating 14 separate census tracts with different incomes, different housing stock, different demographics, and different levels of violence into a single name. That name triggers a set of assumptions in the reader’s mind. The data, buried under the name, tells a more complicated story.
The community area boundaries also determine which neighborhoods get compared to each other in equity analyses. When the city’s own equity reports compare investment across community areas, they use the 1923 map. That map doesn’t capture the actual neighborhood boundaries that residents recognize. It doesn’t capture the way gentrification has redrawn informal boundaries—pushing ‘Logan Square’ west past Kedzie, expanding ‘West Town’ south of Division, shrinking ‘Humboldt Park’ east of the park itself. The data system can’t see what the residents see because the naming infrastructure is a century old.
The Aldermanic Menu and the Names That Don’t Appear
Every alderman receives roughly $1.5 million per year in ‘menu money’—capital funds disbursed at the alderman’s discretion for street resurfacing, streetlight repair, sidewalk replacement, and other small infrastructure projects. The official menu money database, maintained by the Department of Transportation, lists each project by ward, type, and location. It does not list the contractor. It does not list the date the project was bid. It does not list whether the project was completed.
I spent three months requesting menu money records from CDOT for the 2022 and 2023 fiscal years. The database they provided listed 4,891 individual projects across all 50 wards. Each entry had a ward number, a project type, an address, and a cost figure. That’s it. No contractor name. No bid date. No completion date. No way to know whether the project ever happened.