Estimated Completion Date
Overview
The Estimated Completion Date (ECD) is a date by which the application is likely to be completed. It is not based on the individual application but is an estimate of when the majority (90%) of that application type will be completed.
In order to retain parity with our Portal customer experience, we require that anyone integrating with this service refer to the estimated completion timeframes which can be found at https://www.gov.uk/guidance/hm-land-registry-estimated-completion-timeframes. We also see benefit in end users being familiar with the above URL, the insights provided are likely to reduce the need for customer contact. Therefore we also ask that you make your customers aware of the above URL.
The ECD:
- Is calculated on and from the day an application is received by HMLR.
- May take up to an hour to be displayed after application submission.
- Is updated every 30 calendar days until the application is completed or cancelled.
- Is updated if HMLR correspondence is issued (first item of correspondence only).
Application Types
To use the ECD service you will need to know the application reference of the application you wish to find out the ECD for. If you do not know the application reference, please use the application enquiry service to obtain this.
This service is for applications that change the register i.e. register create and register update applications only. This is denoted by the format of the application reference (you may also see this referred to as the ABR or HMLR reference):
A999AAA or AAXXXXX
Where:
A = [A-Z]
9 = [0-9]
X = [0-9A-F]
Process Flow
To request the Estimated Completion Date of an application, you will need to input the Application Reference into your Case Management Software:
Input
- Login details
- Application reference
Output
- Application reference
- Application status
- Application priority date
- Estimated completion date status
- Estimated completion date
- Note: refer to the OpenAPI specification for further details. See link
Process Flow Diagram
Service Working Hours
This service is available 24/7.
Access Control
To use this service you will need to be an existing Business Gateway user. You will also need to ensure that users have at least one of the following access role codes/collection IDs: - L1, L2, L3, WM1, WM2, WM5, C4, VS1, Z1, Z2
If you would like to integrate with this service you can request access at https://www.gov.uk/guidance/apply-for-hm-land-registry-business-e-services.
Rate Limiting
Schemas
Error and Status Codes
When developing for exception handling, use the HTTP codes in the table. The error codes listed are subject to change.
| HTTP code | Title | Error code | Detail |
|---|---|---|---|
| 400 | Parameter is invalid | BG40001 | Application Reference has an invalid format |
| 401 | Unauthorized | BG40004 | Invalid credentials or account is not active |
| 403 | Forbidden | BG40005 | Incorrect user role or organisation is not permitted |
| 404 | Application reference not found | BG40002 | The Application reference provided does not exist |
| 429 | Rate Limit Exceeded | BG40006 | Too many requests, please wait and try again |
| 500 | An error has occurred | BG50001 | Internal server error |
| 504 | Internal service timeout | BG50004 | The gateway has timed out |
Customer Test Stubs
Customer Test Endpoint
The test environment can be accessed at:
https://bgtest.landregistry.gov.uk/bg2test/api/v1/applications/{application_reference}/estimate-completion-date
Where {application_reference} is replaced by the application reference you need to use.
This requires a customer test certificate (this is different to the production client certificates)
Scenarios when ECD is returned
Scenario 1 - Application reference is valid and matches an application. ECD is provided.
ABR: X000XXX
{
"data": {
"application_reference": "X000XXX",
"application_status": "RECEIVED",
"application_priority_date": "20/08/2021",
"estimated_completion_date_status": "AVAILABLE",
"estimated_completion_dates": [
{
"date": "17/03/2023",
"probability": 0.9
}
]
}
}
Scenario 2 - Application reference is valid, application is delayed. ECD is provided.
ABR: X001XXX
{
"data": {
"application_reference": "X001XXX",
"application_status": "DELAYED",
"application_priority_date": "19/01/2023",
"estimated_completion_date_status": "AVAILABLE",
"estimated_completion_dates": [
{
"date": "13/05/2024",
"probability": 0.9
}
]
}
}
Scenarios when ECD is not returned
Scenario 3 - Application reference is valid, application is received. ECD status is exceeded.
ABR: X002XXX
{
"data": {
"application_reference": "X002XXX",
"application_status": "RECEIVED",
"application_priority_date": "12/02/2022",
"estimated_completion_date_status": "EXCEEDED"
}
}
Scenario 4 - Application reference is valid and matches an application. ECD is not yet calculated.
ABR: X003XXX
{
"data": {
"application_reference": "X003XXX",
"application_status": "RECEIVED",
"application_priority_date": "20/04/2022",
"estimated_completion_date_status": "CALCULATING"
}
}
Scenario 5 - Application reference is valid and matches a cancelled application. ECD status is unavailable.
ABR: X004XXX
{
"data": {
"application_reference": "X004XXX",
"application_status": "CANCELLED",
"application_priority_date": "23/08/2022",
"estimated_completion_date_status": "UNAVAILABLE"
}
}
Client-side error scenarios
Scenario 6 - Application reference is invalid.
ABR: 005XXXX
{
"errors": [
{
"code": "BG40001",
"detail": "Application reference has an invalid format.",
"status": "400",
"trace_id": "c62e9b3f-e523-4f04-a941-c6cf0d60c080",
"title": "parameter is invalid."
}
]
}
Scenario 7 - Application reference is valid but does not match a HMLR application.
ABR: X006XXX
{
"errors": [
{
"code": "BG40002",
"detail": "The application provided does not exist.",
"status": "404",
"trace_id": "c62e9b3f-e523-4f04-a941-c6cf0d60c080",
"title": "Application reference not found."
}
]
}