Monitoring qualitative information

While useful, quantitative measurement of the kind described above lacks nuance, which is why it is worth backing it up with qualitative feedback (and, as with any statistic, careful objective interpretation).

The qualitative aspects of good design and placemaking – which are central to all planning policy – can only be assessed by proxy measures or in surveys, focus groups and interviews.

For example, in annual audits of the quality of the urban realm, city authorities in Melbourne, Australia, have developed a range of proxy measures to illustrate the continual improvements made relating the quality of life in the city, including yearly changes in: the number of cafés; number of front doors; number of pedestrians and cycles going through key gateways and public spaces; how people choose to spend their time in public spaces; number of trees; canopy cover; and so on. In understanding the existing context and measuring changes year-on-year, local policies and initiatives focus on achieving positive change and enhancing quality of life improvements over time.

The bespoke Chatham area types illustrate a range of urban qualities that contribute to the success of each place, which may be measured over time. Images: BPTW policies and initiatives focus on achieving positive change and enhancing quality of life improvements over time.

Inspired by this example, the Medway Council Pathfinder team incorporated these metrics into the design aspects of their own town centre code and are establishing a baseline for pedestrian activity, cyclists and trees. For want of time and resource, though, they have yet to establish a system to monitor its effectiveness.

Qualitative feedback is also important during stakeholder engagement and crosscollaboration and during testing and training phases. See also ‘Writing for the reader’.

Careful use of language

Being clear about various code requirements calls for accurate use of language. In a code, you must use it precisely and consistently. Wording such as: ‘should’ , ‘could be’ , ‘consider’ and ‘typically’ introduce ambiguity and cannot properly be enforced, nor accurately assessed or measured in terms of compliance. It is vital in any design code to achieve clarity in its wording and imagery, as this translates to the qualitative requirements that are measured later.

Being clear, accurate and concise in the drafting of the code are pre-requisites for the creation and smooth functioning of a monitoring system. The reader must be able to distinguish between what is part of the code and what is merely guidance on how to meet the code. For related guidance, see also ‘Presenting codes’

Integration with council processes and crossdepartment collaboration

Provided the objectives of a design code have been properly aligned to the local plan and wider corporate objectives through engagement and cross-collaboration, data from monitoring the code’s performance can be used to inform and update those higherlevel plans and objectives.

For example, the Medway Council Pathfinder team completed a digital 3D model of the area covered by their design code – the ‘Chatham Town Centre Massing Reckoner’ – to help to test the code’s parameters. This model is also being used to inform the emerging local plan by exploring options for the area and understanding the flexibility available for acceptable development capacity, based on insights from the code.

Best-practice principles for effective monitoring

Plan and resource a monitoring framework early: add monitoring criteria against design code objectives during initial visioning and scoping phases of developing a design code.

Create checklists for applicants and the development management review process.

Ensure metrics for monitoring are simple, clear and tied to specific outcomes.

Don’t rely solely on quantitative criteria: monitoring changes to the quality of the urban environment requires qualitative measurements as well as quantitative ones.

Allocate resource and build capacity: use a web-based format to gather basic usage data automatically. Otherwise, monitor change with simple digital tools, preferably ones that relevant colleagues are already familiar with from other contexts.

Prioritise what you want to monitor by understanding the code’s main objectives: tie your monitoring checklist to your code compliance checklist.

Engage development management officers in developing your monitoring framework and train them up on how to run the eventual monitoring system.

This piece was written in collaboration with Peter Garitsis, an Urban Designer with over 20 years of experience in both the private and public sector on a wide range and number of development projects. Currently working for Swindon Borough Council. Peter Garitsis – LinkedIn