Back
Technical specification

Request for information (requisition) data

Overview

This dataset shows the number of register change applications we completed that had avoidable requisitions raised on them in the preceding 6 months lodged by account- holder customers who made 10 or more applications in that same period.

It includes all types of avoidable requests for information but excludes:

  • telephone requests for information
  • bankruptcy applications
  • bulk applications
  • applications that we've received but not yet completed

Avoidable requests for information are points that, barring occasional human error, a diligent applicant carrying out the usual range of enquiries and searches will avoid. These include:

  • unexplained name variations
  • lodgement of illegible or incomplete deeds/documents
  • incorrect execution and/or witnessing of a deed/document
  • incorrect fees
  • no/incomplete information as to how a title is held by joint owners
  • identity verification information/evidence not provided/incomplete
  • plans references in the text of deeds/documents not shown on plans
  • no evidence provided of an attorney's power to act
  • incomplete forms lodged
  • no address for service provided
  • no/incomplete evidence of devolution of title following a death

Specification scope

We send requests for information if an application does not have enough information or if there are inconsistencies in the documentation.

The applications we receive are either to update the register or to create new titles.

Inclusions and exclusions

The data includes all types of requests for information but excludes:

  • telephone requests for information
  • bankruptcy applications
  • bulk applications
  • applications that we've received but not yet completed

Relationship to other HMLR data products

This dataset is not linked to any other datasets from HM Land Registry.

Data content and structure

Table 1 - class diagram

Class diagram of the dataset which describes the content and structure
Avoidable requisitions
Organisation Name
Total Applications Completed
Applications with Fully Avoidable Requisitions
Avoidable Requisition %

Table 2 - Avoidable requisitions table structure

Description of the data fields in the dataset
Field name Data type Mandatory Description
Organisation Name Character Yes The name of the customer firm lodging registration applications
Total Applications Completed Numerical Yes The number of registration applications completed in the preceding six months
Applications with Fully Avoidable Requisitions Numerical Yes The number of completed registration applications in the preceding six months where HM Land Registry needed to raise avoidable requisitions
Avoidable Requisition % Numerical Yes The percentage of completed registration applications in the preceding six months where HM Land Registry needed to raise avoidable requisitions

Data quality

We try to make sure that our public data is accurate, but cannot guarantee that it is free from errors or fit for your purpose or use.

Data capture information

This data is created from applications made to HM Land Registry. Most applications are received electronically and added automatically to our systems. Requests for information are recorded against applications throughout the registration process.

Data maintenance

The published data is a snapshot of the previous six months. We will not update this data. We'll publish a new dataset after the end of the following six months.

Data product delivery

Access to the dataset

The dataset is available as a .CSV file on GOV.UK and is released under the Open Government Licence (OGL).

File structure

The data is ordered alphabetically (ascending) by customer name. The data in each file will:

  • use a comma to separate each field: ',' (ASCII 44)
  • enclosed all fields within double quotes: “ ” (ASCII 34)
  • send blank fields without a character between double quotes: “ ”
  • format dates DD-MM-YYYY HH:MM:SS
  • use UTF-8 encoding (the way characters are coded for websites)
  • remove line separation from the data
  • have the column heading name as the first row

File name

The file name will be structured as follows:

Avoidable_Requisitions_<1>_<2>_<3>.csv

<1> Month begin

<2> Month end

<3> Year

Example file name structure for October 2025: Avoidable_Requisitions_April_Sept_2025.csv

Contact us

If you have any questions about this data, email our customer service team.

Email