Why We Link Models Instead of Merging

On any project larger than a single-discipline fit-out, assembling all building data into one monolithic Revit file is a mistake that project teams eventually regret. Linked models — separate .RVT files referenced into a host file via Insert > Link Revit — give each discipline team ownership of its own model, which then contributes to a federated coordination model. The three core reasons this approach dominates professional practice are file performance, discipline ownership, and design authority.

File performance: A single combined architectural-structural-MEP model for a 500,000 SF hospital can exceed 2 GB. Revit's in-memory performance degrades noticeably above 350–400 MB on most workstations. Linked models are loaded as read-only overlays, consuming far less RAM than fully loaded workshared models. Revit also allows you to close links when not needed, reclaiming memory instantly.

Discipline ownership: Structural engineers own the structural model; mechanical contractors own the ductwork model. No one can accidentally delete another discipline's elements, move their grids, or change their ceiling heights. Each team works in their own Central File on their own Revit server folder and publishes updates on an agreed coordination cycle (typically weekly on large projects).

Design authority: When the architect moves a structural grid, the structural engineer sees that change in Coordination Review and decides whether to accept it — maintaining full professional control. This is categorically different from a merged file where anyone with permission could alter anything.

Inserting a Linked Revit Model

Open Insert > Link Revit (keyboard shortcut: none by default, but most firms add one). The dialog offers five positioning modes; choosing the wrong one is the single most common cause of a linked model appearing in the wrong location or at a wrong elevation:

  • Auto - Origin to Origin: Places the link so that its internal project origin aligns with the host file's internal project origin. Use this when all team members started from the same project template and have not moved the survey point or project base point. It is the safest default for new projects.
  • Auto - By Shared Coordinates: Places the link using the shared coordinate system — survey points and project north that have been published between files. This is the correct mode once shared coordinates have been established (see below). It is required when linking consultant files that have been georeferenced to a site survey.
  • Auto - Center to Center: Aligns the bounding-box centers of link and host. Only useful for quick look-sees; never use for production work.
  • Auto - By Room (Room to Room) and By Shared Coordinates (Last Placed): Specialty modes for specific workflows; rarely needed in standard AEC coordination.
  • Manual - Origin, Manual - Base Point, Manual - Center: Lets you click to place the link. Occasionally needed when inheriting consultant files with displaced origins.

After linking, always switch to a section view and verify that the linked building floors align correctly with the host file floors. A 1-inch vertical misalignment between architectural and structural models causes hundreds of false clashes in coordination review.

Controlling Linked Model Visibility

Visibility/Graphics Overrides (keyboard: VG or VV) has a dedicated Revit Links tab that appears whenever at least one model is linked. Each linked model entry expands to reveal two display modes:

  • By Host View: The link displays using all visibility settings of the host view — category on/off states, graphic overrides, detail level, and filters all apply to the linked model. This is ideal for coordination views where you want consistent graphic standards across all linked disciplines.
  • Custom: Clicking Custom opens a nested Visibility/Graphics dialog specific to that linked model. You can turn off individual categories within the link independently of the host view. For example, in a plumbing coordination view you might turn off all MEP categories in the structural link except Structural Framing and Structural Columns.

Linked models also respect worksets if the linked file is workshared. In the Revit Links tab of VG, you can choose which workset from the linked file is visible. Structural engineers commonly put their foundation elements on a separate workset that architectural teams can hide when not relevant to current coordination tasks.

View filters applied to the host view do not propagate into linked models by default. If you need to filter elements within a link (for example, showing only fire-rated walls in an architectural link), switch to Custom mode and apply the filter there.

Establishing Shared Coordinates

Shared coordinates allow multiple Revit files to reference the same real-world survey coordinate system, so that when each file is linked By Shared Coordinates, all models line up correctly — even if their internal project origins are in different positions.

The typical workflow on a new project is:

  1. The architect's file is the coordinate source. The architect uses the survey point to set true north and a real-world coordinate (often from a civil survey) or simply moves the survey point to a convenient landmark on site.
  2. The architect then links the structural model using Auto - Origin to Origin (both files started from the same template). Once the structural model is positioned correctly in the architectural host, navigate to Manage > Coordinates > Publish Coordinates. Select the structural link in the dialog. Revit writes the shared coordinate information back into the structural .RVT file.
  3. The structural engineer now opens their standalone model and sees that its shared coordinates are updated. When they link the architectural model, they choose By Shared Coordinates and the files align perfectly.
  4. For each new discipline added to the project (MEP, interiors, landscape), the architect publishes coordinates to that file after positioning it correctly.

