How 311 works · 6 min read

Why should cities track outcomes instead of counting submissions?

Submissions measure demand; outcomes measure service. A count of 311 requests tells a city what residents noticed. Only a record of what happened to each request, who owned it, when it closed, how, and whether the condition is actually gone, tells the city and its public what was delivered.

Aaron Henehan
Contributor: Aaron Henehan
Published Sep 16, 2026
A laptop on a desk showing a dashboard of tracked outcomes
Illustrative photo.
92%
Reached active handling
84 of 91 filed cases moved into a City workflow, as of Sep 15, 2026.
88%
Reached a terminal outcome
80 of 91 cases closed, cancelled, or duplicate.
$286M
Liability paid, FY2025
Against an $87 million budget, citywide, all claim types.
18+ days
Sidewalks, zero resolved
Same filing quality, different bureau, no completion service level.
The short answer

Because submissions measure demand and outcomes measure service. A count of 311 requests tells a city what residents noticed. Only a record of what happened to each request, who owned it, when it closed, how, and whether the condition is actually gone, tells the city and its public what was delivered. Tea For Streets built CLARK AI around that record. The tracked loop is the product.

The short version

  • Submissions measure demand; outcomes measure service. One cannot stand in for the other.
  • A closure count is not an outcome record: closed can mean repaired, cancelled, duplicate, referred, or “see comments.”
  • Outcome records also matter to risk management. Los Angeles budgeted $87 million for liability payouts in FY2025 and ultimately paid about $286 million. Those citywide payouts cover many kinds of claims, not just street conditions.
  • Budgets are defended in public: “efficiency is an internal argument,” John Kitsmiller, energizeGTM.

What does a submission count actually measure?

Demand, and the friction of the channel. Los Angeles reported more than 2.165 million MyLA311 contacts across the mobile app, website, and call center in the 12 months preceding Executive Directive No. 5 in October 2023. That is a real, useful measure of contact volume, but it does not by itself say what happened after each service request was filed. Submissions can rise because conditions worsen, because access improves, or both. They can fall because conditions improve, because residents use another channel, or because people stop reporting.

A closure rate is one step better and still not a complete outcome record. MyLA311 cases can reach different terminal dispositions, including completed work, cancellation, duplicate handling, referral, or a closure accompanied by explanatory comments. A city-reported repair is useful evidence of an outcome, but it is still different from an independent return visit confirming that the physical condition is gone.

The City has explicitly recognized the need to measure what happens after intake. Executive Directive No. 5 says Los Angeles lacked a formal mechanism to ensure the effectiveness of MyLA311 services and calls for standardized customer-service measures and improved fulfillment information. The Controller's 2021 audit likewise recommended measuring service performance, providing estimated completion times, and proactively collecting customer feedback. See What does “Closed - See Comments” mean on a MyLA311 request?

What did tracking outcomes show in Los Angeles?

As of September 15, 2026, Tea For Streets had filed 91 cases through official 311 channels using CLARK AI. Counted as submissions: 91 filed, all accepted. Tracked as outcomes: a map of where the City's workflows exist. Eighty-four cases (92%) reached active city handling and 80 (88%) a city-reported terminal outcome, closed, cancelled, or duplicate, not independent on-site repair verification. Potholes are 40 of the 91 cases, 44 percent of what we filed; 36 are resolved (90%), with a median city closure of six days.

Sidewalks: five cases filed, zero resolved, all open past 18 days. Same system, same filing quality, entirely different outcome. The replies said “received and filed for future reference,” a place in a backlog, not a work order. Sidewalks belong to a different bureau, under a 30-year court settlement, with no completion service level. We can see it because we track outcomes, not submissions.

Not a complaint about government: evidence of what works, and a service question surfaced by data rather than by a complaint cycle.

A council office can act on “92 percent reached active handling, five sidewalk cases stuck past 18 days,” not on “91 filed.”

What should an outcome record contain, and who needs it?

An outcome record holds six things:

  • The condition as observed: photo, location, type, a measurement where possible, date, observer.
  • The filing: the city's case reference, request type, jurisdiction, filing date.
  • The handling: each city status change, timestamped.
  • The closure: the terminal status, the disposition in words a resident can read, the date.
  • Verification: a return visit to the same spot with a matching capture, dated, by someone other than whoever closed the ticket, resolved, not resolved, or unable to verify.
  • Recurrence: a link to any later report at the same location.

Who needs it:

