Lesson 9.1Lesson 9.1 · Adopting BIM
BIM Maturity: Levels 0-3
The famous ladder of adoption — useful, blurry, and often mistaken for the goal
There is a ladder everyone points to. Climbing it matters; knowing which rung you're on matters less than people think.
Almost every conversation about 'how far along is BIM?' reaches for the same picture: a ladder (or a wedge, or a ramp) of maturity levels, running from Level 0 at the bottom to Level 3 at the top. It is a genuinely useful map — a shared way to describe how far an organisation, a project, or a whole industry has moved from drawing lines to managing information collaboratively.
But it is also one of the most misused ideas in the field. People treat 'reaching Level 2' as a trophy, argue about whether something is 'really Level 3', and mistake the level number for the goal. So this lesson does two things: it explains what each level actually means, in plain terms — and it makes the case that the levels are a description of *collaboration and process maturity*, not a scoreboard, and that the ladder itself is being quietly superseded by the ISO 19650 language you already know. Climb the ladder; just don't worship the rungs.
Everyone wants to say they're Level 2. Almost no one wants to answer 'is your information actually trustworthy?' — which is the real question.
The four levels, in plain terms
The classic maturity model (often drawn as the 'Bew-Richards wedge', from the UK) runs in four steps, and the honest way to read it is as *increasing collaboration*, not increasing software.
Level 0 is unmanaged CAD — 2D drawing, largely on paper or isolated files, no real collaboration or shared standards. Level 1 is managed CAD — 2D and some 3D, with a shared standard structure and often a common data environment for storing information, but with each discipline still working largely in its own silo; the information is organised, but not collaboratively modelled. Level 2 is *collaborative* BIM — each discipline produces its own 3D model and they are shared and combined (federated) to a managed, agreed process, in common formats; the disciplines coordinate through their models. This is the level most national mandates targeted, and the one most serious projects operate at today. Level 3 is full integration — a single, shared, fully interoperable model or information environment, updated in real time across the whole team and lifecycle (sometimes called iBIM). It shades into the connected models and digital twins of Module 8, and it is still largely aspirational.
Notice the axis: what climbs from 0 to 3 is not detail or dimensions but *how much the disciplines share and collaborate through managed information*. That is what maturity actually measures.
Why the levels blur — and are being superseded
For all its usefulness, the level model has real problems that the honest practitioner should hold. The definitions are fuzzy at the edges: reasonable people disagree about exactly where Level 1 ends and Level 2 begins, or what truly counts as Level 3, and the same project can look like different levels depending on who is describing it. The model also grew up in a particular (UK) context and does not map perfectly onto how BIM is practised everywhere.
More importantly, the field has *moved on* from levels as its primary language. The international standard you met in Module 5 — ISO 19650 — describes BIM in terms of *information management* (requirements, the CDE, the delivery process, the roles) rather than a level number, precisely because 'are we at Level 2?' is less useful than 'is our information required, produced, checked and handed over well?'. The levels remain a handy shorthand for a broad conversation about maturity, and you should know them because everyone references them. But when it comes to actually doing and specifying BIM, the ISO 19650 process language is more precise and is steadily replacing the level ladder. Treat the levels as a map of the territory, not the instructions for the journey.
A level tells you roughly how high you've climbed. It doesn't tell you whether the information you produce can actually be trusted.
The point is collaboration, not the number
Strip away the diagram and the deepest truth is this: maturity is about how collaboratively and reliably a team manages information, not about the label on their rung. An organisation can claim 'Level 2' and produce uncoordinated, untrustworthy models; another can quietly run a disciplined, collaborative, well-managed process and deliver enormous value without ever announcing a level. The number is a summary, and a summary is not the substance.
This connects straight back to the very first module: BIM is a *method*, standing on model, process and people (lesson 1.3), and maturity is really the maturity of that method — how well requirements are set, how genuinely disciplines collaborate through the CDE, how reliably information is checked and handed over. So when you assess 'how mature is our BIM?', resist the urge to name a level and stop. Ask the real questions: do we collaborate through shared, managed information? Is what we produce trustworthy? Does it serve the whole lifecycle? Those answers matter far more than whether you badge the result as Level 1, 2, or 3. Use the ladder to orient the conversation — then have the conversation that actually counts.
Climb the maturity ladder — Levels 0 to 3
Climb the ladder — what climbs is collaboration, not detail
Level 2 · Collaborative BIM
Most serious work todayEach discipline produces its own 3D model, and they are shared and combined (federated) to a managed, agreed process in common formats. The disciplines coordinate through their models.
The levels blur at the edges and are being superseded by ISO 19650’s language. Maturity is really the maturity of the method — collaboration and trustworthy information — not the rung label.
Three altitudes on the same idea
Read the band that fits you — or all three.
Learn the ladder as a map of collaboration. BIM maturity runs in four levels (the Bew-Richards wedge): Level 0 unmanaged CAD (2D, no collaboration); Level 1 managed CAD (shared standards and a CDE, but disciplines still siloed); Level 2 collaborative BIM (each discipline's 3D model federated to a managed process — what most mandates targeted and most serious projects do today); Level 3 full integration (a single shared, real-time, interoperable model — still largely aspirational, shading into digital twins). What climbs is *collaboration through managed information*, not detail or dimensions. The catch: the level definitions blur, and the field is moving to ISO 19650's information-management language instead. Know the ladder, but don't mistake the rung for the goal.
Use levels to orient, ISO 19650 to operate. Recognise the levels because everyone references them (most work today aims at 'Level 2' — federated discipline models, managed process, common formats). But when actually doing or specifying BIM, work in the more precise ISO 19650 terms — requirements, CDE, delivery process, roles — because 'are we Level 2?' is fuzzier and less useful than 'is our information required, produced, checked and handed over well?'. Don't chase a level badge; a team can claim Level 2 and still produce uncoordinated, untrustworthy models. The substance is collaboration and reliable information, not the label.
Assess maturity by the method, not the badge. The levels are a useful shorthand for a broad conversation about how far your organisation or supply chain has travelled, and worth knowing since mandates and clients still speak in them. But govern by substance: maturity is really how well you set requirements, how genuinely disciplines collaborate through the CDE, and how reliably information is checked and handed over — the maturity of the *method* (model, process, people) from lesson 1.3. Steer your specifications and assessments toward the ISO 19650 process language that is superseding the level ladder, and resist the vanity of claiming a level. An honest 'disciplined, collaborative, trustworthy' beats a hollow 'Level 2' every time.
“Reaching 'BIM Level 2' (or 3) is the goal — the level number tells you how good your BIM is.”
Do it yourself
Place real situations on the ladder — then ask what the level doesn't tell you.
- 1Write the four levels in one line each: 0 unmanaged CAD; 1 managed CAD, siloed; 2 collaborative federated models, managed process; 3 fully integrated, real-time, shared.
- 2Place three teams: (a) a firm emailing 2D DWGs with no standards; (b) a project where architecture, structure and services each model in 3D and federate weekly to an agreed process; (c) a firm with a CDE and standards but each discipline working alone in 2D/3D. Which level is each?
- 3Now take team (b), your 'Level 2', and ask the questions the level doesn't answer: is the data on their objects trustworthy? Are requirements clearly set? Is handover usable? Notice the level says nothing about these.
- 4Finally, write one line: why is 'we're disciplined, collaborative and our information is trustworthy' a better claim than 'we're Level 2' — and how does that connect to BIM being a method (model, process, people)?
The one line to carry out
Maturity describes how far a team or industry has climbed. The next question is what has been pushing everyone up the ladder — the mandates and national programmes driving BIM adoption across the world. Next: the global roadmaps.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →