153 local authorities, one calm page each

When I planned SENDadvisor, the Local Offer pages were a footnote: one page per local authority, a bit of contact info, a link out. I estimated them at a day each, tops.

They’re now one of the most-used parts of the site. Families spend more time on them than on some of the shiny features I thought would carry the product. The footnote became the headline, and the reason why says something about what "useful" actually means.

What a Local Offer is, and why it’s a mess

Every English local authority is legally required to publish a Local Offer — information about SEND services, support, and provision in their area. It’s a genuinely good idea with a genuinely broken implementation: 153 authorities means 153 different websites, 153 different structures, 153 different navigation schemes, and — in practice — 153 places for a tired parent to get lost.

The information exists. Finding it is the problem.

What the pages do

Each authority’s page on SENDadvisor consolidates, in one place and one consistent layout:

• the Local Offer URL and where it lives on the council’s site — because half the battle is just locating it,
• SEND team contact details, including who actually answers the phone,
• EHCP pathway notes in plain English — what the process is, what happens when, and what the jargon means,
• links to the directory listings for that area — days out, services, and schools, filtered to the authority.

Same structure, every single authority. A parent who has learned the layout for Norfolk can use it for any other county — and for a family moving areas mid-EHCP, that consistency is not a convenience, it’s a lifeline.

Why it worked when the fancy features didn’t

It removes real hours of work. Before this, a family’s research session looked like: Google the council, find the SEND section, decode the navigation, find the Local Offer PDF, find the contact page, start again for the neighbouring county because the specialist service they need is technically over the boundary. The page does that work once, for everyone.

It’s trustworthy without being flashy. Source attribution on every field, last-updated dates, plain-English summaries next to the official terminology. Trust features beat delight features in a stressful context every time — nobody navigating an EHCP rejection wants a delightful UI, they want a correct phone number.

It matched how people actually search. The data showed families weren’t searching "SEND services Norfolk" — they were searching "EHCP help Norfolk", "what is an EHCP", and — most often — the name of their specific council plus "SEND". The page titles and structure meet those searches exactly.

The boring consistency was the innovation. One calm layout, 153 times, beats 153 well-intentioned-but-different council experiences. That’s the whole product insight: consistency across a fragmented landscape is a feature in itself.

The lesson I keep relearning

Features that save a user hours of drudgery beat features that impress other designers. I estimated the Local Offer pages as small because they were technologically small — one template, a data model, some contact fields. But value isn’t proportional to technical difficulty. It’s proportional to the work removed from the user’s life.

Look at your own backlog and find the footnote features — the ones that are cheap for you to build because they’re boring, and expensive for users to live without. That’s usually where the product is hiding.