Pillars in Practice · Get

The Data That Should Already Be There

First in a five-part series on where conveyancing transactions actually lose time, and what changes when each stage works the way it should.

Every conveyancer knows the moment. A matter opens, an instruction lands, and the first two weeks disappear into a slow trickle of information that should have arrived on day one.

A search comes back three days after it was ordered. An identity check sits in a queue because the client hasn't uploaded the right document yet. A property's basic details, the kind of thing that should be settled before anyone even opens a file, get chased over email across three different people.

None of this is anyone's fault exactly. It's what happens when the first stage of a transaction, simply getting hold of the right information, is treated as a series of separate requests instead of one connected job.

Why "Get" is where everything else starts

Every later stage of a transaction depends on what happens here. Risk can't be analysed from data that hasn't arrived. A problem can't be predicted from a flag sitting unread in someone's inbox. A client can't be given an honest update if the conveyancer handling their case is still waiting to find out what's actually going on.

When the Get stage is slow or scattered, it doesn't stay contained. The delay shows up two weeks later as a missed risk, and two weeks after that as a client chasing. It's a capacity problem before it's ever a communication problem.

What good looks like

The transactions that move fastest aren't the ones where nothing goes wrong. They're the ones where the right information turns up in one place, close to the moment the matter opens, instead of trickling in piece by piece over the first few weeks. For a typical file, that means things like:

  • Who legally owns the property, and on what terms, freehold or leasehold, any restrictions on the title
  • What the property is actually like: energy performance, flood risk, planning history, council tax band
  • Who the parties are, with identity verified early rather than chased at the last minute

None of this is exotic information. Most of it sits in public registers and open datasets already. The difference is whether someone has to go and find it, piece by piece, or whether it's already there when the file opens.

How we help

This is the part of the process we built specifically to close. From the moment a file opens, we pull together:

  • Property data: title and tenure, energy performance, flood risk, planning constraints, council tax band
  • Identity checks: started at instruction, not chased later in the process
  • The public records behind both, so nothing has to be requested, found and attached one at a time

The result isn't a faster version of the same waiting game. It's a case file that starts with the information already in it, so the first two weeks can go on the actual work instead of gathering what should have been there from day one.

Where this fits in the bigger picture

Get is the first of five stages every transaction moves through: Get, Analyse, Predict, Communicate, Manage. Each one depends on the last. This series looks at what happens at each stage, and what changes when it works the way that it should.

Next: what happens when the information does arrive, but the risk hiding inside it doesn't get read in time.

Curious how this looks for your firm?
Get in touch and we'll talk through where the gaps are and what closing them could look like.
Get in Touch