Beta, work in progress: figures, definitions and coverage may change between editions.
Not for legal or financial decisions. Permitory counts public records; the issuing agency is the authoritative source for any record.
Permitory publishes counts of public records. Each figure on a report is the number of distinct places in one corridor, in one calendar month, that have a record of a stated kind. The records are those the issuing agencies publish on their open-data portals; the agencies are the authoritative source for every record.
We do not produce scores, ratings, rankings, labels, forecasts or descriptions of any business, address or area. A figure states how many places have a record of a kind; it does not state why.
This page describes how each figure is computed. The tables on it are generated from the same rule files and source registers the computation reads.
A corridor is one unit of a city's official neighborhood boundary set, listed below with the publisher's own dataset and the date the publisher last updated it. A place is counted in the unit whose boundary covers its geocoded location.
A place with no geocoded location, a location outside every unit, or a location covered by more than one unit is counted in the city total only.
When a publisher redraws a boundary set, the series for that city starts again from the new set; counts from different boundary versions are not compared with one another.
| City | Boundary set | Publisher | Dataset | Units | Publisher last update |
|---|---|---|---|---|---|
| Chicago | Boundaries - Community Areas | City of Chicago | igwz-8jzy | 77 | 2025-04-22 |
| New York City | 2020 Neighborhood Tabulation Areas (NTAs) | Department of City Planning (DCP) | 9nt8-h7nd | 262 | 2026-05-28 |
An opening is counted when a license record from the feed listed below is dated in the month by the field shown. Records whose application type is listed as not counted (renewals) are excluded; every other record in the feed counts. Where no application type is listed, the feed is dated by the license's creation date. One place with several licenses dated in the same month counts once.
| Feed | Event | Dated by | Not counted (renewals) |
|---|---|---|---|
| r5kz-chrr | license_granted | license_start_date | application_type = RENEW |
| nrmj-3kcf | Not counted: a filtered view of licenses already counted from another feed. | ||
| Feed | Event | Dated by | Not counted (renewals) |
|---|---|---|---|
| w7w3-xahh | license_granted | license_creation_date |
The figures in this section count places with a record that carries one of the status values listed below for the city, verbatim, where the record's date for that status falls in the month. No other status, and no absence of a record, is counted in this edition. The count states that the records carry that value; it is not a statement by us that a business has ceased operating.
Where the table marks a status value as inferred, the publisher's documentation does not define that value; the rule reads the value's own words. The same note appears on every report figure the rule contributes to.
| Feed | Status field | Status value | Dated by |
|---|---|---|---|
| 4ijn-s7e5 | results | Out of Business | inspection_date |
| Definition inferred from the status value's own words; the publisher does not define it. | |||
Status values in the same rule file that are not counted as closings, with the event type we record for each:
| Feed | Status field | Status value | Recorded as | Publisher defines the value |
|---|---|---|---|---|
| nrmj-3kcf | license_status | AAC | license_ended | yes |
| nrmj-3kcf | license_status | REV | license_ended | yes |
| r5kz-chrr | license_status | AAC | license_ended | yes |
| r5kz-chrr | license_status | REV | license_ended | yes |
| ydr8-5enu | permit_status | COMPLETE | permit_final | no |
No figure is published from these rules in this beta edition; see Coverage.
| Feed | Status field | Status value | Dated by |
|---|---|---|---|
| w7w3-xahh | license_status | Close | first observed in our captures |
| Definition inferred from the status value's own words; the publisher does not define it. | |||
| w7w3-xahh | license_status | Out of Business | first observed in our captures |
| Definition inferred from the status value's own words; the publisher does not define it. | |||
Status values in the same rule file that are not counted as closings, with the event type we record for each:
| Feed | Status field | Status value | Recorded as | Publisher defines the value |
|---|---|---|---|---|
| w7w3-xahh | license_status | Expired | license_expired | no |
| w7w3-xahh | license_status | Failed to Renew | license_expired | no |
| w7w3-xahh | license_status | Revoked | license_ended | no |
| w7w3-xahh | license_status | Surrendered | license_ended | no |
| w7w3-xahh | license_status | Voided | license_ended | no |
A record's date for a status is the date field the publisher gives for it, named in the table. Where the publisher gives no such date, the status is dated by when it first appeared in our captures of the feed.
For a status dated by first appearance, the change happened between two captures; the width of that interval is set by how often the publisher republishes the feed. Such events are reported as an interval, not placed in a month. When such a figure is published, a report states it in this form, where D1 and D2 are the two capture dates and N the number of places. No figure in this edition is dated this way.
First observed between captures of D1 and D2 (no published date): N
Where the status was already present in our first capture of the record, the place is reported separately as undated, in this form. We never state a date for a status the record does not date.
Already in this status at the first capture (no published date): N
Detection lag is the gap between the date a record states and the date we first captured that record. It is measured per feed for openings and per status rule for closings from our own captures and listed below with the number of records measured and the date of measurement.
A lag includes the time a publisher takes to add a record to its published data. Where a publisher releases new records in batches, the lag reflects the interval between releases, and the count for a recent month can rise after the next release.
A month is provisional when its last day plus the listed lag is on or after the report's data date. The report's headline month is the latest month that is not provisional for any figure shown. Later months appear in the chart hatched; their counts can change as later records arrive. Where no lag is listed, only the month still in progress is provisional.
The gap between a stated date and the date a place ceased operating is not in any record we hold and is not measured. Lags longer than our capture window cannot be observed; the window length is listed with each measurement.
Each 90th-percentile lag listed is therefore a lower bound: only records first captured within the capture window are measured, so a longer lag is not in the measurement.
Kind: openings is the lag of opening records. L1 is the lag from a status record's stated date to our first capture of it. Interval marks a status dated by first appearance in our captures; no lag in days applies, and the row is blank.
| Feed | Status value | Kind | Records | Median (days) | 90th percentile (days) | Measured on | Capture window (days) |
|---|---|---|---|---|---|---|---|
| r5kz-chrr | openings | 3215 | 2 | 3 | 2026-11-09 | 138 | |
| 4ijn-s7e5 | Out of Business | L1 | 283 | 5 | 78 | 2026-11-09 | 138 |
| Feed | Status value | Kind | Records | Median (days) | 90th percentile (days) | Measured on | Capture window (days) |
|---|---|---|---|---|---|---|---|
| w7w3-xahh | openings | 2486 | 36 | 67 | 2026-11-09 | 138 | |
| w7w3-xahh | Close | interval | 0 | 2026-11-09 | 138 | ||
| w7w3-xahh | Out of Business | interval | 0 | 2026-11-09 | 138 |
This edition covers the cities listed as "in beta". The other cities Permitory ingests are listed with no figures; their records are captured but not yet counted or published.
Coverage differs by city: a city contributes only the record kinds its agencies publish. A city with fewer sources shows fewer figures; no figure is filled from another city's definition.
| City | Edition | Figures |
|---|---|---|
| Chicago | in beta | Openings
Food inspections with result “Out of Business”
|
| New York City | in beta | Openings
Explicit closings
Not published for New York City in this beta edition. The only status values we count as closings for New York City
come from the licensing feed, which gives no date for them; we date them by first appearance in our captures, so they
cannot be placed in a month.
|
| Los Angeles | not in beta | |
| Boston | not in beta | |
| San Francisco | not in beta | |
| Seattle | not in beta |
Each feed is listed with the publisher's dataset identifier, the credit we display, and the basis on which we republish it: open_data_policy means the publisher's open-data policy; portal_terms_conditional means the portal's terms of use, with the conditions shown below the table.
| Feed | Credit | Basis |
|---|---|---|
| 4ijn-s7e5 | Source: City of Chicago Data Portal — Public Health (data.cityofchicago.org) | portal_terms_conditional |
| r5kz-chrr | Source: City of Chicago Data Portal — Business Affairs & Consumer Protection (data.cityofchicago.org) | portal_terms_conditional |
| Feed | Credit | Basis |
|---|---|---|
| w7w3-xahh | Source: NYC Open Data — Dept. of Consumer & Worker Protection (DCWP) | open_data_policy |
Public records republished as-is; no warranty of accuracy, completeness, or fitness. Point-in-time snapshot; the issuing agency is the authoritative source.
Required by the City of Chicago Data Terms of Use: This site provides applications using data that has been modified for use from its original source, www.cityofchicago.org, the official website of the City of Chicago. The City of Chicago makes no claims as to the content, accuracy, timeliness, or completeness of any of the data provided at this site. The data provided at this site is subject to change at any time. It is understood that the data provided at this site is being used at one’s own risk.
Every report states, for each figure, the feeds it was computed from, the period it covers, the rule-file version, the data date, the boundary set with its dataset, and the unit. From these we can recompute the count from the same record versions.
Reports and this site show counts only. No individual record and no named business is shown.
| City | Rules version | Boundary set | Lags measured on |
|---|---|---|---|
| Chicago | chicago-rules-2026-10-04 | chicago/community_areas/2025-04-22 | 2026-11-09 |
| New York City | nyc-rules-2026-10-04 | nyc/nta2020/2026-05-28 | 2026-11-09 |
Generated
Questions or corrections: support@permitory.com