Transparency data

User guide and technical note for premises in BDUK plans

Published 13 March 2025

Applies to England and Wales

1. Data information  

If you have any questions or feedback, please contact statistics@bduk.gov.uk. If you have an enquiry about a specific premises, please include the unique property reference number (UPRN). We may not respond to every request. Where we identify a data error, we will seek to rectify it either in our own sources, or by engaging with the local authorities, who provide data to the Ordnance Survey (OS).

We plan to publish updated releases of this dataset alongside the latest Open Market Review (OMR) publication (once every four months). This data is regularly reviewed and changes will be made with the next release.

1.1 Data description 

This data provides BDUK’s current view of whether a premises has a current gigabit connection, whether there are future plans for a gigabit connection, as well as our plans to deliver to premises that we believe are not commercially viable. The data does not contain comprehensive information on which premises have historically been delivered by BDUK through vouchers, Gigahubs and Superfast. 

The data is designed to help technical users including broadband suppliers and local councils understand where BDUK plans to deliver and to improve the transparency about the contracts that we’ve signed under Project Gigabit. This data release is optimised for technical users and will be easiest to open, read and analyse using programming software. It may not be suitable for spreadsheet software applications like Excel, which may not display all rows. 

The data contains the same premises as our Open Market Review (OMR) datasets. Further information on this can be found on our Subsidy control classification guidance page. The premises base used is the latest AddressBase Premium epoch (at time of OMR) and filtered to remove premises that are not postal addresses or are demolished premises. If a UPRN is not present in the dataset, it is not included in BDUK’s list of premises asssessed through the OMR process. This might be because it is classified by Ordnance Survey as demolished or derelict, or is a new build not included in the epoch of AddressBase Premium used in our data. 

The data is released as a .csv (comma separated value) file. Some of the columns in the dataset contain commas; these are escaped with quotation marks. This release has been split into 10 different files by English regions and Wales. File names reflect the OMR that forms the base of the data. A sample file of a maximum of 1,000 rows as been provided.

Data column	Recommended data type	Description
uprn	Numeric	Unique property reference number - A unique identifier, up to 12 digits, for every spatial address in Great Britain. Example: 10023158151
struprn	String	The UPRN column with “str” appended at the beginning to help maintain data integrity when using software to read the data Example: str10023158151
bduk_recognised_premises	Boolean	Whether the premises is included within the BDUK premises base; that is, is it a premises where a gigabit-capable connection would provide benefit (e.g. dwelling or business). Example: TRUE
postcode	String	Postcode of the corresponding UPRN. Example: S1 2FJ
lot_id	Numeric	BDUK lot identification (ID) number. Example: 20
lot_name	String	BDUK lot name. Example: South Yorkshire
subsidy_control_status	String	Open Market Review (OMR) status of the UPRN: White, Grey/Black, or Under Review. Example: Gigabit Grey/Black
current_gigabit	Boolean	Whether the premises has an existing gigabit capable connection according to the Open Market Review (OMR) data and our own delivery data. Example: TRUE
future_gigabit	Boolean	Whether the premises has any future plans for a gigabit capable connection according to the Open Market Review (OMR) data . Example: TRUE
local_authority_district_ons_code	String	The 9 character code used by the ONS for local authority districts (LAD) and unitary authorities (UA)
local_authority_district_ons	String	Local Authority district name
region_ons_code	String	The 9 character code used by the ONS for English regions
region_ons	String	Region name
bduk_gis	Boolean	Whether the premises is included within a Gigabit Infrastructure Subsidy (GIS) contract (aka “Gigabit contract”). Example: TRUE
bduk_gis_contract_scope	String	Refers to the scope of contracted premises: Initial, Deferred, or In Procurement. Example: Deferred
final_coverage_date	Date [YYYY-MM-DD]	The current final payment date for all premises in the initial scope of the gigabit contract; note that deferred scope premises (and other premises subsequently added to the contract scope) are likely to be delivered after this date. Example: 2027-04-01
bduk_vouchers	Boolean	Whether the premises is included within an approved vouchers project area. Example: TRUE
bduk_superfast	Boolean	Whether the premises is contracted in an active Superfast programme contract. Example: TRUE
bduk_hubs	Boolean	Whether the premises is in scope of a Gigahubs project. Example: TRUE
supplier	String	The BDUK supplier that is either: contracted to deliver a gigabit capable connection; is lead on an approved vouchers project which includes the premises. Concatenated with forward slashes. Example: Openreach
contract_name	String	The name of the contract; can be used when contacting BDUK or the supplier

