Design codes and the National Model Design Code

The National Model Design Code is not a code you have to comply with. It is a method for producing one, published as guidance alongside the National Design Guide, setting out how an authority should analyse its area, decide the design parameters that matter locally, and write them down in a form an applicant can follow. What binds you is whatever your own council has produced using it.

That distinction gets lost constantly. An officer citing the model code at you is usually citing the checklist behind their own code, and the correct response is to ask which adopted document the requirement actually sits in.

What the National Model Design Code sets out

The model code has two parts. The first describes the coding process: the baseline analysis, the area types, the engagement, and the structure of a finished code. The second is a set of guidance notes on the design parameters themselves.

Its organising logic follows the ten characteristics of the National Design Guide, running from context and identity through built form, movement, nature, public spaces and uses, to homes and buildings, resources and lifespan. Each characteristic generates parameters an authority can code: building lines, plot widths, storey heights, frontage types, boundary treatments, street sections, tree canopy cover, parking arrangement, materials.

The model code is deliberately not a design style. It is agnostic between a terrace in brick and a terrace in render, and prescriptive about the dimensions that determine whether the street works.

How a local design code is prepared and adopted

The typical sequence runs like this:

1. Area-wide baseline analysis identifying character areas and area types.
2. Selection of the parameters that matter in this place, from the model code checklist.
3. Drafting, usually with worked examples and diagrams rather than text alone.
4. Public consultation and testing with local groups.
5. Adoption, either as a supplementary planning document or as part of the development plan.
6. Application, through the validation list and the development management process.

Step five decides everything about weight, and it is the step applicants skip when reading a code.

The Levelling-up and Regeneration Act 2023 provides for design codes to sit within the reformed plan-making system, with commencement tied to the wider transition. Because those arrangements have moved more than once, check the current position on gov.uk and in the authority's own local development scheme rather than assuming. Our planning law timeline tracks changes as they are made.

The weight a code carries in decision making

Three tiers, in descending order of force.

A code adopted as part of the development plan. Determination must be in accordance with it unless material considerations indicate otherwise, and departure needs to be justified.

A code adopted as a supplementary planning document. A material consideration, capable of carrying real weight where it elaborates an adopted policy, but not part of the plan and not able to introduce new policy of its own.

A draft or emerging code. Weight increases as it advances through consultation and reduces where objections are unresolved. An officer can give it some weight, and a committee can be persuaded to give it less.

There is a fourth category worth naming: a code prepared by a landowner or promoter for a large allocation, secured through a planning obligation or a condition on an outline permission. Those bind through the permission rather than through the plan, and they bind you specifically.

What a coded area means for an applicant

Practically, three changes to how you work.

The design parameters become inputs rather than outputs. Building line, storey heights and plot widths are fixed before the plan is drawn, in the same way a site's flood zone is.

The Design and Access Statement needs a compliance schedule. Not prose about how the scheme responds to local character, but a table listing each coded parameter, the requirement, what is proposed, and whether it complies. Where it does not, a short justification against the code's own flexibility provisions.

And departures need evidence rather than preference. Codes normally allow variation where a site constraint requires it. A level change, a retained tree, a sewer easement or an awkward corner plot are the sorts of reasons that work. Wanting a wider frontage is not.

Design review and its role

Design review panels give independent expert advice on schemes, usually before submission, drawing on a standing group of architects, planners and engineers. National policy encourages their use, and many authorities require review for schemes above a size threshold or in a coded area.

What review is good at: testing whether a scheme understands its context, catching a massing problem while it still costs little to fix, and giving an officer independent support for a position.

What it is not: a decision. The panel's report is a material consideration and it does not bind the authority, the applicant or the committee. A scheme can be approved against a critical review, and it happens.

Go early. A panel seeing a scheme at concept stage can change it. A panel seeing it a fortnight before submission produces a report that sits on the file and damages the application. Our note on design codes and design review panels covers how the two interact in more detail.

Evidence a design and access statement should now include

For a scheme in a coded area, the statement should carry:

• The area type the site falls within under the code, identified explicitly.
• The compliance schedule described above.
• Justification for each departure, keyed to the code's flexibility clauses.
• The design review report, if there was one, and how the scheme responded to it.
• Context analysis that engages with the code's baseline rather than repeating it.

Repeating the code's own analysis back at the officer is a common weakness. They wrote it.

Where codes conflict with other policy

Conflicts are real and increasingly common.

A coded window proportion can work against Part O overheating compliance, particularly on a south-facing frontage where the code wants generous glazing and the overheating calculation wants less.

A coded street section based on the national guidance on street design can conflict with a local highway authority's own design guide on carriageway widths and turning heads, and the highway authority is a consultee with its own standards.

A coded tree canopy target can conflict with a coded building line on a narrow plot, or with drainage and utility easements running beneath the verge.

Where a conflict is real, name it in the submission and propose a resolution rather than quietly complying with one requirement and ignoring the other. Officers respond well to an applicant who has spotted the problem in their own code, and badly to a scheme that pretends the conflict is not there.

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

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