Every personal search firm has one. The person who just knows.

They know that Rossendale needs the admin ward included. They know that a particular council has changed its submission email address. They know which councils need a prior appointment before they'll accept anything, and which ones have a back-channel that gets things moving faster.

That knowledge is genuinely valuable. It's also, if it lives only in that person's head, one resignation letter away from being a crisis.

What the council knowledge problem actually looks like

There are over 300 local authorities in England and Wales. Each one is effectively a separate operation with its own way of working.

Some accept email submissions. Some have portals. A small number still want post. Some require the admin ward; most don't. Some need a prior appointment before they'll process anything. Some have specific attachment requirements — the wrong format and they'll reject without telling you why for three days.

And it changes. Councils update their submission contacts. They change their fee structures. They adopt new processes. They migrate to the HM Land Registry national register for LLC1 searches. Sometimes they tell search firms. Often they don't.

A firm that's been processing for years builds up a picture of all of this. The problem is where that picture lives.

Keeping records of how each council works
Photo by Luis F Rodríguez Jiménez on Pexels

The ways it breaks

The key person leaves

This is the most common one. An experienced processor leaves — retirement, a better offer, any reason — and takes with them a mental model of how 200 councils work that nobody has ever written down. The team that remains is competent, but they've lost the institutional knowledge that made the operation smooth.

For a few months, you notice it in small ways. Rejected submissions that wouldn't have happened before. Extra time spent checking things that used to be routine. The odd order that stalls because nobody's sure of the right approach.

A council changes something and nobody updates

A council's search team gets a new email address. Or moves to a portal. Or starts requiring an additional field that they didn't before.

The first person to submit the old way finds out. Ideally they update the record and tell the team. In a manual system — a shared spreadsheet, a notes document, someone's email folder — there's no guarantee that update reaches everywhere it needs to.

The next submission goes out incorrectly. And the one after that, until someone notices the pattern.

An unusual instruction comes in

A search comes in for a council you rarely deal with. Your team knows the common ones well. For this one, they have to look it up — or guess.

If the lookup is a spreadsheet that was last updated eight months ago, you might send the request to the wrong address. Or miss a requirement you didn't know about. Or not know that this particular council needs an appointment and won't touch anything that arrives without one.

You don't find out until the council doesn't respond.

Aerial view of a town — every local authority works differently
Photo by Lewis Ashton on Pexels

The specific things that catch firms out

Not the obvious stuff — your team knows the main requirements for the councils they handle every day. The things that cause problems are the smaller, easily-missed details.

Admin ward. Rossendale Borough Council requires the electoral ward in which the property sits. It's derivable from the UPRN if you know to look for it. If you don't, the request gets rejected. Most firms learn this the hard way once.

Prior appointment councils. Some councils will not process a formal search request until an appointment has been booked. If you send the request without one, it doesn't necessarily come back rejected — sometimes it just sits there. You're chasing a response that will never come because the process hasn't even started.

LLC1 migration. HM Land Registry is moving Local Land Charges data to a single national register for England and Wales. For migrated areas the LLC1 result is available online instantly — free as a result, or £15 for the official certificate. Around a third of authorities have migrated so far (110 of 300-plus as of March 2025), and the share is rising, so firms still requesting every LLC1 from the council directly are adding unnecessary time and cost in migrated areas.

Attachment formats. Some councils are specific about how a boundary plan should be presented. The wrong format doesn't always generate a quick rejection. Sometimes it generates a slower, vaguer response that sends you backwards.

"I've seen firms lose two, three days on a search because of a single missing field that nobody knew was required for that council. Not because the team was careless — they just hadn't been told, because nobody had written it down. Once you know, you know. The problem is finding out the first time."

— Valerie Bennett, Personal Search Veteran · June 2026

What good council knowledge management looks like

The answer is not a better spreadsheet. A spreadsheet is still a document that has to be found, read, trusted, and manually updated. It doesn't tell you when it's out of date.

What works is a live system where council requirements are held as structured data — not a document to be read, but fields that drive behaviour. When a council's contact changes, it changes in the system and automatically applies to the next submission. When a council migrates its LLC1 to the national register, the routing updates. When a new requirement is identified, it's captured once and applies everywhere.

That kind of system means:

  • Any team member can handle any instruction correctly, without asking the person who knows
  • New starters are productive faster because the knowledge is in the system, not in training sessions
  • Changes propagate automatically instead of depending on someone to update a document
  • You're not at risk of a key person leaving and taking the operational brain with them

Valio has every council in England and Wales pre-configured — submission contacts, format requirements, known quirks, LLC1 migration status. When something changes, it's updated centrally. The knowledge isn't in your team's heads. It's in the platform.

How the Valio council knowledge base works → · Where search firms lose time → · The full order workflow → · What a local authority search shows →