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.

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.

Get involved

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 hello@mysociety.org.

—

Image: Sarah Palmer-Edwards

To help us mark WhatDoTheyKnow’s tenth anniversary, we asked volunteers, supporters and users to tell us which Freedom of Information requests from the site’s first ten years particularly stuck in their minds.

The result was an eclectic mix of stories that really show the breadth of how WhatDoTheyKnow has been used. They have very little in common — unless you count the imagination and tenacity of those using FOI to try to uncover significant information.

Doug Paulley, WhatDoTheyKnow volunteer

A exposé that helped bring in the living wage for carers

Doug is one of the team of volunteers who give up their time to keep WhatDoTheyKnow running, using their experience and knowledge of FOI to moderate the site, give users guidance, and help set policy. Doug is also an extremely active user of FOI, having used the act to uncover many examples of discrimination and malpractice over the years.

He highlights the story of a care home talking the talk, but very much failing to walk the walk when it came to paying its staff the living wage.

“The exposure brought about by FOI played a significant part in the campaign for Leonard Cheshire, care home operator with 2,100 residents, to significantly increase carers’ wages to (just short of) the voluntary living wage. Journalist Heather Mills covered the story in Private Eye.” Read the whole story here.

Owen Blacker, mySociety trustee

Missing historic information on Cold War targets

Owen co-founded FaxYourMP, the earliest version of mySociety’s  WriteToThem, and has been an important part of the organisation ever since — he’s now one of our trustees and a non-executive director. He recalls the building and launch of WhatDoTheyKnow and indeed was one of its earliest registered users.

Owen particularly remembers a pass-the-parcel like series of FOI requests in which he was handed from one organisation to another:

“I went round in circles trying to find out some Cold War information that nobody claims to know any more. In 1980, the entire Civil Service, nationwide, ran a dry run of a Cold War nuclear attack on the United Kingdom, called Operation Square Leg. I’m slightly concerned that we spent a lot of money planning the civil contingencies of a Cold War attack — a sensible things to do, arguably — but no longer know where we were expecting to be hit or at what megatonnage.” Owen links to the requests from this blog post.

Will Perrin, Indigo Trust

Safer streets and better data handling

Will is not only a trustee at Indigo, supporting mySociety’s work with parliamentary monitoring organisations in sub-Saharan Africa, but he’s also a trustee of London’s King’s Cross Community Projects. Indeed Kings Cross — a locality in which Will has a personal stake, with a long record of community action — is the subject of two of the three FOI requests he singled out:

First was the Kings Cross Walkability audit which revealed just how hostile to pedestrians the area was back in 2008. At the time, Will wrote in his blog: “Crossing the road in Kings Cross is a nightmare and now we have an official report commissioned by TfL that sets it out in black and white.”

Today he recalls its impact: “This document underpinned the police taking a corporate manslaughter case against TfL to the Criminal Prosecution Service with regard to a cyclist’s death in 2011. The case did not proceed but was instrumental in changing TfL’s attitude to cyclists’ rights.

“Then this request revealed a massive overspend by Network Rail in refurbishing its own offices at Kings Cross”.

Finally, Will’s third choice of request had wider implications for the country as a whole:

“The National Police Chiefs’ Council revealing that there was no governance system in place for the Automatic Numberplate Recognition System (ANPR) and the existence of Met’s ‘Olympic Data Feed‘ led to a new governance system being instilled; some 2 billion records were deleted along with the introduction of a vastly reduced retention period.” Annotations at the foot of this request give a little more background.

Matthew Somerville, mySociety developer

A long-standing pillar of mySociety’s development team, Matthew wrote the core code behind many of mySociety’s most notable websites and tools, including FixMyStreet and TheyWorkForYou. He spends his working days coding for mySociety’s useful tools, and much of his free time coding his own useful tools, if his website is anything to go by. What was his most memorable FOI request?

“It was a request asking Royal Mail for information about all their postboxes, made by Tom Taylor.  I had to write a crowd-sourcing tool to locate them, as the information provided included street name but no actual location; they then (from another FOI request a few years later) released the co-ordinates as well.”

The data is mapped here. Why is this request significant?

“I’m not sure it’s really significant, but I do get plenty of people telling me they’ve used the site, and it’s something Royal Mail never got around to providing (even though that was their reasoning for refusing to release it)…”

—

