#1163 2007 · mySociety (FixMyStreet) · Civic technology / local government
FixMyStreet made complaints public by default, so ignoring one meant ignoring it in public
the problem
Residents didn't know which overlapping council was responsible, and complaints vanished into private systems
background
A single UK address could fall under a City Council, District Council, Borough, County, or Parish Council depending on the type of issue, with no consistent rule for which authority handled which kind of problem, so residents often didn't know who to contact at all. Even when they did reach the right office, reports filed by phone or an internal council web form were invisible to everyone else — there was no way for a neighbor to see that a pothole had already been reported, and no public record that made a council's inaction visible to anyone besides the person who filed the original complaint.
mySociety's answer, launched in February 2007, removed both problems at once. Users pinned a problem's exact location on a map, and the system automatically matched that location and category to the correct responsible council, sending the report by email — but it also published every report publicly on the site by default, turning a private complaint into a visible, dated public record that stayed up whether or not the council acted.
what everyone would do
The available options were lobbying individual councils to improve their own phone and web-form reporting systems, or building a private-complaint tracking tool that still routed reports invisibly to whichever authority happened to answer — neither of which changed councils' incentive to act quickly.
what they saw
mySociety saw the failure wasn't just routing confusion, it was that a private complaint carries no social cost. Publishing every report by default turned each pothole into a small, permanent public record of inaction.
the move
FixMyStreet let anyone drop a pin on a map to report a local problem, automatically routed the report to whichever specific council authority was actually responsible for that location and category, and published every report publicly on the site regardless of whether the responsible council ever fixed it.
why it works
Automatic routing solved the practical confusion over which of several overlapping authorities was responsible, removing the main excuse for inaction, while making every report public by default added a reputational cost to ignoring it that a private phone complaint never carried. Because both fixes lived entirely on mySociety's side of the interaction, the system worked without requiring any council to change its own internal processes or explicitly opt in.
the payoff
By 2017 the site had logged its millionth report, with over 12,000 new reports sent to UK councils every month.
where it breaks
The mechanism depends on the responsible authority caring at least somewhat about public visibility of its performance, and on there being a genuine, resolvable routing ambiguity for the tool to fix; an authority immune to reputational pressure, or a complaint type where the responsible party is already unambiguous and the bottleneck is budget rather than routing, won't respond much faster just because the report is public.
what came after
FixMyStreet's open-source platform was reused to build equivalent civic-reporting sites in Australia, Chile, Switzerland, Japan, Malaysia and numerous other countries, establishing public, auto-routed infrastructure reporting as a standard civic-tech pattern rather than a one-off UK project.
references
- [1]FixMyStreet.commySociety, 2021mysociety.org