How it works
Block by Block lets any resident say what is working and what is not on their block — in under 30 seconds, in their own language, with no account. Those signals become a planning instrument: clustered by issue, weighted by corroboration, and mapped against where money is actually being spent.
This is not another 311. 311 is a complaint intake queue. This is the layer above it: it tells the city what residents think matters most, not just what broke.
What data we hold
Almost none. No account is required to file a report. We never store your precise home location — reports snap to a block segment of roughly 150 meters. A "same here" stores only an anonymous session code, never your identity.
How the priority score works
Each cluster of reports is scored from five ingredients: how many reports it has, how many neighbors corroborated them, how long the issue has persisted, how geographically concentrated it is — and how little budget the category receives compared to the need residents express. An issue raised often where little is being spent rises to the top. Every score can be opened to see exactly why.
About the data in this demo
This pilot is seeded with real, public NYC Open Data: 12 months of 311 service requests for Queens Community District 1 (Astoria) and the city's FY2026 expense budget, scaled per-capita to the district. "Working well" examples are illustrative. No City of New York endorsement is implied.
Reporting is not need
Neighborhoods that trust government less, report less. A score fed by reports alone would reward the loudest blocks, not the neediest. That is why the pilot pairs this platform with offline outreach, why the calculation is open to audit in line with New York's algorithmic accountability framework, and why reporting-propensity normalization is on the roadmap before any citywide scale-up.
Where every number comes from
Every figure on this site maps to a public source or an open calculation. Ask about any number on screen and we show the query.
- 95,999 — all 311 requests, 2025-07-27 to 2026-07-27NYC Open Data · erm2-nwe9 · run this exact query — the window is fixed at both ends, so it returns this number, not a moving one →
- 85,636 — of those, inside the six categories this site scoressame window, filtered to the 84 complaint types the query itself lists →
- 10,363 — 311 requests this platform does NOT cover72 complaint types outside our six categories, counted nowhere else on this site. Largest: GENERAL (1,643), Water System (1,517), Encampment (914), Sewer (626), Consumer Complaint (576) →
- 31,310 records · 2026-03-21 → 2026-07-26 (18 weeks)the analysis window: detailed per-record data behind every cluster, its priority score and its map position. Cluster metrics are never mixed with the 12-month totals above.
- 311 requests per week — 12 monthssame window, daily counts grouped into complete weeks →
- Need vs. spend by categoryNYC Expense Budget FY2026 · mwzb-yiwb · per-capita estimate, not a district allocation (see method) →
- Prioritydeterministic formula over the analysis window — open source, no model in the loop
- AI briefing · Status · exampleillustrative / AI-assisted — clearly labeled, never mixed with measurements
Data: NYC Open Data — 311 Service Requests & FY2026 Expense Budget · Queens CD1 — Astoria · 2026-07-27