One Task, Four Vendors: The Quiet Absurdity of UK Council Portals

You want rid of a sofa. That's the whole brief. One sofa, one collection, one payment.

Forty minutes later you've made an account you'll never use again, typed your postcode five times, been redirected to a payment page that looks like it was designed during the Blair administration, and received a confirmation email from a domain you don't recognise. The sofa is still in the hallway. You are now, unofficially, an expert in your council's procurement history.

This is the everyday texture of local government digital in Britain, and it deserves more scrutiny than it gets. Not because councils are lazy — most of the people running this stuff are doing heroics on a budget that would make a startup founder weep — but because we've collectively decided that fragmentation is just how local services work. It isn't. It's a design choice, repeated a few hundred times.

The front door that never got built

Westminster has spent a decade building a genuinely decent national front door. GOV.UK is one of the better pieces of public-sector web design on the planet: plain language, one visual language, no nonsense. GOV.UK One Login is slowly pushing that logic into identity.

Then you cross the threshold into local services and the spell breaks.

Council tax lives in one system. missed bin reports in another. Blue badge applications in a third. School admissions in a fourth. Garden waste permits, parking permits, library memberships, planning consultations, housing repairs, licensing, registrar bookings — each one a separate island, often with a separate vendor, frequently with a separate login, and almost always with a separate idea of how an address should be written.

Some councils have stitched a facade over this. You'll see a homepage that promises 'Do it online' with a cheery grid of tiles. Click the third tile and you're on a Granicus form. Click the fifth and you're in a Civica portal with a session timeout of ninety seconds. Click the seventh and you're staring at an embedded PDF.

Anatomy of a fourteen-login morning

Here's a realistic run at it, from the perspective of someone moving into a new flat.

Register for council tax: one account. Set up a direct debit: possibly the same account, possibly a payment vendor's checkout that forgets you existed the moment you close the tab. Request a recycling bin: different form, no account, but it does want your council tax reference, which you have written on a scrap of paper somewhere. Book a bulky waste slot: third-party booking widget, new login, and a payment page branded for a company you've never heard of. Apply for a residents' parking permit: fourth portal, and this one wants a scan of your V5C. Join the library: fifth, but at least it's free. Report a pothole: FixMyStreet or a council-branded clone of it, and honestly, this one is fine.

Five different visual languages for one household. Five different mental models of what a 'reference number' is. Five different password requirements, at least two of which will silently reject a symbol you've used everywhere else since 2019.

And here's the bit that stings: none of these systems are broken individually. Each one probably passed its acceptance testing. The failure is compositional. The council has fourteen working products and no product.

Why it happens, and why 'procurement' is only half the answer

The lazy explanation is procurement chaos — and yes, that's real. Local government buys software in departmental silos, on five-year cycles, from a small pool of vendors who have every commercial incentive to keep their walled gardens walled. Replacing a revenues and benefits system is a multi-year, multi-million-pound undertaking that no one wants to start twice.

But the deeper issue is that nobody owns the seam. There's a team that owns council tax software. There's a team that owns the website. There's a comms person who owns the tone of voice. There is, in most authorities, no one whose job title is 'the experience of a resident trying to do a thing'.

That's the gap. Not technology — ownership.

The visual language problem is worse than the login problem

Logins annoy people. Inconsistent language actually confuses them.

One form says 'postcode', another says 'postal code', a third asks for your 'full address including house name if applicable' in a free-text box that then fails to validate. One portal says 'submit', another says 'continue', a third says 'proceed to payment'. One calls it 'bulky waste', another 'bulky item collection', a third 'special collection'. Same service, three names, three mental models.

For anyone who's confident online this is merely irritating. For the third of the country who aren't — and they are disproportionately the people councils exist to help — it's a wall. Every new visual language is a fresh chance to give up.

What good actually looks like, and it's boring

The encouraging news is that the fixes are unglamorous and cheap relative to the systems they sit in front of.

A single resident account that is genuinely optional and genuinely reusable. A shared address lookup — one canonical source, one format, used everywhere. A house style for service names that survives departmental reorganisations. And a hard rule that any new vendor must expose a clean form endpoint rather than force its own skin.

Several councils are quietly doing this. Shared service platforms, cross-authority digital teams, and the steady spread of One Login into local services all point the same way. It's not a moonshot. It's plumbing.

The brief, if anyone's taking notes

Stop thinking of your council website as a directory of departments. Think of it as the one place where a resident's intent — 'I need this gone', 'I've moved', 'my bin didn't come' — gets routed without them having to learn your org chart.

Fourteen vendors can live behind one front door. They just need someone standing at it.