1.2 Data sources, collection and processing 

We use a range of source data to produce this management information. We use geographic data from the Office for National Statistics (ONS). We also use premises information from the Ordnance Survey (AddressBase Premium). Further information on ONS and OS data sources can be found in the “Further information on interpreting the data” section. 

We also use internally held management information on planned delivery. This information was collected for the purposes of delivering Project Gigabit. For Gigabit contracts (Gigabit Infrastructure Subsidy, GIS), we use financial models as submitted to BDUK and exclude premises that are classed as incidental; these are premises that are included in contracts, but suppliers aren’t obliged to deliver them. The financial models can be updated through the lifespan of the contracts, allowing for premises to be added or excluded, based on new information. They undergo multiple levels of assurance before they are included in our data.  

For Superfast, we use Speed and Coverage Templates (SCTs), which are contractual documents agreed between suppliers and local authorities. For vouchers, we use lists of expected premises passed (EPP) for approved vouchers projects; these are assured by the BDUK operations team. For Gigahubs, we use internal management information held on hub locations which are in-scope for build, where the funding is provided by BDUK. Hubs that are funded by other parts of government, including the Department for Education, are not included in this dataset. 

In order to deliver gigabit connections effectively across the UK, BDUK has divided the country into geographic areas called lots. Within the lot, intervention areas (IAs) are developed where subsidy is required to support delivery of gigabit capable broadband. IAs may cover the whole lot or specific parts of the lot where subsidy intervention is required. The columns ‘lot_name’ and ‘lot_id’ show this categorisation. 

We also use BDUK’s Open Market Review (OMR) data. For the March 2025 release, we use the September 2024 OMR data.

All of the data is held centrally on BDUK’s cloud platform. Extensive checks are completed on all data, from testing that unique property reference numbers (UPRNs) are valid UK premises, to assuring that the network we agree to subsidise meets specific technical standards. These assurance checks are both automated and manual. 

1.3 Further information on interpreting the data 

This data release has been designed for industry and technical users, and to improve BDUK’s transparency over its contracts. It provides BDUK’s current view of whether a premises has a gigabit connection as well as our plans to deliver to premises that we believe are not commercially viable. As such, it is not designed to provide a backwards-looking view of premises that BDUK has subsidised; further details on BDUK’s premises passed can be found in our performance report. 

Please see the “Coherence and comparability” section for an explanation of comparisons to Ofcom and ThinkBroadband data. 

The premises included in this release were included in BDUK’s most recent OMR collection. This is derived from the OS AddressBase Premium dataset, filtered to exclude demolished premises and to ensure that all premises are postal addresses.

The ‘bduk_recognised_premises’ column states whether BDUK believes that the premises would benefit from a gigabit capable connection. This is referred to as BDUK’s “premises base” in our performance report. This filter is based on OS AddressBase Premium classifications; the categories are designed to include only those locations where a gigabit-capable connection would provide benefit (e.g. dwelling or business). It is then further modified based on local intelligence.

The ‘subsidy_control_status’ column states whether a premises is classified as white, grey/black, or under review for subsidy control status:

• White – premises with no gigabit network infrastructure and none is likely to be developed within 3 years
• Grey/Black – premises with one or more qualifying gigabit infrastructures from different suppliers being available, or will be deployed within the coming 3 years
• Under Review – premises where suppliers have reported current or planned commercial broadband coverage, but where claimed current gigabit coverage has not been verified, or, in respect of planned build, where evaluators are confident that gigabit infrastructure will be delivered, but some risks to delivery remain, or there are some gaps in evidence

The ‘bduk_gis’ and ‘bduk_gis_contract_scope’ columns refer to whether a premises is contractually included in a Gigabit contract (Gigabit Infrastructure Subsidy, GIS) and whether it is in initial or deferred scope of that contract. Gigabit contracts are subject to change, and premises can be added or removed from the initial scope of the contract. Initial scope premises are subsidised premises that are within the confirmed scope of the contract. Deferred scope premises are included in the contract but not part of the initial scope; these are premises that BDUK deemed to be potentially commercially viable at the point of contract signature; the intention is for these to be delivered after completion of the initial scope of the contract, if they are reclassified as gigabit “White” subsidy control status. In Procurement premises are premises that are currently in procurement.

