Research

Neighborhood Record Bulletin

Recorded property-document activity for East New York and eight comparison neighborhoods, from NYC ACRIS public records, with coverage notes for every ZIP.

ResearchEvidence: Descriptive

Research question

How much property-record activity is being recorded in East New York, and how does it compare with nearby neighborhoods and the city?

Findings

  1. East New York recorded 5,593 document-property events from July 2025 to June 2026, 275.3 per 1,000 eligible properties.

    Evidence: Approved release bulletin-20261012T064343Z-32fb57e5, East New York row (ZIPs 11207, 11208, 11239, full coverage).

  2. In the common March–June 2026 window, East New York recorded 93.3 events per 1,000 eligible properties; covered New York City recorded 69.3.

    Evidence: Same release, comparison table (767,335 eligible properties citywide).

  3. Mortgage and related instrument records were the most common document category in East New York, 1,662 of 5,593 events (30%).

    Evidence: Same release, East New York findings.

Methods

An offline refresh copies ACRIS document and property tables into a build database, links recorded documents to eligible residential properties, and counts document-property events by ZIP grouping. Source and reconciliation checks must pass before an operator publishes a versioned JSON release.

The Bulletin is the first product of the Neighborhood Record. It began under the East New York Crypto Institute name as a way to show residents what public property records say about their own blocks, in numbers they can check.

What it counts

Each event is one recorded ACRIS document linked to one eligible residential property. Deeds, mortgages, satisfactions, assignments, and other instruments all count. The reporting date is the ACRIS recorded date, not the date a document was signed.

How a release is made

  1. Stage a copy of the source tables into a separate build database.
  2. Build the release and run source and reconciliation checks.
  3. An operator reviews the candidate and confirms the publish step.
  4. The published JSON is versioned; a failed refresh leaves the last approved release in place.

The full source lineage is in the repository at docs/neighborhood-record-bulletin-source-lineage.md.

Data

Explore the Bulletin by neighborhood