Copy/Monitor is designed to support both the initial creation and continuing coordination of critical datum elements between linked Revit models. Participating disciplines can copy the approved Levels and Grids from the authoritative architectural or structural model into their own models and establish monitored relationships to the source elements.
If the structural framing decision later changes floor-to-floor elevations or grid positions, Revit generates coordination-review notifications when the linked source model is reloaded. The receiving teams can then assess each change, postpone it where necessary, reject it, or update their corresponding datum elements through a controlled coordination process.
Shared Coordinates ensure that models occupy the correct common spatial position, but they do not monitor changes to individual Levels or Grids. Establishing a primary model in a collaboration platform supports information exchange but does not create element-level coordination relationships. Exporting reports and property information provides only a static record and would require manual comparison after every design revision.
The project must also establish which discipline owns the master datum elements and define how proposed changes are reviewed and approved before dependent teams modify their models.
Reference topics: Copy/Monitor; coordination review; Levels and Grids; datum ownership; linked-model change management; multidisciplinary Revit coordination.

Revit phase mapping is specifically intended to reconcile differences between phase structures in a host model and a linked Revit model. The BIM manager should map Phase 1 in the structural link to Existing in the architectural host and map Phase 2 to New Construction. Revit can then interpret the linked elements' phase-created and phase-demolished conditions in the context of the host view.
This preserves the structural consultant's internal phase definitions and avoids altering a model controlled by another discipline. It also produces consistent display behaviour across host views using phase filters such as Show Previous + Demo, Show Complete, or other project-specific configurations.
A Visibility/Graphics override can alter how an entire link or category appears, but it does not correctly translate the underlying phase relationships. Renaming or restructuring the phases directly in the consultant's model is unnecessary and may disrupt that firm's documentation. A host view template can control link-display settings, but it cannot substitute for correct phase correspondence where the two files use different phase names or phase structures.
Phase mapping is therefore the controlled, non-destructive coordination mechanism for this scenario.
Reference topics: Revit phase mapping; linked-model display; phase filters; demolition views; host and consultant model coordination; multidisciplinary phase standards.

Clash analysis is only valid when the federated inputs represent the correct model versions, include current references, and use the agreed coordinate system. Because the BIM manager has identified outdated links and local-coordinate exports, the current federation is technically unreliable. The appropriate response is to return the affected submissions to the responsible teams, require verification of model references and coordinates, and then reassemble the federation from corrected source files.
Adjusting clash tolerances would suppress or reclassify symptoms without correcting the underlying spatial and version-control defects. This could hide genuine clashes while leaving falsely positioned elements in the coordination environment. Freezing the model and asking trades to work around invalid information transfers avoidable risk into design and construction. Excluding entire models may temporarily reduce clash totals but produces an incomplete coordination dataset and should not precede a controlled correction request.
The BIM manager should validate file versions, export views, linked-model status, shared-coordinate settings, and model origin behavior before rerunning the clash matrix. Only after the federation passes these input-quality checks should coordination analysis resume.
Reference topics: Federated-model assembly; shared-coordinate verification; model-reference currency; coordination input validation; clash-detection governance; multidisciplinary model exchange.

A custom coordination view should be created using the applicable published mechanical and structural models and limited to the patient-room zones required by the approved clash matrix. The clash results can then be filtered by model pair, location, object category, and active status before the filtered list is exported. This produces a targeted report containing only the coordination conditions requested by the project leads.
The custom-view approach maintains the relationship between the clash records and the coordinated model geometry. It also makes the review repeatable: the BIM manager can return to the saved view during subsequent coordination cycles and evaluate whether the same discipline and location criteria have been resolved.
Asking individual disciplines to prepare independent reports creates inconsistent evaluation criteria and weakens the centralized coordination record. Exporting every clash and manually filtering the spreadsheet introduces unnecessary effort and increases the risk of omitting or misclassifying issues. Assigning clashes through the Issues tool is appropriate after clashes have been reviewed and determined to require action, but assignment does not itself generate the requested filtered clash report.
Reference topics: Autodesk Model Coordination; custom coordination views; clash filtering; clash matrices; published models; active-clash reporting; location-based coordination.