How officers weigh carbon in a committee report

Greenhouse gas emissions are a material consideration in a planning decision, and the weight given to them is a matter for the decision maker rather than something fixed by national policy. That is the sentence that explains almost every committee report you will read on the subject. There is a statutory duty on plan making, there is policy support for mitigation, and there is no national numerical test an applicant either passes or fails. Understanding the carbon material consideration weight an officer can realistically give your scheme tells you how to write the submission.

Where the statutory hook sits

Three provisions do the work.

Section 19(1A) of the Planning and Compulsory Purchase Act 2004 requires development plan documents to include policies designed to secure that the development and use of land contributes to the mitigation of, and adaptation to, climate change. That duty is on the plan maker, and it is the reason local plans contain carbon policies at all.

Section 38(6) of the same Act requires determination in accordance with the development plan unless material considerations indicate otherwise. Section 70(2) of the Town and Country Planning Act 1990 requires regard to the plan and to other material considerations. Carbon sits in the second category where the plan is silent, and in the first where the plan has a policy.

The Climate Change Act 2008 sets the national net zero target. It is not a development management test, and an officer who treats it as one is open to challenge. Its practical role is to establish that carbon is capable of being material, which has not been seriously disputed for years.

How carbon enters the planning balance

An officer has to do two things: identify the carbon effects, and give them weight.

Identification is easier than it sounds when the applicant has quantified the effects. Operational emissions from the energy strategy, embodied emissions from materials and construction, transport emissions from the location and the travel offer, and emissions or sequestration from land use change all belong in the assessment.

Weight is where reports diverge. Where the adopted plan has a specific policy with a numerical requirement, the weight is high because the policy is the test. Where the plan has only a general aspiration, the weight an officer can give is correspondingly lower, and a refusal based on it alone is difficult to defend at appeal.

National guidance on climate change in the Planning Practice Guidance is the usual citation. Note the position on local energy efficiency standards, which has been constrained by ministerial statements, with the result that some plan policies seeking standards above the Building Regulations have limited practical effect. Check the current position before relying on such a policy either way.

Quantified against unquantified claims

An officer can weigh a number. An officer cannot weigh an adjective.

Submissions that assert a scheme is low carbon, sustainable or exemplary without a calculation produce committee reports that record the claim and move on. Submissions that give a regulated emissions figure, a percentage improvement over the notional building, an embodied carbon figure per square metre and a stated methodology produce reports that engage with the numbers.

Three habits improve the engagement:

1. State the methodology and its version, whether that is the national calculation methodology for operational energy or a recognised whole life carbon standard for embodied emissions.
2. Give the baseline explicitly. A percentage improvement is meaningless without the baseline it improves on, and baselines are where most confusion starts, as our note on the notional building and why baselines confuse officers explains.
3. Separate what is secured by the application from what is aspiration. Officers discount aspiration heavily and correctly.

A Whole Life Carbon Assessment and an Energy Statement covering those points give an officer something to put in the balance rather than something to summarise.

The limits of what a condition can secure

Conditions have to be necessary, relevant to planning, relevant to the development, enforceable, precise and reasonable. Carbon conditions fail on enforceability more often than on anything else.

A condition requiring a scheme to achieve a stated regulated emissions reduction is enforceable, because the as-built compliance evidence exists. A condition requiring the development to be net zero in operation is usually not, because the term has no agreed definition and the authority cannot measure compliance.

Monitoring is the other weakness. A condition requiring annual reporting of operational energy use for fifteen years is precise and unenforceable in practice, because no authority has the resources. Where ongoing performance matters, a section 106 obligation with a named reporting format and a default mechanism is the better instrument.

Outline applications create their own difficulty, since the carbon case has to be made before the buildings are designed. Our note on carbon reporting in an outline planning application sets out how to frame commitments at that stage.

Objections framed on carbon

Carbon objections come in three shapes, and they have different prospects.

The first argues that the scheme fails a specific adopted policy. That is the strongest form, and the answer is a calculation showing compliance or a case for why the policy should be outweighed.

The second argues that greenfield development is inherently more carbon intensive than brownfield because of transport emissions. That is a genuine point and it is usually already reflected in the plan's site selection, so the answer is to show the plan context and the travel offer.

The third argues that the development is incompatible with the national net zero target. Officers generally record this and give it little weight, because the Act does not operate as a development management test and because the cumulative national target cannot be apportioned to one application.

Reasons for refusal citing carbon

Refusals that rest on carbon alone are uncommon and they tend to arise in two situations: a clear breach of a numerical plan policy, and an EIA development where the environmental statement failed to assess emissions properly.

The assessment point has grown teeth. The Supreme Court decision in R (Finch) v Surrey County Council confirmed that an environmental statement must address effects that are reasonably foreseeable consequences of the development, which has pushed scope and boundary questions to the front of carbon chapters. Where a scheme is EIA development, scope the carbon chapter generously and explain any exclusion.

Where carbon appears as a secondary reason alongside others, it rarely drives the appeal outcome but it does shape the inspector's view of the applicant's evidence.

Drafting to meet the point

Write the carbon case as a short, numbered section that an officer can paste into a report with attribution. That sounds cynical and it reflects how committee reports are actually produced.

Give the policy, the figure, the methodology, the baseline, the comparison and the mechanism by which it will be secured. Acknowledge one weakness honestly rather than claiming none, because an officer who finds an unacknowledged gap discounts the whole document. Then make sure the drawings, the energy model and the materials schedule say the same thing as the statement.

Draft the energy and carbon documents for a scheme with PlanScope and send them for professional review before submission. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.