This week in San Francisco 311

01This week's signals

Three things worth knowing

02Neighborhood movers

Where did requests rise or fall the most?

Neighborhood and category pairs with 20 or more reports this week, compared with the trailing 30-day average. Select a neighborhood to open those cases on the dashboard.

03Recurring problems

Which street and request-type pairs keep coming back?

Street-name and request-type pairs with 5 or more reports in the last 90 days and an open case or a closure in the last 14 days. Grouped by street name, so a pair can cover a whole corridor rather than one block. The 25 with the most reports.

04Method

How these are calculated

• This week is the latest 7 days with published data. DataSF publishes about a day behind, so the week ends on the newest case date in the data, not today.
• Spikes compare reports in the last 7 days with the daily average over the 30 days before that, scaled to 7 days. A pair is flagged at 25% or more above that average with at least 20 reports. If none qualifies, the finding shows the largest drop instead.
• Repeat street and request types group reports by street name and request subtype over 90 days; a long street counts as one pair. If none qualifies, the finding shows how many older cases are still open.
• Time to close compares the median days from request to closure in the city's system for the 5 highest-volume categories: cases closed in the last 30 days against cases closed 31 to 60 days ago. A category is flagged when its median rose by 3 days or more from at least 3. If none qualifies, the finding shows the category with the shortest median time to close.
• Each record is a service request, not a verified incident, and a closed case may be administratively closed rather than fixed. The sentences on this page are fixed templates filled with computed numbers; no AI writes them.