Public leasehold intelligence from IntelliLease.info. Operational platform at intellilease.co.
IntelliLease.info
Buying & Selling · Conveyancing Intelligence

Leasehold Conveyancing & LPE1

Understanding leasehold information requests, why sales get delayed, and how structured records and better process controls may improve response times.

At a glance
63LPE1 fields reviewed
38static or annual fields
4information types
v1proposed framework
OwnerIntelliLease
StatusProposed framework
ScopeLeasehold sales
Statutory statusNon-statutory
AudienceSellers, buyers, conveyancers, request handlers
UseProcess improvement

What is an LPE1?

Most leaseholders only discover LPE1 when they are selling. That is why this page leads with conveyancing, not the form acronym.

Plain English

The LPE1, or Leasehold Property Enquiries form, is the standard information request used during the sale of a leasehold property. It helps the buyer and their solicitor understand service charges, reserve funds, insurance, disputes, major works, management arrangements and other matters that may affect the flat being purchased.

Why sellers care

Slow or incomplete replies can delay exchange, frustrate buyers and cause transactions to wobble. The issue is often not the form itself, but the quality and location of the records behind it.

Why buyers care

The buyer needs to know what obligations, costs, disputes, arrears, insurance arrangements and major works risks may come with the property.

Why fulfilment teams care

Poor records and slow response workflows can create avoidable sale delays and expose weak information management.

Who participates?

Several parties affect the timeline, but the framework remains focused on conveyancing information fulfilment.

ParticipantRole in the processDelay risk
Selling leaseholderAuthorises sale-related disclosure and may need to confirm solicitor details.Slow verification response.
Seller's solicitorRequests leasehold information and coordinates seller-side conveyancing.Incomplete request or late supplementary queries.
Request handlerUsually prepares the LPE1 response from estate, accounting and compliance records.Fragmented records, batch processing, missing master file.
Conveyancing information handlerPrepares or coordinates the information response from the available records.Unclear ownership, incomplete records or slow internal handoffs.
Buyer's solicitorReviews replies and raises follow-up enquiries where information is unclear.Supplementary query cycles.

Compact LPE1 workflow

The managing agent is usually the operational entry point. The process then depends on verification, records, coordination and issue controls.

Positioning: this is an IntelliLease process-improvement model, not a statutory workflow. It is designed to show where acknowledgement, verification, coordination, completion and performance review can sit in a controlled conveyancing fulfilment process.
1

Request received by managing agent

Entry pointTarget: 1 working day acknowledgement

The buyer's solicitor or seller-side representative usually sends the request to the managing agent. The request should be logged, acknowledged and linked to the correct property.

Good practiceLog request date, requester, property, fee status and expected response date.
Failure pathNo acknowledgement creates ambiguity, chasers and loss of buyer confidence.
2

Verification & Authority

Control stageBefore information release

Before preparing or releasing information, the organisation should consider whether it has sufficient assurance that the request relates to the correct property and that information is being disclosed appropriately.

Possible verification controlsSeller notification
Solicitor confirmation
Property reference validation
Authority confirmation
Request logging
Why it mattersHelps support transparency, disclosure controls, auditability and information governance.
3

Information Collection & RASCI Coordination

Responsible: Managing agentCoordination stage

The managing agent coordinates the collection and verification of information required to complete the request. Some information may sit with records, advisers, suppliers, insurers or other parties depending on the building.

Good practiceIdentify who is responsible, accountable, supporting, consulted and informed for each information category.
Failure pathUnclear ownership causes internal handoffs, missing evidence and slow replies.
4

Open estate master file

Records stepStatic and annual fields

The response starts from a current estate information file containing static and annually maintained fields, rather than reconstructing the pack from scratch each time.

Good practiceKeep lease, insurance, service charge, reserve fund, compliance and management records in a structured source.
Failure pathNo master file means manual reconstruction and avoidable delay.
5

Run point-in-time checks

Current-position checkBefore issue

Arrears, disputes, Section 20 consultations, insurance claims and outstanding compliance matters must be checked against the position at the request or issue date.

Good practiceUse live logs for arrears, disputes, claims, Section 20 and major works.
Failure pathOutdated checks may produce inaccurate or incomplete replies.
6

Assemble and quality-check response

Completion stepEvidence check

The LPE1 response is assembled from verified source information and checked for completeness, internal consistency and missing attachments.

Good practiceCheck field completion, attachments, dates, amounts and source records before issue.
Failure pathIncomplete responses trigger supplementary enquiries and delay the transaction.
7

Issue response and close boundary

Issue stepDisclosure record

The completed response is issued and copied appropriately. The response should state the date it reflects and how later supplementary questions will be handled.

Good practiceRetain a full issue record showing recipient, date, version and attachments.
Failure pathOpen-ended supplementary enquiries can drag the process beyond the original request.
8

Review fulfilment performance

Improvement stepMonthly or quarterly

The fulfilment process can be reviewed by tracking request volumes, turnaround time, delay reasons, supplementary enquiries and complaints.

Good practiceAdd conveyancing fulfilment to periodic operational reporting where sale delays are a known issue.
Failure pathNo reporting means recurring delay causes stay invisible.

Information Collection & RASCI

The managing agent usually coordinates fulfilment, but not every information source sits with the managing agent.

