Skip to content
Case study · Clash detection

Mixed-use office tower: weekly clash runs in design development

Federated clash detection across architecture, structure and services during design development, with grouped reports for every coordination meeting.

  • Client: general contractor
  • Sector: commercial
  • Delivered: weekly clash reports
  • Duration: 16 weeks
Student union hostel captured for Scan to BIM
Weekly runsArchitecture, structure, MEP
Model · reportsGrouped clash reports
About the project

Many models, one programme

A contractor brought in early on a mixed-use tower needed the design team’s models checked every week during design development.

Four consultants were issuing models on different days, and the meetings needed a clear list of what to fix and who should fix it.

What we delivered

  • Federated coordination model
  • Weekly clash tests
  • Grouped clash reports
  • Issue tracker
  • Meeting viewpoints
  • Coordination summary
  • Four design teams

    Models arrived from different consultants on different days.

  • Thousands of raw clashes

    Unfiltered results were too many to use.

  • Weekly meetings

    Reports had to be ready before every session.

Have a building to capture? Send your point cloud and scope. We reply with an approach and quote within one working day.

Our process

From brief to coordinated model in six steps

How the work was planned, modeled, checked and handed over.

  1. 01

    Brief & standards

    Scope, LOD, template and naming agreed at kick-off.

  2. 02

    Model set-up

    Shared coordinates, levels, grids and worksets created.

  3. 03

    Modeling

    Each discipline modeled to the agreed level of detail.

  4. 04

    Coordination

    Federated model checked and clashes grouped by level and trade.

  5. 05

    Review & update

    Comments resolved and models updated between meetings.

  6. 06

    Issue

    Models, reports and sheets issued in the client’s formats.

Our solution

Clashes that actually get fixed

Tests were tuned per discipline pair and results grouped by level and zone, so each meeting worked through a short, prioritised list.

  • 0+Clashes closed
  • 0Weekly cycles
  • 0 hReport turnaround
  • Tuned tolerances

    Tests set per discipline pair to remove noise.

  • Grouped by zone

    Results grouped by level and area for each trade.

  • Issue tracking

    Every clash given an owner, status and due date.

  • Meeting-ready reports

    Viewpoints and summaries issued before each session.