Acquire Coordinates (Manage > Coordinates > Acquire Coordinates) is the reverse operation — the host file adopts the shared coordinate system from a selected link. This is used when a civil engineering file (often a DWG site survey) defines the authoritative coordinate system and the architect needs to inherit it rather than define it from scratch.

A critical warning: never move the Survey Point after shared coordinates have been established. Moving the survey point changes the shared coordinate origin, invalidating all previously published coordinates and misaligning every linked model on the project. If relocation is necessary, all files must be republished in sequence.

Copy/Monitor: Tracking Cross-Discipline Elements

Copy/Monitor is one of the most powerful — and most underused — coordination tools in Revit. It solves a specific problem: when structural levels and grids are designed by the structural engineer, the architect needs copies of those elements in the architectural model to host walls, floors, and views. But if the structural engineer later moves a grid line, the architect needs to know.

To set up Copy/Monitor, go to Collaborate > Copy/Monitor > Select Link, then click on the linked model in the canvas. The Copy/Monitor context tab appears with two commands:

  • Copy: Click elements in the linked model to create monitored copies in the host file. Applicable element types include Levels, Grids, Walls, Floors, Openings, and Columns. Click Finish when done.
  • Monitor: Used when you have already created corresponding elements (for example, you already have levels in the host file that correspond to levels in the link). Select the host element, then select the corresponding link element; Revit establishes a monitoring relationship without copying.

Copy/Monitor options (the Options button in the contextual tab) allow you to map element types between disciplines. For example, you can specify that copied Structural Framing elements should become Walls in the host, with a specific wall type assigned automatically. On large projects, configure these mappings at project kick-off in a BIM Execution Plan and enforce them via firm standards.

Coordination Review: Accepting and Rejecting Changes

Once Copy/Monitor relationships are established, Revit watches for changes to monitored elements every time the linked file is reloaded. When the structural engineer moves a grid, Revit flags it. The architectural team runs Collaborate > Coordination Review > Select Link, selects the structural link, and sees a list of all monitored element changes.

The Coordination Review dialog presents each change with the element type, what changed (position, elevation, type, deletion), and action options:

  • Accept Difference: You acknowledge the change and update the host element to match. The grid in the architectural model moves to the new position. Use this when the structural change is correct and the architecture must follow.
  • Reject: You flag the change as incorrect and the monitored relationship remains active (Revit will keep warning you). Use this when the structural change conflicts with an approved design decision — the rejection triggers a coordination issue that must be resolved in a coordination meeting.
  • Postpone: Defers the decision to the next review cycle. Useful when you need to check with the project manager before deciding.

Coordination Review warnings also appear in the standard Revit Warnings dialog (Manage > Review Warnings), but it is best practice to run a dedicated Coordination Review session after each linked file reload rather than relying on the warning system alone.

Naming Conventions and Circular Reference Avoidance

Professional BIM teams follow strict naming conventions for linked models to avoid confusion as files multiply. A typical naming standard follows the ISO 19650 pattern: [ProjectCode]-[Originator]-[Volume/System]-[Level]-[Type]-[Role]-[Number], for example PRJA-ARCH-ZZ-00-M3-AR-0001.rvt. Simpler projects often use [ProjectNumber]-[Discipline]-[BuildingCode].rvt such as 24-0187-STRUCT-A.rvt.

Circular references — where File A links File B and File B also links File A — must be avoided. Revit will warn you when you attempt to create a circular reference, but the warning is easy to dismiss and the resulting behavior (elements not displaying, Revit crashing on sync) can be difficult to diagnose later. The solution is a clear hierarchy: the coordination model links all discipline models; discipline models never link each other or the coordination model.

Best practices summary:

  • Store all linked files in a shared network folder or BIM 360/ACC folder that all team members can access with identical paths.
  • Use Overlay (not Attachment) link type for direct links; Attachment causes nested links to appear in every file that links the host, leading to uncontrolled file loading.
  • Reload links at a consistent schedule (e.g., every Monday morning) rather than ad hoc, so teams know when they have the latest consultant files.
  • Document every linked file in the BIM Execution Plan with file name, discipline, owner contact, and reload cadence.