Publication - Advice and guidance

Superfast, ultrafast and gigabit capable broadband infrastructure - open market review: request for information - January 2026

Published: 19 January 2026
Directorate: Digital Directorate
Topic: Business, industry and innovation, Economy, Programme for Government
ISBN: 9781806436675

An Open Market Review into current and planned broadband infrastructure across Scotland. The outcome will support the planning and prioritisation of public interventions and minimise the risk of disrupting commercial plans. Data collected will inform broadband interventions in Scotland.

Supporting documents

Annex B: Data submission format

Introduction

The Scottish Government requires certain fields of data for each pertinent Scottish address as identified by the UPRN in order to monitor the current and future delivery of superfast and gigabit-capable services. This is done by requesting data on current and future connections from relevant suppliers. The below describes the format of the request file and how to format the data to return to us. If you require any additional support, guidance or clarification with this, please get in touch with us at: gigabitomr@gov.scot

UPRN list files

The Scottish Government can provide a list of UPRNs if required. Please direct any requests to: gigabitomr@gov.scot

The UPRNs used for this OMR will be sourced from Ordnance Survey AddressBase Premium Epoch 124, published January 2026 using the following high-level logic:

addressbase_postal = 'N' are marked as ineligible i.e. not a postal address
CountryCode is ‘S’ i.e. within Scotland
LogicalStatusCode found in the Local Property Identifier is restricted to either to ‘1’ (approved) or ‘6’ (provisional)
LogicalStatusCode found in the BLPU table is restricted to ‘1', but if the BLPU State Code is NULL a LogicalStatusCode of '6' is also accepted.
Sort by entry date (descending) and remove UPRN duplicates (more recent records are given a priority over older records when multiple Local Property Identifier records are given for one UPRN).
A number of specific classifications are also excluded, those which the Scottish Government deem not eligible for a broadband connection. A list of classifications can be made available on request.

Further details can be obtained via the AddressBase Premium Technical Specification.^[10]

Please do not pre-filter your data based on the UPRN files, instead please provide us with your entire UPRN dataset.

If you are using the UPRN files as the starting point for your return, please remove any UPRN rows which are not part of your current or planned network.

Please note that final UPRN datasets generated during IA design and issued as part of the invitation to tender (ITT) for procurements are further filtered, and deprioritised where necessary subject to factors such as UPRN proximity, type and location.

Explanation of Required Fields

The information that to be provided against each property/premises is as follows:

Field name: struprn

Description: The UPRN (see below) prepended with “STR”, this is a mitigation against certain spreadsheet tools treating the UPRN as a large number and removing significant digits

Format: Text

Field name: uprn

Description: The unique property reference number. This is a mandatory field. Any rows without a UPRN will be rejected.

Format: Number

Field name: address

Description: Comma delimited single line address (e.g. 1, Acacia Avenue, Anytown)

Format: Text

Field name: postcode

Description: Standard postcode

Format: Text

Field name: local_authority

Description: The local authority district

Format: Text

Field name: easting

Description: Six figure number for the X co-ordinate (British National Grid)

Format: Number

Field name: northing

Description: Six figure number for the Y co-ordinate (British National Grid)

Format: Number

Field name: longitude

Description: Longitude in the decimal degree format (WGS84)

Format: Number

Field Name: latitude

Description: Latitude in the decimal degree format (WGS84)

Format: Number

The connectivity information that we ask for against each property/premises is as follows (please note the definitions provided after the table below):

Field name: current_tech

Complete this field for UPRNs which are Ready for service (RFS) only

Description: The technology you use for supplying that particular premises, examples of this could be ADSL, FTTP, FTTC etc

Format: Text

Field name: current_max_ds

Complete this field for all UPRNs with ‘Current_Technology’

Description: The maximum wholesale download speed in Mbit/s that you are able to supply to this property. This should be a positive number only.

Format: Number

Field name: current_max_us

Complete this field for all UPRNs with ‘Current_Technology’

Description: The maximum wholesale upload speed in Mbit/s that you are able to supply to this property. This should be a positive number only.

Format: Number

Field name: future_tech

Complete this field for UPRNs that you plan to connect only

Description: The technology you intend to use for supplying that particular premises, examples of this could be FTTC, FTTP etc

Format: Text

Field name: future_max_ds

Complete this field for all UPRNs with ‘Future_Technology’

Description: The maximum wholesale download speed in Mbit/s that you intend to be able to supply to this property. This should be a positive number only.

Format: Number

Field name: future_max_us

Complete this field for all UPRNs with ‘Future_Technology’

Description: The maximum wholesale upload speed in Mbit/s that you intend to be able to supply to this property. This should be a positive number only.

Format: Number

Field name: date_future_rollout

Complete this field for all UPRNs with ‘Future_Technology’

Description: This should be the planned RFS date for the premises and should align to your Calendar Deployment Plan and should correlate and be consistent with the information contained in your Supporting Evidence Pack. This should not be the date that build commences.

Format: DD/MM/YYYY