The ‘final_coverage_date’ column refers to the final payment date for all premises in the initial scope of the gigabit contract; note that deferred scope premises are likely to be delivered after this date. This date is subject to change should a change request to the contract be accepted.  

The ‘bduk_vouchers’ column states whether a premises is in an active approved vouchers project. Vouchers projects are not contractual and suppliers may not provide coverage to all premises within the approved vouchers project. As a result, BDUK regularly reviews active vouchers projects to check progress. If premises are not delivered through vouchers projects, we will look to include them in Gigabit contracts in future. 

The ‘bduk_superfast’ column states whether a premises is contractually included in an active Superfast contract delivering gigabit premises. Many of these premises will have already been delivered through the Superfast contract. Premises in these contracts are subject to descoping; BDUK regularly reviews Superfast contracts and will look to include premises that are not delivered through these contracts in Gigabit contracts in future. 

The ‘bduk_hubs’ column states whether a premises is in scope to be connected as a Gigahub, part of Project Gigabit designed to deliver gigabit infrastructure to rural public sector buildings. Hubs may be descoped at any point and instead included within another intervention. Only hubs that are, as a minimum, in assurance (the step before “in build”) are included.  

It is possible for a premises to be included in more than one intervention. For example, a premises might be in both an approved vouchers project and in the deferred scope of a Gigabit contract. Those premises will be removed from the deferred scope of the contract if they are delivered under the vouchers project, but will remain if they are not. There may be additional overlaps between interventions that were caused by BDUK working at pace to include premises that are not commercially viable in contracts; in some instances, BDUK was not able to process data from one intervention in time to exclude it from another. Approximately 6.4% of all premises in interventions are in scope for more than one intervention (including GIS deferred scope). If a premises is in more than 2 GIS contracts, the date is from the “lead” contract, which is usually the initial scope. There may be some inconsistency with the names of suppliers used (e.g. “ltd” and “limited”). 

To assign ‘local_authority_district_ons’ and ‘region_ons’, we have matched on UPRN to the National Statistical UPRN Lookup (June 2024 edition). If this fails, we then use the postcode to match to the National Statistical Postcode Lookup (February 2025 edition). 

2. Quality characteristics  

2.1 Quality management 

BDUK’s quality assurance strategy sets out minimum standards for quality assurance for analytical products and documentation, as well as roles and responsibilities across the organisation. The quality assurance strategy meets the requirements of the Government Functional Standard for Analysis. 

2.2 Accuracy and reliability 

BDUK has undertaken extensive checks on this data, but the data may have errors associated with the large scale processing of geographic data and data from dozens of suppliers. We believe these errors are infrequent but are working with our data teams to improve data assurance. 

There are around 5,000 premises in GIS contracts that do not appear in this dataset; this is because OS now categorises these as demolished properties, and therefore they are no longer included in our OMR data. We will confirm the status of these premises and will seek to remove them from contracts where the premises no longer requires a gigabit connection.

BDUK’s contracts are subject to change; for example, if through a new OMR we determine that a premises is going to be delivered by another commercial supplier, we will seek to remove that premises from the contract. These contract changes happen rapidly and some recent contract changes are not captured in this data release. 

We are in the process of moving all source datasets to a controlled environment within the BDUK cloud platform and this may lead to minor changes in future releases. 

2.3 Coherence and comparability 

For this data release, the column ‘current_gigabit’ is derived from our own OMR data and delivery data. This means that premises that have received a gigabit connection since our most recent OMR (September 2024) will not have a TRUE flag in this release. Additionally, not all suppliers provide returns to our OMR process, so there are gaps in our coverage. This view may differ from other providers of coverage data including Ofcom and ThinkBroadband for this reason.  

The column ‘future_gigabit’ is also derived only from our own OMR data. We may have contracts for premises that do not appear in that data, either because the supplier has not responded to the OMR or because the OMR reference date was before a contract was agreed. Additionally, this column may not be comparable with the Ofcom Planned Network Deployment (PND) data for 3 reasons: 

1. BDUK’s premises base differs from Ofcom’s premises base; the primary distinction is that our base includes “child” premises (e.g. apartments in houses of multiple occupancy) whereas Ofcom’s does not 
2. Different suppliers respond to Ofcom’s PND data collection requests than respond to our OMR processes, and PND and OMR evaluation methods are not equivalent
3. Reference dates for the PND and the OMR might not be identical