CASE 02 · AUTHORITY vs ACCOUNTABILITY
Helping deliver a multi-country, publicly funded pilot inside a local authority shows that formal project authority and local accountability are rarely the same thing — and that good governance depends on recognising both.
In a multi-country, publicly funded pilot hosted by a local authority, formal project authority and local accountability were not the same thing.
The situation in brief.
Public sector, energy pilot
Twelve organisations, six countries
Host authority, not coordinator
The setting was a publicly funded European pilot exploring whether otherwise-wasted renewable electricity could be converted into a storable fuel and used for heat, power and transport. Twelve organisations across six countries were involved, of very different kinds: a local authority, a university, technology suppliers, a government ministry and a community trust. The local authority was one partner among the twelve. It was not the coordinator, but a substantial part of what the project was trying to prove was happening inside its own communities.
The project’s formal leadership sat elsewhere, with a coordinating foundation in another country. But the vehicles would run in the host authority’s area, the infrastructure would be installed there, and elected members, accountable to the people who elected them, would eventually have questions about all of it.
That created a distinction that is easy to overlook until it has to be worked with directly: formal authority and local accountability do not automatically point the same way. A consortium can allocate decision rights in one direction while democratic accountability pulls in another. Neither is wrong. But a governance structure that recognises only one of them is heading for trouble.
Part of the work was helping build the processes through which the authority’s own obligations — committee requirements, budget scrutiny, the responsibilities of elected members — sat coherently alongside the project’s consortium structure, work packages and reporting lines. Those two systems do not align simply because everyone has signed the same grant agreement.
Elected members mattered more than an international consortium might naturally assume. A technology unfamiliar to most of the public raises questions that are not purely financial or technical — safety, public assets, environmental policy, the implications for local services.
Committee requirements and budget scrutiny sat alongside consortium structures and reporting lines. They did not align simply because a grant agreement had been signed.
An engineer can demonstrate that something is technically safe. That is a different test from whether an elected representative can explain to constituents why it is happening in their community.
A public body has to weigh commercial delivery against public accountability in a way a technology supplier does not. Each partner thinks about obligation differently.
Budget changes were never simply a spreadsheet exercise. They were conversations between organisations with legitimate, sometimes competing claims, which had to survive long after the meeting ended.
Over time it became clear that the authority’s formal position in the consortium did not fully reflect the weight it was actually carrying — operationally, institutionally and politically. That was not about taking control of a European project or challenging the lead partner’s legitimacy. It was a straightforward governance principle: authority has to be considered alongside accountability.
If one organisation carries a disproportionate share of the consequences of a decision, its voice in that decision cannot be treated as incidental.
The physical outcomes eventually made the project tangible: a refuelling station, local-authority vehicles running on the new fuel, and heat demonstrated at a community school. But the less visible moments are the ones that stay with the work — the committee papers, the briefings for elected members, and the negotiations where an international consortium’s interests and a local authority’s obligations did not naturally fit together.
Good governance in that environment did not mean one organisation dominating the other eleven. It meant designing decision-making so that authority, expertise and public accountability could genuinely coexist.
It also meant recognising that the question an elected member asks, because they answer to someone the project manager does not, is often the one a sophisticated consortium would never think to ask.
Leadership teams reading this case study often continue exploring related business challenges, industries and executive perspectives.
Every organisation operates within its own commercial environment, leadership structure and growth journey. These case studies describe patterns rather than templates. Services can be delivered remotely, and we accept requests from organisations wherever they are located.
