FixMyStreet sends users’ street reports to councils across the UK.
But if you’re one of the staff that receives these reports, you might sometimes wish for more insights: which issues are most commonly reported in your area? What’s a bigger problem, dog fouling or potholes? How quickly do reports get fixed, and how does this compare with other councils’ performance?
To make it easy to discover the answers to all these questions, we’ve just rolled out a new stats dashboard on FixMyStreet — and it’s free to access if you work for a council.
Council staff can now view and download information that answers questions such as:
- How many FixMyStreet reports have been made in your area across various time periods?
- How many reports have been made in each category?
- What are the average times between reports being made and being marked as fixed, and how does this compare to other councils?
- Which categories of report are most common within your area?
- Which categories of report does FixMyStreet send to your council, and which email addresses does it use?
From this exclusive area, you can gain a more in-depth understanding of how FixMyStreet is being used in your area, while also getting a taste of the fuller functionality available with FixMyStreet Pro.
So, if you work for a council, head over to the dashboard page now, and start exploring.
This is part II in a series of blog posts about our work with Hackney Council to conduct a discovery and prototyping project to improve the public-facing parts of information request processes. Read the first part here.
With our experience of running WhatDoTheyKnow and Alaveteli, we’re big believers in the importance of information transparency laws in our democratic system. But at the same time, we understand the operational challenges of meeting the statutory requirements of these laws for public bodies.
The challenges of dealing with information requests
While many local authorities have dedicated information governance staff whose job it is to manage requests, finding and compiling the information is often done by hard-pressed staff within services, fitting in information-related work around their core responsibilities.
Requesters sometimes have the expectation that information is all carefully organised in a few databases, ready to be aggregated and extracted at the click of a button. In reality, the degree to which information is well-organised varies a lot between services in a council and between different councils, often because of procurement decisions and departmental priorities stretching back many years.
Working with Hackney Council
We’re part way through our project with Hackney Council that Mark wrote about a few weeks ago, helping them redesign the public-facing parts of their FOI and Subject Access Request (SAR) services, so we’ve seen these challenges up close. We’ve also seen how they can be made even trickier by legacy IT systems that are no longer fit for purpose.
Catching up on the work we’re doing with @mySociety to see how we can make freedom of information and subject access requests better for users. pic.twitter.com/BbZDljBL3C
— Rob Miller (@RobMiller31) February 28, 2018
At our ‘show and tell’ last week with Hackney, we shared findings from some of the research we’ve done, along with early prototypes of potential new FOI and SAR submission forms, both created collaboratively with Hackney Council staff.
Prototyping with the GDS toolkit
We decided to go straight from sketches to HTML-based prototypes for this project. We thought that moving in-browser with real interactive elements would make it easier to test out some of the more complicated interactions and conditional workflow of the SAR process in particular.
Prototyping is about quickly testing hypotheses, and not getting bogged down in implementation details. So it was a pleasure to use the GDS frontend toolkit to build our prototypes. Not only did the GOV.UK toolkit help us build something relatively rich in just a few days, but it also meant we benefited from GDS’s previous work on design patterns developed for exactly this kind of context.
Using public information to reduce FOI requests
When submitting a request via WhatDoTheyKnow, users are automatically shown previously submitted requests that might answer their question, and we know that almost 10% of requesters have a look at these suggestions in more detail.
As you can see here, we took this pattern from WhatDoTheyKnow, and enhanced it further in our FOI prototype.
Now, as well as prompting with previous FOI responses from a disclosure log that we’re hoping to build, we also want to include relevant links to other topical or frequently requested information, drawn from other data sources within the council.
If we can get this to work well, we think it could have a number of benefits:
- Helping the person submitting the FOI get their answer more quickly
- Reducing the number of requests that would otherwise have been sent to the council
- Encouraging more proactive, structured publishing of data by the council.
It’s this last point which we’re really interested in, longer term. We think using a common sense technology approach to highlight possible answers to FOI requests before they are made will get people answers more quickly, reduce the burden on responders, and reinforce efforts to proactively release commonly requested data leading to real transparency benefits.
We’ve been doing usability testing of these prototypes over the last few days, and will be looking very closely at whether our assumptions here stand up to scrutiny.
Reducing back and forth around SARs
Given our background, we’re inevitably very interested in the FOI component of this project, but the Subject Access Request component is no less important. And while there’s none of the same opportunity for pre-emptively answering people’s requests, there’s plenty of scope for making the submission process a lot smoother.
A valid FOI is just a written request and some contact details, but the information needed for a SAR to be valid is much greater and more complicated. For example, along with the specifics of the request, a solicitor asking for personal information on behalf of a parent and their 16-year old child would have to provide proof of ID and address for both family members, a letter of consent from the child, and a letter of authority from the parent, confirming that the solicitor is acting for them. Even the most straightforward SAR calls for the handling of personal data and confirmation of the requestor’s identity and address.
Given all this complexity, it’s easy for there to be a lot of back and forth at the start of a SAR: clarifying a request, asking for documents, arranging receipt of documents, and so on.
We’re hoping to build something that makes it much clearer to the person making the request what they’ll need to do, thereby taking some of that responsibility off the shoulders of the team managing the requests.
The sketch above was our first crack at something that could handle (most of) this complexity, and we’ve made a number of changes since then as our understanding of it all has increased.
Recruiting representative users to test SAR submission has proved challenging and wasn’t helped by the Beast from the East rearing its snow-covered head. But we changed tack and successfully ran some guerilla testing in Hackney’s service centre last week, and we’re hoping to do further testing later in the project that has more chance of benefiting from contacts cultivated by individual services.
Changing the conversation
The conversation around information requests often focuses on the burden of responding. And although the number of information requests local authorities receive is unlikely to decrease any time soon, we’re hoping that through our collaboration with Hackney, we can make handling them a whole lot easier.
If we do it well, we think we could eliminate a lot of the process issues created by poorly-designed legacy systems, while baking in a fundamentally more open and transparent way of operating that has the potential to benefit both citizen and state alike.
If you’re responsible for managing FOI requests or data protection in your own public sector body and you’d like to follow this project in more detail—or if you’d like to participate in some of the discovery work—then please get in touch at firstname.lastname@example.org.
Image: Sarah Palmer-Edwards
All mySociety websites have strong security: when you think about some of the data we’re entrusted with (people’s private correspondence with their MPs, through WriteToThem, is perhaps the most extreme example, but many of our websites also rely on us storing your email address and other personal information) then you’ll easily understand why robust privacy and security measures are built into all our systems from the very beginning.
We’ve recently upped these even more for FixMyStreet. Like everyone else, we’ve been checking our systems and policies ahead of the implementation of the new General Data Protection Regulation in May, and this helped us see a few areas where we could tighten things up.
A common request from our users is that we remove their name from a report they made on FixMyStreet: either they didn’t realise that it would be published on the site, or they’ve changed their mind about it. Note that when you submit your report, there’s a box which you can uncheck if you would like your report to be anonymous:
FixMyStreet remembers your preference and applies it the next time you make a report.
In any case, now users can anonymise their own reports, either singly or all at once. When you’re logged in, just go to any of your reports and click ‘hide my name’. You’ll see both options:
Security for users was already very good, but with the following improvements it can be considered excellent!
- All passwords are now checked against a list of the 577,000 most common choices, and any that appear in this list are not allowed.
- Passwords must now also be of a minimum length.
- If you change your password, you have to input the previous one in order to authorise the change. Those who haven’t previously used a password (since it is possible to make a report without creating an account), will receive a confirmation email to ensure the request has come from the email address given.
- FixMyStreet passwords are hashed with an algorithm called bcrypt, which has a built in ‘work factor’ that can be increased as computers get faster. We’ve bumped this up.
- Admins can now log a user out of all their sessions. This could be useful for example in the case of a user who has logged in via a public computer and is concerned that others may be able to access their account; or for staff admin who share devices.
Image: Timothy Muza (Unsplash)
We created FixMyStreet Pro to help councils and city governments better manage inbound street reports and issues from their residents.
In the past few months we’ve rolled out the FixMyStreet Pro service to new customers including Bath & North East Somerset, Buckinghamshire and Rutland councils; each of whom are taking the opportunity to get rid of legacy software, simplify their operations and make use of a much simpler and intuitive way for their residents and staff to make and manage reports.
We’re now looking for input from councils to help us guide the next phase of our service development on FixMyStreet Pro.
Having spoken to dozens of councils we think we can help them save more money by extending FixMyStreet Pro to other areas like waste and environment services and we would like to explore how much development work that might entail.
Not just for streets
As FixMyStreet’s name would suggest our focus so far has been on handling issues related to highways like potholes, lighting and gullies (drains to me and you), but FixMyStreet Pro already handles reports for a whole range of issues beyond streets.
Typically council users of FixMyStreet Pro have around 13 to 15 different self-selected categories that they accept reports on – each of which can be directed to different teams or departments. Tree reports can be sent directly to the parks department, graffiti or abandoned cars can be passed along to the just the right team in street cleansing.
These ‘front end reports’ all have one thing in common: all we need to make the report is a location and description, plus a contact for the reporter, which could be as simple as an email address or phone number.
But once you get deeper into the glamorous world of bins and waste services for individual residents the situation gets a little more complicated.
Missed bin collections, requests for recycling bags, bulky waste collection – these all require the resident to be identified, the particular property to be checked with the UPRN (Unique Property Reference Number), and in some cases payments levied and collected.
FixMyStreet Pro doesn’t currently offer these additional waste services, although it doesn’t require a huge leap of imagination to see how we could add these adjacent features to the service, not least because we already do a lot of the pieces across our other commercial services.
Fortunately there has already been a lot of work done to define common standards, such as the Local Waste Service Standards Project from 2016 and more recent work by individual councils to apply some of this work – we also have a lot of our own research and experience to draw upon with numerous specific feature requests from our current local authority clients.
To make this happen we’d like to recruit at least two or three friendly councils available for interviews and possibly a workshop or two, to help us determine specific requirements and test out some of our early prototypes and hypotheses. From here we’d aim to develop these features into fully working aspects of FixMyStreet Pro over the summer.
If this is of interest to you, if you’re already grappling with this in your own council, or you’d just like to find out more, please get in touch with email@example.com and we can have a chat.
In the meantime you can always find out more about what FixMyStreet Pro can do on one of our regular Friday Webinars.
Image: Smabs Sputzer CC BY 2.0
What would Eddie Grundy do if he came across a pothole? And how would Linda Snell deal with flytipping on the site of the Ambridge village fete?
Fortunately, these fictional characters now enjoy the same access to FixMyStreet as the rest of us, thanks to the new demo site we’ve built.
The thinking behind it is not, of course, to gather reports from an entirely fictional world. We’re not that mad. Rather, we needed a sandbox interface where we could show councils exactly how FixMyStreet works, and allow them to play about with both the customer end and the admin side, all without causing any major repercussions to the running of the standard site. Enter FixMyStreet Borsetshire.
Prospective buyers of the system from local councils can experience the various levels of administration that the back-end allows. Just log in with the credentials seen on this page and see exactly how reports can be shortlisted, actioned, or moderated.
So, we’re expecting reports of pigs on the loose, flooded culverts and perhaps even a flying flapjack. But if you’re hoping to find out the precise location of Ambridge, unfortunately you’ll be disappointed: the map is actually centred around Chipping Sodbury, far from the village’s supposed Midlands locale.
Image: Martin Pettitt (CC by/2.0)
This month, FixMyStreet.com sent one more report off to a council. There was nothing to distinguish it from all the other reports of fly-tipping, potholes and graffiti… except that it was the one millionth to be sent since the site began.
Back in 2007, when mySociety first launched FixMyStreet, we had a feeling it’d be useful — but we couldn’t have foreseen the take-up it’s had not only here in the UK, but across the world and in many forms. One million seems like a real milestone, so in celebration, here’s a whistle-stop tour of FixMyStreet’s life so far.
First through the doors
The first report ever sent to a council through FixMyStreet was this one, concerning a broken streetlight.
It was created by a mySociety staff member during beta testing of the site, and sent off to Oxford City Council — who fixed the streetlight. Proof of concept, and we were off.
Once it was clear that everything was working smoothly, FixMyStreet had its official launch that March.
Those who know and love FixMyStreet may be surprised to hear that in this first incarnation, it was given the slightly less snappy title of Neighbourhood Fix-It.
Some might suggest that names have never been mySociety’s strong point. Personally I think we got much better at that later.
Just a week after launch, users had already filed over 1,000 reports — a sign that there really was a need for this site.
The reasons for its popularity? After all, all councils these days provide a fault-reporting system themselves, so why the enthusiastic take-up of a site that duplicates this functionality? We think the reasons are twofold:
- You don’t have to worry about which council is responsible for an issue: FixMyStreet just automatically sends it off to the right one. There are lots of reasons why you may not know where to send a street report, not least the UK’s two-tiered system of local authorities.
- We make the reporting process as simple as possible. It’s that whole ‘swans looking graceful but paddling like crazy under the waterline’ thing: we put in an awful amount of work to make sure that you don’t even notice the issues FixMyStreet has to deal with to make the user experience super-smooth. Back in 2012 we blogged about some of the thinking behind the site; for example here’s why FixMyStreet begins by asking just one simple question.
By June we’d realised that Neighbourhood Fix-It wasn’t the snappiest of names, and thus was born FixMyStreet as we know and love it.
In June 2008, Apple launched their app store.
Our developers saw the future, it seems: by December that year, we’d launched a FixMyStreet app (NB, the links in that 2008 post don’t work any more: if you’d like current versions of the app, you’ll find them here for Apple and here for Android).
The FixMyStreet apps have been downloaded more than 40,000 times, and we’re seeing a real growth in those who use it to make their reports: in the last year it accounted for 27% of reports. This reflects a general increase in the use of mobile (you can also use your mobile’s browser to access www.fixmystreet.com) — 55% of our visitors came via a phone or tablet in the last year.
Open for re-use
Like most mySociety software, the code that FixMyStreet runs on is Open Source: that means that anyone can pick it up for free, and run their own site on it.
In March 2011, a group of coders in Norway were the very first to do this, with their version FiksGataMi (it means FixMyStreet in Norwegian. They could have gone for Nabolaget Fikser Det, which means Neighbourhood Fix-It, but, well, you know…).
Since then, we’ve made real efforts to make the code easier for others to deploy, and ensured that the improvements we add to our own FixMyStreet are also available for all the others: just recently we rolled out version 2.1 of the codebase.
Taking a peek to see what’s being reported around the world is one of our favourite, if non-standard, means of armchair travelling.
A Norwegian puddle-prone footbridge gets in the way of christenings, confirmations and school meetings; meanwhile in Spanish city Alcalá de Henares, a resident complains about the smell created by rubbish lorries while allowing us a splendid view across the rooftops; and in Malaysia, a pack of stray dogs is causing problems for one reporter.
We’d wanted to provide a reporting system that bettered those offered by local councils: in June 2012 that goal was seemingly affirmed when some councils purchased the system to place on their own websites.
We officially launched FixMyStreet for Councils, with Bromley and Barnet being the very first local authorities to implement it. Since then, we’ve been in a continual process of improvement, driven by input and collaboration with many councils around the country. Several more have become clients, too. We’ll have more news on the latest developments soon (and meanwhile, if you are from a council, you can learn more here).
One of the nicest things about a codebase like FixMyStreet is that it can be deployed in many — sometimes surprising — ways. If you’ve followed our blog over the years, you’ll have seen the Channel 4 collaboration Empty Homes Spotter; the bicycle incident-reporting platform Collideoscope; and a project fighting corruption in Malaysia.
Bringing out the poetry in potholes
There’s something about FixMyStreet that inspires some users to exercise their powers of descriptive prose: we celebrated many of them in this 2014 post.
Then there are the reports which attract comments from other users. Lots of them, year in, year out. This one about seagulls in Brighton, for example, has become a one-stop forum for people all around the country to come together in their mutual despair of and/or love for our coastal avian friends.
Ever more reports
You can track the progress as we head towards the next million reports on our new stats page; where you might also be interested to see which councils are currently responding to issues most quickly, and what categories of problem are most-reported at any given time.
As you can see, at the moment the site is handling around 4,000 reports a week: but you can expect that to rise when the weather gets colder — we always get a lot more pothole reports in the winter.
And, are you wondering just what that millionth report was about? Nothing is ever simple: because some reports are made and then subsequently deleted at the user’s request, or because they contravene FixMyStreet’s house rules, we can’t just identify report number 1000000 as the millionth. Those deleted reports retain their original numbers, even though they’re not live.
But doing a quick bit of calculation, we suspect that the rightful millionth report might be this utterly unremarkable one in Knowsley. Long live the unsensational reports that simply get things fixed.
Your donations keep our sites running.Donate now
Image: Alison Benbow (CC by/2.0)
We are happy to confirm that FixMyStreet Professional (the service formerly known as FixMyStreet for Councils) has been accepted onto the GCloud9 procurement framework.
Why is this important?
Using GCloud9, which is overseen by the Crown Commercial Service, removes much of the admin burden from public sector teams who are seeking to procure cloud based software and makes it easier to get down to the question of who has the best product for their needs.
What is FixMyStreet Pro?
FixMyStreet Pro represents the outcome of our co-design project with Oxfordshire County Council to take our popular FixMyStreet platform and build in a new set of features that genuinely made it as useful as possible for their staff (and Council staff all over the UK).
With a focus on retaining the user focused design and approach FixMyStreet was known for we have added or improved functionality for Council customer service staff and introduced a whole new set of tools to support Council inspectors including the ability to manage their tasks from within the app and to work offline when out and about.
This project has also made some improvements to the wider user experience for citizens with new front-end features being added all the time based on user research and feedback.
Want to learn more?
You can find out more about the service over on the GCloud Digital Marketplace or check out our own product pages where you can also get in touch with us if you would like to see a demonstration of the service or learn more about how we might be able to help.
You might already be enjoying one of the usability improvements that FixMyStreet version 2.0 has brought, though it’s possible that you haven’t given it much thought.
In these days of eBay and department store shopping, we’re all quite used to refining results through the use of multiple checkboxes.
But for FixMyStreet, we hadn’t given much thought to letting you filter reports by more than one dimension, until Oxfordshire County Council suggested that it would be a useful feature.
For quite some time, you’d been able to filter by category and status (“Show me all pothole reports” or “Show me all ‘unfixed’ reports”), but this new functionality is more flexible.
You can now select multiple categories and multiple statuses simultaneously (“show me all pothole and graffiti reports that are unfixed or in progress”) — and all through the power of tickboxes.
If you’re a non-technical person, that’s all you need to know: just enjoy the additional flexibility next time you visit FixMyStreet. But if you are a coder, you might like to read more about how we achieved this feature: for you, Matthew has written about it over on the FixMyStreet Platform blog.
I’m just a few weeks into my position of Research Associate at mySociety and one of the things I’m really enjoying is the really, really interesting datasets I get to play with.
Take FixMyStreet, the site that allows you to report street issues anywhere in the UK. Councils themselves will only hold data for the issues reported within their own boundaries, but FixMyStreet covers all local authorities, so we’ve ended up with probably the most comprehensive database in the country. We have 20,000 reports about dog poop alone.
Now if you’re me, what to do with all that data? Obviously, you’d want to do something with the dog poop data. But you’d try something a bit more worthy first: that way people won’t ask too many questions about your fascination there. Misdirection.
How does it compare?
So, starting with worthy uses for that massive pile of data, I’ve tried to see how the number of reports in an area compares against other statistics we know about the UK. Grouping reports into ONS-defined areas of around 1,500 people, we can match the number of reports within an area each year against other datasets.
To start with I’m just looking at English data (Scotland, Wales and Northern Ireland have slightly different sets of official statistics that can’t be combined) for the years 2011-2015. I used population density information, how many companies registered in the area, if there’s a railway station, OFCOM stats on broadband and mobile-internet speeds, and components from the indices of multiple deprivation (various measures of how ‘deprived’ an area is, such as poor health, poor education prospects, poor air quality, etc) to try and build a model that predicts how many reports an area will get.
The good news: statistically we can definitely say that some of those things have an effect! Some measures of deprivation make reports go up, others make it go down. Broadband and mobile access makes them go up! Population density and health deprivation makes them go down.
The bad news: my model only explains 10% of the actual reports we received, and most of this isn’t explained by the social factors above but aspects of the platform itself. Just telling the model that the platform has got more successful over time, which councils use FixMyStreet for Councils for their official reporting platform (and so gather more reports) and where our most active users are (who submit a disproportionate amount of the total reports) accounts for 7-8% of what the model explains.
What that means is that most reasons people are and aren’t making reports is unexplained by those factors. So for the moment this model is useful for building a theory, but is far from a comprehensive account of why people report problems.
Here’s my rough model for understanding what drives areas to submit a significantly higher number of reports to FixMyStreet:
- An area must have a problem
Measures of deprivation like the ‘wider barriers to housing deprivation’ metric (this includes indicators on overcrowding and homelessness) as well as crime are associated with an increase in the number of reports. The more problems there are, the more likely a report is — so deprivation indicators we’d imagine would go alongside other problems are a good proxy for this.
- A citizen must be willing or able to report the problem
Areas with worse levels of health deprivation and adult skills deprivation are correlated with lower levels of reports. These indicators might suggest citizens less able to engage with official structures, hence fewer reports in these areas.
People also need to be aware of a problem. The number of companies in an area, or the presence of a railway station both increase the number of reports. I use these as a proxy for foot-traffic – where more people might encounter a problem and report it.
Population density is correlated with decreased reports which might suggest a “someone else’s problem” effect – a slightly decreased willingness to report in built-up areas where you think someone else might well make a report.
- A citizen must be able to use the website
As an online platform, FixMyStreet requires people to have access to the website before they can make a report. The less friction in this experience makes it more likely a report will be made.
This is consistent with the fact that an increased number of slow and fast home broadband connections (and fast more than slow ones) increases reports. This is also consistent with the fact that increased 3G signal in premises is correlated with increased requests.
Reporting problems on mobile will sometimes be easier than turning on the computer, and we’d expect areas where people more habitually use mobiles for internet access to have a higher number of reports than broadband access alone would suggest. If it’s slightly easier, we’d expect slightly more – which is what this weak correlation suggests.
Not all variables my model includes are significant or fit neatly into this model. These are likely working as proxy indicators for currently unaccounted for, but related factors.
I struggle, for instance, to come up with a good theory why measures of education deprivation for young people are associated with an increase in reports. I looked to see if there was a connection between an area having a school and having more reports on the basis of foot-traffic and parents feeling protective over an area – but I didn’t find an effect for schools like I did for registered companies.
So at the moment, these results are a mix of “a-hah, that makes sense” and “hmm, that doesn’t”. But given that we started with a dataset of people reporting dog poop, that’s not a terrible ratio at this point. Expanding the analysis into Scotland and Wales, analysing larger areas, or focusing on specific categories of reports might produce models that explain a bit more about what’s going on when people report what’s going wrong.
I’ll let you know how that goes.
This year, Bristol Council did something unusual and admirable. As far as we’re aware, they’re the first UK council to have taken such a step.
Working with mySociety on custom Open311 ‘middleware’ while adopting FixMyStreet as their fault-reporting system, they now enjoy full flexibility, no matter what the future holds.
Thanks to this open approach, Bristol will extract more value from their existing systems and lower operating costs. With integrated, open solutions, and the raised quality of report formatting that Open311 brings, everyone will benefit.
Councils are increasingly understanding the value of flexibility when it comes to service providers.
Contracts that lock them into a single provider for many years mean that, often, there’s no opportunity to benefit when technology advances, and disproportionate costs can be charged for implementing the slightest changes.
This desire for flexibility was a strong factor in Bristol City Council’s decision to adopt FixMyStreet for Councils — and that opened the door for a conversation about Open311.
We’ve always advocated integration via Open311, to the extent that we offer free hook-up with FixMyStreet to any councils who support it.
Because Open311 is an open standard, it supports the entire landscape of providers like FixMyStreet. Right now, Bristol can accept street fault reports not just from us, but from a full range of services — in other words, any site or app that cares to connect with them can do so. No-one knows what the future will hold: if a game-changing system emerges in the future, it makes sense that you’d be able to accept its reports.
All well and good: but when Bristol City Council implemented FixMyStreet as their fault-reporting system, the concept was taken a little bit further. With our collaboration, Bristol created their own Open311 ‘middleware’, sitting between the two systems and talking to both.
Via this method, their existing CMS, Confirm, can hook up to reports coming through from FixMyStreet. That all works smoothly — but, just as importantly, if Bristol ever decide to replace their CRM provider, they’ll be able to do so with no knock-on effect to FixMyStreet reports. And if they ever decide to replace FixMyStreet with a different provider, or indeed to accept reports from a range of providers, they can do that too.
Bristol found us via the GCloud procurement system, and are the first metropolitan unitary authority to install FixMyStreet.
Bristol launched its FixMyStreet service to the public in the summer of 2016.
This autumn, they added asset-based reporting, meaning that known council properties such as streetlights, grit bins and gullies are all marked on FixMyStreet’s maps. Residents can pinpoint and report the location of faults with these assets far more accurately as a result.
There’ll be a phased rollout across departments, starting with Highways and moving across departments as Bristol extend their own middleware. We’ll be watching with great interest.
Find out more about FixMyStreet for Councils.
Image: Adam Heath (CC by-sa/2.0)