Navisworks has been the standard clash detection and coordination tool in construction for over a decade. It works. Teams know it. Workflows are established. But the limitations of a desktop-based coordination platform are becoming harder to ignore as project teams become more distributed and expectations for real-time collaboration increase.
Cloud-based coordination platforms are not replacing Navisworks overnight, but the shift is accelerating. Understanding the trade-offs helps VDC teams plan their technology strategy rather than being forced into reactive decisions.
Navisworks handles large, complex models with a level of performance that cloud platforms have not fully matched. Federated models with millions of elements, complex clash detection rules with custom tolerances, and 4D simulation with detailed construction sequencing all run reliably in the desktop environment.
Custom clash rules and search sets that teams have refined over years represent significant institutional knowledge. Migrating that logic to a new platform requires effort, and the result may not replicate every capability that experienced coordinators depend on.
For projects where all coordination team members work from the same network or can exchange files efficiently, Navisworks delivers everything needed without the subscription costs and learning curve of a new platform.
Access is the single biggest advantage of cloud coordination platforms. Any stakeholder with a web browser can view the coordinated model, review clashes, and contribute to resolution. No software installation. No file downloads. No version confusion about who has the latest model.
Real-time collaboration means that when one team resolves a clash, every other team sees the update immediately. The sequential workflow of export, upload, distribute, and wait for review compresses into continuous, parallel coordination. On fast-track projects, this acceleration directly impacts schedule.
Issue tracking and accountability improve when coordination happens in a platform that logs every action. Who raised the clash, who was assigned to resolve it, when was it addressed, and what was the resolution are all captured automatically. That audit trail improves accountability and provides documentation for disputes.
Field access to coordination models through mobile devices means that the people installing systems can view clash resolutions in context. A foreman standing at the point of installation can pull up the coordinated model and see exactly how the conflict was resolved. That direct access reduces RFIs and interpretation errors.
Most VDC teams in 2026 are running hybrid workflows. Navisworks handles heavy clash detection and complex coordination sessions. Cloud platforms handle distribution, review, and field access. The desktop tool does the computational heavy lifting. The cloud platform extends access to the broader project team.
This hybrid approach leverages the strengths of both environments. The risk is maintaining synchronization between them. When the Navisworks model and the cloud model diverge, confusion follows. Clear update protocols and version management procedures prevent this disconnect.
VDC teams considering increased cloud adoption should start with the use cases where cloud platforms clearly outperform desktop tools: broad stakeholder access, field coordination, and issue tracking. Keep complex clash detection in Navisworks until cloud platform performance catches up on computational intensity.
Evaluate platforms based on your actual workflow, not feature lists. Can the platform handle your typical model sizes? Does the clash detection logic support your coordination standards? Can your trade partners access the platform without specialized training? These practical questions matter more than theoretical capability comparisons.
A mechanical contractor is reviewing the as-built condition of an existing building before rough-in work on a major addition. The architect’s model shows structural columns at regular 20-foot intervals. The MEP consultant has coordinated ductwork accordingly. But there’s a problem: a concrete column is actually 24 inches wide instead of 12 inches. Another is slightly offset from the grid.
These aren’t design errors. They’re construction reality. The original building was built thirty years ago by craftspeople, not algorithms. Small dimensional variations are everywhere.
Without reality capture, these variations remain hidden until installation starts. The ductwork routing that made sense in the model doesn’t work in the building. Rework follows.
With proper reality capture and integration into the coordination workflow, these conflicts are identified and resolved before work begins. That’s the power of MEP coordination grounded in reality rather than assumption.
An architectural model is a representation of design intent. It assumes regular geometry, standard member sizes, and construction to specification. Real buildings are messier. Structural members vary slightly. Concrete cures with irregularities. Mechanical systems are stubbed at angles and heights that deviate slightly from design. These deviations are often within tolerance and structurally sound, but they’re real.
MEP coordination based solely on design models ignores this reality. Ductwork routing is optimized for the model’s geometry, not the building’s. When installation begins, conflicts emerge.
In renovation and retrofit projects, existing conditions are inherently complex. Asbestos-laden existing mechanical systems, utilities stubbed in unforeseen locations, structural conditions that differ from as-built documentation—these are impossible to coordinate accurately without capturing reality.
Reality capture creates the as-built baseline. MEP coordination proceeds from this baseline, not from assumption.
Scanning a building for MEP coordination has different requirements than scanning for architectural documentation. You need:
Scan planning for MEP is more meticulous than scan planning for general architectural documentation. Station placement must ensure clarity on system routing. Station count is typically higher because detail matters more than in sparse areas.
For MEP coordination, point cloud density should support 25-50mm detail resolution. This allows modelers to extract ductwork centerlines, identify precise clearances, and resolve conflicts with confidence.
Registration accuracy for MEP coordination should target 15-20mm RMS error or better. This ensures that clashes detected in the model are real, not artifacts of registration uncertainty.
Mechanical rooms are dense, complex, and reflective. Piping, ductwork, and equipment create challenging scan environments. Noise and outliers are common. Processing must be rigorous—automatic outlier removal followed by manual inspection to ensure real geometry isn’t removed.
The most powerful workflow combines captured reality with the design model in a single viewer. MEP coordinators load both the scanned point cloud and the design model, then compare them directly.
“Where is this duct routing according to the model? Where is the structural column actually located in the scan? Do they collide?” These questions are answered visually and immediately.
Traditional clash detection runs the MEP model against the structural and architectural models—all design models. Clashes are identified in design space, not reality space. Some design clashes resolve themselves because real-world geometry varies favorably. Others don’t exist because design was conservative.
Running clash detection against the scanned reality is more accurate. Clashes that matter are identified. Clashes that don’t (because reality is favorable) are not.
The scanned point cloud must be registered to the same coordinate system as the design models. This requires integration with surveying control points and project baselines. Without this alignment, comparing scan to model is difficult—they’re in different spaces.
Leading MEP coordinators establish a surveyed baseline, register scans to this baseline, and ensure all design models are coordinated to the same baseline. Then comparison and clash detection are geometric reality, not guesswork.
After rough-in and before wall/ceiling closure, perform an as-built scan to document what was actually installed. Compare this scan against both the design intent and the pre-construction scan to document what changed and why.
This creates a complete audit trail: design intent, pre-construction reality, installation work, and post-installation reality. Discrepancies between design and as-built are documented and explained—invaluable for closeout disputes and future renovations.
Autodesk Navisworks is the standard for multi-discipline coordination. Many firms perform clash detection in Navisworks, then use point cloud data (scanned point clouds) for reference only.
A better workflow: Use Navisworks for model-to-model clash detection. Export clashes to a cloud-based viewer like scanbim.app that can display both point clouds and models simultaneously. Field teams access this viewer to understand clashes in spatial context and verify that proposed resolutions work in reality.
This bridges the gap between design coordination and field reality.
MEP contractors and coordination specialists who master reality-capture-informed coordination have a decisive advantage. They identify conflicts early, prevent rework, and build client confidence through transparent documentation.
Teams that still coordinate purely from design models—without validating against actual building conditions—are exposed to avoidable risk. As reality capture technology becomes standard, clients will expect it.
The question is no longer whether to capture reality for MEP coordination. It’s how to do it systematically and integrate it seamlessly into your workflow.