Chirpy Heat Conference 2025: Insight & Action for Regulation
Is your compliance journey sorted or a struggle?
Full Ofgem regulations are being rolled out for of all heat networks across the UK. This means big changes for housing providers operating heat networks. Here at Chirpy Heat we are here to help you kickstart your compliance journey.
Unless you have been well insulated from it over the last couple of years, you’ll have heard Ofgem is becoming the regulator for heat networks in the UK. This means heat networks will be regulated in line with gas and electricity suppliers and, from January 2026, existing and new heat networks will start to become subject to a wide range of requirements including around consumer protection and performance standards.
Specifically there will need to start reporting on network, portfolio, financial, management and performance data.
Chirpy Heat is offering a four-step Regulation Rollout as a way to quickly get up to speed and get your compliance on track. We’ll support you from the first steps of establishing where you sit against new requirements all the way through to helping get you right up to speed with the compliance changes. We’ll then stay on hand with expert input while you navigate this evolving, complex landscape. Let’s have a closer look at the details of Regulation Rollout’s four key steps:
1 Regulation Readiness Review
Many housing providers are not compliant with regulations and are struggling to understand what these regulations mean for them.
The Regulation Readiness Review answers the question of where you are on the journey to regulatory compliance. It delivers a full assessment of your current and future regulatory position which will be outlined in a report alongside a focused action plan.
The service ensures you have full visibility and understanding of your governance and compliance risk and the actions you are taking to manage this.
2 Compliance Plan
Now that heat network compliance is due, Chirpy Heat will take the review of your regulation readiness and transform it into a strategic compliance plan for managing the required changes.
This means you receive a detailed compliance action plan, including key stages of preparation, transition and ongoing compliance. It will set out regulatory milestones and target dates as well as roles and responsibilities, interdependencies and considerations for your organisation.
3 Heat Network Training
Your comprehensive compliance plan is in place, now it’s time to elevate your team’s knowledge and understanding of heat networks, Chirpy Heat offers two government-funded courses – one on the practical elements of running heat networks and a second on the strategic approaches to future proofing heat networks. The latter, importantly, also covers achieving and maintaining compliance.
Both courses are suitable for building capacity at all levels of your organisation, be it operational teams, board level or contractors. They are perfect for supporting the development and implementation of your compliance plan, and each are fully government funded meaning they come at no cost to you.
4 Expert Partner in the Room
The picture of the new regulations is complex and evolving so Chirpy Heat’s expert consultants will stay on hand, including attending internal meetings, to provide updates on timeframes and requirements. They will also be available to input on heat network management, workflows, risks and funding, and can provide written regulation briefings and bespoke training/ updates.
Your expert partner will continue to boost your organisations’ heat network knowledge, understanding and capacity. We can be in the room for key meetings with stakeholders, board meetings, discussions with contractors, or generally there to support you in managing heat networks and delivering key messaging.
If you know Chirpy Heat already, you’ll know we live and breathe heat networks and love helping get them the best they can be. We’re excited to support new and existing clients thrive as they move forward with meeting new regulations.
Get in touch at [email protected] to discuss how we can support your journey.
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager