UK Checklists: RIBA Plan of Work Stages, Remote Support for Stages 2–4

The RIBA Plan of Work organises a building project into eight stages, Stage 0 through Stage 7, running from strategic definition and briefing through design, construction, handover and in-use review. UK architects, engineers and clients use it as the shared reference for what should happen, when, and who signs it off, at every point in a project.

---

TL;DR:

• Proper use of the responsibility matrix and Job Book requires ongoing checking and sign-off at each stage gateway, not just initial documentation.
• Combining overlays like Passivhaus or accessibility at early stages prevents costly redesigns later in the project lifecycle.
• Building Information Modelling enables early clash detection and real-time coordination, reducing delays and rework during technical design and construction.
• Unresolved decisions from early stages, especially cost or planning conditions, often cause project delays and increased costs when carried into technical design.
• Remote embedded engineering can accelerate Stage 2 to Stage 4 testing and compliance, particularly on complex projects with strict deadlines.

---

Table of Contents

• RIBA Plan of Work stages explained: how the framework actually works
• Stage 0: strategic definition, feasibility and the first client decisions
• Stage 1: preparation and brief, the checklist that shapes everything after
• Stage 2: concept design, where planning strategy and budget get real
• Stage 3: spatial coordination, catching clashes before they hit site
• Stage 4: technical design, the point of no return before site work starts
• Stage 5: manufacturing and construction, keeping site queries under control
• Stage 6: handover and closeout, what you should actually receive
• Stage 7: in use, why the project doesn’t really end at handover
• RIBA overlays: adding Passivhaus, BIM and accessibility without derailing a stage
• How to use the responsibility matrix and Job Book without losing the plot
• Historical development and evolution of the RIBA Plan of Work
• Comparison with other project management frameworks in architecture
• Updates and amendments in the latest RIBA Plan of Work edition
• Role of sustainability and regulations within each stage
• Digital tools and technologies supporting the RIBA stages
• Common challenges and best practices in applying the Plan of Work
• When remote embedded engineering pays off across the RIBA stages
• Sources

RIBA Plan of Work stages explained: how the framework actually works

The RIBA Plan of Work exists because construction projects fail most often at handovers between disciplines, not within them. Each stage carries a task bar setting out what architects, engineers, contractors and clients must deliver before the project moves on.

Teams track this through a responsibility matrix, a grid showing who owns which task at which stage. The RIBA Job Book turns that matrix into working checklists and forms, tying it to appointments, procurement routes and fee stages.

• The Plan defines deliverables and decision points, not design solutions.
• Task bars show overlapping responsibilities across architecture, structure, services and cost.
• The Job Book converts stage requirements into contractual and administrative actions.
• Procurement strategy (traditional, design and build, construction management) shifts when certain stage activities happen.

Stage 0: strategic definition, feasibility and the first client decisions

Stage 0 asks whether the project should happen at all, and in what form. A feasibility study tests options against the client’s budget, site constraints and business case before anyone commits to a design route.

• Options appraisal comparing extend, refurbish, rebuild or do nothing.
• A strategic brief setting core requirements and an initial budget range.
• Appointing the right advisers (architect, cost consultant, structural engineer) for the scale of work.
• A decision milestone where the client formally commits to proceed to Stage 1.

Stage 1: preparation and brief, the checklist that shapes everything after

Stage 1 turns a strategic idea into a working brief a design team can actually design against. Skimping here is the single most common cause of scope creep later.

• Site and building surveys (topographical, structural, ground investigation).
• A project programme and consultant appointment schedule.
• A risk register and outline planning strategy for the site.
• Sign-off on the initial project brief, sustainability aspirations and site information before concept work starts.

Stage 2: concept design, where planning strategy and budget get real

Concept design is where abstract requirements become an actual building form, and where the first serious cost and planning conversations happen. Get this stage wrong and every later stage inherits the problem.

• Concept sketches and massing options tested against the brief.
• Sustainability targets and energy strategy set at outline level.
• Early cost planning to check the concept against the approved budget.
• Pre-application planning engagement, particularly on constrained or heritage sites.
• Client sign-off on a single preferred concept before moving into coordination.

Stage 3: spatial coordination, catching clashes before they hit site

