BIM Modeling & Clash Detection
A clash found in the model costs an email. The same clash found in the field costs a change order, a delay, and somebody's margin. We build the model that finds it first.
Model development
We build architectural, structural and MEP models in Revit to an agreed level of development, typically LOD 300 for coordination and LOD 350 where trades interface. The model is organised so that quantities, areas and schedules can be pulled straight out of it rather than recounted by hand.
Families are built or adapted to match the products actually specified, so a model of a truss, a rooftop unit or a window is the size it will be on site, not a generic placeholder.
We set up worksharing, shared coordinates and a naming standard at the start of the project so that every consultant is working in the same space and files link predictably.
Clash detection and resolution
Coordination runs in Navisworks on a fixed cycle, usually weekly or biweekly depending on the phase. Each run produces a clash report grouped by discipline pair and sorted by severity, with viewpoints saved so anyone can see the conflict in context.
We do not just hand over a list of thousands of raw clashes. Results are filtered, de-duplicated and prioritised: hard clashes between structure and ductwork first, clearance and maintenance-access issues next, tolerance-level items last.
Each item carries a proposed resolution and an owner. We track them to closure and report what was resolved since the last cycle, so the coordination meeting is about decisions rather than about finding the problems.
Why it pays for itself
The cost of resolving a conflict multiplies roughly tenfold at each stage it survives: model, shop drawing, fabrication, installation. On a mid-size commercial project a single unresolved duct-versus-beam conflict can absorb more than the entire coordination budget.
Beyond conflicts, a coordinated model gives you reliable quantities for pricing, accurate sequencing for the schedule, and a record model that the building operator can actually use.
What you get
- Federated Revit model with architectural, structural and MEP disciplines
- Navisworks coordination model and saved viewpoints
- Clash reports on a regular cycle, filtered and prioritised
- Resolution matrix with owners and status tracking
- Quantity and area schedules exported from the model
- Record model at project close-out
Questions
Can you coordinate models produced by other consultants?
Yes. That is the normal case. We receive their models, set up the federated environment and run coordination across all of them.
What if a discipline is still drawing in 2D?
We model from their drawings so the discipline is represented in the coordination model. It is extra work, but it is far cheaper than leaving a blind spot.
How often should clash cycles run?
Weekly during heavy coordination, dropping to biweekly once the model stabilises. The cadence matters more than the frequency. Predictable cycles keep the team in rhythm.