clm-ea60b310a26deb8d
quantitative
San Francisco opened 311 in March 2007
Permanent project revision
Revision 2026-09-27-baseline-popular · effective 2026-09-27
Current revision. This is the snapshot used by the live entity page.
Created the first structured Evidence Passport with 13 claims and 12 source dossiers.
sha256:c8e646d291e223f38eb579c8c660c7baa83d39c07a528ce1bb2bd7c4b06f14c2
add /evidencePassport — Added claim-level evidence mapping and source dossiers.add /revisionHistory — Established a permanent, hash-addressed baseline revision.The text below is copied verbatim from the published record. Each claim names the source dossiers that carry it; caveats stay attached to the claim they qualify.
clm-ea60b310a26deb8d
quantitative
San Francisco opened 311 in March 2007
clm-6ba1d4e9ceb89cb5
quantitative
folding more than 1,000 city phone numbers into one line
clm-10b319ac7fa107e8
quantitative
In May 2010 it agreed the Open311 GeoReport v2 specification jointly with Washington D.C.
clm-c46bd8c164012770
quantitative
whose 311 API the standard grew out of
clm-bb33b76f4a967cf2
descriptive
so outside apps can write into the city's work queue rather than only read from it
clm-22221eb08ed9fe4e
quantitative
Cases since July 2008 are published nightly under a public-domain dedication
clm-acda1e377f5a7d99
quantitative
The city set 12 July 2025 as the shutdown date for that API
clm-9ca59d184745dda7
quantitative
its public endpoint was still returning new requests in September 2026
clm-dbe78ed5a5fdfaf2
quantitative
872,426 service requests created in 2025, counted directly from the city's own open dataset
clm-f630ef1117206e85
quantitative
534,032 through a mobile app (61%), 181,123 on the web (21%) and 149,652 by phone (17%)
clm-7b78915f23f5b188
quantitative
6,139 from agency integrations, 833 by Twitter or email, and 647 test or unlabelled rows
clm-e0ed8d2e7a727b75
descriptive
the city moved to shut its API the year a volunteer app began filing a visible share of some neighbourhoods' reports
clm-397882064b58869d
quantitative
Its own Controller had told SF311 in 2018 to tighten internal controls so that requests are accurately addressed and its published reports can be relied on
This layer records what is known about each source, what is still missing, and the exact snapshot this page is rendering. A missing date, archive or hash stays visible as missing.
Awaiting operator and domain-expert review; publication of this revision implies neither.
sha256:c8e646d291e223f38eb579c8c660c7baa83d39c07a528ce1bb2bd7c4b06f14c2
src-c041d776510df862Operator page: SF311 was founded in 2007 under Mayor Gavin Newsom to replace a landscape of over 50 city agencies and more than 1,000 phone numbers with one number; it answers by phone in over 160 languages.
src-07a4b30bbb64e3b9The League of California Cities' magazine (June 2014): the SF311 center launched in March 2007 and had answered its 16 millionth call by March 2014; service requests are published to the city's open data portal.
src-2f75fe60d6bae0b0Open311's own history: the standard 'first began with an API for Washington D.C.'s 311 system' and became a community under San Francisco's leadership with OpenPlans, Code for America and the White House.
src-1995479a7d0204ffDates the joint specification: 'The two cities currently driving this forward the most, San Francisco and Washington D.C., have come together to agree on and fully interoperate with a new Open311 GeoReport v2 specification.' Same post records that San Francisco 'moved their API from just being available for testing to being deployed as a live, in-production web service'. The v2 spec was frozen on 11 March 2011.
src-ff790016e7e8dbf1The city's public Open311 GeoReport v2 endpoint. On 27 September 2026 it returned live service requests filed the previous day; the companion services.json listed service codes of type 'batch'.
src-8d58629383f3b699The city's Open311 page, hosted by its app vendor Connected Bits: points developers to the Open311 specification, gives the services.json example endpoint, states that no jurisdiction_id is required and that XML and JSON are supported.
src-e90e70d330bcf22eOfficials told the developer of Solve SF on 13 May 2025 that the Open311 API would be shut down on 12 July 2025; the city administrator's office said it 'would have to be fully rebuilt'. Solve SF, launched 29 January 2025, had filed 16,278 of the 336,500 requests made in 2025 to that date, and by its own dashboard — which 311 officials called accurate — 44% of graffiti requests near Valencia Street and 21% of illegal-parking reports in the Richmond.
src-9c71538f9e3452c7Independent confirmation of the city's stated reason: 'changes to the 311 service will make it unaffordable to staff and maintain the old API.'
src-475b76a20f2ed51aThe Public Works Commission's log of correspondence received 2–15 May 2025 records a letter from a member of the public dated 14 May 2025 with the subject '311 shutting down API'.
src-c52553964fb6f6bfThe open dataset of SF311 cases created since 1 July 2008 with location information, updated nightly, under the Open Data Commons Public Domain Dedication and License (PDDL 1.0). The impact figures group calendar-2025 rows on the dataset's source field, counted on 27 September 2026.
src-5ef1e32cf34dba77The Controller's performance audit of 9 August 2018: SF311 should improve internal controls so that requests are accurately addressed and its key reports can be relied on; Call Center performance 'declined substantially from 2013 to 2015'. Seven recommendations.
src-5177b004b1066dd4January 2026 local coverage: nearly 800,000 311 requests in 2025, with third-party tools including Solve SF cited as pushing up volume while City Hall debated limiting its API access. Its headline total is lower than the city's own dataset count.