Published Research Sample

One zoning decision. The evidence behind it.

This Chicago example shows how a short research brief can keep the public action, supporting sources, and next questions together. It is a real record, not a hypothetical property alert or an API response example.

Source links inspected November 2, 2026. The recorded action occurred February 18, 2026.

Decision Brief

Chicago zoning reclassification, application 22957

The Foundry Park example connects a documented zoning action to a property-research workflow.

Supported finding

On February 18, 2026, the Chicago City Council recorded a 48-1 vote on the zoning reclassification identified as application 22957.

The official Clerk report supplies the application reference and vote. The LocalGovIndex record connects the action to its meeting context and available attachments.

Place
Chicago, Illinois
Public body
City Council
Action date
February 18, 2026
Recorded result
Passed, 48-1
Match basis
Application 22957 and its listed zoning addresses

Why it can matter

A property researcher can use this action to identify a change worth examining, locate the approved text and plans, and decide what further project or area diligence is needed.

The vote is evidence of a public decision. It does not establish construction, financing, final buildout, utility service, market demand, or investment performance.

Questions for follow-up

  • What does the final approved text permit or require?
  • Which conditions, phases, and later approvals apply?
  • What subsequent permits or official project updates are available?
  • How does the verified location relate to the properties in your scope?
Source Trail

Open the evidence behind the brief

Each source has a different role. The official vote supports the action; the normalized record helps navigate the related materials.

Use the Evidence

Commission the research or integrate the records

The same source foundation can support different deliverables. Format, matching, coverage, and rights follow the agreed use.

Research & Consulting

A brief around your question

Define a property, project, policy, market, or editorial question. Scope the records, review, and findings your team needs.

Discuss a research project →
Data & API

Records inside your workflow

Review the API or daily feed, inspect target coverage, and agree the rights needed for internal research or a customer-facing integration.

Discuss data access →