Heat networks regulation: regular data reporting guidance

This consultation closed with a decision on 10 March 2026, so I'll note that the deadline has passed and frame the memo as a record of what was consulted on. The source text is mostly Ofgem's web furniture rather than the substantive guidance, so I'll work from what's there and flag the limits.

---

What this is about

Ofgem is consulting on the data heat network operators and suppliers must report once authorisation under the new regulatory regime takes effect. It follows the authorisation and regulatory oversight consultation of 7 November 2024 and the decision of 8 August 2025, and it sits alongside the Fair Pricing Protections work. The earlier documents set the rules: who must be authorised, what consumer protections apply, how pricing is overseen. This one builds the instrument that lets Ofgem see whether any of it is happening. Regular data reporting is the monitoring layer underneath the consumer protection framework.

The guidance covers three things: the specific data points operators must submit, which segments of the market have to report, and the reporting periods and submission timings. The consultation closed on 13 January 2026 and Ofgem published its outcome on 10 March 2026, so this is now settled rather than open. Ofgem reports that stakeholders were broadly supportive and that the heaviest feedback landed on backdating and on the individual data points; the final guidance was amended to reflect that. The substantive content of those data points is in the linked guidance document, which is not reproduced in the source text here, so the detail below describes the structure of the regime rather than the field-level requirements.

The economic question sits underneath the administrative one. Reporting requirements are a fixed compliance cost, and fixed costs fall hardest on small operators. A heat network serving a single block of flats and a national energy services company face the same reporting schema unless Ofgem segments the obligation by size. How that segmentation is drawn, and how far back operators must reconstruct data they were never previously required to keep, determines whether reporting is a routine submission or a barrier that pushes small schemes towards consolidation or exit.

Options on the table

The source text does not set out discrete numbered options, but two design choices carried the bulk of stakeholder feedback and represent the live trade-offs in the guidance.

Backdating of reported data

Backdating asks operators to report historic data from before the reporting regime began. The case for it is that Ofgem starts with a market picture rather than a blank sheet, which matters when the whole point of the regime is consumer protection and you want to catch existing bad practice rather than only future practice. The case against is that operators were under no obligation to collect this data to a defined standard, so reconstructing it is costly, and the cost is heaviest for exactly the smaller and older schemes whose records are weakest. Ofgem says it received the most feedback here and changed the final guidance in response, which points to operators pushing back on the reach of the backdating requirement and Ofgem softening it. The loser if backdating is aggressive is the small legacy operator; the loser if it is light is the consumer whose past treatment stays invisible.

Granularity and scope of the individual data points

The second contested choice is how many data points to require and how finely defined each one is. More fields and tighter definitions give Ofgem a richer, more comparable market view and a stronger basis for enforcing fair pricing protections. They also raise the per-submission cost and the risk of inconsistent interpretation across thousands of operators of very different sophistication. The segmentation question, which operators must report which fields, is the lever that manages this: a tiered schema lets Ofgem demand more from large suppliers and less from small ones. The winners from a heavy schema are Ofgem's analytical function and, indirectly, consumers on poorly run networks; the losers are small operators and their billing and metering agents, who carry the data-assembly burden.

Questions being asked

The source text does not reproduce the numbered consultation questions; those sit in the draft guidance and the online consultation form, which are not included here. From the structure Ofgem describes, the questions cluster under three themes.

The data points themselves

Whether each proposed field is necessary, clearly defined, and capable of being reported consistently. (This is where operators argue a field is ambiguous, duplicative, or disproportionately expensive to produce relative to what it tells Ofgem.)

Reporting segments

Which categories of organisation must report, and whether the obligation is correctly tiered by size or type. (The real question is whether small operators are carved out or given a lighter schema, and where the threshold sits.)

Periods, timing, and backdating

The reporting frequency, submission deadlines, and how far back historic data must go. (Backdating is the contested element: how much retrospective reconstruction is proportionate.)

To see the exact questions, consult the draft guidance and the online consultation linked from the Ofgem page.

How to respond

This consultation is closed. It opened on 17 November 2025, closed on 13 January 2026, and Ofgem published its outcome on 10 March 2026 with the status "Closed (with decision)." There is no live response route.

For the settled position, read the final "Heat networks regulation: regular data reporting guidance" and the full outcome, both linked from the consultation page. Operators preparing to comply should work from the final guidance, not this consultation draft, since the data points and the backdating approach were amended after stakeholder feedback. Anyone wanting to understand how this fits the wider regime should also read the Authorisation and Oversight Decision (8 August 2025) and the Fair Pricing Protections response, which this reporting guidance is built to serve.