Structural Modeling Best Practices: Common Mistakes That Compound Through a Project
November 7, 2026
No Comments
Ask a BIM Coordinator in Dubai whether they use BIM 360 or Navisworks, and the honest answer on most real projects is “both, for different things.” That’s not a cop-out answer — it reflects a genuine split in what each tool is actually built to do, and understanding that split properly is what lets you pick the right tool for a given task instead of defaulting to whichever one you learned first.
Note on naming: Autodesk rebranded BIM 360 as part of Autodesk Construction Cloud, and the coordination module specifically is called Model Coordination. “BIM 360” still gets used informally across the UAE industry to mean this same cloud-based coordination environment, so this guide uses both terms, with Model Coordination as the more technically current name.
Model Coordination exists inside Autodesk Construction Cloud as a cloud-native coordination space. Its core strength is accessibility: any project team member with the right permissions can open a browser, view the federated model, run or review clash detection, and raise or respond to issues, without installing desktop software or holding a Navisworks license. According to Autodesk’s own 2020 product announcement, the intended split in responsibility is that Model Coordination lets design and trade partners create, track, and self-check issues, while Navisworks remains the tool that empowers general contractors to identify and resolve clash and constructability issues at a deeper level.
Navisworks is a desktop application with a considerably longer history in construction coordination, and it carries more advanced functionality than Model Coordination currently offers — more granular clash detection rule sets, quantity takeoff tools, and 4D construction sequencing that ties a schedule directly to the model’s geometry over time. A training-industry source we reviewed reports that running the identical clash test in both Navisworks and BIM 360 should, in principle, produce the same clash results — treat that specific claim as third-party rather than an official Autodesk guarantee, but it reflects the general expectation that both tools are checking the same underlying model geometry, just with different depth of tooling around the results.
| Factor | Model Coordination (BIM 360 / Construction Cloud) | Navisworks |
|---|---|---|
| Access model | Cloud/browser-based, no separate license for core clash checking | Desktop install, requires a Navisworks license |
| Typical primary user | Design teams and trade partners, self-checking their own work | General contractors running advanced, project-wide coordination |
| Clash detection depth | Solid for day-to-day federated model checking | More advanced rule configuration and manual review tools |
| Quantity takeoff | Not a core strength | Built-in, commonly used feature |
| 4D scheduling/sequencing | Not natively supported | Supported, widely used on larger contractor-led projects |
| Native model source | Works directly with Revit models in the cloud | Supports a wide range of federated model formats, including non-Autodesk sources |
This is the part that gets lost when the comparison is framed as a simple either/or choice: Autodesk has built direct integration between the two, specifically so project teams don’t have to pick one and abandon the other. You can create and assign issues directly from inside Navisworks, and run saved Navisworks clash tests against datasets managed by Construction Cloud’s Model Coordination service. There’s also a separate, older BIM 360 Glue service still in use on some legacy project setups, and both Glue and Model Coordination can technically be active on the same project if a transition between them is underway.
The practical pattern that tends to emerge on well-run UAE projects: Model Coordination handles the bulk of ongoing, day-to-day clash detection and collaborative issue tracking across design and trade teams throughout the project, while Navisworks gets reached for specifically when a project needs its deeper capabilities — detailed quantity takeoff, 4D sequencing tied to the construction schedule, or especially granular clash rule configuration that the cloud tool doesn’t yet match.
Project scale and team structure are the honest deciding factors, more than a general preference for one tool over the other.
Smaller and mid-sized Dubai projects, and especially design-side coordination happening before a main contractor is fully mobilized, tend to lean on Model Coordination first — it’s lower-friction to get a multi-disciplinary design team actually using consistently, since there’s no license or install barrier for every participant, and the self-check workflow fits how design teams iterate.
Larger, contractor-led coordination on big UAE infrastructure or major commercial projects, particularly once construction sequencing and detailed quantity extraction become central to the coordination effort, more often still runs primarily through Navisworks, with Model Coordination used alongside it for broader team visibility and issue tracking rather than as the primary clash-detection engine.
This is a genuinely practical factor for UAE firms deciding how to roll either tool out across a team. Model Coordination’s access model, tied to Autodesk Construction Cloud project membership rather than a separate desktop license per seat, tends to make it considerably easier to get an entire multi-disciplinary project team actually using the same coordination environment, including smaller subconsultants or trade contractors who wouldn’t otherwise justify a standalone Navisworks license. Navisworks, by contrast, still requires an actual license per user who needs to open and work in it directly, which is a real cost and procurement consideration for firms deciding how widely to deploy it beyond a core coordination team.
The single most common mistake is treating this as an exclusive choice at the outset, when Autodesk’s own product direction and integration tooling point toward using both, matched to what each one is actually strong at, rather than standardizing the entire project on one tool for every coordination task.
If a design team’s actual need is day-to-day self-checking and issue visibility, not deep clash rule configuration or 4D sequencing, licensing Navisworks broadly across that team is often unnecessary cost and friction compared to simply using Model Coordination, which most of that team can access without any separate license.
The reverse mistake also happens — a project tries to run detailed quantity takeoff or construction sequencing purely inside the cloud coordination environment because it’s already in use for clash tracking, when Navisworks’ dedicated tools for that specific work are considerably more capable and mature.
For a BIM Coordinator new to Model Coordination, the practical setup sequence looks roughly like this: models get published or synced into the Construction Cloud project from Revit, typically through Collaboration for Revit (C4R) or direct cloud publishing, then the service automatically builds a federated model combining the contributed discipline models into one coordinated view. Clash detection rules get configured next — which model groups should be tested against which other groups, and under what tolerance — and the system runs automated checks, surfacing results as issues that can be assigned, commented on, and tracked to resolution directly inside the platform.
The part that trips up teams new to this workflow isn’t usually the technical setup — it’s the discipline of actually reviewing and closing issues promptly rather than letting them accumulate. A coordination platform with hundreds of open, unreviewed issues is barely more useful than no coordination platform at all, since nobody can tell at a glance which clashes are genuinely still live problems and which have already been resolved in a later model update.
Beyond the basic licensing difference covered above, there’s a practical total-cost consideration UAE firms should weigh before committing heavily to one tool’s workflow. Model Coordination’s access model ties to Construction Cloud project membership, which many firms already hold as part of a broader Autodesk AEC Collection subscription, making incremental cost to add more project participants relatively low. Navisworks licensing is a separate line item, and firms should realistically budget for it per seat for whoever genuinely needs direct desktop access to its deeper tools, rather than assuming it’s bundled automatically with other Autodesk software a firm already owns.
For subcontractors and smaller trade partners brought onto a project specifically for coordination input, this cost difference often decides the practical rollout: it’s far easier to get a steel fabricator or MEP subcontractor’s team into a browser-based Model Coordination view than to justify procuring them Navisworks seats for what might be a relatively narrow coordination task on their part of the project.
If you’re starting out and have to prioritize, the honest, practical answer for most UAE BIM Coordinator career paths is to get comfortable with cloud-based coordination first — Model Coordination’s workflow, issue tracking, and federated model review — since it’s the tool you’ll use daily on the broadest range of projects regardless of their size or contractor structure. Navisworks’ deeper capabilities, particularly quantity takeoff and 4D sequencing, are genuinely valuable skills to add next, especially if your career path leans toward larger contractor-side coordination roles, but they’re a narrower specialization layered on top of the daily coordination fundamentals rather than a substitute for them.
This ordering also tends to match how UAE employers structure job postings in this space: entry and mid-level BIM Coordinator roles usually list cloud coordination platform experience as a baseline expectation, with Navisworks proficiency showing up more specifically in postings for senior coordination roles or contractor-side VDC (Virtual Design and Construction) positions where sequencing and takeoff are part of the actual job.
Both tools will happily generate a long list of flagged clashes. The actual coordination work — the part that determines whether a project benefits from any of this or just accumulates an unreviewed backlog — is assigning each issue to the right responsible party, tracking it to an actual resolved status, and confirming the resolution against an updated model rather than just a verbal assurance that “it’s been fixed.” Teams new to either platform sometimes treat the clash report itself as the deliverable, when the real deliverable is a closed-out, verified issue log that genuinely reflects a coordinated, buildable model.
On Dubai’s larger BIM-mandated and BIM-aligned projects, job postings for BIM Coordinator and BIM Manager roles increasingly list both Construction Cloud/Model Coordination platform experience and Navisworks proficiency as expected skills, not alternatives to choose between. Being fluent in only one half of this toolkit is a real, limiting gap on larger project teams, where you’ll likely be expected to move between a cloud coordination environment for daily issue tracking and Navisworks for deeper coordination tasks within the same role.
Reading about the difference between these tools only gets you so far — the real skill is knowing, on an actual live model with real clashes and real issue threads, when to stay inside Model Coordination’s self-check workflow and when a problem genuinely needs Navisworks’ deeper tooling. Orbit’s BIM 360 / Construction Cloud course in Dubai works through this hands-on, covering Model Coordination setup, clash detection, and issue tracking inside real multi-disciplinary project workflows, alongside the coordination fundamentals that carry directly into using Navisworks for the deeper tasks it’s still genuinely the stronger tool for.
No — Model Coordination runs clash detection in the cloud directly on native Revit models without requiring a separate Navisworks license. Navisworks becomes relevant when you need its deeper, more advanced coordination tools specifically.
BIM 360 was rebranded under the broader Autodesk Construction Cloud umbrella, with Model Coordination as the specific module handling clash detection and coordination. “BIM 360” is still widely used informally across the UAE industry to refer to this same cloud coordination environment.
Yes, and this is the common real-world pattern rather than the exception. Autodesk has built direct integration allowing issues to be created and assigned from Navisworks, and saved Navisworks clash tests to run against Model Coordination-managed datasets.
Larger, contractor-led coordination involving detailed quantity takeoff or 4D construction sequencing more often still relies primarily on Navisworks, while Model Coordination is commonly used alongside it for broader team visibility and day-to-day issue tracking across the wider project team.
Model Coordination is Autodesk’s current coordination offering, but Glue remains active as a separate legacy service on some projects, and both can technically be enabled on the same project during a transition period. New projects should default to Model Coordination rather than setting up Glue from scratch.
Model Coordination’s browser-based interface and more guided workflow generally get a new user comfortable with day-to-day clash review and issue tracking within a few weeks of regular project use. Navisworks, with its deeper rule configuration, quantity takeoff tools, and 4D sequencing, has a longer genuine learning curve to use well rather than just adequately — structured, hands-on training tends to compress that considerably compared to self-teaching through trial and error on a live project.
Specific tool mandates vary by entity and project type, and some UAE authorities focus their requirements on BIM submission formats and information management discipline rather than naming a specific coordination platform. Always confirm the actual contractual and submission requirements for your specific project rather than assuming a general industry pattern applies, since this detail genuinely does vary between clients and project categories.
Construction Cloud access is tied to project membership rather than a separate per-feature purchase for basic coordination participation, so project administrators can typically add trade partners as project members with the specific permissions they need for issue review and self-checking, without that partner needing a broader Autodesk software subscription of their own. The exact invitation and permission process depends on how the main contractor or lead consultant has configured the project, which is worth confirming early rather than assuming access automatically.