Ask three consultants on the same project how far along it is and you can get three honest, incompatible answers. The structural engineer is thinking about a package that went out weeks ago. The façade specialist is waiting on a decision nobody has recorded. The cost consultant is pricing a version of the building that has since changed. None of them is wrong, and none of them is describing the same project.
This is the problem the RIBA Plan of Work solves, and it is worth being clear that it is a communication problem rather than a design one. The framework divides a project from first strategic thinking through to the building in use, and it has become common shorthand well beyond the United Kingdom, including across the Gulf. Its usefulness is not the numbering. It is that it gives every party a shared answer to two questions: what is being decided now, and what is being locked.
What the RIBA stages are
The Plan of Work sets out eight stages, numbered 0 to 7. Each describes a distinct phase of thinking and production, with its own purpose, its own outputs and its own decisions. Stage 0 asks whether there should be a project at all. Stage 7 covers the building once people are living or working in it. Everything between the two is the work of turning a requirement into something that can be built.
The framework describes a process. It is not a contract and not a regulation, and it carries no statutory force anywhere, including in the United Kingdom where it originates. What it carries instead is agreement, which on a project involving a dozen consultants drawn from several markets turns out to be worth a great deal.
Seven stages or eight?
Both numbers are in common use, and the confusion is understandable. The Plan of Work contains eight stages, but they are numbered from zero rather than from one. Counting the labels gives eight. Counting from the first numbered stage to the last gives the range 0 to 7, which is often shortened to "the seven stages" or written as "stages 1 to 7", quietly dropping Stage 0.
The distinction matters more than it looks. Stage 0 is where a client establishes whether building is the right response to the problem in front of them. Where it is skipped, the question does not go away. It arrives at the design team already answered by assumption, and assumptions of that kind have a habit of resurfacing at the point where revisiting them is expensive. Earlier editions of the framework used different terminology, which is a further reason the numbering is remembered inconsistently. The current structure runs 0 to 7.
The stages
| Stage | Name | What it settles |
|---|---|---|
| Stage 0 | Strategic Definition | Whether to build at all, and on what basis. |
| Stage 1 | Preparation and Briefing | The brief: requirements, site information, budget, programme and risk. |
| Stage 2 | Concept Design | Massing, orientation, spatial arrangement and architectural character. |
| Stage 3 | Spatial Coordination | Whether the concept is genuinely buildable once every discipline is reconciled. |
| Stage 4 | Technical Design | How the building is actually made, in drawings and specifications. |
| Stage 5 | Manufacturing and Construction | The building is built, and the design is tested against reality. |
| Stage 6 | Handover | Completion, commissioning and the information needed to operate the building. |
| Stage 7 | Use | Operation, and what the finished building teaches the next one. |
Stage 0: Strategic Definition
This is the stage before there is a project. It establishes what the client is trying to achieve and whether a building is the right way to achieve it, and it usually sits before design begins and often before an architect is appointed. The work is strategic rather than spatial: testing the business case, examining the options, and considering alternatives that include doing nothing, or doing something other than building.
What it locks: whether to proceed at all, and on what basis.
Stage 1: Preparation and Briefing
Here the brief is properly developed. It settles the requirements, the site information, the budget, the programme, the project risks and the parameters within which design will operate. Feasibility studies belong here, as does the assembly of the wider project team.
What it locks: the problem the design is solving. A brief still loosely defined at the end of Stage 1 tends to get resolved later by change, and change is rarely cheap.
Stage 2: Concept Design
The architectural response takes shape. Massing, orientation, spatial arrangement, circulation and the outline of the architectural character are established here, with the other disciplines contributing early strategies alongside.
What it locks: more than is often assumed. Massing and orientation decisions taken at Stage 2 shape cost, efficiency and quality for the remainder of the project. It is the stage that most rewards attention and among the most commonly compressed, which is why we treat pre-concept and concept design as a distinct capability rather than an opening formality.
Stage 3: Spatial Coordination
The concept is tested against every other discipline, including structure, services, façade and vertical transportation. Where those disciplines conflict, and on a complex building they generally do somewhere, the resolution belongs here rather than on site.
What it locks: whether the concept is genuinely buildable. Issues left unresolved at Stage 3 do not disappear. They reappear during construction, where they cost more to solve and disrupt more when they are solved.
Stage 4: Technical Design
The coordinated design becomes the information from which the building is constructed: detailed drawings and specifications, together with the specialist subcontractor design that sits alongside them.
What it locks: how the building is actually made, down to the junctions and the materials.
Stage 5: Manufacturing and Construction
The building goes up. The design team's role shifts from production to response: answering queries, reviewing submittals, and observing that what is being built reflects what was designed.
What it locks: everything, in the most literal sense.
Stage 6: Handover
Completion, commissioning and the transfer of the finished building to the client, together with the information required to operate it. It is administrative in character and consequential in effect, because a building handed over without proper operational information is harder to run for the whole of its life.
What it locks: how well the building can be operated by the people who inherit it.
Stage 7: Use
This begins once the building is occupied. Where post-occupancy evaluation is carried out, it is the point at which a project stops being a set of intentions and becomes evidence, feeding what has been learned into the next one.
What it locks: nothing further on this project, and a good deal on the next.
Why the framework matters more than the numbers
Two properties make the Plan of Work useful in practice, and neither has much to do with remembering which number goes with which name.
It creates a shared vocabulary. Saying "we are at Stage 3" tells a structural engineer, a façade specialist and a cost consultant the same thing at the same moment. That sounds modest. On a project team assembled from several markets and several professional traditions, it is harder to achieve than almost anything else in the programme, and it is the difference between the three incompatible answers at the top of this article and one answer everybody recognises.
It makes the cost of change legible. Changing the massing at Stage 2 is a design exercise. Changing it at Stage 4 invalidates coordinated work across every discipline. At Stage 5 it becomes a variation, with cost and programme consequences visible to everyone, including the client's financiers. The framework makes that escalation explicit, which is a large part of why it is worth using even where nothing obliges you to.
Where the framework stops
The Plan of Work describes how developed a design is. It says nothing about whether the project has permission to proceed, and the two are not the same thing. Any building also has to satisfy the planning and approval requirements of the place it is being built in, and those run on their own timing rather than on the design programme's.
Aligning the two is the practical discipline. A stage that completes without an input it depended on produces coordinated documentation that may still need revising, which is the cost of change arriving by a different route.
What a particular project has to satisfy, and when, is specific to that project and is best established at inception rather than assumed. The stage numbering will not tell you, and a framework that describes design cannot describe permission.
Holding those two sequences against each other is a large part of what design management and project management exist to do, which is why we hold them as capabilities in their own right rather than folding them into design.
Common misconceptions
"The stages are sequential and never overlap"
In practice they overlap considerably. Long-lead packages are frequently developed to Stage 4 while other parts of the same building are still at Stage 3. The framework describes the state of a work package at least as often as the state of a whole project, and on a large development the two are rarely the same thing.
"RIBA stages are only relevant to UK projects"
The framework travelled because the problem it solves travels: describing design progress consistently between parties who do not share a professional background. It carries no regulatory force in the UAE. It remains one of the more reliable common languages available on an international project team.
"Skipping the early stages saves time"
Compressing Stages 1 and 2 can appear to save time, and the saving is real for a while. What it buys is a decision deferred rather than avoided, and the questions those stages settle are the ones most subsequent decisions rest on. They return later, when changing them is considerably more disruptive.
"Stage 4 is when the design is finished"
Technical design completes the information needed to build. Construction still generates queries, material substitutions and site conditions requiring architectural judgement, which is why construction-stage attendance is a defined service rather than an afterthought.
What this means for a client
- Understand what each stage decides, and be wary of compressing the early ones
- Confirm which stages your appointment actually covers — it may not be all of them
- Establish early what the project will have to satisfy beyond the design itself
- Expect the cost of change to rise appreciably after Stage 3
- Agree deliverables stage by stage, not just stage names — two practices can both report "Stage 3 complete" and mean different things by it
Stages are only half the programme. Architect fees in Dubai explains how the stage structure translates into a fee, and lead design consultancy sets out who holds the stages together when several practices are involved.
On Fairmont Residences Solara Tower — 51 storeys and 246 residences rising 270 metres in Downtown Dubai — a massing change discovered at Stage 4 would mean re-coordinating structure, services and façade across every one of those storeys, not one drawing. The framework earns its keep exactly at that scale, which is why we hold the same stage discipline on a five-storey building as a fifty-storey one: the cost of skipping it simply arrives sooner on the smaller project.
Our capabilities are structured around this sequence, from early concept work through coordination and delivery. If you are planning a programme and want to talk through how the stages should be scoped, get in touch.