So there we are: a handful of the 458,219 requests that WhatDoTheyKnow has processed to date. There are so many stories around FOI requests: each of them represents someone’s burning question; many of them result in a response that’s important, or fascinating, or historic. And that’s what makes WhatDoTheyKnow so rewarding to work on.

We’ve talked a lot about our new service for journalists and other professional users of Freedom of Information — but it’s not always the professionals who uncover the news stories.

This week, we mark WhatDoTheyKnow’s tenth anniversary. As part of the celebrations, we thought we’d look back on the news stories that came about because of requests made through the site. Many of these began with an FOI request submitted by a user with no links to the press, and were picked up by news outlets because the response was of public interest.

From the restrictions on what names can be given to a baby in this country, to an accidental torpedo release, and via a geographically-accurate Tube map, it makes for fascinating reading. You can see them all here.

On 22 February 2008, we posted an announcement on this very blog: “the new mySociety Freedom of Information site is now live”.

More than 450,000 requests later, WhatDoTheyKnow is marking its tenth anniversary: as part of the celebrations, we’ve put together a timeline showing how WhatDoTheyKnow has intersected with the history of FOI in the UK since we first gained our right to information in 2005. If nothing else, you may enjoy looking at the site’s rather more primitive design back in its early days.

The past decade has seen legal challenges, contributions to Parliamentary inquiries, and the development of our code for use in other countries (26 and counting). It has proved that an ambitious project can be kept going thanks to the efforts of unpaid but skilled and dedicated volunteers.

Most of all, though, it’s seen you, the general public, submitting requests for information, and sharing the responses you receive. That was always the idea, and, it turns out, it’s a pretty sound one.

An article in the current Private Eye Magazine has drawn our attention to the use that disability campaigner John Slater is making of our Freedom of Information service WhatDoTheyKnow.com.

In December 2016, Mr Slater asked the Department for Work and Pensions (DWP) to release the monthly “management information reports” received from contractors ATOS and Capita in relation to their work assessing eligibility for Personal Independence Payment benefits.

Mr Slater has pursued his request for over a year, and wasn’t put off by an initial response which stated that the information requested wasn’t held, nor a subsequent response refusing to release the material citing the contractors’ “commercial interests”.

In December 2017, a year after Mr Slater made his request, the Information Commissioner ordered the DWP to release the material, stating “The Commissioner has not been satisfied that disclosing the withheld information would be likely to damage the commercial standing of ATOS and Capita”. The Information Commissioner dismissed the DWP’s concerns that the information requested could be “misinterpreted in ways that could lead to reputational damage to both the Department and the PIP Providers as well as prejudice the efficient conduct of public affairs”.

The Information Commissioner’s decision notice was highly critical of the way the DWP had handled the case, noting the use of “standard paragraphs” rather than a discussion of the public interest tailored to the material in question, and DWP failing to engage promptly with the Information Commissioner, thus causing further delay.

The DWP have not yet complied with the Information Commissioner’s decision; they have appealed and a tribunal hearing is scheduled for April 2018.

This request is far from the only one showing Mr Slater’s persistence in pursuing the release of information held by the Department for Work and Pensions.

A request for Project Assessment Review Reports for the Universal Credit Programme that Mr Slater made in April 2016 was initially accepted and the department said they were considering it. Mr Slater chased up the lack of a response in June, and again in August and September, but when, six months after his original request, Mr Slater chased them again in October they deemed his persistence to be vexatious and rejected the request.

That request has now been further rejected by the DWP, who say that the information “if released would, or would be likely to, prejudice the free and frank provision of advice or which would otherwise, or would be likely otherwise to, prejudice the effective conduct of public affairs.”

Mr Slater has referred that decision to the Information Commissioner too.

On the 5th of December 2017, Debbie Abrahams MP, the Shadow Secretary of State for Work and Pensions, deployed the Parliamentary procedure of a motion for “an humble Address be presented to Her Majesty” to seek the release of the documents to the Work and Pensions Committee. MPs agreed the motion unanimously.

The committee are currently in correspondence with the Government over redaction, and arrangements for access to the material.

The committee chair, Frank Field MP, has suggested that:

A couple of copies would be made. These copies will be kept securely and members would be invited to come to the Committee office to read them. No-one else, other than the committee members, will be invited to make this journey to our Committee office and members will not be able to make copies, or take notes, about the documents.

– so despite the decision by the House of Commons the public still might not get to see the material via that route.

