Structural Modeling Best Practices: Common Mistakes That Compound Through a Project
November 7, 2026
No Comments
Plenty has already been written explaining what ISO 19650 is. Far less has been written about the more useful, more immediate question a lot of UAE project teams are actually sitting on: does this specific project, right now, genuinely need formal ISO 19650 compliance, or is it something to think about later? Below are five concrete, observable signs that the answer is “now,” not “eventually” — framed as a diagnostic checklist rather than another standard explainer.
A single-discipline project with one design team and straightforward handover rarely needs the full weight of ISO 19650’s formal process. The moment architectural, structural, MEP, facade, and specialist subcontractor models all need to exist in the same coordinated space — each one producing information the others depend on — the lack of a defined Common Data Environment, clear roles, and status-tracked information starts costing real time almost immediately. If your project has more than two or three contributing disciplines regularly exchanging models and drawings, that’s already a meaningful signal, independent of anything your contract explicitly requires.
This is the most direct, unambiguous signal on this list, and it’s one teams sometimes miss simply because the language doesn’t always say “ISO 19650” in plain words. Under ISO 19650-2, the appointing party’s tender pack is expected to carry the Exchange Information Requirements and a requirement for a pre-appointment BIM Execution Plan, and both ISO 19650-2 and 19650-3 require the appointing party to issue a formal information protocol as part of the tender and appointment documents. If your tender response has to include a BEP, or references an EIR document defining what information has to be delivered, in what format, and at what stage — that’s a direct contractual trigger, not a “nice to have,” and a pre-appointment BEP responding to it genuinely needs to follow the structure of that EIR even though its content will obviously differ.
Teams sometimes respond to this kind of tender requirement with a generic, boilerplate BEP that doesn’t actually engage with the specific EIR it’s responding to. That approach creates real risk at the point the winning bid becomes a contractual commitment, because the post-appointment BEP becomes the actual reference document the project gets held to.
Every multi-disciplinary project has some clashes — that’s normal and expected. What’s a genuine warning sign is a pattern of discovering the same category of clash repeatedly, late in the process, after it’s already caused rework or a site-level problem. That pattern usually isn’t really a modeling-skill problem. It’s a symptom that nobody has defined when information is actually checked and approved before it gets relied upon by another discipline — exactly the gap ISO 19650’s Common Data Environment states (Work in Progress, Shared, Published, Archive) exist to close, by forcing a defined check before information gets treated as coordinated rather than letting teams discover problems only once they’ve already propagated downstream.
| Sign | What It Actually Indicates | What ISO 19650 Process Addresses |
|---|---|---|
| Multi-disciplinary overlapping models | No shared information environment or clear ownership | Defined CDE, roles, and responsibilities |
| EIR/BEP referenced in tender | Direct contractual information management requirement | Formal pre- and post-appointment BEP response |
| Repeated late-stage clashes | No enforced check before information is relied upon | WIP-to-Shared approval discipline |
| Client-mandated information protocol with no response plan | Contractual obligation not yet operationalized | Information Manager role and delivery plan |
| International JV partner already running ISO 19650 | Mismatched process expectations across the team | Aligned information management approach project-wide |
The appointing party’s obligation to issue a formal information protocol as part of tender and appointment documents is explicit in both ISO 19650-2 and 19650-3. If your project has received one — even if it arrived buried inside a larger contract package and wasn’t flagged loudly — and nobody on your delivery team has actually built a response plan around it, that’s a live compliance gap right now, not a future risk. The pre-tender stage is specifically where the appointing party is expected to comprehensively develop these requirements so they’re clearly set out by the time tender stage arrives, which means by the time you’re holding the document, the expectation is that your side responds with an equally clear BEP, not a general assurance that “we’ll figure out the information management as we go.”
Dubai and the wider UAE regularly bring together local consultants and contractors with international joint-venture partners, many of whom already run ISO 19650-aligned processes as standard practice on projects outside the region. When that’s the case on your project, the practical reality is that your team will be expected to meet that same process discipline during coordination, information exchange, and handover — regardless of whether your own direct contract explicitly names ISO 19650. Mismatched expectations here show up fast and painfully: one side submitting structured, status-tracked information through a defined CDE, and the other side emailing spreadsheets and PDF drawings with no formal check process behind them.
None of these signs resolve themselves by being ignored — they compound. A project that keeps discovering the same clashes late (Sign 3) while also having no response plan for a client-issued information protocol (Sign 4) is heading toward exactly the kind of coordination breakdown that shows up as real rework cost, disputed responsibility for a late discovery, and — in the worst cases — a client or main contractor losing confidence in a consultant’s or subcontractor’s ability to deliver coordinated information at all. None of that is reversible quickly once a project is already underway and behind on this front; building the process from week one is considerably cheaper than retrofitting it in month six.
The realistic first step isn’t a massive process overhaul — it’s naming someone accountable for information management (even informally, if a dedicated Information Manager role isn’t yet justified at your project’s scale), getting an honest read of what the actual EIR or information protocol requires if one exists, and setting up even a basic Common Data Environment with real WIP/Shared/Published states enforced, rather than treated as folder labels. From there, the formal BEP, naming conventions, and more detailed process can be built out — but that first step of someone actually owning the problem is what separates projects that get this under control quickly from ones that let it drift for months.
Recognizing these signs is one thing; actually running a compliant information management process — building a real EIR response, setting up a working CDE, defining roles that hold up under a genuine client audit — is a distinct, learnable skill set that most project teams don’t have in-house by default. Orbit’s BIM Standards / ISO 19650 Compliance course in Dubai is built around exactly this gap — hands-on work with real EIR/BEP documents and CDE setup, not just an explanation of the standard’s clause structure.
Picture a mid-rise mixed-use development in Dubai with a local architectural consultant, a structural engineer, an MEP firm, a facade specialist, and a main contractor bringing in a European JV partner for the tower’s more complex sections. In month one, the architectural and structural teams exchange models informally by email, each assuming the other’s latest file is current. By month three, the facade team discovers a structural clash that should have been caught weeks earlier, because nobody had defined when a structural model was actually “checked” versus just “the latest version someone happened to send.” That’s Sign 3 and Sign 1 compounding together in a completely ordinary, realistic way — not a worst-case scenario, just an average project that never built the process early.
Now picture the same project, but the client’s tender pack included an EIR requiring a formal BEP response (Sign 2), and the JV partner already expected ISO 19650-aligned coordination from its own standard practice (Sign 5). In that version, the team sets up a real Common Data Environment from week one, assigns someone to own WIP-to-Shared checks, and the facade clash gets caught in a scheduled coordination review weeks before it would have otherwise surfaced on site. Same project type, same disciplines, same city — the only difference is whether the signs got recognized and acted on early or ignored until they became expensive.
Before moving to a full formal ISO 19650 rollout, it’s worth running your own project honestly against a short checklist, since not every project needs the same level of investment:
Two or more “yes” answers across this checklist is a reasonably reliable signal that formal ISO 19650 process is worth building now rather than later — and critically, building it now is building it while it’s still cheap, before months of informally exchanged, unstructured information have already accumulated across the project.
It’s worth saying plainly: not every project needs the full formal weight of ISO 19650 compliance immediately. A small, single-discipline project with a short timeline and no multi-party coordination genuinely may not need a dedicated Information Manager or a formally structured BEP on day one. The five signs above are deliberately built around observable, concrete triggers rather than a blanket “every project should do this” message, precisely so a team can make an honest, proportionate call rather than either over-investing in process a small project doesn’t need, or under-investing in process a genuinely multi-disciplinary, contractually-mandated project can’t safely skip.
A fit-out project for a single retail tenant and a multi-tower mixed-use masterplan with a dozen subconsultants sit at opposite ends of this spectrum, and treating them identically wastes effort either way. The fit-out project might reasonably run on a lighter information management approach with basic version control and clear sign-off points, without needing a formally documented EIR response. The masterplan project, by contrast, almost certainly already has — or should have — a formal information protocol from the client, multiple BEPs from different appointed parties needing to align with each other, and a genuine need for a dedicated Information Manager role, because the coordination surface area between a dozen contributing teams is large enough that informal process will break down relatively quickly without someone actively managing it.
Recognizing which end of that spectrum your current project actually sits on — honestly, not optimistically — is itself part of the skill ISO 19650 training is meant to build. Teams that have been through structured training tend to make this call more accurately and earlier than teams learning the hard way, discovering the need only after a specific clash, dispute, or late-stage information failure has already made the gap impossible to ignore.
No. ISO 19650’s process applies to any project where the appointing party chooses to require it, and that increasingly includes private commercial, residential, and mixed-use developments, not only large government-mandated infrastructure work. The deciding factor is what’s actually written into the tender and contract documents for your specific project, not the project category alone.
Check specifically for a referenced Exchange Information Requirements (EIR) document or an explicit requirement to submit a pre-appointment BIM Execution Plan (BEP) as part of the tender response. If either is present, that’s a direct contractual trigger, independent of whether the tender uses the exact phrase “ISO 19650” anywhere in its text.
Technically, yes, but it’s considerably more disruptive and expensive than building the process from the start, since by the time a gap becomes obvious enough to force a mid-project change, inconsistent files, unclear approval history, and uncoordinated information have usually already accumulated across months of work.
In practice, this usually falls to whoever is acting as BIM Manager or Coordinator, since they’re closest to the day-to-day information flow between disciplines, but project and contracts managers reviewing tender documents are equally positioned to catch Sign 2 and Sign 4 specifically, since those are visible directly in contract paperwork before any modeling work even begins.
Not automatically by contract, but practically, yes in most cases — if your JV partner already runs an ISO 19650-aligned process as their default way of working, mismatched expectations during coordination and handover create real friction regardless of what your own direct appointment document specifies, so aligning proactively is usually the more sensible path.