Historical Context & Motivation
Before Building Information Modeling (BIM) transformed the architecture, engineering, and construction (AEC) industry, coordination between disciplines relied on manual overlay of two-dimensional drawings—a process rife with error and miscommunication. Architects would issue floor-plan sheets, structural engineers would trace their own grids on separate vellum, and mechanical consultants would develop ductwork layouts referencing yet another independent coordinate system. When one discipline shifted a grid line or adjusted a floor elevation, the change had to be communicated verbally or through written addenda, and downstream teams frequently missed the memo. The resulting clashes—columns punching through ducts, slabs at mismatched elevations—cost the industry billions of dollars in rework annually. Copy/Monitor emerged within Autodesk Revit as a purpose-built solution to this exact coordination gap, enabling one model to watch specific elements in a linked model and flag discrepancies automatically.
The central question Copy/Monitor addresses is deceptively simple: How can separate Revit models, maintained by different design teams, share foundational reference elements—levels and grids—without manual synchronization? Understanding the answer requires grasping how linked models interact, what it means to "copy" versus "monitor," and how the Coordination Review workflow surfaces and resolves discrepancies. This lesson introduces those core mechanics.
Core Principles & Definitions
Copy/Monitor operates on a straightforward premise: one Revit model (the host model) links to another (the linked model) and creates local copies of key datum elements—primarily levels and grids—while maintaining a persistent monitoring relationship back to the originals. When the original element in the linked model changes (renamed, moved, deleted), Revit records the discrepancy and presents it in the Coordination Review dialog so the host-model user can decide how to respond. The tool thus separates the act of copying data from the ongoing responsibility of monitoring that data for drift.
Linked Model
Copy
Monitor
Coordination Review
Datum Elements
Visual Explanation — The Copy/Monitor Workflow
The diagram above captures the full lifecycle of a Copy/Monitor operation on datum elements. On the left, the linked model (in this scenario, the architect's file) contains the authoritative levels and grids for the project. When the structural engineer initiates Copy/Monitor from the Collaborate tab, Revit creates native copies of those elements in the host model—represented by the solid cyan and violet lines on the right. Crucially, each copied element carries a hidden monitoring relationship (the dashed return arrow) that ties it back to the original. If the architect later raises Level 2 from 12′-0″ to 13′-0″, Revit does not silently update the structural model; instead, it queues the discrepancy in the Coordination Review dialog (the amber box at the bottom), giving the structural engineer full agency to accept, reject, or postpone the change. This workflow respects each discipline's authorial control while still enforcing cross-model awareness—a core tenet of effective BIM coordination.
How Copy/Monitor Works — Step-by-Step Mechanism
Initiating Copy/Monitor
The Copy/Monitor command is accessed from the Collaborate tab on the Revit ribbon, under the Coordinate panel. Upon clicking Copy/Monitor → Select Link, you pick the linked model instance in your view. This activates a temporary mode—the ribbon transforms to show four contextual buttons: Copy, Monitor, Options, and Finish. You remain in this mode until you click Finish, allowing you to copy or monitor multiple elements in a single session.
Copy vs. Monitor — Two Distinct Actions
It is important to understand that Copy and Monitor are conceptually separate operations, though they are almost always used together. When you click Copy and then select a level or grid in the linked model, Revit duplicates that element into your host model and simultaneously establishes a monitoring relationship. By contrast, Monitor (used alone) does not create a new element—it links an existing element in your host model to a corresponding element in the linked model. This is useful when you have already drawn your own grids and levels and simply want Revit to track them against the linked model's versions. In both cases, Revit stores the relationship in an internal mapping table tied to the link instance.
Options Dialog — Controlling Copy Behavior
Before selecting any elements to copy, it is wise to click Options on the contextual ribbon. This dialog presents category-specific settings. For Levels, you can choose whether to copy the original level's name or apply a prefix/suffix (e.g., appending "_STR" for structural). For Grids, the same renaming options apply, along with a toggle governing whether to replicate the grid's extent or adopt the host model's default extents. These settings prevent naming collisions and allow each discipline to maintain its own naming convention while preserving the monitoring link.
Detailed Breakdown — Coordination Review Actions
Once monitoring relationships are established, the ongoing value of Copy/Monitor resides in the Coordination Review dialog. Accessed via Collaborate → Coordination Review, this tool scans all monitored pairs and lists every discrepancy in a tabular format. Each row identifies the element category (level, grid, column, etc.), describes the nature of the change, and offers a set of resolution actions. Understanding these actions is essential to using Copy/Monitor effectively in a production environment.
| Action | Effect on Host Model | When to Use |
|---|---|---|
| Accept | Updates the host element to match the linked model's change (e.g., moves a level to the new elevation). | When the linked model's change is authoritative and should propagate to your discipline. |
| Reject | Keeps the host element unchanged. The monitoring relationship is preserved but the alert is dismissed. | When the change is irrelevant to your discipline or was made in error. |
| Postpone | No changes made. The discrepancy remains in the review list for future action. | When you need to consult the other team before deciding. |
| Rename (levels only) | Updates the host level's name to match the linked model's renamed level while keeping the elevation intact. | When only the naming convention changed, not the physical datum. |
| Stop Monitoring | Severs the monitoring relationship entirely. The copied element remains but is no longer tracked. | When an element has been permanently diverged between the two models (e.g., a mezzanine level only in one model). |
Worked Example — Copying Levels & Grids from an Architectural Link
Imagine you are the structural engineer on a mid-rise residential project. The architect has issued their Revit model containing five levels and a grid system of eight column lines. Your task is to establish your structural model with matching datums using Copy/Monitor.
Insert → Link Revit. Browse to the architect's .rvt file. Under Positioning, select Auto — Shared Coordinates (or Auto — Origin to Origin if shared coordinates have not been established). Click Open.Collaborate → Copy/Monitor → Select Link. Click on the linked architectural model in the view. The ribbon changes to show the Copy/Monitor contextual tools.Options on the contextual ribbon. In the Levels tab, set the Copy behavior to Copy Original for naming (or add a suffix like "_S" if your firm's BIM Execution Plan requires discipline prefixes). In the Grids tab, similarly confirm naming rules. Click OK.Copy on the ribbon. Switch to an elevation or section view where levels are visible. Click each level line in the linked model—Level 1, Level 2, Level 3, Level 4, Roof. Each click creates a native copy in your model with a monitoring icon (a small eye symbol). Next, switch to a plan view. Click each grid line (A through H). Revit copies all eight grids and establishes monitoring links.Finish on the contextual ribbon to exit Copy/Monitor mode. Open Collaborate → Coordination Review and select the architectural link. The dialog should show no pending discrepancies—the models are synchronized. If the architect later changes Level 3 from 24′-0″ to 25′-6″, this dialog will flag that change the next time you reload the link and open Coordination Review.Strengths, Limitations & Comparisons
Copy/Monitor is a powerful coordination tool, but it operates within specific constraints. Understanding both its strengths and its boundaries will help you decide when to use it—and when to complement it with other coordination strategies such as Interference Checks (clash detection) or manual review protocols.
| Strengths | Limitations |
|---|---|
| Automates detection of datum changes across linked models—no manual checking required. | Limited to specific element categories: levels, grids, columns, walls, floors, and openings. Cannot monitor MEP elements, rooms, or custom families. |
| Preserves each team's authorial control—changes are proposed, not forced. | Only works with Revit-to-Revit links. IFC or DWG links cannot participate in Copy/Monitor. |
| Supports flexible naming conventions through the Options dialog. | If the linked file path breaks (file moved or renamed), all monitoring relationships become orphaned until the link is repaired. |
| Coordination Review provides a clear, actionable list—ideal for BIM coordination meetings. | Monitoring is one-directional (host watches the link). The linked model cannot see what the host has done. |
| Once set up, monitoring persists across sessions and file saves with no ongoing overhead. | Large projects with hundreds of monitored elements may experience minor performance lag when running Coordination Review. |
Connection to Advanced Coordination Workflows
Copy/Monitor for levels and grids is often the very first coordination task in a BIM project—a foundational setup that enables all subsequent interdisciplinary work. As your Revit proficiency grows, you will encounter more advanced coordination techniques that build upon or extend this foundation. The table below maps introductory concepts from this lesson to their advanced counterparts.
| Introductory Concept (This Lesson) | Advanced Extension |
|---|---|
| Copy/Monitor for levels and grids | Copy/Monitor for structural columns, walls, floors, and openings—allowing full structural-architectural datum plus geometry coordination. |
| Coordination Review (manual, within Revit) | Automated clash detection via Navisworks Manage or BIM 360 Model Coordination, which detects geometric intersections across all disciplines. |
| Single linked model (one-to-one) | Multi-model federation: architectural, structural, MEP, civil, and landscape models all linked into a coordination model with multiple Copy/Monitor relationships. |
| Origin-to-Origin positioning | Shared Coordinates workflow: Acquire/Publish Coordinates to maintain true survey-point alignment across models and for export to GIS or construction layout. |
| Manual Coordination Review dialog | Dynamo or Revit API scripting to automate Coordination Review reporting, generating spreadsheets or dashboards for BIM coordination meetings. |
As a visual arts student working in Revit, you may initially engage with Copy/Monitor primarily when collaborating with consultants on design studio projects or internships. In professional practice, the BIM Execution Plan (BEP) for a project will specify exactly which model serves as the datum authority, which disciplines copy and monitor, and at what project milestones Coordination Review must be run. Mastering the introductory workflow covered here positions you to participate confidently in those larger coordination frameworks.
Practice Problems
Lesson Summary
Copy/Monitor is Revit's built-in tool for keeping levels and grids synchronized across linked models maintained by different disciplines. Accessed from the Collaborate tab, the tool offers two actions: Copy (which creates a local duplicate and a monitoring link) and Monitor (which pairs an existing host element to a linked element for tracking). The Options dialog controls naming conventions and copy behavior before elements are selected.
When changes occur in the linked model, the Coordination Review dialog presents every discrepancy with actionable choices: accept, reject, postpone, or stop monitoring. This workflow preserves each team's authorial control while automating change detection—the core value proposition of BIM-based coordination. Remember that monitoring is one-directional, that Copy/Monitor only works between Revit files, and that it is best paired with clash detection tools and clear BIM execution planning for comprehensive project coordination.