IGCSE vs GCSE: What’s the Difference and Which Is Right for You?
August 18, 2026
No Comments
“What BIM Level are you working to?” is a question that trips up a surprising number of professionals moving into BIM roles, partly because the terminology has shifted over the past several years. This guide breaks down the original UK BIM maturity levels — Level 0 through Level 3 — explains exactly how ISO 19650 relates to that framework, and looks at what level of BIM maturity Dubai and Abu Dhabi projects typically expect from the professionals working on them.
The BIM maturity levels model originated in the UK as a way to describe how collaboratively a project team works with digital information, ranging from no digital collaboration at all (Level 0) through to fully integrated, cloud-based collaboration across a building’s entire lifecycle (Level 3). The UK government adopted this framework as policy, mandating BIM Level 2 on all centrally-funded public construction projects from 2016 onward — a decision that is widely credited with accelerating BIM adoption across the UK construction industry far faster than market forces alone would have achieved.
The levels are not simply about which software you use. They describe the degree of collaboration, standardization, and structured information exchange happening between everyone working on a project — the architect, structural engineer, MEP consultant, contractor, and client.
Level 0 is essentially unmanaged 2D CAD drafting, with data typically exchanged as paper drawings or basic electronic files such as PDFs. There is no shared model, no collaboration process, and no structured exchange of digital information between disciplines. Each consultant works independently and coordination happens manually — overlaying printed drawings on a light table, or comparing PDFs by eye. This describes most construction projects globally before digital collaboration tools became standard practice, and it still describes plenty of small, low-complexity projects today.
Level 1 introduces some structure: a mix of 2D and 3D CAD is used, often with a Common Data Environment beginning to appear for managing drawing revisions and version control, but each discipline is still largely working in isolation. There isn’t yet genuine model-based collaboration between disciplines — the architect might have a 3D model, the structural engineer might have a separate one, but they are not systematically coordinated together within one shared digital environment. Level 1 represented the state of most mid-size firms as CAD tools matured through the 1990s and 2000s but before true BIM authoring software became standard.
Level 2 is where BIM as most people understand it today actually begins. Each discipline creates and maintains its own 3D model — architectural, structural, MEP — but these models are shared, linked, and coordinated together, typically through file-based collaboration in a Common Data Environment, with clash detection run across the federated model. This is the level the UK mandated for centrally-funded public projects from 2016, and it remains the most commonly referenced target maturity level on commercial and infrastructure projects internationally, including across much of the Gulf region.
Level 2 does not require every consultant to work inside a single shared model file — it specifically allows each discipline to use its own software and maintain its own model, provided those models are properly coordinated and exchanged in agreed, structured formats.
Level 3, sometimes referred to as “Open BIM” or full integration, describes a single, shared, cloud-hosted model that every discipline works within simultaneously, using open, non-proprietary data standards so that the model isn’t locked to any one software vendor. In practice, Level 3 as originally envisioned — a genuinely unified, real-time, single source-of-truth model across every discipline and the entire asset lifecycle — remains more of a long-term industry direction than a fully achieved standard on most live projects, even now. Elements of it are increasingly common — cloud-based common data environments, real-time model federation — but a fully vendor-neutral, single-model Level 3 environment is still the exception rather than the rule.
| Level | Description | Collaboration Style | Typical Era / Status |
|---|---|---|---|
| Level 0 | Unmanaged CAD, paper or basic electronic drawings | None — each party works independently | Pre-digital collaboration; still seen on very small projects |
| Level 1 | Managed 2D/3D CAD with basic version control | Limited; disciplines largely isolated | Common through the 1990s–2000s |
| Level 2 | Collaborative 3D models per discipline, federated and coordinated | Structured file-based collaboration via a Common Data Environment | UK-mandated from 2016; current baseline standard internationally |
| Level 3 | Single, shared, cloud-based model using open data standards | Full real-time integration across disciplines and lifecycle | Long-term industry direction; partial adoption today |
In 2018, the International Organization for Standardization published ISO 19650, developed jointly by the British Standards Institution, the Centre for Digital Built Britain, and the UK BIM Alliance, as an international evolution of the principles first set out in BIM Level 2. Rather than describing a single “level” a project has achieved, ISO 19650 focuses on the actual mechanics of information management: how requirements are defined, how a Common Data Environment is structured and governed, how information is exchanged between parties, and how responsibility for information delivery is assigned across a project team.
In practical terms, most projects that would previously have been described as “BIM Level 2” are now described as ISO 19650-compliant, since the standard captures the same collaborative, federated-model approach but with far more detail on process, documentation, and roles — concepts such as the BIM Execution Plan (BEP), Exchange Information Requirements (EIR), and the Common Data Environment’s status-based workflow (Work in Progress, Shared, Published, Archived) all originate from Level 2 thinking but are formally codified in ISO 19650. The shift represents a move from a technology-and-collaboration framing of BIM maturity toward a genuinely process-and-information-management framing — which is why “which BIM Level are you on” has largely been replaced in professional conversation by “are you working to ISO 19650.”
Dubai Municipality’s BIM circular mandates BIM submission on projects above a defined value threshold and on high-rise developments above a set number of floors, and in practice the workflow it expects — coordinated 3D models per discipline, structured clash detection, digital model submission alongside traditional permit drawings — corresponds closely to BIM Level 2 / ISO 19650 working practice rather than Level 0 or Level 1. Abu Dhabi Municipality (ADM) runs its own building permit and submission framework with its own conventions, distinct enough from Dubai’s that professionals moving between the two emirates need to understand both sets of requirements rather than assuming one format applies everywhere in the UAE.
For a working BIM professional in Dubai, this means the practical skill that actually gets tested on the job isn’t abstractly “knowing BIM” — it’s being able to produce coordinated, clash-checked discipline models inside a managed Common Data Environment, to a defined Level of Development, in the specific submission format the relevant authority expects. Orbit’s Revit Architecture, Revit Structure, and Revit MEP courses each build toward Dubai Municipality and Abu Dhabi Municipality submission standards directly, rather than teaching Revit in the abstract and leaving students to work out local requirements later.
Understanding the BIM Levels framework matters less as trivia and more because it explains why certain workflows are non-negotiable on BIM-mandated projects:
Even though ISO 19650 has largely superseded the formal “Level 0/1/2/3” language in official project documentation, understanding the levels framework still matters for a working BIM professional for a simple reason: it gives you a fast, shared vocabulary for describing how mature a project’s or a firm’s actual collaboration practice is, independent of what its paperwork claims. A project can nominally reference ISO 19650 in its BIM Execution Plan while its day-to-day working practice is genuinely closer to Level 1 — disciplines modeling in relative isolation, coordination happening late and manually. Recognizing that gap between documented intent and actual practice is a skill in itself, and the levels framework remains one of the clearest mental models for spotting it.
It’s worth grounding this in a concrete example rather than leaving it abstract. On a genuine Level 2 / ISO 19650 project, a BIM Coordinator’s week typically includes: reviewing newly uploaded discipline models in the Common Data Environment against their Work-in-Progress or Shared status; running a federated clash detection pass in Navisworks across the architectural, structural, and MEP models; logging and assigning identified clashes back to the relevant discipline lead for resolution; checking that models being issued for a particular drawing set actually meet the Level of Development agreed for that project stage; and updating the Master Information Delivery Plan if a discipline’s delivery schedule has genuinely shifted. None of this requires exotic technology — it requires disciplined, consistent process, which is exactly what separates projects that talk about BIM Level 2 from projects that actually operate at it.
For a firm or individual trying to honestly gauge where they currently sit, a few practical questions are more useful than the formal level definitions alone: Do different disciplines’ models actually get linked and clash-checked before issue, or only compared manually and occasionally? Is there a single managed location every team member pulls the current, approved model from, or do coordinated updates still happen by email attachment? Are Levels of Development actually defined and followed at each project stage, or applied loosely and inconsistently? Answering honestly against these questions usually places a firm somewhere between Level 1 and Level 2 in practice, regardless of what its marketing materials or tender responses claim — and identifying that gap honestly is the first step toward closing it.
One point of genuine confusion worth clearing up directly: BIM maturity Levels (0 through 3) and Levels of Development (LOD 100 through 400) are two entirely different measurement scales that happen to share similar-sounding names. BIM maturity Levels describe how collaboratively a project team works — the process and technology maturity across the whole team. Levels of Development describe how detailed a specific model element is at a given project stage — a door at LOD 200 might just be a generic placeholder, while the same door at LOD 400 carries its exact manufacturer, hardware specification, and installation detail. A project can be operating at BIM Level 2 collaboration maturity while individual elements within its model sit at varying LOD stages appropriate to where the design currently stands. Understanding that these are independent scales, measuring different things, avoids a genuinely common source of confusion for people new to BIM terminology.
BIM maturity levels didn’t spread through the industry purely through voluntary adoption — government procurement mandates played the decisive role in most markets. The UK’s 2016 requirement for BIM Level 2 on all centrally-funded public projects is the clearest example: rather than leaving adoption to individual firms’ judgment, the UK government effectively required any firm wanting to bid on public work to demonstrate Level 2 capability, which forced the wider supply chain — architects, engineers, contractors, and their software and training providers — to mature quickly in response. The Gulf region has followed a broadly similar pattern: rather than a single nationwide mandate, individual authorities including Dubai Municipality have introduced their own BIM circulars targeting specific project value thresholds and building heights, which has had a comparable effect of forcing the local design and construction supply chain toward Level 2 / ISO 19650-equivalent working practice on a growing share of the market, even without a single unified UAE-wide BIM law.
In practice, a meaningful share of projects that describe themselves as “BIM Level 2” or “ISO 19650-compliant” in their marketing or tender documentation fall short of that standard in daily execution — models get built in isolation and only loosely coordinated, the Common Data Environment exists nominally but its status discipline isn’t actually enforced, and clash detection happens late or inconsistently rather than as a routine part of the design process. The consequences show up predictably: coordination errors that should have been caught digitally get discovered on site instead, at far higher cost to fix; schedule slippage as design teams scramble to resolve conflicts that a properly run Level 2 process would have surfaced months earlier; and disputes between consultants and contractors over which discipline’s model was actually “approved” at a given point in time, a problem the CDE’s status system exists specifically to prevent. Recognizing the gap between a project’s claimed BIM maturity and its actual working practice is a genuinely valuable skill for a BIM Coordinator or Manager, since closing that gap — not just checking a compliance box — is where real value gets delivered.
Some commentators have speculated about a theoretical “Level 4” or beyond, extending Level 3’s open, integrated model concept into areas such as generative design, real-time IoT data feeding directly back into an operational Asset Information Model, or AI-assisted clash resolution. None of this is formally codified the way Levels 0 through 3 are, and treating it as an established framework would overstate how settled the terminology actually is. What is genuinely happening on the ground, rather than purely speculative, is a steady deepening of Level 2 / ISO 19650 practice: more projects genuinely operating at that standard rather than merely claiming it, more mature Common Data Environment tooling, and closer integration between design models and downstream facilities management systems after handover. For a working BIM professional, the practical advice is to focus on genuinely mastering Level 2 / ISO 19650 working practice, since that is where actual hiring demand and project requirements sit today, rather than chasing speculative future terminology that hasn’t yet translated into concrete job requirements.
If you’re a working professional trying to apply this framework practically, a short self-check is more useful than memorizing definitions. Before your next project kicks off, ask whether the Exchange Information Requirements have actually been discussed with every discipline lead, not just circulated as a document; whether everyone genuinely understands which Common Data Environment folder or platform status represents the current approved version; and whether a clash-detection pass is scheduled as a routine, recurring task rather than a one-off event squeezed in near the end. Projects that can answer yes to all three are usually operating close to genuine Level 2 / ISO 19650 practice. Projects that can’t are a candidate for exactly the kind of process improvement a well-trained BIM Coordinator is positioned to lead.
You will still hear “Level 2” used informally, especially by professionals who trained before ISO 19650 became widespread, but formal project documentation and tender requirements now almost always reference ISO 19650 directly rather than the older Level 2 terminology.
Focus on understanding Level 2 working practice in depth, since it describes the collaborative, coordinated-model workflow used on the overwhelming majority of live BIM-mandated projects today, including in Dubai and Abu Dhabi.
Not necessarily new software so much as open, vendor-neutral data standards and genuinely real-time, cloud-hosted collaboration across every discipline simultaneously — which is more a shift in process and data standards than a single software purchase.
Projects falling under Dubai Municipality’s BIM circular are expected to work at a standard corresponding to Level 2 / ISO 19650: coordinated discipline models, digital clash detection, and structured model submission rather than 2D-only documentation.
Yes — smaller, lower-complexity projects without a BIM mandate still commonly operate at Level 0 or Level 1, and there is nothing inherently wrong with that when the project’s scale doesn’t justify the overhead of a fully coordinated BIM environment.
