Chicago Community Areas vs. Wards — picking your bid territory

A practical territory guide for general contractors and subs working in Chicago · Updated April 2026

The short answer: use Community Areas to define a bid territory based on neighborhood, building stock, and actual project work. Use Wards if you're tracking political and development incentives — TIF districts, alderman-driven zoning, planned developments. The two systems do not line up. A single Ward can cross five Community Areas, and a single Community Area can be split across three Wards. Most contractors who pick territory get one of these wrong, and it costs them either chasing the wrong neighborhoods or missing the projects in the right ones.

Chicago's permit feed (Socrata dataset ydr8-5enu at data.cityofchicago.org) puts both fields on every row. That means you can filter by either system — the question is which one matches your business model.

A quick history — how Chicago divides itself

Chicago has two parallel territory systems because they were created for different reasons.

The 77 Community Areas were defined in the 1920s by the University of Chicago's Social Science Research Committee, originally for census and sociological research. They were drawn around natural neighborhood boundaries — the river, major rail lines, parks, ethnic enclaves of the time. They've barely changed in a century. Names like Lincoln Park, Hyde Park, Bridgeport, Logan Square, Englewood, Pilsen, Albany Park — those are Community Areas. The boundaries match how Chicagoans actually talk about where they live.

The 50 Wards are political. Each elects an alderman to City Council. They're redrawn every ten years after the census, and the redrawing is famously contested. Ward boundaries follow voter-population balancing, not neighborhood logic. Wards 1, 27, 32, and 43 all have pieces of Wicker Park. Pilsen sits in three different Wards.

The contractor implication: if you tell a Chicago property owner "we work in Lincoln Park," they understand. If you tell them "we work in the 43rd Ward," they'll think you're a political operative.

Why both fields exist on a Chicago permit

Chicago's Department of Buildings tracks both because they're useful for different reasons.

• Community Area drives building-stock analysis (what kinds of buildings are typical in this neighborhood) and historic data (what's been built here over time).
• Ward drives political and incentive analysis (which alderman has weight on planned developments, which TIF district covers this address, which zoning amendments are pending).

For a permit dataset, having both means a contractor can carve up the city by either system depending on what they need to know. Permit Pipeline's Chicago feed lets subscribers filter by either or both.

Picking territory by Community Area

Community Areas are the right cut for almost any contractor whose business is shaped by building stock or neighborhood character. Examples:

• Pre-war multifamily renovation specialists. Filter by Community Areas with dense pre-war housing stock — Logan Square, Lakeview, Lincoln Park, Hyde Park, Edgewater, Uptown.
• New construction GCs. The Loop, Near North Side, Near West Side, Near South Side, West Loop / Fulton Market — these Community Areas dominate the new-construction pipeline by dollar value.
• Industrial and adaptive reuse contractors. Pilsen, Bridgeport, Lower West Side, McKinley Park, North Lawndale — older industrial stock under conversion pressure.
• Single-family / two-flat remodelers. Bungalow-belt Community Areas — Portage Park, Belmont Cragin, Avondale, Albany Park, Garfield Ridge, Mount Greenwood.
• Affordable housing developers. Englewood, West Englewood, Austin, Humboldt Park, Chicago Lawn — large affordable-housing pipelines and active CHA / nonprofit work.

The Community Area framework also matches how owners and architects talk about projects. When a developer says "we're building in West Loop," the bid territory is a Community Area — not a Ward. Aligning your filter to how the buyer thinks closes the gap between your sales pitch and their mental model.

Picking territory by Ward

Wards are the right cut when your business model touches political or incentive-driven work:

• Public-sector and CHA-adjacent work. Aldermanic prerogative still drives a lot of how local funding gets allocated.
• TIF-district work. Tax Increment Financing district boundaries roughly track Ward boundaries; if you're chasing TIF-funded redevelopment, Ward is the relevant filter.
• Zoning-amendment-dependent projects. Up-zonings, planned developments, and special-use permits all flow through Ward-based aldermanic input.
• Affordable Requirements Ordinance projects. ARO triggers depend on geographic zones that overlap Wards more cleanly than Community Areas.
• Sign and signage permits. Sign approvals often involve aldermanic letter-of-support requirements per Ward.

If you do work that depends on getting an alderman to call back — or on knowing which Ward a development incentive covers — Ward is the filter that tracks your sales motion.

Where Community Areas and Wards diverge in practice

The two systems can mislead in ways worth being explicit about:

• "Wicker Park" is split. The Community Area is West Town, but the historic Wicker Park neighborhood crosses Wards 1, 26, 27, and 32. If you market by Ward, you'll miss half of Wicker Park unless you list four Wards.
• "Pilsen" is split. Pilsen sits in the Lower West Side Community Area but spans three Wards.
• The Loop and West Loop have different politics. Both fall in the broader Near West Side / Loop Community Area cluster, but they're in different Wards with different aldermen — and the two have very different planned-development pipelines.
• South Side ARO zones don't follow neighborhood lines. The Affordable Requirements Ordinance maps follow Ward and zoning logic, not Community Area boundaries. If you build market-rate multifamily and want to avoid ARO triggers, you cannot rely on Community Area filtering alone.

A practical workflow for narrowing your bid territory

Most contractors should pick a small set of Community Areas as their primary filter, and add Ward as a secondary filter only if their work depends on political or incentive geography.

1. List the Community Areas where you've done your last 10 jobs. That's your real territory, regardless of what your sales deck says.
2. Add adjacent Community Areas that share building stock. Logan Square + Avondale + Hermosa, for example, share pre-war two-flat housing. A contractor who works one usually can work the other.
3. Filter the daily permit feed to those Community Areas only. You'll typically narrow Chicago's roughly 4,000 weekly permits to 100–300 — manageable to read.
4. Layer Ward only if your work needs it. ARO-shaped multifamily, TIF-funded redevelopment, planned-development zoning amendments — those need Ward.
5. Re-read your filter every quarter. Your last 10 jobs change. So does the active permit volume by neighborhood.

Permit Pipeline's Chicago feed lets specialty subs and general contractors pre-set their territory by Community Area, Ward, or ZIP, and only see permits that match. Most subscribers default to Community Area filtering with a 10–15 area list. See what your filter would surface today.

Why this matters for outreach

Specificity wins reply rates. The contractor who emails an owner saying "we've done three similar jobs in Logan Square in the past year" gets a response. The contractor who says "we cover the 35th Ward" gets ignored. Owners think in neighborhoods. Match how the buyer thinks, and the rest of the message lands harder.

Pick the Community Areas that match your business. Keep the Ward filter for the specific cases where political geography is the actual buying signal. And read the daily permit feed — that's where the work is, weeks before it ever hits a bid list.