RASCI RoleTypical participant in LPE1 fulfilment
ResponsibleManaging agent coordinating the request and response assembly.
AccountableEntity or function responsible for the conveyancing information process.
SupportingInformation holders, records owners, insurers, accountants, compliance providers and service providers where relevant.
ConsultedSeller, seller's solicitor and relevant internal information sources.
InformedBuyer, buyer's solicitor and selling leaseholder as appropriate.
Framework boundary: the specific parties may vary between developments. The framework focuses on the information request process, not any particular estate governance structure.

Why LPE1 delays occur

Most preventable delays are records-management, workflow or verification failures, not deep legal complexity.

No estate master file

Static and annual fields are rebuilt for every sale request.

High

Fragmented records

Insurance, accounts, arrears, disputes and compliance records sit in different places.

High

Point-in-time logs missing

Section 20, arrears, disputes and claims require manual searching.

High

Missing verification and authority process

Requests may pause while authority, contact details, solicitor instructions or property references are confirmed.

High

Batch processing

Requests are handled on set days rather than when received.

Medium

Supplementary query cycles

Questions arrive in waves because original responses are incomplete or unclear.

Medium

Internal dependency

Some information depends on records outside the main fulfilment system.

Medium

No performance monitoring

Delays repeat because no one measures turnaround or failure reasons.

High

The IntelliLease information classification model

This is the core idea: not every LPE1 field should be treated the same. Some should be pre-maintained. Some must be checked fresh.

TYPE 01

Static

  • Lease term
  • Ground rent structure
  • Management structure
  • Subletting rules
  • Estate governance details
Pre-populate
TYPE 02

Annual

  • Service charge budget
  • Reserve fund balance
  • Insurance renewal
  • Compliance certificates
  • Accounts cycle
Update yearly
TYPE 03

Transaction

  • Seller name
  • Buyer details
  • Solicitor details
  • Request date
  • Fee status
Per request
TYPE 04

Point-in-time

  • Arrears
  • Active disputes
  • Section 20 status
  • Insurance claims
  • Outstanding compliance actions
Fresh check
Operational point: if static and annual fields are maintained properly, the LPE1 process becomes mainly transaction data plus point-in-time verification. That is the difference between a controlled process and repeated manual reconstruction.
Field typeOperational treatmentRisk if unmanaged
StaticSet once, reviewed when lease or governance structure changes.Wrong structural answers repeated across every sale.
AnnualUpdated on budget, insurance, accounts or compliance cycle.Outdated insurance, accounts or service charge information.
TransactionCompleted for each sale request.Wrong parties, dates, fees or contact details.
Point-in-timeChecked fresh at request or issue date.Incorrect arrears, disputes, claims or major works position.

Process improvement framework

This is deliberately framed as recommendations, not invented regulation. It is an operational improvement model for better records, clearer ownership and shorter avoidable delays.

Estate Information Master File

A maintained estate file containing static and annual information used repeatedly across LPE1 requests.

Benefit: less reconstructionDepends on record quality

One-Day Acknowledgement Target

A defined target for confirming receipt, request scope, fee status and expected response boundary.

Benefit: visibilityDepends on intake process

Leaseholder Verification Step

A process step to confirm sale context, named solicitor and authority before personal data is released.

Benefit: transparencyDepends on contact details

Structured Record Ownership

Clear ownership for accounts, insurance, disputes, Section 20, arrears and compliance records.

Benefit: accountabilityDepends on governance maturity

Five-Day Completion Target

An internal target for completion once authority and records are available. Not a statutory requirement.

Benefit: disciplineDo not present as law

Performance Reporting

Monthly or quarterly reporting of volumes, turnaround, reasons for delay and recurring failure points.

Benefit: continuous improvementDepends on KPI capture

Governance and compliance considerations

The page should not shout “breach”. It should identify process areas that may warrant governance review.

AreaConsiderationSafer wording
Verification and authorityBefore information is released, the process should establish that the request relates to the correct property and an appropriate disclosure route has been identified.May improve disclosure control and auditability.
Data protectionPersonal data may be disclosed as part of LPE1 replies. Verification and transparency should be considered.May reduce disclosure and transparency risk.
Record keepingIncomplete or scattered records increase completion time and the chance of inaccurate replies.May improve consistency and auditability.
Accountabilityrequest handlers may need visibility of request handler performance where sales are repeatedly delayed.May support request-handling oversight.
Audit trailIssue date, version, source records and recipients should be retained.May support later review if enquiries are disputed.
Supplementary enquiriesUnbounded follow-up questions can extend the process indefinitely.May benefit from a clear response boundary.
Boundary: this page is public information and process-improvement guidance. It is not legal advice, not a formal industry code and not a substitute for professional advice on a specific transaction.

Related resources

These are the obvious commercial follow-ons. Keep them as coming soon until Lemon Squeezy and fulfilment are ready.

LPE1 Delay Diagnostic

A short diagnostic for leaseholders or boards to identify likely sources of sale-delay risk.

Coming soon

Estate Information Master File Template

Template structure for pre-maintaining estate information used in repeated LPE1 requests.

Coming soon

Conveyancing Governance Toolkit

Board-facing checklist, SLA model, verification process and KPI structure.

Coming soon

Estate Record Review

Bespoke review of whether estate records are ready to support sales and information requests.

Bespoke

Applying This Framework

This framework is designed for leasehold conveyancing information request fulfilment. It focuses on the records, workflow, verification steps and response controls needed to prepare consistent LPE1 replies.

For further information, implementation support, process reviews, or estate records assessments, contact hello@intellilease.co.