Stage 3 exists to resolve conflicts between disciplines on paper, not on scaffolding. Structural grids, service routes and architectural layouts get tested against each other, usually through a shared 3D model.

• Coordination between structural engineering, building services and architectural layout.
• Clash detection and resolution using shared models, reducing the risk of rework once construction starts.
• Updated cost information reflecting the coordinated design.
• A coordinated design pack ready to progress into full technical detail at Stage 4.

Stage 4: technical design, the point of no return before site work starts

Technical design has to be genuinely finished, not merely advanced, before tender or construction. This is where structural calculations, specifications and Building Regulations compliance get locked down.

• Full construction information: drawings, schedules and specifications ready to build from.
• Specialist structural and services calculations completed and checked.
• Building Regulations compliance confirmed, including fire, thermal and structural sign-off.
• Coordinated technical package issued for tender or contractor pricing.

Pro Tip: Resolve technical design before the contractor mobilises on site, not during the first few weeks of the programme. Practitioners consistently find that unresolved design queries after mobilisation cause the costliest and slowest variations, because changes now touch procured materials, subcontractor programmes and site sequencing all at once.

Stage 5: manufacturing and construction, keeping site queries under control

Stage 5 is the build itself, but the design team’s job doesn’t stop when the contractor mobilises. Requests for information and site instructions still flow, and someone has to answer them quickly enough to keep the programme moving.

• Contractor mobilisation, site setup and quality control procedures.
• Timely responses to RFIs and site instructions from the design team.
• As-built records started as work progresses, not reconstructed afterwards.
• Regular progress reporting against the agreed programme and budget.

Expect some genuine overlap here. On complex projects, Stage 4 technical design and Stage 5 construction often run in parallel, with later work packages still being finalised while earlier ones are already on site.

Stage 6: handover and closeout, what you should actually receive

Handover is where a lot of clients get short-changed, mainly because they don’t know what to ask for. A proper closeout gives you a working building plus the paperwork to run it.

• Commissioning of building systems and formal handover to the client or operator.
• Operation and maintenance manuals, warranties and, where relevant, user training.
• A snagging list agreed before the defects liability period starts.
• Final account agreed and the defects period formally closed out.

Stage 7: in use, why the project doesn’t really end at handover

Stage 7 covers the building’s operational life, and it’s the stage most guides skip past fastest, wrongly. Post-occupancy evaluation checks whether the building performs as designed, not just as drawn.

• Post-occupancy evaluation against the original design intent and energy targets.
• Ongoing maintenance planning based on how the building actually performs.
• Performance monitoring feeding lessons learned back to the design team.
• Architecture for London notes that a refurbishment or extension often restarts the cycle at Stage 0, using Stage 7 findings as the new feasibility evidence.

RIBA overlays: adding Passivhaus, BIM and accessibility without derailing a stage

Overlays layer specialist requirements onto the standard eight stages rather than bolting them on at the end. Designing Buildings describes overlays covering Passivhaus, inclusive design, smart buildings and sustainability, each with its own task bar sitting alongside the core Plan.

• Passivhaus overlay: airtightness and fabric-first targets need setting from Stage 2, not retrofitted at Stage 4.
• Inclusive design overlay: access strategy shaped at Stage 1 brief stage, checked again at Stage 3.
• BIM overlay: information requirements set out through the UK BIM Framework, defining what models and data get exchanged at each stage.
• Landscape overlay: the Landscape Institute’s digital plan of work for landscape shows how a single discipline can run its own overlay against the main stages.

Overlays work because they force specialist decisions into the stage where they’re cheapest to change, rather than letting them surface as problems during technical design or, worse, on site once materials are ordered.

How to use the responsibility matrix and Job Book without losing the plot

A responsibility matrix only earns its place if someone actually checks it at each stage gateway, not just files it.

1. Read the task bar for the current stage and confirm who owns each listed task, not just who’s named on the appointment.
2. Require a written sign-off from the client at every stage gateway before design work progresses, using the Job Book’s checklists as the template.
3. Note appointment and scope changes in the contract as they happen, rather than reconciling them retrospectively at Stage 4 or 5.
4. Cross-check budget updates against the live cost tracking recommended at each stage, so cost surprises surface early rather than at tender.

Historical development and evolution of the RIBA Plan of Work

