Peer-city benchmarks — CivicTrue City Edition
CivicTrue City Edition
SAMPLE DATA The peer cities and their figures are invented to show how this screen works. They are not real results. New York City’s requests, population and share closed are real. Its staff headcount and closing rule, and every peer-city value, are samples.

Peer-city benchmarks

Your city against peer cities, Jan–Sep 2026. Only problems every city tracks, counted the same way and set against each city’s population and staff headcount.

Compare your city with
New York City (your city) · 8.6M
Problem

{{ summary }}

Requests per 1,000 residents

Volume is neither good nor bad: more requests can mean more problems, or more people reporting them.

{{ b.name }}
{{ b.v }}

Requests per staff member

Requests divided by the staff each city assigns to this service, so cities of different sizes and staffing compare on the same footing. Peer median: {{ medR }}.

{{ b.name }}
{{ b.v }}

Share closed within a week

Slowest first. Dashed line: median of the peers you picked ({{ medTxt }}). † counts a request closed before the work is done.

{{ b.name }}
{{ b.v }}
New York City {{ nyc.t }}{{ nyc.w }}

Side by side

Staff headcount is the full-time staff each city’s budget assigns to this service. Population is the latest census estimate.

{{ probName }}, Jan–Sep 2026
City Residents Staff headcount Staff per 100,000 residents Requests Requests per staff member Closed within a week
{{ r.name }} {{ r.pop }} {{ r.hc }} {{ r.per }} {{ r.req }} {{ r.rps }} {{ r.sh }}

Cities define “closed” differently

A city that closes a request when a crew is assigned will look faster than one that waits until the work is inspected. Read the share closed alongside each city’s rule.

City A request counts as closed when… Effect on share closed
{{ d.name }} {{ d.rule }} {{ d.eff }}