There is no universal rule for clash responsibility. The party that must act depends on the contract, BIM execution plan, trade scopes, design responsibility, and the decision involved.
Finding an electrical clash does not mean owning its solution. One party may detect it, another may develop an option, and an engineer may need to approve a design change.
Detection Is Not Ownership
A coordination platform may report that a conduit intersects a duct, but it cannot decide which system should move or whether a change is acceptable.
Detect → Assign → Develop a solution → Approve when required → Update → Verify
Different parties may handle each step. BIMForum’s BIM Project Execution Plan Guide covers project milestones and coordination expectations. It also notes that RFI responses may be needed before coordination is signed off for an area.
This is why BIM execution procedures should be understood before coordination begins. Software records the work, but project documents establish authority.
Example Clash Responsibility Matrix
This is an example only. Actual duties must follow the contract, BIM execution plan, scopes, and project procedures.
Issue or step | BIM coordinator | Electrical trade | Other trade | Engineer or designer | GC/VDC lead |
Detect clash | Supports detection | Supports detection | Supports detection | As needed | Oversees process |
Assign issue | Supports tracking | — | — | — | Assigns per project workflow |
Develop electrical reroute | Coordinates models | Leads within authorized scope | Coordinates affected system | Reviews if design is affected | Facilitates |
Change engineering intent | Does not approve | Proposes or flags | Proposes or flags | Reviews or approves as applicable | Facilitates review |
Update trade model | Checks coordination | Updates electrical scope | Updates its scope | Per project scope | Tracks status |
Verify resolution | Reruns checks | Confirms electrical change | Confirms affected work | As required | Coordinates closure |
A matrix like this can be developed during BIM implementation. It should describe the workflow, not assume duties from job titles.
Who Decides Which Trade Moves?
“Electrical always moves around ductwork” is not a workable rule. The team should review both systems and the consequences of each option.
Factors include system rigidity, gravity requirements, structure, equipment connections, clearances, access, route size, installation sequence, and available space. Cost, schedule, prefabrication, and design intent may also matter.
MEP BIM services can expose the physical choices, while authorized project parties decide which option can proceed. Coordination priority does not determine contractual responsibility.
Electrical Clashes Need Different Responses
A conduit crossing a duct may be resolved through trade coordination when rerouting remains within approved authority. Electrical BIM services can update the route and check the combined model.
A cable tray intersecting a beam may need another route, a different penetration, or structural review. A pipe inside switchgear access space may be governed by access and clearance requirements.
A feeder reroute that adds significant length can affect design assumptions and may need engineering review. If design documents place two systems in the same required space, the response may be an RFI.
This is where electrical constructability and design authority separate. The BIM team can develop options but cannot approve changes outside its scope.
A Coordination Meeting Does Not Close the Clash
A clash is not closed because the team discussed it or agreed that one trade would move:
Issue assigned → Decision recorded → Model updated → Federated model refreshed → Clash test rerun → Resolution verified → Issue closed
Clash detection services can rerun the test after updated models are loaded. The affected trades confirm the new condition, while the assigned party tracks closure.
The change must reach shop drawing production and field information so they do not show different conditions.
Data-Center Example: Conduit Rack vs Chilled-Water Piping
In a data-center corridor, a conduit rack conflicts with chilled-water piping. Moving the conduit appears easier because the piping is less flexible.
The proposed reroute adds length, creates difficult bends, interferes with another electrical system, and affects prefabricated rack sections. The team compares options instead of assigning the move to electrical.
Electrical develops a route, mechanical checks the piping, and the BIM coordinator reviews both models. Because feeder length may affect engineering assumptions, the question enters the review or RFI process. After approval, the models are updated and retested.
Clash Responsibility Must Be Defined by the Project
The answer to clash responsibility is not automatically the BIM coordinator, electrical trade, or smaller system. Each stage may belong to a different party.
A reliable BIM coordination process records decisions and keeps the issue open until revised models are checked. Project documents remain the controlling sources.
Frequently Asked Questions
-
Who is responsible for resolving BIM clashes?
It depends on the contract, trade scopes, execution plan, and whether the solution changes design intent.
-
Is the BIM coordinator responsible for every clash?
No. The coordinator may detect, assign, track, and verify issues without having authority to redesign a trade system.
-
Who decides which MEP trade moves?
The decision follows project rules and considers constraints, access, clearances, installation, and design intent.
-
When does a clash require an RFI?
An RFI may be needed when the solution affects engineering criteria, design intent, equipment, or another party’s authority.
-
Who verifies that a BIM clash has been resolved?
The assigned party tracks closure, affected trades confirm their changes, and the coordination team reruns the check.
Is Every Coordination Issue Actually Closed?
Eracore supports clash detection, issue tracking, model updates, and coordinated drawings so decisions carry through to installation.