The Plan of Work has existed in some form since 1963, when RIBA first published a stage-based structure to standardise how architectural practices organised project work. That original version used a letter-coded system (Stages A to L) rather than the numbered stages used today, and it focused almost entirely on the architect’s own workflow.

Successive revisions through the 1990s and 2000s widened the scope to reflect how projects actually ran, bringing in cost consultants, structural engineers and, eventually, contractors as named participants rather than background actors. The 2013 edition marked the shift to the current numbering, Stage 0 to Stage 7, and introduced the idea of task bars running across disciplines rather than a single linear handover chain.

The 2020 edition, still the current reference, sharpened the focus on sustainability outcomes, embedded digital information management more explicitly, and clarified the overlay concept so specialist requirements could sit alongside the core stages without rewriting them. That’s a meaningful shift from the 1963 original: the Plan moved from describing one profession’s internal process to describing how an entire multidisciplinary team, client included, moves a project from idea to operation.

What hasn’t changed is the underlying logic. Every version has organised work around decision points rather than calendar time, and every version has treated the brief as the document everything else measures against. That consistency is why practices still reference “RIBA stages” as shorthand decades after the letter-coded system disappeared.

Comparison with other project management frameworks in architecture

The RIBA Plan of Work isn’t the only structured framework construction and design teams use, and it’s worth knowing where it sits relative to the alternatives.

Generic project management standards, such as the frameworks published by the Association for Project Management, focus on governance, risk and stakeholder management across any industry, not specifically on design and construction sequencing. They’re useful for programme-level oversight on large developments but don’t tell an architect what a Stage 3 coordination package should contain.

The IStructE publishes its own structural engineer’s plan of work, mapped directly onto the RIBA stages rather than replacing them. It exists because structural design decisions (foundation type, frame material, load paths) often need resolving earlier than the RIBA Plan’s generic task bar implies, particularly on complex or constrained sites.

Government-focused frameworks like the Government Soft Landings approach overlay operational readiness and building performance requirements onto existing stage structures, RIBA’s included, rather than standing as a competing sequence.

The practical difference is scope. RIBA’s Plan covers the whole project lifecycle from strategic definition to in-use review, with named deliverables at every gate. Generic PM frameworks cover process and governance without specifying design content. Discipline-specific plans (structural, landscape, services) add depth within one profession but rely on RIBA’s numbering to stay synchronised with everyone else. For a UK building project, the RIBA Plan is the framework virtually every consultant already speaks, which is exactly why it works as the coordination layer even when specialist plans run alongside it.

Updates and amendments in the latest RIBA Plan of Work edition

The 2020 edition remains the current version, and it changed more than the numbering suggests. Three shifts stand out for anyone still working from an older copy.

Sustainability moved from an add-on consideration to a stage-by-stage requirement. Earlier editions treated environmental performance as something to address mainly at Stage 2 concept design. The 2020 version embeds sustainability checkpoints across every stage, from strategic definition through to post-occupancy evaluation at Stage 7, reflecting how UK planning authorities and Building Regulations have tightened energy and carbon expectations since the previous major revision.

Digital information requirements became explicit rather than assumed. The 2020 edition ties directly into the information management approach behind the UK BIM Framework, setting out what information should exist at each stage gate and in what format, rather than leaving model and data exchange to individual practice convention.

The overlay concept was formalised. Rather than treating specialist requirements as bespoke additions each practice invented for itself, the 2020 edition gives overlays a defined structure, which is why Passivhaus, inclusive design and smart building overlays now follow a consistent pattern across different practices and projects.

The RIBA Job Book was updated alongside the Plan itself, with its 10th edition providing checklists and forms matched to the 2020 stage structure rather than the older lettered version. Anyone still working from Job Book checklists tied to a pre-2020 Plan is very likely working from mismatched documentation, worth checking before relying on it for a live project.

Role of sustainability and regulations within each stage

Sustainability and regulatory compliance aren’t a single checkpoint in the RIBA Plan; they’re distributed across every stage, and skipping the early ones is the most common way projects end up retrofitting compliance under time pressure.

At Stage 0 and Stage 1, sustainability shows up as strategic ambition: energy targets, embodied carbon aspirations and site-specific constraints like flood risk or conservation status, all of which shape the brief before a single drawing exists. Building Regulations awareness at this point is mostly about identifying which Approved Documents will govern the project, not yet complying with them.

