Guidance

HM Land Registry request for information (requisition) data

Information on how many requests for information we send to customers about their applications.

This dataset is based on the 500 customers that lodge the most applications with us. It shows the number and type of applications we receive and complete, and how many requests for information (formerly known as requisitions) we send to customers.

It includes all types of requests for information, whether they are avoidable or not, but excludes:

  • telephone requests for information
  • bankruptcy applications
  • bulk applications

Download the data

This data is updated every 3 months and is available as a csv file or Google Sheet.

Help using Google Sheets

The data is available as a view only Google Sheet. To edit the data:

  1. Open the Google Sheet.
  2. Select file.
  3. Select download as.
  4. Select your preferred download option.

Find out:

Using or publishing Request for information data

Publication of this dataset supports the Government’s open approach to data. It is available free of charge for use and re-use under the Open Government Licence (OGL). Make sure that you understand the terms of the OGL before using the data.

If you use or publish this data, you must add the following attribution statement:

Contains HM Land Registry data © Crown copyright and database right 2019. This data is licensed under the Open Government Licence v3.0.

You must also provide a link in the data you publish to this explanation of the dataset.

Column headers used in this data

Column headers used Data type Description
Customer name Character Name of the customer that has lodged applications.
FR intake Numerical Number of first registration applications lodged by the customer in the preceding quarter.
TP intake Numerical Number of transfer of part applications lodged by the customer in the preceding quarter.
DFL intake Numerical Number of dispositionary first lease (new lease) applications lodged by the customer in the preceding quarter.
Register update intake Numerical Number of register update applications lodged by the customer in the preceding quarter.
FR output Numerical Number of first registration applications completed by HM Land Registry in the preceding quarter.
TP output Numerical Number of transfer of part applications completed by HM Land Registry in the preceding quarter.
DFL output Numerical Number of dispositionary first lease (new lease) applications completed by HM Land Registry in the preceding quarter.
Register update output Numerical Number of register update applications completed by HM Land Registry in the preceding quarter.
FR requests for information Numerical Number of requests for information raised against first registration applications completed in the preceding quarter.
TP requests for information Numerical Number of requests for information raised against transfer of part applications completed in the preceding quarter.
DFL requests for information Numerical Number of requests for information raised against dispositionary first lease (new lease) applications completed in the preceding quarter.
Register update requests for information Numerical Number of requests for information raised against register update applications completed in the preceding quarter.

All fields are mandatory.

File structure

The data will be ordered alphabetically (ascending) by customer name.

Each file will:

  • use a comma to delimit each field: ‘,’ (ASCII 44)
  • enclose all fields within double-quotes: ”” (ASCII 34)
  • transmit null fields without a character between double quotes: ””
  • format dates as DD-MM-YYYY HH:MM:SS
  • use UTF-8 and ASCII encoding
  • have the carriage return and line feeds removed from the data
  • have the column heading name as the first row

About requests for information

Requests for information are raised when HM Land Registry receives register update and register create applications that do not contain all the evidence or information needed for the application to proceed, or there are discrepancies or anomalies in the documentation that has been submitted.

Register update applications are applications made to update a register that already exists, for example, recording the names of the new owners of a property. Register create applications are applications that involve creating a brand new title, for example, a previously unregistered property being registered for the first time or a sale of part of an existing title.

Sometimes, HM Land Registry raises requests for information through no fault of the applicant or a third party. Examples include:

  • where HM Land Registry is exercising its power to ask for more information under rule 17 of the Land Registration Rules 2003: “If the registrar at any time considers that the production of any further documents or evidence or the giving of any notice is necessary or desirable, he may refuse to complete or proceed with an application, or to do any act or make any entry, until such documents, evidence or notices have been supplied or given.”
  • where HM Land Registry raises a request for information in error (which we are taking steps to avoid)

However, some of these issues arise from errors and oversights by conveyancers and in other cases from third parties not providing the evidence they need in a timely fashion. Examples include:

  • no evidence of consents by third parties needed for registrations to proceed
  • no evidence of mortgages being paid off
  • name discrepancies
  • documents not being signed or witnessed properly
  • evidence of the authority of attorneys to sign documents not being provided

Proportionally, more requests for information are raised for register create applications than register update applications. This is because register create applications are more complex and so there is more scope for requests for information to arise. So, conveyancers whose business involves a greater proportion of work that results in new titles may receive proportionately more requests for information than a firm with a different profile of work.

Accuracy of the data

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

Contact

If you have any questions about this data, please contact:

Customer Service

Published 28 March 2019