Mr Slater has been in touch with us and told us he finds the service provided by WhatDoTheyKnow extremely helpful when submitting and managing FOI requests.

He said that the ease of submitting requests and built in workflow that keeps track of time, reminding users that a response should have been issued, is invaluable. He also likes that a single platform exists where information obtained by its users is made available for everyone, as that embodies the spirit of the Freedom of Information Act.

—
Image: John-Mark Kuznietsov (Unsplash)

If you happen to have visited the WhatDoTheyKnowPro page recently, you might have noticed that we’ve changed from offering free beta testers’ accounts to rolling out the payment interface.

Yes, we’ve launched! But not with a bang: having quietly introduced the payment option, we wanted to wait for a while and check that there were no issues before making a public announcement. Consider this that public announcement.

Just a reminder at this stage, in case you haven’t followed along with previous blog posts: WhatDoTheyKnowPro is a Freedom of Information toolkit which provides extra help with sending and organising requests. It’s designed to provide extra functionality for journalists and other people who use FOI in their jobs; if you’re a standard user of WhatDoTheyKnow, there’s nothing to  pay and there never will be. We’ll always keep the site, and all its current functionality, free for everyone.

The question of price

Launching WhatDoTheyKnowPro provoked an interesting debate on where to position it, pricewise.

It’s not that we’ve never put a price on any of our services before: mySociety is a social enterprise, and we charge for some use of our APIs; our council clients pay us for FixMyStreet Pro; you can buy transit-time maps on Mapumental. These sources of income are just part of what help us to provide our core citizen-facing services for free.

And we’re hardly trailblazers in that respect: in fact, it was fascinating to read the Knight Foundation’s recent report Scaling Civic Tech and see how common it is in our sector to rely on a variety of revenue streams, from user donations to philanthropic grants, to paid-for services.

But while we may have experience in charging for our services, it’s definitely the first time we’ve had to price up a Freedom of Information toolkit for journalists and professionals!

What’s it worth?

We were effectively in the position of many an enterprise startup: with a market proposition that doesn’t exist in this exact form anywhere else. How do you know how to price something in those circumstances? Set it too low and you could miss out on important revenue; too high and you’ll alienate potential customers, many of whom are freelance journalists paying for their work tools out of their own pockets.

Still, this project has been a process of tackling problems and questions thoughtfully — from deciding which features to include in this initial version, to debating how to encourage journalists to link back to the news stories they’ve created once they’re live. Perhaps we could bring the same approach to pricing.

Ask the experts

Fortunately, with over 100 beta testers, we had a pool of users who knew the service well enough to be able to give an expert opinion on how much value it was bringing them. Sending out a survey brought some very useful responses, not to mention feedback about what our beta users liked and what they’d appreciate in future roll-outs.

That said, we’re well aware of research indicating that people are not always experts on what they are actually willing to pay.

And of course, it makes sense that different people will attach different values to a service, depending not only on their own finances but, in this case all sorts of other factors such as how frequently they use FOI and how accustomed they are to paying for technology.

Faced with responses to the survey that ranged between a suggested price of £1.00 a month to £50.00, that was, in some strange sense, reassuring to know.

To be fair, those were the extremes. There was a good consensus in the middle and that helped us decide on an introductory price of £10 a month.  We’ll assess this after a few months to see whether it’s bringing the number of sign-ups we expect.

Open for business

If you’re a journalist or someone who uses FOI in your work, you can now go and give WhatDoTheyKnowPro a go! We hope you’ll let us know how you find it.

—
Image: Sven Scheuermeier (Unsplash)

How many Freedom of Information requests are sent through WhatDoTheyKnow as compared to those made directly to public bodies? Our new mini-site lets you explore Cabinet Office statistics in comparison to numbers from WhatDoTheyKnow.

Every quarter, the Cabinet Office releases Freedom of Information stats for a collection of central government ministries, departments and agencies. This provides a good benchmark for understanding how requests made from WhatDoTheyKnow relate to requests made through other routes. Back in 2010 we ran several blog posts about this, though we haven’t released any comparisons in recent years — and we’re now making up for lost time.

In 2016, WhatDoTheyKnow was the source of 17.14% of requests to audited public bodies. On the other hand, most WhatDoTheyKnow requests (88.51%) went to public bodies that the Cabinet Office figures don’t cover.

