311 Service Request Apps and What Happens to a Report
There is a pothole on my street that I reported in March. It was fixed in June, badly, and reopened by August.

There is a pothole on my street that I reported in March. It was fixed in June, badly, and reopened by August. Somewhere in that loop sat a ticket with a number, a category, a closure code and a date, and for most of the time I had no idea which of those four things was holding it up.
Service request apps, the mobile front end to the old 311 phone line, are the most used piece of civic technology in most cities and the least explained. People download one, take a photo, press send, and then hear nothing for weeks. This piece walks through what happens to a report after it leaves your phone, why some tickets close in 48 hours and others sit for a year, and the handful of things you can control that actually change the outcome.
What happens between your photo and a repair crew
A report moves through four stages, and only the first is visible to you.
The app writes a record into a work order system. Most mid sized cities run one of a few commercial platforms, with Accela, Cityworks, Salesforce Public Sector and SeeClickFix covering the bulk of North American deployments. Many of them speak Open311, a shared specification whose GeoReport v2 version defines the service list, the request format and the status field. That standard is the reason a third party app can submit a ticket to a city it has no contract with.
Next the ticket gets routed by category. This is the step that decides everything. A pothole filed under "street defect" lands with the paving crew. The same pothole filed under "other" lands in a general queue where a clerk reads it and reassigns it, usually within a week, sometimes never. Chicago and New York both publish category lists that run past 200 entries, and the gap between the right one and the near miss is often measured in months.
Then comes triage against a service level target. Cities publish these unevenly, but the pattern holds: a missed trash collection is typically promised in 1 to 3 business days, a dead streetlight in 10 to 14, a pothole in 7 to 30 depending on severity and season, and a sidewalk replacement in 6 to 18 months because it sits in a capital programme rather than a maintenance one. Asphalt plants in cold climates shut from roughly November to March, so a January pothole report in a northern city is a spring job no matter how it is worded.
Finally the ticket closes with a code. "Closed, repair completed" and "closed, no action necessary" look identical in most app interfaces, which is where a lot of resident frustration comes from.
The counter-take: twenty neighbours reporting the same hole does nothing
The standard advice on local forums is to rally the street and flood the system, on the theory that volume gets attention. I used to believe this. The data published by cities on their own portals says otherwise.
Nearly every platform does duplicate consolidation. Reports landing within a set radius of an existing open ticket, commonly 25 to 50 metres for street assets, get merged into the parent and marked as duplicates. Twenty reports become one work order with a duplicate count attached. Some cities surface that count to supervisors, most do not use it to reorder the queue, and a few treat a high duplicate count as a sign the original location description was vague.
What does move a ticket, in my experience and in the closure data I have read through: a precise location, the correct category, a photograph with something in it for scale, and a clear statement of hazard. "Pothole 40 cm wide and 12 cm deep, northbound lane, 20 m south of the junction with Mill Lane, cyclist swerved into traffic to avoid it on Tuesday" is a different document from "road is terrible". The first one can be assigned, sized and scheduled by someone who has never visited the street. The second one needs a site visit before it can be sized, and site visits are scheduled behind actual repairs.
One more thing worth knowing: a single report routed to a council member's office through a casework system often outruns fifty app submissions, because that route carries a human who chases it. That is not how a well built system should work, and it is how most of them do.
How to file a report that survives triage
- Find your city's own app or portal first. Third party apps that submit through Open311 work in participating cities, but status updates come back thinner. Search the city domain rather than an app store listing.
- Pick the narrowest category that fits. Read past the first three options. "Pothole" and "street resurfacing" go to different crews with different budgets, and your choice decides which one owns the problem.
- Stand next to the problem when you submit. Phone photos carry a geotag, and most apps pull location from that or from live GPS. Filing from your sofa drops the pin on your house.
- Add a size and a reference point. Measurements and a nearby house number or junction let a crew size the job from the desk. A shoe or a drinks can in the frame does the same work.
- State the hazard plainly, once. Risk to cyclists, to a school route, to a wheelchair crossing, or standing water over a drain. Hazard language moves items up most priority matrices. Repeating it four times does not.
- Write down the ticket number. Without it you cannot follow up, and you cannot tell a reopened problem from a new one.
- Check the closure code, not the closure. If a ticket closes as no action necessary and the hole is still there, reopen or refile with a note referencing the old number. Cities track reopen rates, and that number gets read.
What the city builder games get wrong about this
I have spent more hours than I will admit in city management games, and they taught me a model of municipal service that took years to unlearn. In a game, a complaint icon pops up over a building, you click it, a truck leaves a depot, and the icon clears. The loop is immediate and the only real constraint is money you can borrow at a fixed rate.
Real service queues have constraints the simulations mostly skip. Crews are specialised and not interchangeable, so a paving team cannot clear a drain. Work has to be bundled geographically to be affordable, which is why your pothole may genuinely wait for three more nearby to justify sending a crew. Materials are seasonal. Some assets belong to a utility, a state highway agency or a railway rather than the city, and a ticket on those gets forwarded out of the system entirely, which is one of the most common reasons a report vanishes without explanation.
The simulations do get one thing right, and it is the thing residents underuse. In a game you can see the service coverage map. In a real city you can see something close to it, because 311 data is one of the most commonly published datasets on municipal portals, usually with the date opened, date closed, category and block level location. Pull a year of pothole tickets for your ward, count the ones closed inside the promised window, and you have an argument instead of a complaint. Our guide to how residents use city open data portals covers where those files live and how to search them.
When the app is the wrong tool
Service request systems are built for discrete, visible, physical problems. They handle a broken streetlight well and a policy dispute badly. If what you want is a change to how a budget is allocated, a ticket is the wrong container, and the better route is the public meeting agenda. We walk through that in how to submit public comment online to your city council.
If you want the internal emails about why a street was skipped in the resurfacing programme, that is a records matter rather than a service matter. Service tickets rarely contain decision history. See how to file a public records request online for the wording that gets a response.
And if a report concerns an immediate danger, a live wire, a gas smell, a flooded road, do not use the app at all. Those queues are checked on business hours in most cities, and nothing in the design treats them as urgent.
FAQ
How long should a 311 request take to close?
It depends entirely on the category. Missed collections and noise complaints usually close in 1 to 3 business days. Streetlights run 10 to 14 days. Potholes range from 7 to 30 days in season and much longer over winter. Sidewalk and drainage work often sits in a capital programme measured in months.
Do third party reporting apps actually reach the city?
In cities that have implemented the Open311 specification, yes, and the ticket number comes back to you. Elsewhere the report may sit in the app company's database with no municipal recipient. Checking whether your city lists an Open311 endpoint takes a minute and saves a lot of wasted effort.
Does reporting the same problem repeatedly help?
Not usually. Nearby reports get merged into one work order as duplicates, and most cities do not reprioritise on duplicate count. A single accurate report with measurements, a photo and a hazard note does more than twenty vague ones.
Why did my request close with no repair?
Most often because it was closed as no action necessary, which can mean the asset belongs to another agency, the defect fell under the threshold for intervention, or the inspector could not find it from the location given. Reopen the ticket and reference the original number rather than filing fresh.
More in Civic Tech
Civic Tech
How to File a Public Records Request Online That Works
You want a copy of something your city already has. Maybe the police overtime totals for last year, the inspection report on...
Civic Tech
Open Data Portals and How Residents Use City Records
You want to know how many potholes your street has reported this year, or how much the city spent on overtime, and the answer...
Civic Tech
Online Petitions and Whether They Change Anything
You signed it, shared it, maybe even forwarded it to your family group chat, and then nothing seemed to happen.