Most Coordination Meetings Are Painful
Everyone has sat through a coordination meeting that accomplished nothing. Two hours of staring at a model while one person clicks through clashes that three other people cannot see on the projector screen. The trades are checked out. The GC is frustrated. The VDC coordinator is wondering why nobody cares about the 847 clashes they found.
Coordination meetings do not have to be painful. When they are run well, they become the most productive meeting on the project. The difference is preparation, facilitation, and focus.
Preparation Makes or Breaks the Meeting
Effective coordination meetings require significant preparation before anyone enters the room. The VDC team should have already identified the critical clashes, grouped them by location and system, and prioritized them by impact. Walking into a meeting with an unfiltered clash report and saying “lets start at number one” guarantees a wasted session.
Pre-meeting packages that show each trade their specific clashes with enough context to understand the issue enable attendees to come prepared with solutions rather than spending meeting time understanding problems. Send these packages 48 hours before the meeting, not the night before.
Model preparation is equally important. Set up saved viewpoints for each discussion item. Pre-configure section cuts that clearly show the conflict. Having to navigate to each clash during the meeting wastes time and tests patience.
Facilitation Techniques That Work
Start with the highest-impact items. If you lose attendees after 45 minutes, at least the critical issues got addressed. Saving important items for the end of a two-hour meeting means they never get adequate attention.
Keep the discussion solution-oriented. The meeting should identify who moves what, by when. It should not relitigate design decisions or debate whose system was there first. When discussions become circular, the facilitator needs to capture the disagreement, assign a resolution owner, and move on.
Use visual markup tools during the meeting so decisions are documented in real time. Waiting to document resolutions after the meeting introduces memory errors and disputes about what was agreed.
The Right People in the Room
Coordination meetings need people with authority to make routing and installation decisions. Sending a junior engineer who cannot commit to moving a duct run means that clash comes back next week unresolved. Establish early that coordination meetings require decision-makers, not observers.
Limit attendance to the trades actively involved in the current coordination zone. Having eight trades in the room when only three have conflicts in the area being discussed wastes five peoples time and makes the meeting feel irrelevant to most attendees.
Meeting Cadence and Duration
Shorter, more frequent meetings outperform long monthly sessions. A focused 60-minute weekly meeting maintains momentum and catches issues before they compound. A sprawling 3-hour monthly meeting creates a backlog of unresolved clashes and a dread that kills attendance.
Set hard stop times and honor them. Meetings that consistently run over teach people that the scheduled time is meaningless, which erodes both attendance and engagement.
Measuring Coordination Effectiveness
Track resolution rates between meetings. If the same clashes appear week after week unresolved, the meetings are not working regardless of attendance. The goal is not to identify clashes. It is to resolve them. Measure accordingly.