Design codes and the scale at which one applies

A design code is not a document that scales down gracefully. Below a certain size it adds cost, delay and a compliance exercise without changing what gets built, because the same team designs and delivers the whole scheme in one go. Above a certain size it is the only thing that holds quality together across phases, housebuilders and a decade of market change. The design code requirement scale question therefore has a practical answer: a code earns its cost when more than one designer, more than one builder or more than one phase will deliver the scheme.

Local policy may override that judgement, and increasingly does. The National Model Design Code sets the framework, and the Levelling-up and Regeneration Act 2023 moves towards authority-wide codes with development plan weight, though the commencement position should be checked before relying on it.

What a design code does that a masterplan does not

A masterplan shows an intended outcome. A design code sets rules that any designer must follow to reach an acceptable outcome, without specifying the outcome itself.

The difference matters at reserved matters. A masterplan showing a terrace of 14 houses with a particular roofline is a picture. A code saying that on this street type the building line sits 2 m behind the back of footway, eaves heights fall between 5.4 m and 6.6 m, and parking is provided to the rear or in on-plot side bays no wider than one car, is a test. The second can be applied to a layout nobody has drawn yet.

Codes are also area-specific in a way masterplans are not. The National Model Design Code's approach is to divide a site or an area into character areas, then code each one: street types, block structure, building types, heights, frontage treatment, materials, boundary treatment, parking, planting and public space. The coding plan ties the rules to geography.

What a code does not do is replace design judgement. The deeper discussion of where a code binds and where it leaves room is set out in the piece on what a design code fixes and what it leaves open.

Where codes are required by local policy

Three situations produce a requirement rather than a choice.

Local plan allocation policies for strategic sites commonly require a design code to be prepared and approved before or alongside reserved matters. Read the allocation policy before assuming a code is optional, because the requirement is usually explicit and sometimes names the stage at which the code must be submitted.

Authorities with an adopted area-wide or site-specific code apply it to any application in the coded area. That is a different thing from being asked to prepare one, and it means the design and access statement has to demonstrate compliance with somebody else's rules.

Garden communities, new settlements and development corporation areas almost always code, and the code is often a condition of the enabling consent rather than a planning requirement at all.

The scale at which a code earns its cost

Those bands are judgements rather than policy thresholds, and the delivery pattern matters more than the unit count. A 90-home scheme split between two housebuilders with a shared spine road benefits from a code. A 300-home scheme built by one contractor under a single detailed permission probably does not need one, because the detailed drawings do the job.

The cost of a code is not mainly the document. It is the time spent agreeing it with the authority, the design work needed to test that the code can actually deliver the consented capacity, and the compliance checking at every reserved matters submission. On a scheme that will never face a second designer, all three are overhead.

The one argument for coding a smaller site is land value. Where parcels are to be sold to builders, a code is what protects the vendor's interest in quality and what gives the authority confidence to grant outline permission for a scheme nobody has designed yet.

Coding plans and parameter plans together

These two documents are often confused, and on an outline application both are needed because they do different jobs.

Parameter plans form part of the permission and fix the envelope: access points, development zones, maximum and minimum building heights, land use areas, green infrastructure and the primary street network. They are what the outline permission is granted for, and departing from them needs a section 73 application or a fresh permission.

A coding plan sits inside the design code and allocates rules to character areas and street types. It is usually approved under condition rather than forming part of the permission itself, which gives it more flexibility and less legal weight.

The practical discipline is to keep them consistent and to make the parameter plans no tighter than necessary. Parameter plans drawn with over-precise height ranges turn every market-driven adjustment into a planning application, while a code can be varied by agreement. The relationship between the two, and how binding each is, is examined further in what design codes are and how binding they are.

Securing the code through condition

The usual mechanism on an outline permission is a two-part condition: a design code to be submitted and approved before the first reserved matters application, and all reserved matters to accord with the approved code.

Three drafting points are worth negotiating.

First, the code should be approvable in parts, so that a code for the first phase's character areas can be approved while later areas remain open. A condition requiring the whole site to be coded before anything can be submitted stalls delivery for a year.

Second, the condition should allow minor departures where justified in writing, otherwise every variation becomes an application to vary the code.

Third, be clear what happens where the code and the parameter plans conflict. Say in the condition which prevails, because the two documents are prepared at different times by different people and they will diverge somewhere.

Phasing interacts with all of this, since a code approved for phase one has to anticipate what phases three and four will need. That timing problem is covered in the guide to phasing a large scheme without gaming thresholds.

Reviewing a code at reserved matters

Build the compliance process into the code itself, because an officer with no checking framework will review every submission from first principles and the code will have bought nothing.

What works is a compliance schedule submitted with each reserved matters application: one row per code requirement, with the drawing reference that demonstrates it and a short note where a departure is proposed. It takes a day to produce and saves weeks of correspondence.

Expect the authority to involve a design review panel at the coding stage on larger schemes, and sometimes again at reserved matters. The two processes serve different purposes and a panel is not a substitute for a code, a distinction drawn out in the piece on design codes and design review panels.

One honest uncertainty: codes vary enormously in how well they survive contact with a volume housebuilder's standard house types. A code written around a plot-based approach, with no type that the builder already has on its system, gets renegotiated. Testing the code against real house types during drafting, rather than after, is the difference between a code that is applied and a code that is argued about.

Deciding early

Make the call before the outline application is submitted, not after permission is granted.

Three questions settle it. Will more than one designer or builder deliver this scheme. Does the allocation policy or an adopted local code already require one. And is the land to be sold in parcels. Two yes answers means code.

Where the answer is no, put the effort into a detailed Design and Access Statement with real elevations, a materials schedule, street sections and boundary treatment details. That is what the officer actually needs on a single-phase scheme, and it is a far better use of the fee than a code nobody will ever apply.

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.