One interesting conclusion from this is that most FOI activity in the UK is not immediately visible from the official statistics. You can read more about what we learned from the numbers, or explore the data for yourself on the mini-site.

—
Image: Jerry Kiesewetter (Unsplash)

When you send a Freedom of Information request through WhatDoTheyKnow.com, every part of the exchange is published online. Those who have browsed the site will know that you can read the correspondence around each request from beginning to end, including the initial enquiry, auto-replies, any holding letters, messages seeking clarification, and finally, the response — or refusal.

We built the site so that, when information was released, that information would be available for everyone. The result is the massive online archive, all searchable, that you can find on WhatDoTheyKnow today. That being the case, why do we bother publishing out all the rest of the correspondence? Why not simply publish the end result, that is, the actual information?

Well, we believe there’s value even in what you might consider the ephemera of everything else, not least that it helps demystify the various steps of the FOI process.

This week, an article by ‘FOIMan’ Paul Gibbons showed that the publication of this material can also help with research. He was able to look at 250 ‘refusal notices’ — that is, times when authorities had turned down requests for information — and pull out examples of best and worst practice.

The result will benefit us all, from those requesting information to those who process the requests: for the former, it sets out what to expect from a refusal, and for the latter, it highlights how to ensure that you are sticking to the law as well as ensuring a good experience for the public.

A refusal, as Gibbons points out, does not have to be a shutting of the gates in the face of the requester: it can help educate, point people towards a better means of obtaining the information they need, or even clarify for the FOI officer where withholding the information may in fact be inappropriate. We’re very glad to have seen our data being used in this way.

—
Image: Gemma Evans (Unsplash)

Code for Croatia are one of many groups around the world who have used our software Alaveteli to set up a Freedom of Information site — ImamoPravoZnati (“We have the right to know”) was launched in 2015 and has processed more than 4,000 requests.

Many organisations might count that a success and leave it there, but Code for Croatia are clearly a little more ambitious. We’ve been interested to hear about their two latest projects.

A platform for consumer complaints

The Alaveteli code was written to send FOI requests to public authorities. But in essence, it’s little more than a system for sending emails to a predetermined list of recipients, and publishing the whole thread of correspondence online.

Change that list of recipients, and you can create a whole new type of site. Reklamacije (“Complaints”) puts the process of making consumer complaints online. It’s early days as yet — the site’s still in the beta phase, during which testers are putting it through its paces. There have been messages about bank closures, insurance policies… and even the inconsistent quality of the quesadillas at a Mexican food chain.

As we’ve often mentioned here on this blog, our FixMyStreet codebase has been put to many different purposes that require map-based reporting, but as far as we’re aware this is the first non-FOI use of Alaveteli so we’ll be watching with interest. Perhaps it might give you ideas about setting up a similar service elsewhere?

Probing travel expenses

Code for Croatia have also launched a campaign asking users to request details of ministers’ travel expenses.

If that sounds familiar, you’ll be remembering that back in January, AccessInfo did much the same with EU Commissioners and their expenses on the European Union FOI site AskTheEU. We can tentatively say that they were successful, too: it’s been announced that the EU expenses will be proactively published every two months. AskTheEU say they welcome the move ‘cautiously’, so let’s see how it all pans out.

The key to both these campaigns is pre-filled requests that make it really simple for supporters to make a request to a specific politician, while ensuring that the requests aren’t duplicated.

That’s something that Gemma explained how to do in this blog post — it’s a massive benefit of the friendly global Alaveteli community that we can all share insights like this, and especially that other groups can try out initiatives that have proved successful.

We’ve just listed Sustainability and Transformation Partnerships on our UK Freedom of Information service WhatDoTheyKnow.com. These new bodies bring together NHS organisations and local councils with the aim of better co-ordinating health and care services in England (see NHS England’s webpage introducing them).

In most parts of the country Sustainability and Transformation Partnerships are unimaginatively named. In a few places though the bodies have been more adventurous: we have the bold and strident sounding Success Regime Essex, as well as Together We’re Better in Staffordshire, Transforming Health and Social Care in Kent and Medway, Joined Up Care Derbyshire and one called BOB.

Some of these bodies appear to be just coming into being, with almost nothing about them online at all and others are more established with staff, websites, boards and published meeting minutes. When researching these organisations we found a handful offered Freedom of Information contact addresses, and commendably Kent and Medway’s even has a log of responses it has already made to FOI requests.

