Every building has more systems competing for the same space than any single drawing can show. Structural framing, HVAC distribution, plumbing piping, electrical conduit, fire suppression mains, and specialty systems all need to occupy the same ceiling plenums, mechanical rooms, and wall chases. When those systems conflict, the project pays for it in change orders, schedule delays, and RFIs during construction.

Systems coordination is the disciplined process of combining all the discipline models into a single federated view, running automated clash detection, reviewing the results in coordination meetings, and resolving every conflict before the construction documents are issued. On the ARE, you need to understand how this process works, who owns each step, and how to evaluate the right resolution strategy when conflicts arise.

The architect does not just identify clashes. The architect leads the process: setting the LOD requirements for each phase, running or overseeing the interference detection, issuing coordination reports, and evaluating whether a proposed resolution in one system creates a new problem in another. A duct rerouted around a beam may now conflict with a sprinkler branch. A raised pipe may push the ceiling below the height required by program. Every resolution must be evaluated across all systems simultaneously.

BIM-based clash detection automates the identification of geometric conflicts but does not resolve them. The analysis and judgment required to resolve conflicts in order of priority, evaluate trade-offs between alternative solutions, and communicate decisions back to the team are architectural skills. This topic covers how that process works from design development through construction documents, what the standard LOD requirements mean for the reliability of the coordination, and what happens at coordination meetings where conflicts are tracked, assigned, and closed.