53. Coordinating codes, the right tool for the job!

In an earlier post (49.) I examined the proposals advanced in the Housing and Planning Act that aim at moving towards a new means of permitting development via ‘Permission in Principle’ (PiP) relating to sites on a register of brownfield land or otherwise identified in the development plan. The new system will in effect give advanced approval to housing projects up and down the country long before fundamental design or a wide range of other material considerations are ever considered. It will do this on the basis of a red line around a site and some crude evaluation of the quantum of housing that the site can accommodate.

As soon as this new system was mooted, it raised the big question in my mind about how will place quality be guaranteed under such a system. Also, how would the vital support of communities be garnered when they are, in effect, presented with a done deal long before they ever get a chance to comment. The Act itself (in Clause 150) makes provision for a new process of ‘Technical details consent’ to be determined in accordance with PiP, and PiP plus the technical details consent will represent the planning permission. This, however, raises a number of concerns:

  • First, the nature and shape of the place that is being created is not a ‘technical detail’, but is instead a fundamental part of the process of assessing a planning application. Without proper consideration of the fundamental design considerations that relate to matters such as height, density, landscape, layout, connectivity and so forth, and what this means for how uses and spaces are distributed on a site, it is impossible to properly determine whether a proposal for development is or is not suitable for a site.
  • Second, it is very difficult to assess the quantum of development appropriate for a site and the right mix of uses (both issues that the legislation proposes should be decided at PiP stage), without having due regard to how this will actually be delivered. Will it, for example, be stacked up high in a single tower, laid out in streets, or perhaps distributed in a series of detached units?
  • Third, communities will quite rightly be resistant to the giving of Permission in Principle to new development without having any sense of what that would mean on the ground and how it might effect the surrounding context and properties. What is envisaged may actually increase rather than decrease local resistance to development.

The coordinating code, a possible solution

Taking as a starting point three aims of i) streamlining the process of securing consent to develop, ii) increasing certainty for developers and investors, and iii) maintaining a focus on quality outcomes; I argued previously that it may be possible to combine the designation of PiP with the production of a design code for each allocated site. Design codes are tools that establish the key urban design parameters for a site with a particular focus on making the place, but without the requirement for a fixed and detailed masterplan. Their use is encouraged in paragraph 59 of the NPPF.

Since then I have been working on what the nature of such a code would be, and, working with Studio REAL have developed the idea of a Coordinating code. This would be a slimmed down and very simple code that (preferably on a single A3 sheet) would establish the critical principles for making the place.

pip-co-ordinating-code_examplev3_160321-copy-2-2

Indicative coordinating code

As shown in the indicative example they would:

  1. Focus on the four ‘place’ issues that are common to almost all sites: community and land use; landscape setting; movement; and built form / massing issues
  2. Contain minimal text that describes only these fundamental design parameters and that ‘fixes’ the expected design response
  3. Illustrate, through a simple plan graphic, the design concept in two dimensional terms in order that the essential parameters of place are fully understood.

In effect this would bring a proper consideration of fundamental (not detailed) design and place quality concerns forward in order to streamline the technical consents process later on. It would guarantee a level of quality to give certainty to both developers and local communities about what the development would entail, and would provide a basis against which to make an estimate of the number of dwellings that the site would be likely to support. Finally it would help to avoid increased community opposition to proposals as communities would have a much better idea of what they are being asked to support.

Coordinating codes would be simple, quick and easy to prepare (the example took two days) either by local authorities in-house, by consultants, or developers promoting a particular site. And, because they would be site specific (not generic) and clear and easy to understand, the qualities they espouse could be subject to public engagement early in the development process and would help to ensure a greater focus on securing early agreement about the need for high quality new development.

Small (and simple) is beautiful

Whilst the Government have yet to fully embrace the idea (although have made warm noises about using codes with PiP in the House of Lords and elsewhere), the Federation of Master Builders (FMB) who represent small housebuilders up and down the country, have not been so reticent. Indeed, just before Christmas they published an important new report – Small is Beautiful – that examines the potential to deliver on small sites and, in this process, to fully release the potential of SME builders once again.

The report strongly endorses the idea of using coordinating codes and argues that they have the potential “to reduce the uncertainties around bringing forward applications for small sites” (whether or whether not associated with PiP). They suggest:

“coordinating codes are similar to design codes, but slimmed down and simplified to be applied quickly to specific sites, or groups of sites at the neighbourhood level. They demonstrate the fundamental (but not detailed or prescriptive) design parameters with minimal text and simple graphics. They provide clarity and agreement over what is expected at the outset of a project”.

When surveyed, a clear majority of the FMB’s members suggested that they would be ‘open’ or ‘very open’ to the use of such codes. For me this is an idea whose time has come. We desperately need to make planning propositional once again, reviving the role of planning as a positive, confident and proactive force for change. We also need to do this in a manner that is flexible (whilst increasing certainty), brings communities along with the proposals, and that doesn’t break the bank to prepare. The coordinating code is quite simply the right tool for the job!

Matthew Carmona

Professor of Planning & Urban Design

Bartlett School of Planning, UCL

m.carmona@ucl.ac.uk

January 2017