Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
A wide shaded pedestrian spine running through a large Indian campus — a tree-lined paved walkway connecting multi-storey buildings, with vehicle roads and parking kept to the edges, people walking the car-free core.
Unit IIIArchitectural Design VII

Circulation & Movement

Separating people, vehicles and services across a large development.

≈ 35 min + studio work

Move thousands of people, hundreds of vehicles and a constant flow of services through a campus, and circulation becomes the hardest problem in the studio. This unit is about MOVEMENT at the large scale: separating and integrating pedestrian, vehicular and service flows so they support rather than fight each other; the movement systems that organise the whole; parking and access; and weaving services through a group of multi-storey buildings. As Edmund Bacon argued, movement is what organises urban form.

Learning objectives

By the end of this unit, you will be able to — mapped to the course outcomes for Architectural Design VII:

1
CO1 · Understand

Separate and integrate pedestrian, vehicular and service movement at the large scale.

2
CO1 · Apply

Design a movement system — hierarchy, spine, loop — for a campus or urban centre.

3
CO2 · Apply

Resolve parking and access for a large development.

4
CO2 · Understand

Weave services through a group of multi-storey buildings.

Pedestrian, vehicle, service

Three flows, one design

Three movements must be separated yet integrated; movement systems organise urban form, and the pedestrian comes first.[1]

Three flows, one design pedestrian — shaded, continuous, first vehicle — loop on the edge, park & drop service — rear lanes & yards, unseen Conflict — a truck crossing the spine, cars in the square — is the commonest failure at this scale.
DiagramPedestrian, vehicle and service movement separated yet integrated across a development

People, vehicles, services

A large development carries three different movements that must be SEPARATED yet INTEGRATED: pedestrians (who want a safe, shaded, continuous walking realm), vehicles (who need access and parking but should not dominate), and services (deliveries, waste, emergency, maintenance — which must reach every building unseen). Conflict between them — a service truck crossing a pedestrian spine, cars flooding a square — is the commonest failure at this scale.[1]

Movement organises the form vehicle loop (edge) pedestrian spine access Design the hierarchy and it reads; leave it to chance and it is a maze (Bacon).
DiagramA movement hierarchy of a pedestrian spine, a vehicle loop and access lanes organising a campus
The unseen flows

Services through the group

Services need their own routes and yards, run horizontally between buildings and vertically within them, and share routes with the hard constraint of emergency access.[4]

Services — horizontal & vertical riser / core horizontal trunk between buildings Where the trunk meets the riser is a major urban-scale design move — back to the armature.
DiagramServices run horizontally as trunk routes between buildings and vertically as cores and risers within each

The unseen flows

Services — deliveries, kitchens, laundry, waste, plant maintenance — need their own routes and yards that reach every building without crossing the public realm. A service spine or rear-access lane, screened service courts, and dedicated cores keep the messy necessary flows working and invisible. Forgetting service access is a classic studio error that only shows up when the building is 'finished'.[4]

Circulation in one table

At a glance

AspectOneThe other
Three flowsConflicting: trucks cross the spineIntegrated: layered by route and level
Who comes firstCar-led: parking dominatesPedestrian-first: shaded walking realm
ServicesForgotten until 'finished'Own routes and yards, designed early
Movement frameworkLeft to chance: a mazeDesigned hierarchy: legible
Emergency accessAn afterthoughtA hard constraint to every building
Vocabulary

Key terms

Three flows

Pedestrian, vehicular and service movement — separated yet integrated across a development.

Movement system

The framework of spines, loops and hierarchies that organises movement and urban form (Bacon).

Pedestrian primacy

Designing a continuous, shaded, barrier-free walking realm as the first move; cars as guests.

Service spine / lane

A dedicated route and yards reaching every building without crossing the public realm.

Vehicle hierarchy

Arterial → loop → access, with parking peripheral or structured.

Drop-off

A defined point for vehicles to set down and pick up without entering the pedestrian core.

Fire-tender access

Required emergency-vehicle access and turning to within a set distance of every building (NBC).

Integrated movement

Layering the three flows by route, level and time so each works without spoiling the others.

Apply it

Studio task

Draw a movement diagram for your scheme on three layers — pedestrian, vehicle, service — then overlay them to find conflicts and resolve them by route, level or time. Mark the drop-offs, the parking, the service yards, and prove that a fire tender can reach within the required distance of every building.

Check your understanding

Self-assessment

1. Edmund Bacon argued that the primary organiser of urban form is —

2. On a well-designed campus, the three flows — pedestrian, vehicle, service — should be —

3. A classic studio error at the urban scale is to forget —

In a nutshell

Recap

A large development carries three flows — pedestrian, vehicle, service — that must be separated yet integrated.
Movement systems organise urban form (Bacon); design the movement hierarchy first and the development becomes legible.
Put the pedestrian first — a continuous, shaded, barrier-free walking realm; the car is a guest.
Give services their own routes and yards, and coordinate horizontal trunks with vertical cores through the group.
Emergency and fire-tender access to every building is a hard NBC constraint, designed alongside the everyday.
The evidence

References & further reading

  1. [1]Bacon, Edmund N. — Design of Cities (Viking Press, 1967) — movement systems as the organiser of urban form.
  2. [4]BIS — NBC 2016, Part 4 (fire-tender access) & Part 3 (parking, circulation); Kliment Building Type Basics.

Further reading

  • Edmund N. Bacon — Design of Cities (1967).
  • BIS — NBC 2016, Parts 3 & 4 (circulation, parking, fire access).
  • Joseph De Chiara & Lee Koppelman — Time-Saver Standards for Site Planning.

Sources gathered and fact-checked June 2026. Published values vary by source, sample and method — treat as indicative and confirm against the cited standard before structural use.