Before BIM, coordinating mechanical ducts with structural beams meant overlaying translucent sheets on a light table and hoping someone caught the conflict. Now, software does that checking automatically, across every discipline, in seconds.

Clash detection is the automated process of identifying spatial conflicts between building system elements modeled by different disciplines. A duct runs through a beam. A pipe occupies the same space as a conduit. A sprinkler head sits inside a light fixture. These are clashes, and finding them on paper used to cost projects millions in field rework.

BIM-based coordination workflows go further than just running clash checks. They establish who is responsible for which models, what level of geometric detail is required, how often coordination meetings happen, and how conflicts get documented, tracked, and resolved. The entire process gets spelled out in a BIM Execution Plan before anyone starts modeling.

For PjM, this topic sits at the intersection of quality control and project delivery. You need to understand the distinction between design coordination (the architect's responsibility during design) and construction coordination (the contractor's responsibility during construction). Getting that boundary wrong creates claims, finger-pointing, and failed expectations. You also need to know how Level of Development requirements shape what can and cannot be coordinated at each project phase.

The exam tests your ability to evaluate coordination workflows, assign responsibilities correctly, and make judgment calls when coordination breaks down.