Design codes and design review panels in decisions

A design review panel is advisory. A design code, once adopted, is not. That single distinction explains most of what happens to a scheme as it moves through a council's design process, and architects who understand it early stop treating panel comments as instructions and start treating the code as the thing to design against.

Both sit under the same national framework. The National Design Guide sets out ten characteristics of well-designed places, and the National Model Design Code gives councils a method for turning those characteristics into local, mapped, measurable rules.

Why councils adopt design codes and how they gain weight

A design code converts general policy into specific instruction: block sizes, frontage types, building lines, storey heights, materials palettes, boundary treatments, street sections, parking arrangements, tree planting rates. It replaces "development should respect local character" with a drawing and a number.

Weight depends entirely on status. A code adopted as part of the development plan, whether in a local plan, an area action plan or a neighbourhood plan, carries the full force of section 38(6) and the determination has to be made in accordance with it unless material considerations indicate otherwise. A code adopted as a supplementary planning document is a material consideration and can carry substantial weight, but it cannot introduce new policy or contradict the adopted plan.

The Levelling-up and Regeneration Act 2023 made provision for design codes covering an authority's area. As at September 2026, check the commencement position and any regulations before assuming a code is mandatory in the district you are working in.

Read the code's own status page before you design to it. If it was consulted on but never adopted, it is a draft, and its weight is a matter of argument rather than a given.

What a design review panel does

A panel is a group of built environment professionals, usually independent of the council, who review schemes and give written advice. They are not decision makers. The report goes to the case officer, and the officer decides how much weight to give it.

Referral is usually triggered by scale, prominence or sensitivity, and the thresholds are set locally. Major applications, tall buildings, sites in conservation areas and schemes in a designated regeneration area are the common triggers. Some authorities require a panel review before a major application is validated. Others make it a recommendation at pre-application stage.

Panels charge. The fee is set by the panel or the council and normally reflects the size of the scheme and whether the review is a single session or a series, so budget for more than one appearance on a large scheme.

How the panel report is used

The report is published, and it becomes part of the application file. Objectors read it. Members read it. An inspector at appeal will read it and will notice whether the applicant responded to the criticisms or ignored them.

That is the practical point. A panel report identifying three concerns, followed by a submission that addresses two and is silent on the third, hands the officer a ready-made reason for refusal. Answering a comment by explaining why the panel was wrong is entirely acceptable, provided the reasoning is on paper.

Ask for a second review where the scheme has changed materially in response. A short follow-up note from the panel confirming that the concerns have been met is one of the more useful documents you can put in front of a committee.

Panels vary in how they work, and it is worth asking the secretariat how yours operates before the session. Some publish the report within days and copy it to the applicant for factual correction first. Some hold the review as a workshop with no written output until a later session. Some include a local authority officer on the panel, which changes the dynamic considerably, because the officer who will write the report has already formed a view in the room.

The honest uncertainty is how much weight any given officer gives a panel view. Where the panel and the case officer disagree, the officer's recommendation is the one that reaches committee.

Preparing for a panel session

Panels see a lot of schemes and they respond to clarity. What works:

1. Lead with the site and the context: constraints, levels, existing character, and the analysis that generated the response.
2. Show the design development, including the options rejected and why. Panels are more interested in the reasoning than in the final image.
3. Bring a physical or digital massing model in context, rather than visualisations from flattering viewpoints.
4. Include the sections. Most panel criticism of housing schemes concerns the relationship between buildings, streets and levels, which only sections show.
5. Ask two or three specific questions you want advice on, rather than presenting and waiting.
6. Send the pack in advance, in the format requested, by the deadline.

Do not send the sales visualisations. A panel that spots rendered sunshine on a north-facing elevation stops trusting the rest of the pack.

Reflecting comments in the design and access statement

The design and access statement is where the response to both the code and the panel belongs. Two structural moves make it work.

First, a compliance table against the design code, clause by clause, showing where the scheme complies and where it departs, with the justification for each departure. Officers are far more likely to accept a reasoned departure that is declared than one they discover.

Second, a short section listing each panel comment and the change made in response, or the reason no change was made. Keep it factual and avoid restating the whole design narrative.

Householder and small schemes work the same way at a smaller scale, where the equivalent document is often a householder design guide SPD rather than a full code.

Where a code conflicts with an older local plan

This happens more often than it should, usually where a code prepared in the last few years sits over a local plan adopted a decade ago. The rules for resolving it are not complicated.

Where the code is part of the development plan and the older policy is also part of it, the later document generally prevails on the point of conflict, and the plan itself will often say so. Where the code is a supplementary planning document, it cannot override an adopted policy, so a code that requires something the plan does not is guidance rather than requirement, and its weight depends on how recently it was adopted and how thoroughly it was consulted on.

Where the conflict is real and material, say so in the planning statement, set out both positions and explain which should prevail and why. Do not quietly design to whichever document suits the scheme and hope nobody reads the other one. If the scheme is contentious, that argument will be made in public at committee, and knowing whether the decision will be taken by members or under delegated powers changes how the case should be presented.

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

Draft the policy and design compliance sections of your submission in minutes, then refine them against the code. See PlanScope pricing. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.