Field name: delivery_phase

Complete this field for all UPRNs with ‘Future_Technology’

Description: The planned phase for any future rollout which each UPRN shall form part of, e.g. Phase 1/Phase 2 etc, Tranche 1/Tranche 2 etc, Region 1/Region 2 etc

Format: Text

Field name: design_stage

Complete this field for all UPRNs with ‘Future_Technology’

Description: The current phase of your coverage by using one of the following field entries: 0. On hold, 0. On hold – blocked, 1. Awaiting HLD, 2. HLD complete, 3. LLD complete, 4. Build team appointed, 5. In build, or 6. RFS

Format:Text

Field name: funding_stage

Complete this field for all UPRNs with ‘Future_Technology’

Description: Field entries to use: 1. No funding planned or committed, 2. Funding planned, but not committed, or 3. Funding committed

Format: Text

Field name: public_intervention

Complete this field for all UPRNs with either ‘Current_Technology’ or ‘Future_Technology’

Description: Define if coverage has been or is planned to be connected using a public intervention.

Format: Yes/No

Field name: public_intervention_type

Complete this field for all UPRNs with ‘Current_Technology’ or ‘Future_Technology’ where ‘Public_Intervention’ is ‘Yes’

Description: This is the public intervention type, whereby the field entries to use are outlined in the definitions below.

Format: Text

Field name: public_intervention_reference

Complete this field for all UPRNs with ‘Current_Technology’ or ‘Future_Technology’ where ‘Public_Intervention’ is ‘Yes’

Description: This is the public intervention reference, whereby the field entries to use are outlined in the definitions below.

Format: Text

Field name: gbvs_prp_reference

Complete this field for all UPRNs with ‘Current_Technology’ or ‘Future_Technology’) where ‘Public_Intervention’ is ‘Yes’ and Public_Intervention_Type is GBVS (pre request) or GBVS (post request)

Description: This is a Gigabit Broadband Voucher Scheme pre-registered package (PRP) project reference; examples of field entries are as follows:

AA1001 (Pre-BDUK Voucher Funding Platform),

AB10000001 (Post-BDUK Voucher Funding Platform)

Format: Text

Field name: loc_code

Complete this field for all UPRNs where design_stage is ‘0. On hold’ or ‘0. On hold – blocked’.

Description: This is the Limit Of Construction (LOC) code for use alongside the design_stage entries of ‘0. On hold – blocked' and ‘0. On hold’. If there is more than one LOC code applicable please choose the primary reason for the build being on hold. The field entries to use are outlined in the definitions below.

Format: Text

Response Definitions

Ready for Service (RFS): RFS means a service can be ordered by a Communications Provider (CP) or end user for the premises and provisioned within industry standard timescales with no excess construction charges being applied to the CP or end user directly or indirectly (i.e. any end user would expect to pay only a published pre-agreed connection charge, if one was to be imposed, too), unless and to the extent that such excess construction charges are incurred due to a reason directly attributable to the private land of the end user, or of any landlord of the end user.

Future Rollout: All UPRNs must have a date of future rollout based on the expected RFS date for each premise. These dates must correlate with information provided in your Deployment Plan as part of your supporting evidence.

Delivery Phase: These phases should align to your Calendar Deployment Plan and should correlate and be consistent with the information contained in your Supporting Evidence Pack. Include context regarding each delivery phase in your Supporting Evidence Pack such as the risks and dependencies for the successful delivery of each phase and the mitigations/arrangements that you have in place to address these risks; a description regarding your resourcing plan for each phase; key milestones within each phase and the subsequent activities/timeframes to achieve RFS.

Design Phases:

‘0. On hold’ – Planned build to the premises has been placed on hold proactively, but may be restarted in future. Premises in this category should therefore be recorded in the Future_Technology columns. Build is not blocked by any external factors, but is likely to have been placed on hold for strategic decisions, perhaps related to funding or competitor activity for example (which should be explained in supporting evidence and clarified in your use of the ‘LOC_Code’ column).

‘0. On hold – blocked' – Build to complete the fibre network, in line with the Ready for Service definition, is blocked without a solution in place. Premises in this category should therefore be recorded in the Future_Technology columns. This is most likely to be caused by lack of 3rd party wayleaves, but could be as a result of other external blockers (which should be explained in supporting evidence and clarified in your use of the ‘LOC_Code’ column).

‘1. Awaiting HLD’ – High Level Design (HLD) has not yet been completed. ‘2. HLD complete’ – HLD/area level plan has been completed. However, Low Level Design (LLD) work has not yet been completed or is in progress. ‘3. LLD complete’ – LLD and survey work has been completed, however, subcontractors/build partners, or in-house resources to complete the network build, are still to be appointed. ‘4. Build team appointed’ – Subcontractors / build partners or if applicable in-house civil resource has been appointed and commissioned to start the network build in accordance with the LLDs. All the necessary planning, acquisitions and wayleave agreements are finalised to allow the network to be constructed. ‘5. In build’ – Network build is in progress, however premises are not yet able to take up a service. ‘6. RFS’ – Network build and end-to-end testing is complete and premises are RFS.

