How a planning officer report is structured

Read the recommendation first, then the conditions, then the planning balance. Everything else in a planning officer report is the working that supports those three, and reading in that order tells you within five minutes whether the case is won, lost or still moving. The planning officer report structure is broadly consistent across England because it has to discharge the same statutory duties wherever it is written, whether the decision is delegated or goes to committee.

The report is also the document that gets tested. On appeal it is the authority's starting position. On judicial review it is the evidence of how the decision maker reasoned. Officers write with both in mind.

The sections a report almost always has

A typical report runs in a fixed order. Application details and the recommendation, then the site and its surroundings, then the proposal. Relevant planning history follows, then consultation responses from statutory and non-statutory consultees, then representations from neighbours and interested parties. After that comes the development plan and other material considerations, the assessment broken into topic headings, the planning balance, and finally the recommendation restated with conditions or reasons for refusal appended.

Committee reports add a front sheet with the ward, the case officer, the applicant, the recommendation and often a summary of why the application is before members rather than being determined under delegated powers.

Appendices vary. Some authorities append the full consultee letters. Others summarise and hold the originals on the register, which is one reason to check what should be published there. Our note on the statutory planning register covers what the authority is obliged to make available.

Why the conditions repay reading before the assessment

Conditions tell you what the officer thinks is unresolved. A condition requiring a detailed drainage scheme before development starts means the drainage case has not been made on the submitted information. A condition requiring materials samples means the elevations are accepted in principle but not in detail. A Grampian condition requiring works on land outside the application site means a third party consent is still outstanding.

The six tests in national guidance apply to every one of them: necessary, relevant to planning, relevant to the development, enforceable, precise and reasonable in all other respects. A condition that fails any of those tests is a point worth making before the decision rather than after, because a badly drafted condition is expensive to discharge and hard to vary.

Count the conditions that bite before development starts. Each one is a delay, and the applicant's written agreement is needed before most of them can be imposed.

How consultee responses are summarised

The summary is the officer's, not the consultee's. That matters when a highway authority sends a two page letter raising three concerns and requesting further information, and the report records it as no objection subject to conditions.

Read the summary against the original wherever the point is contested. A holding objection, which asks for information before the consultee can take a position, is not the same as a resolved objection, and the distinction sometimes blurs in the drafting.

Representations are summarised too, usually with a count and a list of themes. Where amended plans have been received, check whether a further consultation round ran and whether the report says so. The rules and the practical consequences are set out in our piece on re-consultation after amended plans.

The policy section and what it has to contain

Section 38(6) of the Planning and Compulsory Purchase Act 2004 requires the determination to be made in accordance with the development plan unless material considerations indicate otherwise. The report therefore has to identify the development plan correctly: the adopted local plan with its date, any adopted neighbourhood plan, and any remaining saved policies from an earlier plan.

Weight is the live issue. Where a policy is out of date, or where an emerging plan is at examination, the report should say what weight is being given and why. Emerging plan weight turns on the stage reached, the extent of unresolved objections and the degree of consistency with national policy.

The National Planning Policy Framework is a material consideration rather than part of the development plan. The current Framework was published on 17 August 2026 and is organised by policy codes rather than the paragraph numbers used in the December 2024 edition, so a report that still cites old paragraph numbers is either working from a superseded copy or quoting an older document. Check the edition cited before relying on a paragraph reference in your own submission, and verify it against the published Framework.

Statutory duties recorded on the face of the report

Several duties have to be discharged expressly, and the report is where that is evidenced.

A recital that a duty has been considered, with nothing showing how, is the classic weakness. Where a listed building is affected, look for the words that record the statutory weight rather than a general balancing exercise, because the courts have treated the section 66 duty as demanding more than ordinary weight.

The planning balance

This is the section that decides the case. It should identify the harms, identify the benefits, attach weight to each, and reach a conclusion.

Two versions exist. The straightforward one applies where the plan is up to date and the proposal accords with it. The other applies where the most important policies for determining the application are out of date, or where the authority cannot demonstrate its housing land supply, and national policy then directs a tilted balance in favour of granting permission unless the adverse impacts would significantly and demonstrably outweigh the benefits when assessed against the Framework as a whole.

Check which balance the officer has applied and whether the trigger for it is correctly stated. Getting that wrong is one of the more common grounds on which decisions are challenged.

Where the authority is both applicant and decision maker, the balance attracts extra scrutiny, and the procedural safeguards are worth knowing: see our note on applications made by the council on its own land.

Errors worth raising before the meeting

Raise factual errors in writing, to the case officer, with the correction and the source, and copy the committee clerk where the item is going to members. Do it early enough for an update sheet to be produced.

The corrections that change outcomes are narrow. A misdescribed site area. A policy quoted from a superseded plan. A consultee position misreported. A distance to a listed building stated wrongly. A missing planning history entry that establishes a fallback position. Those are worth a letter.

Disagreements about weight are not errors, and a letter arguing that the officer has undervalued a benefit rarely moves a recommendation. It may still be worth making the point for the record, because the appeal statement will build on it.

A well drafted Planning Statement submitted with the application reduces the risk of all of this, because it gives the officer the policy structure, the history and the balance in a form the report can follow. Officers under time pressure tend to write around the best structured document in the file.

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

Enter your postcode on PlanScope to see which supporting documents your application is likely to need. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.