Navisworks
Model review and coordination software used for federating multi-disciplinary BIM models and running clash detection.
Federating Models From Multiple Native Platforms
Navisworks is the tool we rely on most for federating discipline models — Revit architectural, structural and MEP, Tekla structural steel, Civil 3D site models — into a single combined view for coordination review and clash detection, without needing every discipline to be modelled in the same native platform.
Clash detection reports generated through Navisworks are only as useful as how they're prioritised, and we structure reports so hard clashes that genuinely block construction are clearly separated from soft clearance issues that are easily resolved, rather than delivering an unsorted list that buries the problems that actually matter.
Construction Sequencing and Organising a Large Model
Construction sequencing review is another common use we put Navisworks to — linking a federated model to a construction programme lets a team visually check that the sequence of installation actually works before it's committed to, catching access and clearance problems that a static model review wouldn't necessarily reveal.
Navisworks' selection sets and search sets are a practical tool for organising a large federated model into meaningful, reusable groupings — by discipline, by level, by construction package — which makes repeated coordination reviews considerably faster than manually re-selecting the same elements each time.
Managing Federation Timing and Trackable Comments
For projects where several consultants are producing models on different update cycles, we manage federation timing deliberately, confirming which model version each discipline's latest issue represents before running a review, since a clash report generated against an outdated services model produces confidently wrong results.
Viewpoint and comment tools in Navisworks support a structured, trackable coordination conversation between disciplines — saved viewpoints tied to specific clash issues, with clear ownership and status, keep a coordination process organised in a way that email threads and static screenshots don't.
TimeLiner Validation and Early Quantity Checks
TimeLiner, Navisworks' construction sequencing tool, is a practical way to validate a proposed construction programme visually against the actual federated model, catching an installation sequence that looks fine on a Gantt chart but is physically impossible given real site access and clearance constraints — a mismatch that's considerably cheaper to catch in a model review than during actual construction.
Quantification tools within Navisworks support extracting rough quantities directly from a federated model for early cost estimation purposes, and while this isn't a substitute for a dedicated quantity surveying process, it's a genuinely useful sense-check against a separately prepared estimate, particularly at early design stages.
A Dated Record and Distinguishing Clash Severity
For projects with a large number of open coordination issues across multiple review cycles, we maintain a clear, dated record of what was raised, resolved and re-checked at each cycle, which becomes a valuable record if a coordination dispute or question arises later in the project.
Clearance and soft-clash checking — verifying adequate maintenance access or installation clearance around equipment, not just hard geometric intersection — is set up as a distinct rule category from hard clash detection, since these two categories of issue carry different urgency and are typically resolved by different people on a project team.
Federation Accuracy and Automated Reporting
For projects using Navisworks primarily for coordination rather than fabrication, we still apply the same rigour to confirming model federation accuracy as we would for a fabrication-focused review, since a coordination decision based on a poorly federated model can be just as costly to unwind as a fabrication error, even without the immediate physical consequence.
Batch processing and automated report generation for recurring, scheduled coordination reviews reduces the manual overhead of producing a consistent report format at every review cycle, letting the design team focus their time on interpreting and resolving findings rather than reformatting the report itself each time.
Sharing a Federated Model Beyond the Design Team
Where a federated model needs to be shared with a client or authority who doesn't have Navisworks themselves, we export lightweight, published formats that preserve the coordination review's key findings in a format the recipient can actually open and review without needing the full authoring software.
What It's Used For
- Federated model review
- Clash detection across disciplines
- Construction sequencing review
- Coordinating models from multiple native platforms into a single review environment
- Structured, trackable coordination workflows using saved viewpoints
Typical Deliverables
- Federated coordination models
- Clash detection reports
- Tracked coordination viewpoints and issue logs
Related Industries
Frequently Asked Questions
- No, Navisworks is specifically designed to federate models from multiple native platforms — Revit, Tekla, Civil 3D and others — into a single combined view, so different disciplines can stay in whichever platform suits their work best.
- We separate hard clashes that would genuinely block construction from soft clearance issues that are easily resolved, so the design team's attention goes to what actually matters rather than an unsorted list.
- Yes, linking a federated model to a construction programme lets a team visually review whether an installation sequence actually works before it's committed to on site.
- We use selection and search sets to group elements meaningfully — by discipline, level or construction package — which makes repeated reviews considerably faster than reselecting elements manually each time.
- We confirm which version of each discipline model is current before running a review, since a clash report generated against an outdated model produces confidently wrong results.
- Yes, saved viewpoints tied to specific issues with clear ownership and status give a coordination process a trackable structure that email threads and screenshots don't.
- Yes, linking a proposed sequence to the model can catch an installation order that looks fine on a Gantt chart but is physically impossible given real site constraints.
- Yes, rough quantities extracted from a federated model are a useful sense-check against a separately prepared estimate, particularly at early design stages, though not a substitute for formal quantity surveying.
- Yes, we keep a clear record of what was raised, resolved and re-checked at each cycle, which is a valuable reference if a coordination question arises later in the project.
- Yes, federating a scan-to-BIM model alongside new design elements for clash detection is a common coordination task on renovation and retrofit projects.
- Yes, a summary confirming the status of every raised clash — resolved, accepted or deferred with reasoning — is a valuable document to issue alongside the coordinated model.
- Yes, specialist models — fire services, façade, vertical transportation — can be federated alongside the core architectural, structural and MEP models where supplied in a compatible format.
- Yes, we agree a sensible review cadence with your team upfront, since running clash detection too infrequently risks a large, unmanageable issue list building up unnoticed.
- Yes, these building types carry unusually dense services coordination requirements, and federated clash detection is particularly valuable given how tightly packed structural and services elements typically are.
- Yes, presentation walkthroughs built from the coordinated federated model are available alongside our core clash detection and coordination work.
- Yes, point cloud data can be federated alongside design models for coordination review against existing conditions.
- Yes, soft-clash and clearance checking is set up as its own distinct rule category, since clearance issues carry different urgency and are typically resolved by different people than a genuine hard clash.
- Yes, we export lightweight, published formats that preserve the review's key findings in a format the recipient can open and review without needing the full authoring software.
- Yes, batch processing and automated reporting reduce the manual overhead of reformatting a consistent report at every cycle, letting the design team focus on interpreting and resolving findings instead.
- We apply the same model federation accuracy checks we'd use for a fabrication-focused review, since a coordination decision made against a poorly federated model can be costly to unwind even without an immediate physical consequence.
- Yes, specialist models beyond the core architectural, structural and MEP disciplines can be added to a federation where supplied in a compatible format.
- Yes, an ongoing coordination arrangement with a regular review cadence is a common and effective way this service is used across a project's construction documentation phase.
- Yes, a one-off federated review ahead of a specific milestone, such as issue-for-construction, is just as workable as an ongoing coordination arrangement.
Get a Quote for Navisworks Work
Tell us what you need and our team can review the project requirements.