The framework every UK practice runs on
The RIBA Plan of Work is the eight-stage framework that carries a project from a client's vague ambition to a building that has been operating for a year with the lessons written down.
Every project moves through it, every fee proposal references it, and a government client will expect deliverables aligned to it before they will expect anything else.
The day-to-day reality in 2026 looks nothing like the framework imagined when it was last revised. Here is what each stage means in a modern practice.
Find your engine
Where are you in the RIBA Plan of Work?
Choose a stage to see which BIM Engines take on the work.
Stage 0
Strategic definition
Turn an uncertain site and brief into evidence the client can act on.
Stage 0, strategic definition
The client does not yet know if they have a building project. They have a need, a site, a budget, a constraint.
Stage 0 is the conversation about whether building is even the right answer. Deliverables are light: a strategic brief, delivery options, an early view on procurement route.
The work has shifted toward feasibility modelling, embodied carbon screening, and a cold look at planning risk. Practices that win at Stage 0 model three options in a week, not two months.
Stage 1, preparation and briefing
The brief gets written while the site is surveyed and the team assembled, and the rules of the game get set: objective, budget, programme, statutory constraints.
In a connected practice this is also where the project record opens, the team is bound to it with the right permissions, and the deliverables list for the whole job gets stubbed out so nothing falls through later.
Stage 2, concept design
The first real design moves: massing, plan strategy, structural concept, services strategy.
The deliverable is a concept report the client signs off, locking the basic decisions before detail gets expensive.
Environmental analysis now belongs inside the design loop, not bolted on at the end. Daylight, overheating, embodied carbon, operational energy. The best Stage 2 reports come from teams who run those analyses in hours.
Stage 3, spatial coordination
The design resolves enough for the structural engineer, services engineer, cost consultant, and architect to reconcile their work.
Stage 3 ends with a design dimensionally consistent across drawings and models, a cost plan within tolerance, and the major planning hurdles cleared.
The shift: coordination now means the federated model resolves without clashes, not that the drawings agree on paper.
Stage 4, technical design
The deepest stage. Every junction, every specification, every product resolved. The output is a tender package complete enough to build from.
Procurement begins in earnest here, with material schedules built, long-lead items identified, and specifications written against both.
A connected specification-to-procurement pipeline pays back more at this stage than at any other. Re-keying a material schedule into a spreadsheet is friction a 2026 practice should have engineered away.
Stage 5, manufacturing and construction
The building gets built, and the architect shifts from designer to contract administrator: inspections, RFIs, submittals, change orders, payment certificates.
The paperwork volume is enormous and the cost of getting any of it wrong is high.
A practice running Stage 5 on email and a shared drive is leaving margin on the floor and carrying risk it does not need.
Stage 6, handover
The building gets commissioned. The architect produces an as-built record, an O&M manual, and a building user guide. Defects get logged and resolved through the liability period.
Short but consequential: a clean handover protects the practice from years of post-completion claims.
Stage 7, use
The newest formal stage. The architect returns at intervals to capture how the building actually performs, and feeds that into the next project.
Post-occupancy evaluation, performance gap analysis, user feedback. Stage 7 is what turns a project-by-project business into a learning organization.
Where modern software changes the shape
The Plan of Work was designed when each stage produced a deliverable handed across a desk to the next person.
Modern practice is continuous instead. The model stays alive across stages, the cost plan updates as the design changes, and the specification feeds procurement, which feeds the construction record, which in turn feeds the as-built model and the O&M manual.
The stage gates still matter, but the deliverables flow through them, not into them.
Built right, a gate is a checkpoint on a continuous record, not a translation between formats. That is the practice we are building software for.