Stage 2 concept design is where sustainability targets get tested against a real building form for the first time, alongside early planning policy compliance. Planning authorities increasingly expect evidence of energy strategy and, in many London boroughs, whole-life carbon assessment at this stage, not later.

Stage 3 and Stage 4 are where regulatory compliance becomes concrete rather than aspirational. Structural calculations must satisfy Eurocodes, fire strategy must satisfy Part B of the Building Regulations, and thermal performance must satisfy Part L, all resolved and checked before technical design closes. CIBSE guidance on building services performance typically gets applied most heavily here, since services design directly affects both energy compliance and occupant comfort outcomes.

Stage 5 and Stage 6 shift the focus to verification: commissioning checks that installed systems actually perform as calculated, not just as specified. Stage 7 closes the loop with post-occupancy evaluation, checking whether real-world energy use matches the Stage 2 targets, information that then feeds directly into the next project’s Stage 0 feasibility work.

Digital tools and technologies supporting the RIBA stages

Building Information Modelling has become the default coordination method for Stage 2 through Stage 5, and the UK BIM Framework sets out how information should be structured and exchanged between disciplines at each stage gate, rather than leaving it to informal file-sharing conventions.

Shared 3D models let architects, structural engineers and services consultants check their work against each other continuously through Stage 3 spatial coordination, catching clashes on screen rather than discovering them when a duct and a beam want the same space on site. This is the practical mechanism behind clash detection, and it’s the single biggest reason Stage 3 exists as a distinct stage at all.

Cloud-based document management and cost tracking tools support the Job Book’s checklist approach by giving every party visibility into what’s been signed off and what’s still outstanding, useful for real-time budget tracking as costs firm up through Stage 2 to Stage 4.

The NBS links specification writing directly to information management practice, meaning the specifications produced at Stage 4 connect straight through to procurement and, later, to the operation and maintenance documentation handed over at Stage 6.

None of this technology changes what the RIBA stages require. It changes how quickly a team can prove they’ve met the requirement, and how easily that evidence survives a change of contractor, consultant or client representative partway through a project.

Common challenges and best practices in applying the Plan of Work

The Plan of Work fails most often not because teams don’t know the stages, but because they treat stage boundaries as suggestions rather than gates.

The most frequent problem is carrying unresolved decisions from Stage 2 into Stage 4, hoping they’ll resolve themselves during technical design. They rarely do. A concept that was never properly costed, or a planning consent with conditions nobody read closely, resurfaces at the worst possible point, usually after the technical package is nearly complete.

A second recurring issue is treating the responsibility matrix as paperwork rather than a working tool. Teams that only consult the Job Book checklists when something has already gone wrong lose the framework’s actual benefit, which is catching the gap before it becomes a problem.

Overlays get mishandled almost as often. Adding a Passivhaus or accessibility overlay at Stage 4, after the concept is fixed, forces expensive redesign that would have been a minor adjustment at Stage 2. The overlay guidance exists specifically to prevent this, but only if someone applies it early enough to matter.

Good practice tends to share a few habits: sign-off at every stage gate rather than a general sense of progress; a genuinely resourced Stage 1 brief rather than a rushed placeholder; and treating Stage 4 technical design as a hard deadline rather than a target. Teams that build in overlap deliberately, running early Stage 5 procurement alongside late Stage 4 detailing on complex projects, tend to fare better than teams that pretend the stages are strictly sequential when the programme clearly isn’t.

When remote embedded engineering pays off across the RIBA stages

Remote embedded engineers add most value from Stage 2 through Stage 4, when structural options need testing fast enough to keep concept design moving and technical packages need finishing to Eurocode standard before tender. Speed here protects the Stage 4 deadline that so many projects miss.

The practical benefits are turnaround time, direct Eurocode compliance without translation overhead, and cost control against a fixed capacity rather than variable overtime. When selecting support, check integration speed, NDA terms, and whether outputs arrive genuinely review-ready rather than needing rework.

Xponexus Engineering provides exactly this model: embedded structural and civil engineering support for UK consultancies, kicked off within 48 hours, working inside your existing workflow rather than alongside it.

— Mohammed

Sources

• RIBA Plan of Work
• Overlays to the RIBA plan of work — Designing Buildings