How Do You Avoid Design Coordination Clashes?

Start with agreed design responsibilities and a shared information programme, then test interfaces in drawings and models before construction. Software can find geometric conflicts; people still decide which system moves and whether the change is acceptable.

Which clashes deserve attention first?

Prioritise high-impact interfaces: structure versus major plant or risers, fire and smoke systems, access and maintainability, ceiling zones, penetrations and services serving occupied areas. A model may report many minor overlaps. Sort issues by buildability, safety, cost and programme effect rather than the count of clashes.

What does a working process look like?

Set model coordinates, exchange dates, information requirements and an issue register. Give each issue an owner, due date and proposed resolution. Review it with the affected designers and trades; then update the authoritative drawings and specification. An issue marked “closed” in a model has little value if the construction set still shows the old arrangement.

When should coordination happen?

At design milestones and before trade procurement, fabrication or site installation. Late specialist inputs may require another pass. Reserve space and access for real equipment early instead of treating a model as proof the system can be installed or maintained.

A clash report should end with a decision, not a screenshot. Record whether a service moves, a beam changes, an access zone is protected or a designer confirms the overlap is acceptable. Then issue the revised construction document and verify the affected trade has received it.

Team Vanguard has used model-led documentation and coordination on complex projects. The useful measure is whether the team can make and communicate a decision in time. Read how BIM coordination works or contact us.

Sources and further reading

• buildingSMART — BIM Collaboration Format
• NBS — RIBA Plan of Work and responsibility matrix