Heat network connection requirements in local plan policy

Heat network connection planning policy usually bites in one of three ways: a requirement to connect to an existing network, a requirement to design the scheme so it can connect later, or a requirement to prove that neither is feasible. All three are settled at layout stage, because all three need plant space, a pipe route and a hydraulic design that a retrofit cannot conjure. Find out which one applies before the ground floor plan is fixed.

Why authorities ask for connection at all

A heat network only works financially if it has enough connected load. Authorities with a network in or near their area therefore use planning policy to protect the pipeline of future customers, and the requirement falls on development that happens to sit along the route.

The Energy Act 2023 created the framework for heat network zoning in England, with zone designation and connection duties to be set out in secondary legislation and a regulatory role for Ofgem. The regime is being brought into force in stages, so as at September 2026 the detail of what a zone requires of a given building is still being brought into force. Check the current position before you assume either a duty or a freedom.

London has run ahead of this. London Plan Policy SI 3 asks major development in a Heat Network Priority Area to have a communal low-temperature heating system, with the heat source chosen through a hierarchy that puts connection to a local existing or planned network first. Several authorities elsewhere have adopted similar wording in local plan energy policies.

Safeguarded routes and how zones are drawn

Look for three separate things in the development plan. A zone or priority area boundary. A safeguarded pipe route, sometimes shown on the policies map. And a policy that sets the test for schemes inside either.

Priority areas are usually drawn from heat density mapping, so they follow dense residential and mixed-use areas rather than administrative boundaries. A site can be inside a priority area with no network within a kilometre, which is exactly the situation where the connection-ready requirement applies instead of connection.

Safeguarded routes matter more than people expect. Building over one, or filling it with a basement or an attenuation tank, can generate an objection from the authority's own energy team late in the determination, and the fix is almost always a layout change.

Ask the authority directly, in writing, at pre-application stage: is the site in a zone or priority area, is there a safeguarded route across or adjacent to it, which network operator is relevant, and what has the authority secured on nearby consents. That last question is the useful one. Recent decisions nearby tell you what wording the officers will actually ask for.

What connection ready actually means

The phrase sounds soft. The engineering behind it is not.

• A plant room or energy centre space of stated area and head height, at a level and location a pipe can reach, usually at or near the site boundary closest to the route.
• Capped primary connection points brought to the site boundary, with valves, chambers and a recorded position.
• Space for a heat exchanger, thermal store and pumps, with access for replacement plant.
• Distribution designed for low-temperature operation, so emitters and pipe sizes suit flow temperatures a network can deliver.
• Hydraulic separation between the network side and the building side, so the building can run on its own interim heat source without redesign.

The last two are where schemes fail. A building sized around high-temperature radiators and an interim gas or air source system will not accept network heat without replacing emitters in every flat. If the policy says connection ready, the low-temperature design is the requirement, and the interim plant is the temporary part.

CIBSE and the Association for Decentralised Energy publish a code of practice for heat networks that authorities increasingly reference by name in conditions. Read it before you design the interface, not after.

The design consequences developers underestimate

Plant space is the obvious one. An energy centre takes ground-floor or basement area that would otherwise be lettable or saleable, needs ventilation, and produces a flue that has to go somewhere visible.

Then there is the riser strategy. Communal heating needs vertical distribution, insulated to limit standing losses, and heat interface units in each dwelling that need service access from common parts rather than through a bedroom. Retrofitting that into a stair core designed around individual boilers is expensive and sometimes impossible.

Overheating is the third. Communal distribution adds heat gain to corridors and cores, which feeds straight into the Overheating Risk Assessment under the CIBSE TM59 method and can push a scheme towards mechanical cooling it did not want.

An illustrative example. A 60-unit block on a corner site, inside a priority area, with the network 400 metres away and a delivery date two years after practical completion. The workable answer is a low-temperature communal system with an interim heat pump plant room, capped connections to the boundary, and a section 106 obligation to connect within a defined period of the network becoming available. The figures and timescales here are illustrative.

Securing the obligation and choosing the trigger

Connection is usually secured by planning obligation rather than by condition, because it involves an act by a third party and a payment. The drafting points that matter are the definition of availability, the notice period, the cap on cost, and what happens if the network never arrives.

Resist an unqualified obligation to connect. A well-drafted clause ties the duty to the network being available within a stated distance and at a stated point, within a stated period, on terms that are not materially worse than the alternative. Without those qualifications you have signed up to an open-ended liability priced by a monopoly supplier.

Where the requirement is connection ready only, a condition can work: approval of a connection strategy before superstructure, and evidence of installed capped connections before first occupation. Keep the discharge evidence, because a purchaser's solicitor will ask for it.

Making the feasibility and viability case

Some sites genuinely cannot connect. The argument has to be evidenced rather than asserted, and it belongs in the Energy Statement alongside the rest of the energy strategy.

Set out the distance to the nearest network, the operator's published or written position on capacity and timing, the route and its constraints, the capital cost of connection with its source, and the comparison with the alternative low-carbon system on both carbon and cost. Where cost is the obstacle, the argument moves into viability territory and needs to be run properly through a Viability Assessment rather than as a line in the energy chapter.

Officers are sceptical of feasibility studies commissioned to reach a predetermined answer, and they are right to be. A study that concludes connection is not viable, but shows the scheme designed to accept it later, is far more persuasive than one that rules out the network entirely. The assumptions behind the modelling get tested too, and the note on energy modelling assumptions officers challenge sets out which ones attract attention.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.

Draft your energy and sustainability documents on PlanScope, then have the network interface checked by your building services engineer.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.