Design code or a design guide supplementary document

The practical difference between a design code and a design guide supplementary planning document is status, and status decides weight. A design code brought forward as part of the development plan engages section 38(6) of the Planning and Compulsory Purchase Act 2004, so an application that conflicts with it has to overcome the plan-led presumption. A design guide adopted as a supplementary planning document is a material consideration, and an inspector can give it as little weight as the argument deserves. Everything else, including how prescriptive the drafting is, follows from that distinction rather than causing it.

Prescription against guidance

A code sets parameters. Plot widths, building lines, storey heights, frontage types, materials, boundary treatments, parking arrangement and street sections, mapped to defined area types across a site or a district.

A guide explains an approach. It shows what good looks like, illustrates successful precedents, and usually uses the language of should and encourage rather than must and shall.

Both can be well written or badly written. The failure mode differs. A bad code is one that fixes the wrong parameter, such as a materials palette that cannot be delivered within the scheme's cost plan. A bad guide is one that reads as a coffee table book and gives an officer nothing to refuse on.

What a code fixes and how

The National Model Design Code sets out the method: establish area types, produce a coding plan that maps those types, and set parameters for each. The parameters are where the work lives, and they should be capable of a yes or no answer on a drawing.

Good coding distinguishes between what is fixed and what is left to the designer. Storey heights and building lines fixed. Window proportion described rather than dictated. That separation is the whole craft, and the article on what a design code fixes and what it leaves open goes through where the line usually falls.

A guide has no coding plan. It applies across an area by theme rather than by place, which is why householder design guides work well as guides and masterplanned urban extensions do not.

Status in the development plan

This is the part that decides outcomes.

A design code can reach development plan status by several routes. It can be incorporated into a local plan as policy, prepared as a development plan document in its own right, or included in a made neighbourhood plan. Each of those routes puts it inside the development plan for section 38(6) purposes.

A supplementary planning document sits outside the development plan. It supplements adopted policy and cannot create new policy, which is a limit that matters more than most authorities admit when drafting one.

The Levelling-up and Regeneration Act 2023 provides for supplementary plans to replace supplementary planning documents, forming part of the development plan rather than sitting alongside it. As at September 2026 the transition is governed by commencement regulations and the position has been moving, so check the current commencement and transitional arrangements before you advise a client on the weight a document carries.

Weight in a decision and at appeal

Inspectors apply a consistent logic to both. A development plan document is the starting point, and departure has to be justified by other material considerations. A supplementary planning document carries weight to the extent that it is consistent with the plan it supplements, was properly consulted on, and does not stray into new policy.

Two patterns show up repeatedly in decisions. Supplementary guidance that imposes a numerical standard the local plan does not support gets discounted. Supplementary guidance that interprets and illustrates an adopted policy, and was consulted on properly, is given real weight.

For applicants that produces a workable approach. Where a scheme conflicts with a design guide SPD, identify the adopted policy the guide is supplementing and argue against the guide's interpretation of it. Where a scheme conflicts with a coded parameter in the development plan, that argument is not available and the case has to be made on material considerations that outweigh the conflict.

Preparation and consultation

The processes are not comparable in cost or duration.

A development plan document requires sustainability appraisal, the regulation 18 and regulation 19 consultation stages, submission, independent examination by an inspector against the tests of soundness, and adoption. Years, not months.

A supplementary planning document requires consultation under the Local Planning Regulations and adoption by the authority. No examination, no soundness test, and no inspector to rule on whether a parameter is justified.

That gap explains a lot of what is on council websites. The SPD route is quick and produces a document quickly discounted at appeal. The plan route is slow and produces a document that holds.

For a private masterplan, a third route exists: prepare the code, secure it through a condition or a section 106 obligation on an outline permission, and have it approved as part of the reserved matters framework. The code then binds through the permission rather than through the plan, which is a different mechanism with different consequences for reserved matters and condition discharge.

How each behaves in negotiation

A code changes the conversation from taste to compliance. The officer asks whether the frontage type matches the coding plan. The applicant answers with a drawing. That is faster, more predictable, and it removes a large part of the discretion that makes design negotiation slow.

It also removes flexibility that applicants sometimes need. A coded parameter that does not suit an awkward corner plot is harder to argue away than a paragraph in a guide, because the code was examined and the guide was not.

A guide keeps the conversation open, which suits authorities with design review arrangements and a strong in-house team. Where a council relies on a panel rather than a code, the interaction between the two matters, and design codes and design review panels covers how the two fit together.

An illustrative example. An authority adopts a borough-wide householder design guide as an SPD and, separately, a coded framework for a 1,200 home urban extension inside its local plan review. A two storey side extension refused under the SPD is allowed at appeal because the inspector finds the SPD's 1 metre set-back requirement has no basis in adopted policy. A house type refused on the urban extension for breaching the coded building line is dismissed at appeal, because the code is development plan policy. Same council, same year, opposite outcomes. This example is illustrative.

Which one a council should prepare

Ask what the document has to do.

If the answer is to give certainty about form on land that will be developed by several parties over a decade, code it and put it in the plan. The preparation cost is real, and it buys predictable delivery and a defensible refusal.

If the answer is to raise the standard of householder extensions and small infill across a whole district, a guide is proportionate. Coding every street in a borough is not a sensible use of a plan-making budget.

The awkward middle is a district-wide design code, which several authorities are now preparing. Those work where the coding is properly area-based and the parameters are few, and they fail where they become a guide with a coding plan stapled to the front.

For applicants, the practical step is simply to check the status of every design document cited in a pre-application response. Ask whether it is part of the development plan, when it was adopted, and which policy it supplements. That question changes how you write the Design and Access Statement and how you pitch the case.

Enter your postcode on PlanScope to see which documents your scheme is likely to need, then check the local design policy status before you draft the design case.

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.