CityOps
NYC 311 / SERVICE REQUESTS
Source checked Feb 1, 2025, 3:00 AM EST
Historical case study · supported Jan 1–31, 2025 · 3 problems5,000 records loaded · 2025-01-01 to 2025-02-01
RESOLUTION / CREATION COHORTS

How long do requests take to close?

Closure patterns, mature seven-day cohorts, and the latest observed open work.

Metric definitions ↗
SEVEN-DAY OUTCOME

Closure by creation week

Eligible requests in the selected range, grouped by Monday week start; edge weeks may be partial

∅

No mature weekly cohorts

Choose an earlier date range with fully observed creation weeks.

OPEN AT LAST REFRESH

Age of open requests

Selected cohort only · latest ingested status

0–2 days0
3–7 days2
8–14 days0
15–30 days0
31+ days0

A historical backlog series requires saved daily status snapshots; current status is not projected backward.

CLOSE DURATION

Distribution by problem

Valid closed requests only · hours shown as days where helpful

ProblemClosed sampleMedian75th percentile90th percentileStill open
HEAT/HOT WATER171.5 d2.2 d2.4 d0
Illegal Parking1611.3 h12.3 h12.7 h1
Noise - Residential95.3 h5.9 h6.3 h1

Closure is a recorded administrative state, not proof that a resident’s underlying issue was resolved. CityOps does not assert an official seven-day service target.