Risk managers. California Government Code §835 can impose liability for injury caused by a dangerous condition of public property when the statutory elements are met, including, in one path to liability, actual or constructive notice with sufficient time to take protective measures. A documented service request can therefore matter to the factual record around notice and response, although whether it establishes legal notice depends on the circumstances. Los Angeles budgeted $87 million for liability payouts in FY2025 and ultimately paid about $286 million citywide. Those payouts span many kinds of claims, including matters unrelated to streets, so they are context for the scale of municipal risk rather than a measure of the cost of 311 failures.

Department heads and elected officials. Govtech sales advisor John Kitsmiller of energizeGTM argues that internal efficiency alone is often not enough to defend a public budget decision; the case also has to connect to an outcome that can be explained to residents and elected officials. That is a useful test here: does the headline describe a citizen outcome, or only a process improvement? An outcome record gives a public works director a sentence to say out loud: what was reported, what reached active handling, how it closed, how long it took, and what was independently verified.

One rule keeps the record trustworthy: Tea For Streets publishes city outcome data under written neutrality rules, the same metrics for every district, no editorializing, advance notice, never suppression.

A person photographing a curb ramp on a city sidewalk with a phone
The condition as observed: a photo, a location, a date, an observer.
Field notes · Tea For Streets

Spill the Tea

91Cases filed through official 311 channels, as of Sep 15, 2026
92%Reached active City handling
6 daysMedian pothole closure, City reported

“The tracked loop is the product” began as an observation: most reporting tools stop at “submitted,” and everything a city and a resident care about happens after that. So CLARK AI follows every case through Received, On It, and Resolved and holds the record of what the City did, Resolved meaning a city-reported terminal outcome, never upgraded to Fixed without a return visit.

Outcome tracking cuts both ways; that is the point. It produced the sidewalk finding and “trash in 44 hours,” and we publish both: alone, the slow lane would be a complaint; together they are evidence. The record also protects a department as much as it tests it: the fact sheet a department head can hand a council member without editing.

To start: pick one issue class and one corridor, track every case to a legible closure for eight to twelve weeks, and verify a sample. No new 311 system needed. Our own limit is scale: 83 cases, largely team-filed, published dated.

FAQ

Isn't a closure rate already an outcome metric?

+
No. Closure is a workflow status that includes cancelled, duplicate, referred, and closed-with-internal-comments cases. An outcome metric asks whether the condition is gone, and who confirmed it.

What 311 outcome metrics should a city publish?

+
Time to active handling and to terminal outcome, by type and district; the share of closures a resident can read; a verified-resolution rate with its denominator and method; how often closed cases are re-reported.

Doesn't outcome tracking expose city departments?

+
It can also protect them by preserving a clear record of what was reported, when the City responded, and what was later verified. Under Government Code §835, notice and the opportunity to take protective measures can be legally significant, but liability depends on multiple statutory elements and the facts of a particular case. Same metrics for every district and no suppression keep the reporting fair.

What does “the tracked loop is the product” mean?

+
That the value is not the submission but the record of what happened after it: filing, handling, legible closure, verification, recurrence. CLARK AI is built to hold that record.

What makes outcome data credible enough for a case study?

+
A denominator, a date, a method, and a named person who will take a call.
CLARK AI by Tea For Streets
Report what you see.
Free to report, right from your iPhone.
Download on the App Store
  1. City of Los Angeles Mayor Karen Bass, Executive Directive No. 5: Improving Customer Experience, Oct. 30, 2023: more than 2.165 million MyLA311 contacts in the preceding 12 months; no formal mechanism to ensure MyLA311 effectiveness; calls for standardized customer-service measures.
  2. Los Angeles City Controller, The 411 on 311: Calling for a Customer-First Approach, Mar. 2021: recommends measuring service performance, estimated completion times, and proactive customer feedback.
  3. Los Angeles City Controller, Liability Claims Dashboard and FY2025/FY2026 reporting: $87 million budgeted for liability payouts in FY2025, about $286 million ultimately paid citywide, across all claim types.
  4. City of Los Angeles, MyLA311 service-request data and budget reporting.
  5. California Legislative Information, Government Code §835: liability for a dangerous condition of public property, including actual or constructive notice with sufficient time to take protective measures.
  6. John Kitsmiller, energizeGTM, GovTech GTM Weekly newsletter and 2026 WIIFM Field Guide: “efficiency is an internal argument.”
  7. Tea For Streets production data: City of Los Angeles cases filed through official 311 channels, as of September 15, 2026.