Funding Stage: The status of funding allocated to the UPRN. If your funding allocation is linked to your Delivery_Phase please reflect that in your data and explain in your Supporting Evidence Pack. The Scottish Government’s assessment of supplier returns will be based, in full, on the evidence requested in Annex C. As such, we cannot guarantee that we will accept how suppliers have categorised the status of their funding position.

Funding Stage Options:

‘1. No funding planned or committed’ - While you may be planning to deliver to this UPRN, the funding is not yet in place to do so and/or you are seeking funding. ‘2. Funding planned, but not committed’ - You have in principle funding agreed to deliver to this UPRN, but the funding is not immediately available, requires further decisions such as Board approval, or is dependent on (for example) performance metrics. ‘3. Funding committed’ - Funding has been identified and has been allocated to delivery of this UPRN. There are no further conditions around drawing down or using funding and the funding is ring-fenced solely for the delivery of associated premises. This should be explained clearly in your financial plan, which should be provided as part of your Supporting Evidence Pack.

Public Intervention:

Define if coverage has been or is planned to be connected using a public intervention. ‘Yes’ will be marked when a premises is dependent on funding from vouchers, GigaHubs, Superfast, LFFN, RGC, R100, SBVS or GIS Programmes, or when an existing service was built with funding from one of those Programmes. Any other public interventions (such as Local Authority schemes) should also be acknowledged and marked as a ‘Yes’ here. Further explanation should be referenced within your Supporting Evidence Pack. An entry of ‘No’ would indicate that the premises is planned to be built, or has already been built, entirely through commercial funding with no dependency on public intervention. Evidence of this funding should be provided in your Supporting Evidence Pack. Where you have indicated that a UPRN is dependent on public intervention by providing a ‘Yes’ in the ‘Public_Intervention’ column within your data coverage response; the approach by the Scottish Government is to provide a default Gigabit White determination to any planned build and to supersede this determination with project-specific intervention data as described in the OMR/PR - Subsidy Control Classification Guidance. Any current build would not usually undergo this same approach.

Public Intervention Type:

GIS (pre contract award)’ - Gigabit Infrastructure Subsidy, pre contract award; GIS (post contract award)’ – Gigabit Infrastructure Subsidy, post contract award for contracted and ‘Incidental Coverage’ premises, relevant only where you have secured a GIS contract. For a definition of Incidental Coverage premises, please refer to the instructions for completing the Financial Model in the ITT or contract; ‘Superfast’ – Coverage from the 2012 or 2016 National Broadband Scheme, including the Digital Scotland Superfast Broadband Programme (DSSB); ‘R100’ – Coverage planned or delivered via the R100 contracts; ‘SBVS (post approval)’ – voucher approved, not yet delivered; ‘SBVS (build complete)’ – voucher receipted, service delivered; ‘GBVS (pre request)’ – GBVS, before a Voucher has been requested;

‘GBVS (post request)’ – GBVS, after a Voucher has been requested / issued; ‘LFFN’ - Local Full Fibre Network; ‘GigaHubs’ – GigaHubs Project; ‘RGC’ – Rural Gigabit Connectivity. Additional public intervention types can also be provided, such as Local Authority funded schemes.

Public Intervention Reference:

GIS (pre contract award) – eg C0999, Lot 1;

GIS (post contract award) – eg C0999, Lot 1;

Superfast – Superfast Contract eg R100 North;

GBVS (pre request) – Gigabit Broadband Voucher Scheme ‘blank’ as no Voucher IDs available;

GBVS (post request) – Gigabit Broadband Voucher Scheme Voucher ID once requested and issued eg GV3NITM6;

SBVS (post requrest) – eg SBVS[UPRN]

GBVS PRP Reference:

Complete this field for all UPRNs with ‘Current_Technology’ or ‘Future_Technology’ where ‘Public_Intervention’ is ‘Yes’. Where an entry for both ‘Current_Technology’ and ‘Future_Technology’ is provided this entry will relate to the ‘Future_Technology’. This is a Gigabit Broadband Voucher Scheme voucher project reference, examples of field entries are as follows:

AA1001 (Pre BDUK Voucher Funding Platform), AB10000001 (Post BDUK Voucher Funding Platform)

LOC Code:

The following table of LOC Code types should be used when populating your LOC_Code column. If you believe you have a LOC type that is not covered here, please use the 15- OTHER code and add an additional ‘LOC_Code_Description’ column at the end of your data return to provide a free-text explanation of the non-standard issue you are experiencing.

If there is more than one reason that your build is on hold, please choose the primary reason for the build being on hold and consider adding further LOC_Code columns (e.g. ‘LOC_Code_1’, ‘LOC_Code_2’ and so on) to the end of your data return to provide a secondary, tertiary code etc if needed

loc_code: 1-JUP

LOC Type: Joint user pole

LOC Description: Joint user pole license unable to be obtained