For firms managing post-completion manually

The manual process works. Until one thing slips.

Portals, spreadsheets, calendar reminders. You've built a system. It works — most of the time. The question isn't whether it works today. It's what happens on the day the OS1 expires before anyone noticed, or the SDLT deadline passes while a fee earner is on annual leave.

Glyd is what you put in place so that day doesn't happen. Document extraction. AP1 and SDLT auto-generated. Every deadline tracked automatically. Every risk visible before it becomes a problem.

The specific failure modes

The manual process has three places where things go wrong.

These aren't unusual. They happen to experienced, careful fee earners — because the workflow is structured to let them happen.

Deadlines tracked by memory

OS1 priority expires in 30 working days — not calendar days. The SDLT deadline is 14 days from effective date. Leasehold notice deadlines vary by lease. A spreadsheet or calendar reminder can miss any of these the moment a fee earner is on leave, sick, or simply distracted by a completion.

A missed OS1 expiry can void the priority search — leaving the title unprotected and the fee earner personally exposed.

Errors caught by HMLR, not you

Manual AP1 completion creates transcription errors — name inconsistencies, title number mismatches, OS1 validity checked by hand rather than system. HMLR raises the requisition. You investigate, correct, re-submit. The matter sits open for weeks longer than it needed to.

Most requisitions are caused by identifiable, preventable errors. They repeat, across firms, year after year.

No audit trail when it matters

SRA and CLC inspectors ask specific questions: what happened on this matter, when, and who was responsible. A spreadsheet and a portal activity log are not an evidence pack. Reconstructing the timeline after the fact is a significant management burden — at exactly the moment you don't have time for it.

Glyd's immutable audit trail means the evidence pack is generated in 30 seconds — before anyone arrives.

What changes immediately

Here's what day one looks like.

Not a migration project. Not a workflow overhaul. Your first matter in Glyd.

Before

Download TR1 and mortgage deed from your portal

With Glyd

Upload TR1 and mortgage deed to Glyd. Glyd reads every field.

30 seconds

Before

Open the AP1 form. Enter title number, names, price, address manually

With Glyd

AP1 opens pre-populated. Review the extracted data. Flag anything that doesn't match.

2 minutes

Before

Run through a mental checklist (or don't) for common errors

With Glyd

Eight pre-flight checks run automatically. Blockers prevent submission until resolved.

Automatic

Before

Calculate OS1 expiry in working days — manually

With Glyd

OS1 expiry, SDLT deadline, and all other deadlines calculated and tracked the moment the matter is created.

Automatic

Before

Log a calendar reminder for each deadline

With Glyd

No calendar entries needed. Glyd escalates automatically at 5 days and 2 days out.

None needed

Before

Review the draft AP1 and submit via the portal

With Glyd

Review Glyd's AP1 draft. Approve. Glyd submits. Nothing goes to HMLR without your sign-off.

3 minutes

The AI drafts. You decide. That's not a compromise — it's how professional accountability works. And it's faster than the manual alternative.

When volume increases

The manual process doesn't scale. Glyd does.

At 20 matters a month, a manual post-completion workflow is manageable with care. At 50 matters, it requires dedicated time every day and a robust system for tracking what's open. At 100 matters, it requires either more people or a tool that handles the tracking automatically.

Glyd scales with your volume. Every matter has the same workflow, the same checks, the same deadline tracking — regardless of how many are open simultaneously.

See it on your first matter. Before you commit to anything.

We'll walk through a freehold purchase from document upload to submission confirmation. Watch the extraction. See the pre-flight check. Check whether it would have caught the last requisition you received.

Request access

Typical response: within 2 working days.

Common questions from firms making the switch

What about our client data and GDPR?

UK data residency — Google Cloud London (europe-west2) only. AI inference on Vertex AI — your data is never used to train models. Data Processing Agreement signed at firm onboarding. You remain the data controller.

Will the AI make a mistake that causes a PII claim?

AI drafts every form. A qualified fee earner approves every submission. Nothing goes to HMLR or HMRC without explicit sign-off. The approval gate is not optional — it's built into every workflow.

How long does it take to set up?

Most firms are processing their first matter within one working day of onboarding. There is no complex migration — Glyd starts with new matters. Existing open matters can be added manually.

What if HMLR or HMRC API goes down?

Submissions are queued. Auto-retry on recovery. You're notified of any delay. No silent failures — you always know the status of every submission.

Is it right for our firm size?

Glyd works for 1-fee-earner CLC firms and 50-fee-earner practices. The compliance dashboard scales with volume. Per-matter pricing means you pay for what you use.

What happens when there's a problem?

We're onboarding our first firms with high-touch support. Every pilot firm gets direct access to the founding team during onboarding.

UK data only · Google Cloud London
No model training on your data
AI drafts. You approve. Always.
GDPR-compliant · DPA at onboarding
Immutable audit trail — exportable on demand
Pen-tested pre-launch