Design Development & Coordination

Design development is where a scheme grows from an idea into a buildable, coordinated whole, and its defining feature is that it becomes multi-disciplinary and dense. The single most important object of this stage is the coordinated model - often a federated model, in which each discipline's model (architecture, structure, services) is brought together into one shared three-dimensional space so that everyone is designing against the same coordinated reality. Building information modelling makes this possible: the model is not just geometry but a coordinated database of elements, each owned by a discipline, all occupying the same volume and expected to fit. The central challenge is exactly that fitting - resolving the countless spatial relationships where architecture, structure and services meet, so the building can actually be built without collisions, without cramped unbuildable pockets, and without spaces that technically comply yet fail as places to be.

Traditionally this coordination is done on screen: overlaying discipline drawings, orbiting the federated model, and running automated clash detection that lists every place two elements physically intersect. These screen tools are fast, precise and indispensable, and nothing in this lesson replaces them - numeric clash detection in the verified BIM environment remains the authoritative check for whether elements collide. But screen review has a persistent blind spot that follows directly from the flatland problem: it tells you the numbers and shows you the geometry, but it does not let you feel the space. A clearance can pass every numeric check and still be a bad place to stand; a services zone can be clash-free and still be awkward, tight or confusing once a maintenance worker is actually in it. This is the gap immersion addresses. By letting the coordination team step inside the federated model at true scale, spatial computing adds a bodily, spatial layer of review on top of the numeric one - not to replace clash detection, but to catch the human, experiential problems that pass the numbers and would otherwise only be discovered, expensively, on site. The figure shows the disciplines federating into one coordinated model that can then be walked as a single space.

An immersive coordination review is straightforward in concept and genuinely useful in practice: the federated model is brought into a headset, and the design and coordination team walk through it together at true scale, as if inspecting the half-built building. Instead of each person squinting at their own screen and mentally reconstructing how the ducts pass over the beams above a corridor, everyone can stand in that corridor, look up, and simply see it. This changes the quality of a design review in several concrete ways. It makes spatial relationships between disciplines immediate and obvious rather than something to be inferred from overlaid plans. It lets non-specialists in the room - a client, a project manager, a contractor - understand the coordination issues too, because they can see the space rather than read the drawings. And it surfaces the experiential questions that the screen review, focused on geometry and numbers, tends to skip: is this plant room actually usable, does this bulkhead make the entrance feel low, is this riser awkward to access.

The practical value is that problems get caught earlier and understood better. A team that walks its coordinated model before drawings are finalised can feel an awkward junction, a mean clearance or a confusing services route while it is still cheap to change - rather than discovering it when a contractor hits it on site. But keep the honest frame from the whole course. Preparing a federated model for a usable immersive review is real work and takes time; the hardware is tiring for long sessions, so reviews should be focused and short; and only some of the team can be immersed comfortably at once. Most importantly, the immersive review is a way of seeing and understanding, not a measuring instrument - you do not read dimensions or confirm clearances off the headset. The authoritative checks stay in the verified BIM environment. Immersion earns its place here by adding spatial understanding and shared comprehension to a coordination process whose binding truth remains the coordinated model, the numeric clash reports, and the drawings.

The sharpest argument for immersion in coordination is that it catches a specific, costly class of problem that screens systematically hide: the spatial awkwardness that is not a numeric clash. Automated clash detection is excellent at finding hard collisions - two solid elements occupying the same point - and it should always be run. But a great many real coordination failures are not hard clashes at all. They are clearances that technically pass but feel oppressive; head-height that is legal but uncomfortable once you are under it; a services run that does not intersect anything yet is impossible to reach for maintenance; a space that reads as generous in plan but is cramped once you are standing in it among the structure and ducts; sightlines blocked by a column no drawing made obvious. None of these trip a clash report, because nothing physically collides - and all of them are exactly the kind of thing your body notices the instant you stand in the space.

This is where the flatland problem and immersion meet most usefully in the middle of the process. The figure contrasts the two views: on the plan, a duct clears a beam by the numbers and everything looks fine; standing under it at true scale, the same arrangement feels low and oppressive, a bad place to be that no clearance figure captured. Immersion surfaces that felt verdict early, while it is still a cheap change on the model rather than an expensive one on site. Used this way, an immersive coordination review is a genuine complement to numeric clash detection - the two catch different failures. The numbers catch collisions; the body catches awkwardness, tightness and confusion. But the discipline holds firm: what you feel is understanding that flags something to investigate and resolve properly, never a measurement or a decision of record. When immersion tells you a clearance feels wrong, you take that back to the verified model, check the real dimensions, and coordinate the fix there with the responsible engineers - the headset raised the question, the model and the specialists answer it.

Design development and coordination is a stage where immersion earns its place more clearly than in concept, but it still has to earn it task by task, and much of the daily work rightly stays on the screen. Immersion earns its place best at particular moments: a coordination review of a complex, congested area (a plant room, a service-dense ceiling, a tight core) where the spatial relationships between disciplines are hard to grasp from drawings; a milestone design review where the whole team, including non-specialists, needs a shared understanding of how the developed design actually works as space; and any junction where you suspect a clearance may be numerically fine but experientially poor. In these situations, standing in the model together beats overlaid plans and a small orbiting screen model, because the problems are fundamentally spatial and experiential.

But the screen wins the majority of development work, and honesty about that is part of the skill. The precise, iterative daily labour of coordination - editing elements, checking exact dimensions, running and resolving clash reports, producing the drawings - is faster and better on screen, and the drawings remain the precise, shareable, legal record that the whole team and the contractor work to. Immersion is a periodic layer of spatial review on top of that screen-based process, not a replacement for it; it is reached for when a spatial or experiential question genuinely beats a drawing, and set aside for the fast, numeric, documentary work that fills most of the stage. And through all of it the boundary from the whole course holds without exception: the immersive review is a tool for seeing, understanding and communicating the coordinated design - it is never the source of truth. Binding dimensions, clearances, clash resolution and technical decisions stay with the verified BIM model, the numeric clash reports, the drawings, and the qualified engineers who own each discipline. Immersion makes the team understand the coordinated space better and earlier; the coordinated model and the specialists remain what everyone is actually held to.