What changed in reported requests?
Intake, closure, and area signals for the selected creation period.
Selected versus prior period
Reported requests · equal-length windows
One bin per day; scroll to inspect the full period. Bars open matching request records. Missing days within coverage count as zero.
What residents reported
Share within the selected requests
Across boroughs
Raw report counts, not incident prevalence
What sits behind the headline?
Compare problem movement, seven-day outcomes, and the mix within each borough. Every view uses the filters above.
Which problems moved?
Selected minus preceding equal-length period
Bar length compares absolute count change within this view. A zero prior count has no percentage change. Select a problem to filter the dashboard.
Without closure by day seven
Not closed within seven days · per 1,000 eligible requests
Not closed within seven days per 1,000 eligible requests. Bars use a relative scale; values are labeled. Rates with fewer than 30 eligible requests are withheld. This is distinct from currently open work.
What each borough reports
Share of selected requests within each borough · totals shown at right
Each bar totals 100% of selected requests in that borough. Length is composition, not borough volume; totals are shown at right. Select a segment to filter both area and problem.
Read the change in context.
Selected reports rose 0% against the preceding equal-length period. Check problem mix and borough patterns before treating a count shift as an operational change.
311 counts measure reports received. The seven-day threshold is an analytical definition, not an official NYC service target.