NESOOFGEMDESNZ
feed

Heat Pump Ready Programme Round 2: innovation funding competition

DESNZ·funding_competition·LOW·21 Apr 2026·source document

Summary

Heat Pump Ready Programme Round 2 innovation competition. Targets capital cost, space requirements and install time as barriers to uptake.

Why it matters

Heat-policy innovation funding. Sits within the consumer-transition workstream rather than the generation or network layer.

Key facts

  • Round 2
  • Innovation funding

Areas affected

heat pumpsheat policy

Related programmes

Heat Pump Ready
Memo3,774 words

The Heat Pump Ready Programme innovation funding competition will support applied research and development projects. The programme supports developing and bringing forward innovative technologies focusing on overcoming the following identified barriers to heat pump uptake: capital cost of heat pump system hardware and components in property changes required internal and external space requirement time taken for heat pump install from accepted quote Eligibility Please refer to the competition guidance which contains a comprehensive list of eligibility requirements. Eligibility requirements include: your application must indicate which of the following barriers your project will address: capital cost of heat pump system hardware and components in‑property changes required for heat pump installations internal and external space requirement for heat pump installations time taken for heat pump install from accepted quote if your innovation affects energy performance, it must achieve a seasonal performance factor of at least 3.5 in a real-world home environment by the end of the project your project must be genuine R&D/innovation, not already commercially deployed in the UK, with private match funding, UK-based delivery/benefits, a grant request of £200k to £2 million, agreement to the terms, delivery to the programme timeline, the right team set-up, and six‑monthly stage gate reviews Online launch event To find out more about the application process and details of how to apply, register for our online competition launch event by 1pm on 5 May 2026 . The competition launch event will take place at 4pm on 6 May 2026 . How to apply Read the competition guidance for information about how to prepare your application. The deadline to submit applications is 1pm on 25 June 2026 . The portal link will be available from Friday 24 April 2026. Only applications received via the portal will be valid. A list of clarification questions will be published shortly after the competition launch. The deadline for submitting questions regarding the competition is 14 May 2026 . Please email your questions to heatinnovation@energysecurity.gov.uk . ### Front Sheet | | | | | | | | | | | | | | | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | | Declaration 4: The General Data Protection Regulation | | | | | | | | | | | | | | | Assurance Questionnaire for Contractors | | | | | | | | | | | | | | | | | NOTE: To complete your application for Heat Pump Ready (HPR) Round 2 - Innovation Funding Competition (IFC), you must download, complete and sign where relevant and upload the document to the online application form. | | | | | | | | | | | | Name of Organisation: | | | | | | | | | | | | | | | Name: | | | | | | | | | | | | | | | Position: | | | | | | | | | | | | | | | Email: | | | | | | | | | | | | | | | Declaration: | | Select | | | | | | | | | | | | | I certify that this questionnaire has been completely accurately on behalf of the organisation. | | x | | | | | | | | | | | | ### GDPR Assurance Questionnaire | | | | | | | | | | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ASSURANCE QUESTIONNAIRE FOR | | | | | | | | | | CONTRACTORS | | | | | | | | | | Instructions: For every statement on the left, please select which status applies to your organisation | | | | | | | | | | by using the drop-down options in the 'status' column | | | | | | | | | | Documentation: Information you hold | | | | | Status | | | | | Your business has conducted an information audit to map data flows. | | | | | | | | | | Your business has documented what personal data you hold, where it came from, who you share it with, and what you do with it. | | | | | | | | | | NOTE: You may be required to make these records available to the Information Commissioner's Office (ICO) on request. | | | | | | | | | | Accountability & Governance | | | | | Status | | | | | Your business has an appropriate data protection policy | | | | | | | | | | Data Protection Officer (DPO) | | | | | Status | | | | | Your business has nominated a data protection lead or Data Protection Officer (DPO). | | | | | | | | | | Information Risks & Data Protection Impact Assessments | | | | | Status | | | | | Your business manages information risks in a structured way so that management understands the business impact of personal data related risks and manages them effectively. | | | | | | | | | | Data Protection by Design | | | | | Status | | | | | Your business has implemented appropriate technical and organisational measures to show you have considered and integrated data protection into your processing activities. | | | | | | | | | | Training & Awareness | | | | | Status | | | | | Your business provides data protection awareness training for all staff. | | | | | | | | | | Operational Base | | | | | Status | | | | | If your business operates outside the EU, you have appointed a representative within the EU in writing. | | | | | This is not applicable to the organisation. | | | | | Breach Notification | | | | | Status | | | | | Your business has effective processes to identify, report, manage and resolve any personal data breaches. BEIS must be notified within 48 hours about any breaches involving personal data being processed on our behalf. | | | | | | | | | | Individual Rights: Right of Access | | | | | Status | | | | | Your business has a process to respond to a data controllers request for information (following an individuals' request to access their personal data). | | | | | | | | | | Right to Rectification & Data Quality | | | | | Status | | | | | Your business has processes to ensure that the personal data you hold remains accurate and up to date. | | | | | | | | | | Right to Erasure including Retention & Disposal | | | | | Status | | | | | Your business has a process to routinely and securely dispose of personal data that is no longer required in line with agreed timescales as stated within the terms and conditions. | | | | | | | | | ### Sheet1 | This will be implemented by time of contract award. | | | | | | | --- | --- | --- | --- | --- | --- | | This will NOT be implemented by time of contract award. | | | | | | | This is not applicable to the organisation. | | | | | | ### Guidance | | Guidance | | | | --- | --- | --- | --- | | | This template is for applicants to the Heat Pump Ready Programe to demonstrate the risks they anticipate facing in the delivery of their innovation project should they be successful in obtaining government funding through the Programme's competition. | | | | | Column Structure | | | | | What do the different colours mean? | Green = on track Amber = at risk Red = off track / needs urgent action. | | | | Risk Owner(s) | Enter the name(s) of the team member(s) best placed to own and manage the risk. Top Tip: Where there is dual ownership for a risk, select one person who is responsible for making updates and consulting the other person(s) in each reporting round to minimise confusion around accountability (e.g. by highlighting their name in bold). | | | | Short Name | Enter a very short title for the risk that summarises the detailed Risk Description so that the risk can be easily located in future. | | | | Mitigating Actions | Enter a summary of the mitigation(s) for the risk. If there is more than one, use numbering convention "a) b) c)" etc for each action and give an owner and estimated due date for each. | | | | Mitigation RAG | Enter a confidence rating for the mitigation(s). This can be relatively subjective but you should ideally consider 1) your confidence that the mitigation(s) will be delivered on time and 2) your confidence that the mitigation(s) will adequately mitigate the risk when selecting a rating. | | | | Latest Update/ Comment | Enter detail to explain the current risk rating and mitigation RAG selected and to explain any change that has (or hasn't) taken place in this reporting round. | | ### Risk Log | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Project Title: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lead Organisation: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Risks & Mitigations Log | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Risk Details | | | | | | | | | | | | | | | | Mitigation Details | | | | | | Risk Ratings: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Approach: | | | | Mitigation Ratings: | | | | | | | ID | Level | Risk Owner(s) | Short Name | Risk Type/ Category | Risk Description Use definition convention "There is a risk that… This could be caused by… This could lead to…" | Initial/ Unmitigated Rating | Target Rating | Approach / Status | Current Rating | Proximity | Expiry | Reason for Escalation | Date Raised | Date Closed | Reason for Closure | Mitigating Actions Use numbering convention "a) b) c)" etc for each action and give an owner and estimated due date for each | Mitigation RAG | Latest Update/ Comment | Extra Detail | Team/ Other Comments | Drop-down Menu Options: | Very High Impact / Very Likely (>90%) | Very High Impact / Likely (65-90%) | Very High Impact / Possible (35-65%) | Very High Impact / Unlikely (10-35%) | Very High Impact / Very Unlikely (<10%) | High Impact / Very Likely (>90%) | High Impact / Likely (65-90%) | High Impact / Possible (35-65%) | High Impact / Unlikely (10-35%) | High Impact / Very Unlikely (<10%) | Medium Impact / Very Likely (>90%) | Medium Impact / Likely (65-90%) | Medium Impact / Possible (35-65%) | Medium Impact / Unlikely (10-35%) | Medium Impact / Very Unlikely (<10%) | Low Impact / Very Likely (>90%) | Low Impact / Likely (65-90%) | Low Impact / Possible (35-65%) | Low Impact / Unlikely (10-35%) | Low Impact / Very Unlikely (<10%) | Very Low Impact / Very Likely (>90%) | Very Low Impact / Likely (65-90%) | Very Low Impact / Possible (35-65%) | Very Low Impact / Unlikely (10-35%) | Very Low Impact / Very Unlikely (<10%) | Closed: Realised | Closed: Mitigated | Closed: Expired | Closed: Merged | | Treat (Mitigate) | Tolerate | Closed | | R | A/R | A | A/G | G | C | | R01 | | | | | There is a risk that: [text] This could be caused by: [text] This could lead to: [text] | Medium Impact / Unlikely (10-35%) | Medium Impact / Very Unlikely (<10%) | Accept | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | High Impact / Possible (35-65%) | Medium Impact / Unlikely (10-35%) | Accept | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | High Impact / Possible (35-65%) | Medium Impact / Unlikely (10-35%) | Accept | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Possible (35-65%) | Low Impact / Unlikely (10-35%) | Accept | Medium Impact / Very Likely (>90%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Very High Impact / Likely (65-90%) | High Impact / Unlikely (10-35%) | Accept | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Very High Impact / Likely (65-90%) | High Impact / Unlikely (10-35%) | Accept | High Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Possible (35-65%) | Low Impact / Possible (35-65%) | Accept | Medium Impact / Possible (35-65%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Accept | High Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Low Impact / Likely (65-90%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Possible (35-65%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Low Impact / Likely (65-90%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Low Impact / Likely (65-90%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Accept | Medium Impact / Likely (65-90%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Medium Impact / Unlikely (10-35%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Accept | Medium Impact / Possible (35-65%) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |