How it's made

Where the needs in the library come from

We don't guess what residents need. We start with what councils already publish, and test every need before it goes in.

  1. We read council websites

    We read 141,675 pages from 136 council websites, of every type and size.

  2. We find the tasks

    We pick out the 24,554 pages where a resident does something: pay, apply, book, report or find out.

  3. We group the same task together

    Councils describe the same task in different ways. We group them, so each task is counted once. That gives 7,299 topics.

  4. We put the most common first

    Tasks that most councils offer, and that most people search for, are written first.

  5. We write the need

    AI writes a first draft: what the resident needs to do, why it matters, and what a good page does. It works from the council pages we read.

  6. We test it on real websites

    We try each new need on three council websites. If at least two can pass, the need is fair and clear.

  7. David checks every one

    Nothing goes into the library until David has read it, changed what needs changing, and agreed it.

  8. Councils help improve it

    Signed-in readers can comment. We change the library when a council shows us something we got wrong, and list every change.

Why we do it this way

A need only helps your team if it's fair. Testing on real websites means every check is one that councils can meet. Starting from real council pages means the library covers what residents actually ask for.

Who checks the library

David has spent the last 10 years helping councils save time and money by making their websites easier to use.

Why I'm building this library · See our progress

Want to see how your website does on these needs?

I'll test your pages and show you which ones to fix first.

Talk to David