Design codes in planning: what they are and how binding

A design code is a set of illustrated, measurable rules for how development in a defined area should be built: heights in storeys, plot widths, setbacks, street types, materials palettes, boundary treatments, parking arrangements. How binding it gets depends entirely on how it was adopted. A code adopted as a development plan document sits inside the statutory development plan and carries full weight under section 38(6). A code adopted as a supplementary planning document is a material consideration and nothing more, though in practice officers apply it as though it were policy.

That gap between formal weight and practical weight is where most arguments about design codes happen.

Codes, guides and supplementary planning documents

The three instruments overlap, and councils use the names loosely.

A guide tells you the terrace should relate to the street. A code tells you the building line is 4 metres from the back of footway, the parapet is between 9 and 11 metres, and the front boundary is a 900mm brick wall. The difference is testability. An officer can measure a code. A guide invites debate.

Councils increasingly publish both, and the code usually sits underneath the guide as an annexe. Check the cover page for the adoption route before you decide how hard to argue.

What the National Model Design Code sets out

The National Model Design Code, published by the department in 2021 alongside the National Design Guide, is not itself a code that applies to any site. It is a method: a two-part document that tells councils how to prepare a code, plus guidance notes on producing one.

It works through ten characteristics of well-designed places, running from context and identity through built form, movement, nature, public space, uses, homes and buildings, resources and lifespan. For each, it sets out what a local code should specify and what evidence should sit behind it.

Two ideas from it are worth knowing because they shape almost every code you will meet in practice. The first is that a code should be based on a local baseline study rather than imported standards. The second is that coding should be spatial, applying different rules to different parts of a settlement rather than one rule everywhere. That second idea is the area type.

Area types and the coding plan

An area type is a category of place with shared characteristics: suburban low density, urban terraced, town centre, edge of settlement, rural village core. The coding plan is the drawing that assigns every parcel in the coded area to one of those types.

Your first job with any code is to find your site on the coding plan and read only the rules for that area type. Applicants regularly quote the wrong section, usually the one with the easiest parameters, and officers regularly notice.

Within an area type the rules typically cover:

• Building heights, expressed in storeys with a maximum ridge or parapet height in metres.
• Plot width, depth and coverage, and the position of the building line.
• Street hierarchy and carriageway widths, cross-referenced to Manual for Streets.
• Parking type and quantum, and whether frontage parking is permitted.
• Materials, window proportion, roof pitch and boundary treatment.
• Tree planting, front garden depth and the treatment of the private-public threshold.

Where a code is prepared for a strategic allocation, the coding plan often carries mandatory and discretionary rules in separate columns. Mandatory rules are the ones that will appear as a reason for refusal.

Adoption and the weight that follows

The Levelling-up and Regeneration Act 2023 gives design codes a firmer footing, requiring authorities to prepare design codes for their area and allowing them to be adopted as supplementary plans as part of the wider plan-making reforms. Commencement of the plan-making provisions has been staged, so check where your authority sits before you assume a code has statutory force.

Until then, the practical hierarchy an officer applies looks like this.

1. A code inside an adopted local plan, area action plan or neighbourhood plan is development plan policy.
2. A code adopted as an SPD after public consultation is a material consideration with real weight, because it interprets an adopted design policy.
3. A code published for consultation but not adopted carries limited weight, which reduces further if the responses are unresolved.
4. A masterplan code secured by a section 106 obligation or a condition on an outline permission binds the reserved matters, regardless of its planning status.

That fourth route catches people out. If the outline permission was granted subject to a condition requiring reserved matters to accord with an approved design code, the code is enforceable through the condition even though nobody adopted it as policy.

Where codes reach householder and minor schemes

Most codes are written for allocations and regeneration areas, and a rear extension in a 1960s cul-de-sac will never engage one. But three situations bring codes into small applications.

Article 4 direction areas often pair the removal of permitted development rights with a design code or householder design guide, so that alterations which no longer benefit from the General Permitted Development Order are judged against a written standard. Conservation areas with a recent appraisal frequently carry a coded materials and window schedule. And infill plots inside a coded allocation are held to the same parameters as the surrounding phases, which can mean a prescribed roof form on a single house.

Whether the work is development at all is a separate question, and our note on what section 55 actually means covers that threshold.

Answering a compliance schedule

Larger codes come with a compliance schedule: a table listing each mandatory rule with a column for the applicant to state how the scheme complies. Fill it in properly and your Design and Access Statement becomes much shorter, because the schedule carries the detail and the statement carries the reasoning.

Three habits make the difference.

State the parameter, the proposed figure and the drawing reference, in that order. "Rule BF-04, maximum parapet 11.0m, proposed 10.6m, drawing 1042-P-210 revision C." An officer checking twenty rules wants to verify, not to search.

Where you depart from a rule, say so plainly in the schedule rather than leaving the cell blank or writing "complies". Codes almost always allow departures where the applicant demonstrates an equivalent or better outcome against the design objective the rule serves. Name the objective, explain the alternative, and show it on a drawing.

And check the code against the local plan policy it sits under. Occasionally a code overstates its parent policy, most often on parking or on private amenity space, and where the two conflict the adopted policy governs.

Codes reward the applicant who engages with them early. Design to the coding plan before the drawings are fixed, because retrofitting a 10.6-metre parapet onto a scheme designed at 13 metres costs more than reading the document did.

Browse the 66 PlanScope report types to see which supporting documents a coded site usually needs, and remember that PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. This is general guidance rather than legal advice, so check the position with your local planning authority before relying on it.