November was another busy month for our Climate programme, with progress on a number of fronts – from the return of an old friend, in the shape of the Council Climate Scorecards; to the development of two new ones, as a result of our prototyping process earlier this year. We’ve also been working hard to share our data and tools with new audiences. Here’s a quick round up:
Constituency data for climate campaigners
As Alexander mentioned in October, we’ve been working on a Beta version of platform that brings together data about MPs, constituencies, and local climate action, as part of a project with The Climate Coalition. The aim is to help campaigners at both national and local levels to understand where to focus their efforts on enabling real local action on climate goals.
This month—thanks to the involvement of not only Struan and Alexander but also Graeme, on loan from our Transparency programme—we’ve made lots of progress, adding the features and importing the datasets we’ll need for testing out the minimum viable product with target users in the New Year. I look forward to sharing more with you in the coming months!
Exposing high-emissions local authority contracts
Another service that’s come out of one of our earlier prototyping weeks is ‘Contract Countdown’, which aims to give citizens advance notice of large, high-emissions local authority contracts that might be expiring in six, 12, or more months.
This November, Alexander finished developing the final pieces of a working Alpha version – including the use of real contracts from UK Contracts Finder and the Find A Tender service, and pulling in the details of local authority climate officers and councillors with climate/environment responsibilities (so we could test the idea of helping users contact these representatives).
And Siôn and I have been testing the alpha with target users – including local and national journalists, local authority climate officers and procurement officers, and local climate activists. We aim to continue getting feedback on the Alpha throughout December, and maybe January, after which point we can make a decision on whether to develop and launch a full service later in 2023.
Climate Action Scorecards 2023
Speaking of next year, preparations are already underway for next year’s follow-up to the Council Climate Scorecards project—this month saw Lucas and I work with Climate Emergency UK to design and publish their draft methodology for the assessment that will begin next year.
With CEUK’s assessors now looking at councils’ climate actions, in addition to their plans, we wanted to make it as easy as possible to understand precisely which questions your local authority will be scored on. I think we came up with a nice solution, where you can filter the list of draft questions by your local authority name or postcode, as well as by local authority type.
Sharing our data and tools
In other news, Alex updated our deprivation and urban/rural classification datasets to show relative figures for local authorities and Westminster parliamentary constituencies. We also published a local authorities lookup dataset that makes it easy to convert between the many names and codes used to identify local authorities.
If you want to use these new datasets—or any of our data in fact—Alex runs drop-in office hours on Thursdays and Fridays to talk about just that. We’re also happy to help collect or analyse climate-related data for free, as part of our work on supporting the UK’s climate data ecosystem – you can read more about that here.
Speaking of data ecosystems, you’ll now find a number of mySociety’s open climate datasets listed in Subak’s Data Catalogue, and Icebreaker One’s OpenNetZero catalogue.
Finally, Myf and Siôn in particular have continued to share and talk about our tools, and how people are using them to support local climate action, this month. Highlights include attending the Natural History Consortium’s Communicate conference; giving a hands-on workshop about all of mySociety’s tools for London’s small charities and community groups at Superhighways’ “Where’s The Power In Data” conference; and publishing a really exciting case study about how an officer at Surrey County Council used CAPE to share experiences and best practices with other similar councils elsewhere the UK.
Last week saw the first TICTeC Civic Tech Surgery, a new format for us and a hands-on approach to fixing some of the pervasive problems in civic tech.
The TICTeC Labs programme goes like this: we gather experts together to lead a discussion on the challenges, potential solutions and ideas within one topic area affecting the civic tech community. If interested, participants can apply to take suggested ideas forward in a smaller working group, building solutions with the aid of a grant to support their work.
Our first Surgery saw four experts tackling the problems that occur when NGOs and non-profits take on work within governments and public authorities, something mySociety is well acquainted with thanks to our activity — now all under the banner of SocietyWorks — selling Software as a Service.
Adding their ideas and experience to the conversation were Aline Muylaert of CitizenLab; Amanda Clarke, Associate Professor at Carleton University; Gabriella Razzano of OpenUp in South Africa and Ebtihaj Khan from Code for Pakistan.
Notes from the meeting can be seen here, as well as the full recording of the session here, but we’ll summarise the main points here.
Procurement in government It can be hard for small organisations to compete against the big players, especially because bidding for a piece of work often involves jumping through many bureaucratic hoops.
The structure of governments Set ways of doing things can often be incompatible with the Agile approach that is most favoured by civic technologists. Also, if you are affecting how one department of government works, ideally the benefits would ripple out across all other departments, but the siloed nature of government departments often prevents this.
The short-term nature of governments When building anything, of course you want it to have a lasting effect; but elections and changes in political control often mean that a project is thrown out when a new regime takes over.
The world view of governments An added task comes in educating governments about the motivations of civic technologists, and the value of putting citizens at the centre of work. They also need to know about the benefits of keeping projects running longterm.
The knowledge within governments As government staff often don’t have detailed technical skills themselves, the door is open for big players to demand high dollar contracts that lock clients into a single vendor.
Shaking up procurement One solution that can be effective is in ‘micro contracting’ – breaking a large requirement into several smaller pieces of work, thus allowing smaller organisations to bid for them. Mandates that procurement should be for open source development would also be beneficial.
Clever contracts Civic tech providers can add clauses to their contracts which mean that time is dedicated for user-centred research, for example, or make clear that Agile methods will be used. Adding goals around impact is one way to try to ensure that the real reason for the development isn’t forgotten. Once contracts have been drawn up, the templates could be shared for other governments or civic technologists to use.
Nurturing government staff If they are around long enough for relationships to be built, staff can be inducted into healthy civic tech approaches; for example they can be included in bootcamp sessions.
Writing case studies It’s really useful to be able to share concrete examples of where civic tech interventions have resulted in tangible improvements, and government clients can find these very motivating and exciting. At the same time we could look to write some case studies with examples of where the problems we’ve identified were solved, eg by introducing Agile methods into the work, as a persuader.
Research We can learn a lot of research conducted 40-50 years ago, when many of the issues with public/private contracting, a new idea back then, were the same as they are now. We also need new qualitative data from the people working on data projects: if we can uncover corruption (which we know is an issue in places across the world) it will cause an uproar.
Some of this discussion also took place on Padlet and you can see more ideas there.
We are now inviting people to join the working group (aka Action Lab), which will comprise up to 6 people who are keen to further develop solutions together, for the benefit of the wider civic tech community.
To keep an eye on this progress, and to know more about the next Surgery, see the TICTeC website or sign up for email updates.
GCloud 11 is live: it’s the latest iteration of GOV.UK’s Digital Marketplace, making it easier for those in the public sector to find and procure cloud-based software services — including ours.
This time around there are two offerings from mySociety: FixMyStreet Pro, which has been on GCloud since 2017, and FOI for Councils, available via this channel for the first time.
Regular followers will be well aware that FixMyStreet Pro is a street fault reporting service which can integrate with any existing council system, offering great opportunities to cut costs and increase efficiency.
Meanwhile our FOI for Councils service streamlines authorities’ FOI workflows and reduces unnecessary requests, relieving the burden in what is often an overstretched resource.
The great benefit of GCloud from the public sector point of view is that suppliers come ready-verified, saving the time and inconvenience of going through the regular procurement process. All the information you need about the service is readily accessible, and then when you’ve made your decision it’s very simple to get things moving.
We’re pleased to offer these two services via GCloud — and will be equally happy to answer any questions you may have.
Local government has a need for all kinds of services, from taxis to stationery. And to ensure that they get the best deals, they acquire them through a procurement process—one that, as suppliers of software to councils, we’ve become very familiar with ourselves.
It’s quite simple: every category of goods or services has its own ID number. You identify the ones that are closest to what you provide—so in our case, it might be software development, software consultancy, and the provision of software packages.
Then you sign up to receive notifications every time a council puts out a request for tenders that fall within one of those categories.
Our newest team member, Camilla, has been spending a lot of time signing up for these notifications across all the various platforms in the UK (buy her a drink if you see her: procurement websites might just be amongst the most infuriating and clunky known to man), and as a result, she’s noticed that as well as all the categories you’d expect, there are also plenty more that you wouldn’t.
For example, who knew that councils had such a regular need for
15112310 Foie gras
98331000 Turkish bath services
16710000 Pedestrian-controlled agricultural tractors
35321100 Hand guns
and as if that’s not enough…
35321300 Machine guns
There are plenty more categories that might make you go ‘hmm’ – take a look for yourself.
Oh, and here’s a thought – if you’d like to ask your own local council what their expenditure is on nightwear, foie gras or machine guns, you can do so very easily at our own WhatDoTheyKnow.com.
Image: Dynamosquito (CC)