Case Studies › Conveyancing

Conveyancing Document Intake Desk

How a 6-person conveyancing firm stopped losing matter readiness races.

Harbour Conveyancing, Bristol | 6-person firm | Mac Studio M3 Ultra 512GB

The firm

Harbour Conveyancing is a small residential conveyancing practice in Bristol — two solicitors, three licensed conveyancers, and one part-time admin assistant. They handle 40-60 residential matters at any given time, split between buyer-side purchases, seller-side sales, and remortgages.

They're good at the legal work. They're drowning in the document chasing.

The problem

Every conveyancing matter starts the same way: a pile of documents lands, and someone has to chase, check, and organise them before any actual legal work can begin.

For a typical buyer-side purchase, the firm needs:

What actually happens:

A matter opens on Monday. The admin assistant emails the client a list of required documents. The client sends some, forgets others. The seller's solicitor sends the contract pack but the TA6 has three unanswered questions. The mortgage broker promises the offer "next week." The management pack from the freeholder is delayed. Nobody notices the gifted deposit letter is missing until the solicitor asks for it three weeks later.

By week four, the matter still isn't exchange-ready. The client is calling daily. The estate agent is calling daily. The broker is calling. The solicitor is spending her afternoon explaining to three different people that they're waiting on documents, not on legal work.

The cost:

The firm's owner, Sarah, put it plainly: "I didn't train for six years to spend my afternoons chasing clients for bank statements."

What Foundry does

Foundry sits on a Mac Studio in the office — the same kind of computer you'd see on a designer's desk. It's quiet, doesn't need a server room, and plugs into a normal power socket.

Here's what Sarah's team set up:

A document intake desk that works like a checklist, not a robot.

When documents arrive — by email, upload, or the firm's case management system — Foundry reads them. Not to give legal advice. Not to approve anything. Just to answer one question: is this matter's document pack complete?

For each document, Foundry:

  1. Identifies what it is — "This is a TA6 property information form" or "This is a bank statement covering March-May 2026"
  2. Checks it's the right document for this matter — "This TA6 is for 12 Harbour View, which matches the matter address"
  3. Extracts key information — client name, property address, dates, amounts, signatures present or missing
  4. Flags problems — "The TA6 has three unanswered questions in section 4" or "The passport expired in February" or "The declared gift amount is £25,000 but no donor letter has been received"
  5. Updates the matter readiness checklist — showing exactly what's received, what's missing, and what needs attention

Crucially, Foundry does not:

Every output is a draft for a human to review. Every action requires a person to say "yes, send that."

What it looks like day to day

Monday morning, 8:45 AM

Sarah opens the matter dashboard. Three matters need attention:

Total time: 12 minutes.

Previously, getting to the same point would have taken Sarah and the admin assistant 2-3 hours of reading through email chains, checking the matter file, and identifying the gaps manually.

The numbers

MetricBeforeAfterChange
Admin hours/week on document chasing15-204-670% reduction
Solicitor hours/week checking matter readiness3-50.5-185% reduction
Average time to exchange-ready5-7 weeks3-4 weeks2-3 weeks faster
Client complaints about communication3-4/month<1/month75% reduction
Matters delayed by missing documents1.5/month0.2/monthNear eliminated
Data sent to cloud providersAll (email, OCR tools)NoneFully local

Financial impact:

Foundry cost: £999 setup + £99/month = £2,187 first year. Existing Mac Studio, no new hardware.

What stayed cloud

Foundry doesn't replace anything. It sits beside the existing systems, handling the document triage that nobody's tools were doing well.

What it doesn't do

What the team says

"The first week it was running, it caught a missing donor letter on a £30,000 gifted deposit that we wouldn't have spotted for another two weeks. That alone justified the setup cost." Sarah, firm owner
"I used to start every Monday dreading the email backlog. Now I look at the dashboard, see what needs me, and I'm done in twenty minutes. The rest of the morning is actual legal work." James, licensed conveyancer
"Clients have stopped calling to ask 'what's happening.' They get the chase emails automatically, they know what's outstanding, and the communication complaints have basically stopped." Admin assistant

Is this right for your firm?

This setup works for:

Not a fit if you:

Want to see it on a sample conveyancing matter? Book a Foundry Fit Review →

Technical details

Hardware
Mac Studio M3 Ultra, 512GB unified memory
Model
Qwen3-Coder-30B (Q5_K_M), running via llama.cpp
Pipeline
Hermes watched-folder → document classification → field extraction → completeness check → exception flagging → human review queue
Document families
Client care/engagement, ID/proof of address, source-of-funds/wealth, title/title-adjacent, TA forms (TA6/TA7/TA10/TA13), mortgage offers, search results, leasehold/management packs, completion/undertakings, post-completion/registration
Original preservation
Source PDFs retained with file hashes. Derived working copies clearly separated from originals.
No-cloud posture
All document processing local. No outbound API calls.
Observability
llm_stats dashboard showing model health, memory pressure, throughput, and processing times
Integration
Reads from watched folder or case management export. Outputs to review queue and optional export to CMS.
Proof gates
Local-only | Original preservation | Classification benchmark | Field extraction benchmark | Exception detection | Audit bundle | Human review gate

← Back to all case studies | Next: Client Support →