Data literacy worksheet · Reviewed 25 October 2026
A count of 311 requests measures recorded requests within a defined selection. It is not automatically a count of unique physical problems, people affected or verified violations. This guide provides a method for explaining a count without overstating it. All numerical examples below are fictional.
Define the unit before calculating
NYC describes a service request as an inquiry sent to an agency for further action. Before reporting a count, identify the record’s unique key, the date field, geography and request category you selected. Write those choices beside the number. “Noise requests created during June in this area” is more precise than “June noise problems.”
| Question | Research note |
|---|---|
| What is counted? | Rows, distinct request identifiers or another defined unit |
| Which date? | Created date, closed date or another field |
| Which geography? | Borough, community district or explicitly defined boundary |
| Which categories? | Exact source labels and filters |
| What was excluded? | Missing location, duplicate identifiers or other stated exclusions |
| When retrieved? | Download time and dataset update information |
Compare like with like
Suppose one fictional area has 120 requests and another has 80. The first has more recorded requests in that selection. You cannot conclude from those totals alone that conditions are worse, because the comparison has not accounted for the number of people, properties, reporting behavior or repeated requests about one issue.
If you calculate a rate, name the denominator and explain why it fits the question. Do not mix a population estimate from one geography with requests from another. If you lack a defensible denominator, report counts and limitations rather than manufacturing a more scientific-looking rate.
Read status descriptions with care
A closed request is a workflow status. To understand the recorded outcome, read the resolution description and any relevant agency record. NYC311 provides service-request lookup and explains that certain request types use other status channels. Do not assume every category has the same coverage or follow-up process.
Check changes in the dataset itself
NYC Open Data has published changes to 311 column labels and the split between current and historical datasets. Before combining exports, compare their fields and date coverage. A trend can change because the selection or schema changed, even when the chart looks continuous.
Publish your filters, retrieval date and a short limitations paragraph with any finding. A reader should be able to distinguish what the data records from what you infer about the neighborhood.
Primary references: NYC 311 Reporting, Service Request Status, and NYC Open Data’s 311 updates.