Reach the 2% AR rate floor. Defend the rest.
HMLR publishes your avoidable requisition rate. Some of the causes sit inside your firm. Some sit outside it. The Defensible Requisition Blueprint resolves the controllable portion and evidences the uncontrollable portion separately.
Three pressures the AR rate creates
If you are running a conveyancing department of 5–20 fee earners and the AR number has reached partner-level attention, you will recognise these.
Matters bounce back with requisitions
After submission, the same preventable issues keep triggering requisitions. The supervisor queue fills with "can you just look at this one" messages. Fee earners reopen files they thought were finished, post-completion becomes a loop of resubmissions, and time-to-register stretches. Non-billable rework drags on capacity that should be on live matters.
Files stuck in pending with no clean answer
Paused requisitions stop fee earners giving clients, lenders, and agents a clean answer to "is it registered yet?" The team absorbs repeated "what's stuck at HMLR?" check-ins. Supervisors chase status updates instead of preventing the next requisition. Post-completion feels like a black hole to everyone outside the firm.
A public number that includes causes you don't control
HMLR's published AR data includes firm-caused, HMLR-caused, and third-party-caused requisitions in a single headline rate. Panels, referrers, and clients form opinions from that rate even though the data cannot separate causes. The reputational weight of a blended number sits on the managing partner.
Why the standard responses don't move the number
Five mistakes in thinking and action that keep the AR rate where it is. Each one maps to a stage of the matter lifecycle where intervention is possible and being missed.
"We can tidy up Land Registry detail post-completion."
Thin intake means execution wording and restriction requirements are only discovered when HMLR bounces the application. By then the matter has already closed and the evidence is harder to recover.
"The team knows what's needed, a checklist will slow us down."
Each fee earner builds their own pack. Certificates and supporting evidence get missed or are the wrong version. The variation lands as a requisition.
"Everyone's already looked at the file, a final check is duplication."
No deliberate end-to-end review before submission, so HMLR is the first thing comparing the pack as one unit. Errors that any pre-submission cross-check would have caught are surfaced 20 business days later.
"It's with HMLR now, tracking won't change anything."
Registration sits in limbo until a client chase or requisition triggers a fire drill. The 20-business-day response window starts ticking before the firm is paying attention.
"HMLR's training is doing the heavy lifting, reminders and topping it up will get our AR rate to zero."
Partner emails and spot checks substitute for mapped, enforced workflow change. People revert under pressure, and the residual uncontrollable AR portion is mistaken for ongoing process failure.
The Defensible Requisition Blueprint
Five operational principles that resolve the controllable AR causes across the matter lifecycle, and evidence the uncontrollable portion separately. Together they describe what EIS delivers to a conveyancing department working under this engagement.
Requisition-Proof Intake
Capture every execution detail, restriction requirement, and supporting-document trigger at the point of instruction, before exchange. The matter file leaves intake with the evidence HMLR will look for already assembled, not with a list of things to chase later.
Document Pack Discipline
Standardise the exact supporting documents, certificates, and evidence per matter type, with versioned templates rather than fee-earner memory. The pack assembled for any transaction matches HMLR's practice guides every time, regardless of who built it.
Submission Pack Reconciliation
One deliberate end-to-end cross-check before submission. Names, dates, plans, fees, SDLT/LTT evidence, and property descriptions are reconciled across every document in the pack. The submission is treated as a single unit before lodgement, not as a collection of separately-prepared parts.
Submission-to-Registration Tracking
Registration treated as a tracked workflow with clear statuses, owners, and response windows. When HMLR raises a requisition, the firm sees it, owns it, and responds inside the 20-business-day window, and evidences the response trail when the cause sits outside the firm's control.
Workflow Hardening
The discipline of the first four principles built into the firm's case management system through required fields, peer review gates, prompts, and submission blocks that prevent applications progressing while gaps remain. The workflow enforces the standard so individual memory does not have to.
What changes when the Blueprint is in place
An AR rate you can stand behind
A public AR rate at the irreducible floor. Controllable causes resolved across the matter lifecycle. The uncontrollable residual separately evidenced through tracking, so panels and referrers see a number that tells a credible quality story.
Right-first-time submissions
Errors caught pre-submission rather than discovered through HMLR's response. Standardised packs reconciled as a single unit before lodgement. Fee earners able to give clients, lenders, and agents a clean answer to "is it registered yet?"
Public data on your side
The HMLR public dataset converted from a defensive reputational liability into an active quality signal. Panels and referrers see a measure the firm stands behind, supported by operational evidence rather than asserted by claim.
2% AR rate floor.
The irreducible floor of avoidable requisitions for a firm running the Blueprint. Controllable causes resolved, uncontrollable causes separately defensible. The diagnostic below shows where your firm sits today and what the path looks like.
Five minutes. Fifteen questions. Your firm's AR position scored across the five Blueprint principles.