Authority-wide design codes and what they bind

The practical question behind any design code requirement is whether the document in front of you is part of the development plan or merely a material consideration, because that single distinction decides how much argument you need to depart from it. An authority-wide code adopted as part of a local plan or a supplementary plan carries the weight of the development plan under section 38(6) of the Planning and Compulsory Purchase Act 2004. The same drawings published as non-statutory guidance do not. Everything else about coding follows from that.

Where the requirement comes from

Two sources sit behind the current push for codes.

National policy expects local planning authorities to prepare design guides or codes consistent with the National Design Guide and the National Model Design Code, and to set out the design expectations for their area in a document that has been through community engagement. Policy also makes clear that a code carries more weight where it forms part of a plan.

The Levelling-up and Regeneration Act 2023 then reworked plan-making itself. Its provisions create a new structure of local plans and supplementary plans, replace supplementary planning documents with supplementary plans subject to independent examination, and provide for National Development Management Policies to sit alongside local policy. Design codes fit into that structure as either part of a local plan or as a supplementary plan.

Those plan-making provisions have been brought into force in stages through regulations and transitional arrangements, and the detail has moved more than once. Check the current position on gov.uk and against your authority's own local development scheme before relying on a particular route, and read it alongside the note on plan-making reform and emerging plans.

Authority-wide codes against area and site codes

Codes operate at three scales and they do different work.

An authority-wide code covers the whole administrative area. It can only sensibly fix the parameters that hold good everywhere: street types and their dimensions, building typologies, frontage and boundary treatments, parking approaches, the treatment of corners, and the characteristics that definition of local character attaches to. It usually works through a character area map, with different parameters applied to each area.

An area code covers a neighbourhood, a town centre or a growth area. It can be more prescriptive, because the context is known and the testing has been done against real street sections.

A site code covers a single allocation or masterplan and is often secured by condition or through a section 106 obligation. It is the only scale at which plot-level detail, down to window proportions and material specifications, can be fixed without producing absurdities.

The failure mode for an authority-wide code is over-reach. A borough-wide requirement for a specific brick type, or a single roof pitch, will be departed from so often that the code loses authority. A code that sets out three permitted street sections and tells you how to choose between them will not.

The status a code holds in the development plan

Where the code is part of the local plan or a supplementary plan, applications are determined in accordance with it unless material considerations indicate otherwise. That is a strong position, and it means a departure needs a reasoned case rather than a preference.

Where the code is published as guidance outside the plan, it is a material consideration whose weight depends on how it was prepared, how recently, and how much engagement sat behind it. A code adopted after consultation and endorsed by the authority will carry real weight. A code written by consultants, published on a webpage and never consulted on will carry little. The distinction between those routes is set out further in the comparison of a design code and a design guide supplementary document, and the question of how binding a code is in practice is addressed in design codes in planning.

Read the code's own language carefully. Most distinguish mandatory requirements from recommended ones, typically through "must" and "should", and some add a third tier of guidance. A departure from a "must" needs justification in the planning case. A departure from a "should" needs an explanation in the design narrative and usually nothing more.

The relationship with the national model code

The National Model Design Code is not itself a code for anywhere. It is a process document and a set of guidance notes, structured around the ten characteristics of the National Design Guide, which authorities use to produce their own code.

And its practical contribution is the baseline assessment. The model code expects an authority to analyse what its area actually looks like, recording block sizes, street widths, building heights, plot ratios, boundary types and green cover, before it writes parameters. That matters to an applicant, because a code built on a published baseline can be argued with on its own terms. If the code requires a 2.5 m front boundary setback and the baseline study records a prevailing setback of 1.8 m in that character area, the code is vulnerable at that point.

Ask for the baseline evidence. It is normally published alongside the code and it is the most useful document in the pack.

How a code is tested before adoption

The testing depends on the route.

A code within a local plan goes through examination against the soundness tests: whether it has been positively prepared, whether it is justified by evidence, whether it is effective and deliverable, and whether it is consistent with national policy. Viability is part of that. A code whose parameters cannot be delivered on the typical site in the area, at the densities the plan requires, is not effective.

A supplementary plan under the 2023 Act framework is also subject to independent examination, which is the substantive change from the old supplementary planning document route. Under that older route, an authority could adopt a design document after consultation with no external scrutiny, and the weight it carried was correspondingly arguable.

For an applicant, the examination documents repay reading even years later. Where an inspector modified a parameter, or an authority conceded one in a statement of common ground, that history is the first place to look when you need to depart from it.

Using a code in a design and access statement

A Design and Access Statement that engages properly with a code is structured around the code rather than around the designer's own narrative.

The structure that works:

1. Identify the character area the site sits in and the parameters that apply to it.
2. Set out a compliance schedule listing each mandatory requirement, the scheme's response and a plain statement of compliance or departure.
3. For each departure, give the reason, the evidence and the policy basis. Site constraints, levels, tree root protection areas, daylight to neighbours, highway requirements and viability are all legitimate reasons where they are evidenced.
4. Address the recommended provisions more briefly, in the design narrative.
5. Record where the code is silent, because codes often do not cover the thing a scheme is actually proposing.

A compliance schedule is a short document and it saves weeks. It tells the case officer, the design review panel and the committee exactly where the argument is, and it stops a consultation response that lists eight supposed breaches, six of which are not breaches at all.

Where a code conflicts with other policy

Four conflicts come up, in rough order of how often.

The code against a development plan policy adopted at a different time. Where two development plan policies conflict, section 38(5) of the 2004 Act gives priority to the one in the later-adopted document. Establish the adoption dates before arguing the merits.

The code against National Development Management Policies. The 2023 Act framework provides for national policies of that kind to prevail where there is a conflict with the development plan, which is a change applicants should check as those policies come into force.

The code against highway or technical standards. A code calling for narrow streets and on-street parking can collide with the local highway authority's adoption standards. This is the commonest practical conflict on housing sites, and it is resolved by negotiation rather than by hierarchy, so raise it at pre-application.

The code against accessibility or building regulations requirements. Level thresholds, visibility, refuse carry distances and fire service access are not negotiable against a design parameter, and a code that produces a non-compliant layout has to give way.

Illustrative example: a 36-dwelling scheme in a character area whose authority-wide code requires 2 m front setbacks, perimeter blocks, parking to the side or rear and a 45 per cent maximum frontage width for garages. The levels on this site force a retaining structure that reduces the setback to 1.4 m on eight plots. The compliance schedule records the departure, cross-refers to the levels drawing and the baseline study showing setbacks of 1.5 m nearby, and proposes a hedge and railing treatment in mitigation. The officer report treats the departure as justified.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. Plan-making rules and code requirements change, so follow them on the PlanScope planning law timeline and verify the current statutory position on gov.uk before you rely on it.