Post-occupancy reporting conditions on major schemes

A post-occupancy energy monitoring condition asks you to measure what a building actually uses once people are in it, and to send those figures to the council for a set number of years. The London Plan requires major development to monitor and report energy performance, and authorities outside London increasingly copy the approach. The part that catches schemes out is not the reporting. It is that the reporting depends on a metering strategy that had to be fixed at design stage, long before anyone read the condition carefully.

Retrofitting sub-meters into a completed block to satisfy a condition costs more than installing them would have, and sometimes it is not possible at all.

What the obligation usually asks for

The standard shape has three reporting points. A prediction at planning stage, based on a modelled estimate of operational energy. An as-built figure once the building is complete, reflecting what was actually installed rather than what was consented. Then measured in-use data, submitted annually, typically for five years from first occupation.

The metrics are normally annual energy use intensity in kWh per square metre of gross internal area, along with regulated and unregulated consumption split out, on-site generation, and carbon emissions derived from the current grid factor. Where a heat network serves the site, network level generation and distribution losses are usually reported separately, because that is where the heat network connection requirement tends to underperform the design case.

Some authorities also ask for occupancy data, so consumption can be normalised. Be careful what you agree to here, since occupancy figures for a residential block are harder to collect honestly than they look on paper.

For commercial buildings the reporting is usually easier and more revealing, because a single occupier holds the meters and the facilities team already tracks consumption. For build to rent and student accommodation the landlord holds almost everything, which makes reporting straightforward and the results uncomfortable, since communal heating losses show up plainly. For a mixed tenure block sold to individual owners, reporting quality drops sharply after the management company changes hands.

Metering has to be decided at design stage

This is the section to read before signing the planning conditions. An energy reporting duty is only deliverable if the building meters what the duty describes.

That means end use sub-metering for heating, hot water, lighting, small power and any communal plant, with landlord supplies separated from tenant supplies, and generation metered at the inverter rather than inferred. Communal heat metering needs to distinguish generation, distribution losses and delivered heat, or the reported efficiency is a guess. Where a scheme has commercial units at ground floor and residential above, the split has to be physical rather than apportioned.

Get the metering schedule into the Energy Statement at application stage and cross-reference it in the condition wording. A condition that says report energy use, against a building whose landlord supply lumps lifts, corridor lighting and the commercial units together, produces a number nobody can act on.

Two further details are worth fixing early. Decide how the data leaves the building, because manual meter reads across five years will not happen and an automatic meter reading system with a data logger will. And decide who holds the data contract, since a monitoring platform paid for by the contractor tends to stop at the end of the defects period, roughly four years before the last report is due.

The performance gap, presented honestly

Buildings use more energy in operation than compliance modelling suggests. That is well established and it is mostly not a scandal, because the Part L calculation is a regulated comparison with fixed assumptions about occupancy, hours and small power, and was never meant to predict a bill.

The defensible approach is to publish a realistic operational prediction at design stage, using an appropriate industry method, alongside the compliance figure, and to make clear which is which. Then the in-use report compares like with like. Where the measured figure still exceeds the prediction, say why: commissioning issues, controls set to manual override, higher occupancy, a heat network running at a flow temperature nobody dropped after handover.

A report that explains an overshoot reads as competent. A report that quietly compares against the compliance figure and declares success reads as evasive, and officers who have seen a few of them notice.

Residential data and what you cannot collect

Consumption data for an individual dwelling is personal data and belongs to a relationship between the occupier and their supplier. A developer or managing agent cannot simply harvest it because a planning obligation says so.

Scope the obligation to what the landlord controls: communal plant, landlord supplies, generation, and any heat network delivering metered heat. Where dwelling level reporting is wanted, the workable route is an opt-in through the managing agent, with aggregated and anonymised reporting, and the obligation should say that anonymised aggregation is acceptable. Agree that at drafting stage. Arguing it in year three, with a resident association copied in, goes badly.

Enforcement and why the instrument matters

A condition is enforceable by a breach of condition notice, but it attaches to the permission and the practical difficulty is identifying who is now responsible. Five years after occupation the developer has usually sold, and the management company may not know the condition exists.

An obligation under section 106 binds the land and is enforceable against successors in title, which is why authorities that intend to follow up use a deed. The deed should name the reporting party by role rather than by company, state the format, give a submission date each year, and set a clear end date. It should also say what happens when a building changes hands, because the handover of the reporting duty is the point at which most monitoring quietly stops.

Negotiating something you can actually deliver

Reporting obligations fail for practical reasons far more often than for bad faith. The building changes hands, the monitoring platform licence lapses, the person who understood the meter schedule leaves, or the obligation asks for a metric the building never measured. All four are foreseeable at drafting stage, and fixing them there costs almost nothing.

Three moves usually improve the drafting without weakening it. Tie the reported metric to meters that exist on an approved metering schedule. Set the first in-use report at a fixed period after practical completion rather than after first occupation, so a slow sales rate does not create an impossible deadline. And put an end date on the obligation rather than leaving it open.

One honest uncertainty: nobody has settled what a council should do with the data once it arrives. Some authorities publish anonymised results, others file them. That is worth asking at pre-application, because a scheme reporting into a published dataset needs a different internal sign-off from one reporting into a filing cabinet.

Draft the supporting evidence base with PlanScope, from the Sustainability Statement to the Whole Life Carbon Assessment, and review the outputs with your energy consultant before submission. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. This is general guidance, not legal advice, so check the position with your local planning authority or a qualified professional before relying on it.