City Signals / Dashboard

San Francisco 311, neighborhood by neighborhood

Recurring service requests, case volume and closure patterns across the city, refreshed every 6 hours.

Loading public 311 records…
Service requests
—
In loaded records matching filters
Open cases
—
Open share of filtered records
Median time to close
—
Closed cases only; calendar time
Repeat street and request-type pairs
—
3+ reports on the same street and request type*

Request volume over time

Daily case openings
Waiting for data
Each bar represents a day. Counts reflect reported cases, not unique incidents.

Most reported categories

Share of filtered cases
Waiting for data

Recurring street-level patterns

Street + request subtype
Waiting for data
*Repeated requests are a signal for investigation, not proof that the same issue was unresolved.

Geographic distribution

Reported locations
San Francisco · approximate coordinate plot
Location dots are approximate and may overlap. Not a street-level basemap.

Recent requests

Latest 12 matching cases
OpenedCategory / subtypeNeighborhoodStreetStatusCase
Waiting for data

About this San Francisco 311 dashboard

City Signals shows what San Franciscans are reporting to 311, neighborhood by neighborhood. It reads the City and County of San Francisco's public 311 Cases dataset on DataSF and refreshes every 6 hours, covering the last 7, 30 or 90 days of service requests.

What you can see

  • Service request volume by day, for all of San Francisco or a single neighborhood such as the Mission, South of Market, the Tenderloin or the Financial District.
  • Open cases and the median time to close a 311 case.
  • The most reported categories, such as street and sidewalk cleaning, parking enforcement, graffiti and encampments.
  • Recurring street-level issues: the same type of problem reported again and again on the same street.
  • A map of reported locations, the latest cases, and a CSV export of any filtered view.

Who it is for

Business improvement districts, community benefit districts, city operations staff, and anyone who wants to know where the city needs attention, without downloading and cleaning the raw data themselves.

How to read the numbers

Each record is a service request, not a verified incident: one problem can generate many reports. Time to close measures when a case was closed in the city's system, which may be an administrative closure rather than a confirmed fix. Neighborhoods follow the city's analysis neighborhood boundaries. City Signals is built by Sora Labs and is not an official City and County of San Francisco product.

Source: San Francisco 311 Cases, DataSF · This page reads a snapshot of the last 90 days that is refreshed every 6 hours; the publisher itself updates the dataset roughly nightly. A case's closure timestamp may reflect administrative closure rather than physical completion. If the snapshot is unavailable the page falls back to a live API query capped at 20,000 rows, and says so. No Citizen app content is used. Created by Sora Labs as a product prototype.