BIM in Saudi Arabia is being adopted at pace, driven by Vision 2030 giga-projects, expanding transport and utility infrastructure, and tightening documentation requirements on public works. What is less widely understood is how that adoption actually works in the Kingdom: which standards apply, where the requirements come from, and why they differ so sharply between a giga-project package and a mid-size commercial building in Riyadh.
This guide covers the drivers behind adoption, the standards and codes that shape deliverables, how requirements vary by client type, the approval layers a model has to survive, and the points where implementation most often stalls. For the delivery side — modelling scope, coordination and documentation output — see our BIM services in Saudi Arabia.
- What Is Driving BIM in Saudi Arabia
- The standards landscape: ISO 19650 and the Saudi Building Code
- BIM dimensions and deliverables explained
- How requirements differ by client type
- Approval layers beyond the consultant
- Sector adoption across the Kingdom
- Where implementation stalls
- A project readiness checklist
- Frequently asked questions
What Is Driving BIM in Saudi Arabia
Three forces are doing most of the work, and they operate differently from one another.
Project scale. The giga-project programme — NEOM, Qiddiya, Red Sea Global, Diriyah, New Murabba and the Riyadh Metro among others — involves coordination volumes that 2D workflows cannot absorb. When a single package spans multiple contractors across several disciplines with concurrent design and construction, a federated model stops being an efficiency measure and becomes the only practical coordination method.
Client-side capability. Large Saudi developers and government entities have built internal digital delivery teams over the past several years. That changes the demand side: information requirements are now written into tender documents by people who understand what they are asking for, which raises the floor for what a submission has to contain.
Lifecycle and asset data. Owners increasingly want the model to survive handover — asset registers, maintenance data, space management. This shifts the emphasis from geometry to structured information, and it is the requirement most bidders underestimate.
Contractual, not statutory — an important distinction
There is a common misconception that BIM is legally mandated across Saudi Arabia the way certain jurisdictions have imposed public-sector mandates. In practice, most BIM requirements in the Kingdom arrive contractually — through the employer’s information requirements in a tender package, or through a client’s own digital delivery standard — rather than through a blanket national regulation.
The Standards Landscape
ISO 19650
ISO 19650 is the international standard series for managing information across the asset lifecycle using BIM. It is the framework most commonly referenced in Saudi tender documents that specify a formal information management approach. Our guide to BIM standards covers the wider standards picture.
The series is structured around concepts that appear repeatedly in Saudi employer’s information requirements:
- Organisational, asset, project and exchange information requirements — what the client needs, expressed at four levels
- The BIM Execution Plan (BEP) — how the delivery team will meet those requirements, submitted pre- and post-appointment
- The Common Data Environment (CDE) — a single controlled source for project information with defined status codes
- Level of information need — replacing the older, looser “LOD” shorthand with a requirement defined per purpose rather than a global number
Adoption in the Kingdom is uneven. Giga-projects and international consultants generally work to it explicitly. Mid-market projects often reference it in name while running a document control process that does not actually implement it — which produces the familiar situation of a project with a CDE in the specification and email attachments in practice.
The Saudi Building Code
The Saudi Building Code (SBC) governs technical compliance for buildings in the Kingdom, covering structural, mechanical, electrical, sanitary, energy conservation and fire protection requirements across its constituent codes.
The SBC does not prescribe how a model is built. What it does is determine what the model has to be able to demonstrate — clearances, fire ratings, egress geometry, system capacities, energy performance parameters. A model that carries geometry but not the parameters needed to evidence compliance will still generate a full round of consultant comments.
The practical implication for information management is that compliance-relevant data should be modelled as structured parameters rather than left in drawing annotations, so that checking is repeatable and the information survives into the handover dataset.
Client-specific and operator standards
Beyond the code, several categories of client operate their own engineering standards that take precedence within their scope — most visibly in the energy and industrial sector, where operator-specific engineering standards govern design and documentation on facilities within their remit. Where these apply, they typically override generic project conventions, and the delivery team’s first task is establishing which document set actually governs.
BIM Dimensions and Deliverables Explained
The “dimensions” terminology is used loosely across the industry. The definitions below reflect common usage, but the only definition that matters on a given project is the one in that project’s information requirements.
| Dimension | What it adds | Typical use in the Kingdom |
|---|---|---|
| 3D | Coordinated geometry across disciplines | Baseline on any project with a BIM requirement |
| 4D | Construction sequencing linked to the programme | Common on giga-projects and complex phasing |
| 5D | Cost data and quantity extraction | Growing, often driven by contractor-side estimating |
| 6D | Sustainability and energy performance | Rising with energy conservation requirements |
| 7D | Asset and facility management data | Requested at handover more often than it is delivered well |
Alongside the dimensions, the deliverables most frequently specified are:
- Federated modelling. Combining discipline models into a single coordination environment. The value is entirely dependent on model discipline — consistent origins, agreed naming, controlled revisions.
- Clash detection. Identifying conflicts between structure, architecture and building services before construction. The output that matters is not the raw clash count but a triaged, assigned and closed-out report. Our guide to BIM clash detection covers the process in detail.
- BIM coordination. The process around clash detection — coordination meetings, issue assignment, resolution tracking. This is a workflow, not a software output, and it is where most of the actual value is realised.
- Model-based documentation. Extracting drawings from the coordinated model rather than drafting them separately, so that geometry stays consistent across every view. The level of development required depends on the output — see our guide to BIM levels of development from LOD 100 to 500.
- Asset information delivery. Structured data handover for operations, typically as a defined schema agreed at the outset rather than assembled at the end.
How Requirements Differ by Client Type
This is the section most likely to affect a bid, and it is rarely written down anywhere.
| Client type | Typical requirement level | What usually catches teams out |
|---|---|---|
| Giga-project developers | Full ISO 19650 implementation, detailed EIR, defined CDE, structured handover | Naming and classification conventions specific to that programme |
| Government entities and ministries | Varies widely by entity and project; often a defined deliverable list without a full information framework | Approval workflows that sit outside the CDE |
| Large private developers | Increasingly formal, often modelled on international consultant practice | Scope creep between coordination and documentation |
| Mid-market commercial | BIM specified but loosely defined | The absence of an EIR, which leaves the scope open to interpretation |
| Industrial and energy facilities | Operator engineering standards take precedence | Assuming project conventions apply where operator standards govern |
The pattern is consistent: the risk is rarely modelling capability. It is the gap between what the tender says and what the client’s review process actually expects.
Approval Layers Beyond the Consultant
A coordinated model is not the end of the chain. Several approval layers apply to Saudi projects, each with its own timeline, and planning for consultant review alone is a common programming error.
- Consultant review. Design conformance review of submitted documentation, with defined review periods on most substantial contracts.
- Municipal approval. Building permit and related approvals administered through the municipal system, with requirements varying by municipality and project category.
- Civil Defence. Fire protection systems, fire-rated construction, penetration fire-stopping, smoke management and egress-related works carry an additional review layer alongside Saudi Building Code requirements.
- Utility and infrastructure authorities. Works touching power, water, drainage or public realm interface frequently require sign-off from the relevant provider.
The response is procedural rather than technical: mark authority-dependent items on the submittal register from the outset and give them longer lead times than consultant-only items. The same discipline applies to the documentation itself — our guide to shop drawings in construction covers the submittal cycle and review outcomes in full.
Sector Adoption Across the Kingdom
- Infrastructure and transport. Among the strongest adoption, driven by project scale and the coordination demands of linear assets crossing multiple utility corridors.
- Commercial and mixed-use. Widespread on larger developments, where facade and building services coordination provide clear and measurable returns.
- Industrial facilities. Adoption driven by system density rather than architectural complexity, and typically governed by operator standards rather than general project conventions.
- Healthcare and hospitality. Strong adoption where operator or brand standards add a review layer with its own information requirements.
- Residential. The most uneven. High-rise and large-scale developments frequently use BIM; smaller residential work often does not, and the economics rarely support it at that scale.
Where Implementation Stalls
Six failure patterns account for most of the difficulty, and none of them are software problems.
| Failure pattern | What it looks like | The fix |
|---|---|---|
| No employer’s information requirements | BIM is specified without defining what information is needed, in what format, at what stage | Agree an EIR before appointment; everything downstream depends on it |
| A CDE in name only | The specification names a common data environment; the project runs on shared drives and email | Stand up the CDE at kick-off with agreed status codes, or accept the version-control risk |
| Modelling to a number, not a purpose | “LOD 400” written across an entire package regardless of element or purpose | Define level of information need per element and per use |
| Coordination treated as a deliverable | A clash report is produced and filed; nobody is assigned, nothing is closed out | Run coordination as a tracked process with owners and closure dates |
| Handover data assembled at the end | Asset information retrofitted in the final weeks, incomplete and inconsistent | Agree the data schema at the outset and populate as the model develops |
| Capability gap | Modellers available; experienced coordinators and information managers are not | Assign information management explicitly rather than assuming it happens |
A Project Readiness Checklist
Before mobilising on a Saudi project with a BIM requirement:
- The employer’s information requirements have been read in full, not skimmed for the deliverable list.
- The governing standard is identified — ISO 19650, a client-specific standard, or an operator standard.
- Level of information need is defined per element and purpose, not as a single global number.
- The CDE is identified, access is confirmed, and status codes are agreed and documented.
- Naming and classification conventions are confirmed against the client’s own specification.
- The BIM Execution Plan addresses the actual requirements rather than restating generic capability.
- Authority-dependent items are flagged on the submittal register with extended lead times.
- The handover data schema is agreed at the outset, not deferred.
- Software versions and exchange formats are confirmed across all delivery parties.
- Responsibility for federation and clash management is assigned in writing.
Frequently Asked Questions
Is BIM in Saudi Arabia mandatory?
BIM requirements in the Kingdom generally arrive through contract — employer’s information requirements in tender documents or a client’s own digital delivery standard — rather than through a blanket national regulation. Requirements vary considerably between clients and project types, so the governing document is the project’s own specification rather than a single national rule.
Which BIM standard applies on Saudi projects?
ISO 19650 is the most commonly referenced international framework for information management on projects that specify a formal approach. Individual clients frequently publish their own standards that sit alongside or above it, and operator-specific engineering standards take precedence within their scope. Confirm which document governs before setting up the project.
What is the difference between BIM and CAD?
CAD produces drawings. BIM produces a data-rich model from which drawings, schedules and quantities are derived. The practical distinction is that changing an element in BIM updates every view and schedule that references it, whereas CAD requires each drawing to be updated separately. The second difference is data: a BIM element carries information that a CAD line does not.
What does the Saudi Building Code require from a BIM model?
The SBC does not specify how a model is built. It determines what the model must be able to demonstrate — clearances, fire ratings, egress geometry, system capacities and energy performance. Modelling compliance-relevant data as structured parameters rather than drawing annotations makes checking repeatable and preserves the information into handover.
What is an EIR and why does it matter?
The employer’s information requirements define what information the client needs, when, in what format and for what purpose. It is the document that makes a BIM scope enforceable. Projects without one tend to produce disputes at handover about what was actually in scope, because neither party can point to an agreed definition of the deliverable.
Does BIM approval replace Civil Defence or municipal approval?
No. Consultant review of model-derived documentation is separate from authority approval. Fire safety, municipal permitting and utility connections carry their own review processes with their own timelines, and these should be reflected in the submittal programme from the outset.
Which software is used on Saudi projects?
Autodesk Revit and Navisworks are the most widely used for building projects, with Civil 3D common on infrastructure and ArchiCAD present on some architectural workflows. The governing factor is usually the exchange format the client requires rather than the authoring tool itself — confirm the required deliverable format before selecting the toolset.
How does BIM adoption in Saudi Arabia compare with the UAE?
Both markets have adopted BIM substantially. The UAE introduced municipal requirements for certain building categories earlier, while Saudi adoption has been driven more heavily by giga-project contractual requirements. The practical result is broadly similar maturity reached through different routes, with the same underlying standards referenced in both.
What is a CDE and why does it keep appearing in tender documents?
A common data environment is a single controlled source for project information, with defined status codes governing what each document may be used for. It appears in tender documents because it is the mechanism that makes information management auditable — without it, version control depends on individual discipline and fails quietly.
What level of information is needed for handover?
That depends entirely on what the operator intends to do with the data. A schema agreed at the outset — defining which assets are recorded, which attributes are captured and in what format — produces usable handover data. A schema agreed at the end produces a spreadsheet nobody opens twice.
Conclusion
BIM in Saudi Arabia is no longer an emerging practice — on any project of scale it is the default coordination method. What remains uneven is the information management discipline around it: whether requirements are properly defined, whether the CDE is real, whether coordination is a process or a deliverable, and whether handover data is designed in or bolted on.
The technical capability to model is widely available. The differentiator on Saudi projects is understanding which standard governs, what the client’s review process actually expects, and how many approval layers sit between a coordinated model and a construction release.
