Most search firms run their entire operation out of a shared inbox.
Orders come in as emails. Sometimes they're on a form, often they're free text in the body of a message. The team reads each one, works out what's being asked for, and gets it moving. Council responses come back to the same inbox, where they sit among everything else until someone picks them up.
It works. For a while. It works when you're small and one person knows what's in flight. Then volume grows, a second person joins, someone goes on leave, and the cracks show. The inbox was never built to be an order system. It just got used as one because it was there.
Why does the shared inbox fail as you grow?
The shared inbox fails because it has no concept of an order or a status. An email is just an email. Nothing tells you what's outstanding, what's overdue, or who's already on it. You find out something was missed when the solicitor rings to ask where it is.
That's the heart of it. The inbox holds messages, not work. Every other problem grows from that one gap.
You can't see status. An order that arrived this morning and an order that's been sitting for a week look identical in a list of unread mail. The only way to know the difference is to remember, or to open each one and reconstruct where it got to.
Two people reply to the same thing. With no record of who picked up what, duplication is constant. Someone places a search that's already been placed. Someone chases a council that already responded. It's wasted effort, and worse, it's the kind that makes the firm look disorganised to the people ordering.
Things slip. A response comes back, gets glanced at on a busy afternoon, and never gets actioned. The search is effectively done and nobody knows. Days pass. The solicitor is waiting on something that's been sitting in your inbox the whole time.
What does "good" actually look like?
Good looks like every order being a tracked record with a status, not a message in a pile. The order email is parsed into a structured record the moment it arrives. Council responses are matched back to that record automatically. Anyone can see, at a glance, exactly where every order sits.
That's the whole shift. The inbox stops being the system. It becomes just one of the doors work comes through.
Orders parsed into records
When an order email lands, the details get pulled into a proper record: the address, the property, what's been requested, who it's for. Now it's a thing with a state, not a message to be remembered. It can be assigned, tracked, and reported on. It can't quietly disappear below the fold.
Responses matched to orders
When a council replies, the response links to the original order rather than floating loose in the inbox. The order's status moves forward on its own. You don't need someone to open the email, work out which order it belongs to, and update a spreadsheet. The match happens, and the picture stays current.
Status visible to everyone
Every order shows where it is: awaiting placement, with the council, response received, report being built, issued. When a solicitor asks "where's my search?", anyone on the team can answer in seconds without reading a single email. That alone changes how the firm feels to deal with.
Shared inbox vs tracked orders
The difference between the two ways of working is stark once you put them side by side. One relies on people remembering and reading; the other relies on the system knowing. Here's how they compare on the things that actually cost you time and credibility.
| Shared inbox | Tracked orders | |
|---|---|---|
| What an order is | An email in a pile | A record with a status |
| Knowing what's outstanding | Read through the inbox | Visible at a glance |
| Council response handling | Spotted and actioned by hand | Matched to the order automatically |
| Risk of duplicate replies | High — no record of who's on it | Low — ownership is clear |
| Chasing late responses | Someone has to notice | Overdue orders flagged by data |
| Answering "where is it?" | Scroll and reconstruct | One look at the status |
The firms that make this jump tell me the same thing afterwards: the relief isn't really about speed. It's about not lying awake wondering what got missed today.
How do you handle responses from 300-plus councils?
You handle it by matching every response to its order automatically, because doing it by hand across that many sources is where things break. There are over 300 local authorities in England and Wales, and that number is falling as councils reorganise. Each one has its own way of replying.
Some send a PDF. Some reply in the email body. Some use a portal and email you a notification. The formats vary, the addresses they reply from vary, and the turnaround varies council to council.
In a shared inbox, every one of those replies is a small manual job: read it, work out which order it belongs to, find that order, update its status, file the attachment. Multiply that by your weekly volume and it's a real chunk of someone's day spent just sorting post.
Match responses to orders automatically and that whole job mostly disappears. The reply arrives, it's tied to the right order, the status moves, the attachment is filed against the record. The team only gets involved when something genuinely needs a human, like a council asking a question or flagging a problem. That's the difference between handling 300 councils and being buried by them.
Why should chasing be driven by data, not the inbox?
Chasing should be driven by data because the inbox can't tell you what's late — it can only tell you what's arrived. Data-driven chasing flags orders past their expected return date automatically, so you act before the solicitor does. Inbox chasing means someone has to notice the absence of an email, which almost never happens reliably.
Think about how chasing works when it's manual. Someone, usually your most experienced person, scrolls the inbox and the spreadsheet trying to remember which orders went out when, and works out by feel which ones are overdue. It's slow, it's never complete, and it depends entirely on that person being in and having time.
The thing nobody admits is that inbox chasing only ever catches what you happen to look for. The orders that get missed are the ones you forgot to check — and you can't notice an email that never came. Data doesn't forget. A status that says "expected back two days ago" surfaces itself whether or not anyone went looking.
When the system flags overdue orders for you, chasing becomes a short, deliberate task instead of a fishing expedition. You see the list of what's actually late, you act on it, you're done. And you're chasing before the solicitor calls, which is the whole point.
"I've watched people defend the shared inbox for years. 'We know our orders.' You don't — you know the ones you happen to remember. The day someone's off sick, the inbox tells you nothing. A tracked order tells you everything, whether you remember it or not."
— Valerie Bennett, Personal Search Veteran · June 2026
Where does this fit in the wider operation?
This fits at the front of everything else: intake and response handling sit at the very start and end of the search, so getting them tracked is what makes the rest measurable. Once orders are records with statuses, every later stage — placement, report build, invoice — has something solid to hang off.
It connects to the work you're already trying to improve. If you've looked at where firms lose time, you'll know the losses cluster before the request goes out and after the response comes back. Untracked email intake is exactly that. The same goes for the council knowledge problem — knowing each council's format is far more useful when responses are matched to orders automatically rather than sorted by hand.
It's also one piece of the order-to-invoice workflow. Tracked intake is the start of the chain that ends with an invoice raised automatically the moment a report is issued. The inbox can't do any of that, because the inbox doesn't know what an order is.
Across the firms we've worked with, the recurring pattern is the same: the shared inbox holds up until two people are working it at once, and from that point on duplication and misses become a weekly occurrence rather than a rare one.
The fix isn't more discipline or a tidier inbox. You can't out-discipline a tool that was never built for the job. The fix is treating orders as orders — records with a status, responses matched to them, late ones flagged by data. Once you've worked that way, going back to scrolling an inbox to find out where things stand feels like working blind.
See how Valio tracks orders end to end → · The full order-to-invoice workflow → · Where firms lose time →