Most Sustainability and Transformation Partnerships will be subject to Freedom of Information (FOI) law as all their members are public bodies. Some may not be subject to FOI though, for example Surrey Heartlands Sustainability and Transformation Partnership appears to have private company Virgin Care as a member, exempting it from the relevant definition; we list the body on WhatDoTheyKnow anyway as part of our activism seeking to expand the scope of the law.

What information will a Sustainability and Transformation Partnership hold?

A few partnerships publish their key governance documents (constitutions, terms of reference, memoranda of understanding), and minutes and papers from their boards; these can give an insight into the organisation’s activities and reading them may suggest information which could be made public via a Freedom of Information request. If the basics of board minutes, and governance documents aren’t published you can use WhatDoTheyKnow to get them online and easily for everyone to access.

FOI responses from Kent and Medway show large sums of money being paid to “consultants/external advisory firms” to develop a Sustainability and Transformation Plan and hint at bodies elsewhere doing similar. Freedom of Information requests could be made to partnerships elsewhere to ask for information on their budgets and spending.

The future

It is anticipated that Sustainability and Transformation Partnerships may “evolve” into “Accountable Care Organisations” ACOs, responsible for all public healthcare in a region; this would make them immensely important public bodies.

We’ll keep an eye on the organisational changes and try to keep our service up-to-date.
Maintaining the database of public bodies is a key part of running WhatDoTheyKnow; we have to react to reorganisations in the public sector, and bodies forming, merging, changing their names or ceasing to exist.

NHS Sustainability and Transformation Partnerships on WhatDoTheyKnow

• Alliance Local Delivery System (Warrington, St Helens, Halton, and Knowsley)
• Better Care Together – Leicester, Leicestershire & Rutland
• Birmingham and Solihull Sustainability and Transformation Partnership
• Bristol, North Somerset, South Gloucestershire Sustainability and Transformation Partnership
• Buckinghamshire, Oxfordshire and Berkshire West Sustainability and Transformation Partnership
• Cambridgeshire and Peterborough Sustainability and Transformation Programme
• Cheshire and Wirral Local Delivery System
• Cornwall and the Isles of Scilly Shaping Our Future Transformation Board
• Coventry and Warwickshire Sustainability and Transformation Partnership
• DDT, Hambleton, Richmondshire and Whitby Sustainability and Transformation Partnership
• Devon Sustainability and Transformation Partnership
• Dorset Sustainability and Transformation Partnership
• Frimley Health and Care Sustainability and Transformation Partnership
• Greater Manchester Health and Social Care Partnership
• Hampshire and the Isle of Wight Sustainability and Transformation Partnership
• Healthier Lancashire and South Cumbria
• Herefordshire and Worcestershire Sustainability and Transformation Partnership
• Hertfordshire and West Essex Sustainability and Transformation Partnership
• Humber, Coast and Vale Sustainability and Transformation Partnership
• Joined Up Care Derbyshire
• Lincolnshire Sustainability and Transformation Partnership
• Milton Keynes, Bedfordshire and Luton Sustainability and Transformation Partnership
• Norfolk and Waveney Sustainability and Transformation Partnership
• Northamptonshire Sustainability and Transformation Partnership
• North East London Sustainability and Transformation Partnership
• North London Partners in Health and Care.
• North Mersey Local Delivery System
• Northumberland, Tyne and Wear Sustainability and Transformation Partnership
• North West London Joint Health and Care Transformation Group
• Nottinghamshire Sustainability and Transformation Partnership
• One Gloucestershire Sustainability and Transformation Partnership
• Our Healthier South East London
• Shropshire and Telford and Wrekin Sustainability and Transformation Plan Partnership Board
• Somerset Partnership
• South West London Sustainability and Transformation Partnership
• South Yorkshire and Bassetlaw Sustainability and Transformation Partnership
• Success Regime Essex
• Suffolk and North East Essex Sustainability and Transformation Partnership
• Surrey Heartlands Sustainability and Transformation Partnership
• Sussex and East Surrey Sustainability and Transformation Partnership
• The Black Country Sustainability and Transformation Partnership
• Together We’re Better (Staffordshire)
• Transforming Health and Social Care in Kent and Medway
• West, North and East Cumbria Sustainability and Transformation Partnership
• West Yorkshire and Harrogate Sustainability and Transformation Partnership

__
Image: LydiaShiningBrightly (CC-by/2.0)