← vital-city-community-data

Repeat Requests

About Substack Support my work
Visuals in this post: Agency Responses Repeat Requests Open Data Releases 311 Channels
data.nycuriosity.com › Community Data Pipeline › Repeat Requests
Community Data October 2026

At least two in three community board budget requests have been asked for before

At least two in three FY2027 community board budget requests had been made before, and 521 date back to FY2019 or earlier. Matched across nine registers.

Download CSV (members)

At least two in three FY2027 community board budget requests had been made before

FY2027 budget requests by the number of budget cycles since the same board first made the same request of the same agency, matched against every adopted register from FY2019 to FY2026.

Source: NYC OMB, Register of Community Board Budget Requests, FY2019–FY2027 registers (NYC Open Data) Note: A request counts as a repeat when the same board asked the same agency for it in an earlier adopted register, matched on the request's explanation text (at least 90% similar) or on a previous tracking number the board cited. The registers on NYC Open Data start with FY2019, so '9 or more' means first requested in FY2019 or earlier. 46 requests with a blank or very short explanation could not be matched and are left out of the bars.

521 requests on the FY2027 list were first requested in FY2019 or earlier, the earliest registers in the data.

Method: A request counts as a repeat when the same board asked the same agency for it in an earlier adopted register, matched on the request's explanation text (at least 90% similar) or on a previous tracking number the board cited. The registers on NYC Open Data start with FY2019, so '9 or more' means first requested in FY2019 or earlier.

Boards edit request text over time, so the repeat count is a floor: a request reworded by more than about 10% counts as new. In a hand-checked sample of 30 requests the method marked as new, 7 were rewordings of an earlier request; none of 30 sampled matches was a false match. 46 requests with a blank or very short explanation could not be matched and are left out of the bars.