Copy/Monitor for Coordination — Use Copy/Monitor conceptually for coordination (intro) - Autodesk Revit

SECTION 1

Historical Context & Motivation

Before digital coordination tools existed, architects, structural engineers, and mechanical designers each drew their part of a building on separate sheets of paper. When one team moved a column or shifted a wall, the others had no automatic way to know. Errors surfaced late—often only on the construction site—when a duct collided with a beam that had quietly migrated three feet. Autodesk introduced Copy/Monitor in Revit precisely to solve this quiet miscommunication between disciplines that share the same building but not the same file.

As a visual arts student, you already understand how a single composition depends on many elements agreeing with one another—value, line, and proportion must stay in harmony even when you revise one region. Copy/Monitor extends that same discipline of visual consistency across multiple authors who never touch the same canvas directly.

2000 • Revit Debuts

Revit Technology Corporation releases the first parametric building modeler, making elements aware of one another within a single file.

2002 • Autodesk Acquires Revit

Autodesk purchases Revit and begins integrating multi-discipline workflows for architecture, structure, and systems.

2005 • Copy/Monitor Matures

Cross-file coordination tools solidify, letting linked models track shared elements like grids, levels, and columns.

2010s • BIM Mandates

Governments and large firms require Building Information Modeling, making disciplined coordination a legal and contractual expectation.

The gap this concept addresses is deceptively simple: how can two independent models agree on the elements they both care about—without merging into one unmanageable file? Copy/Monitor is Revit's answer to that coordination question.

SECTION 2

Core Principles & Definitions

Copy/Monitor rests on a small set of ideas that, once understood, make the whole workflow feel intuitive. At its heart, the tool lets you copy a shared element from a linked model into your own, then monitor the original so Revit alerts you whenever the source changes. You are not simply importing geometry; you are establishing a living relationship between two files.

Linked Model

A separate Revit file referenced inside yours—like a photograph pinned to your studio wall for reference, visible but not directly editable.

Copy

Creating a native version of a linked element inside your model, so it belongs to your file yet remains tied to its origin.

Monitor

Establishing a watchful link so Revit flags any change to the original element, prompting you to accept or reject it.

Coordination Review

The dialog where Revit reports monitored changes, letting you resolve mismatches deliberately rather than silently.

✦

KEY TAKEAWAY

Think of Copy/Monitor like the underdrawing and finished layers in a collaborative mural. One artist lays the guiding lines (the source model), and each subsequent painter copies those lines into their own panel. If the lead artist later shifts a contour, everyone downstream gets a note to adjust—rather than discovering the mismatch only after the paint dries.

SECTION 3

Visual Explanation

The diagram below shows the essential flow. A source model contains shared elements. Your model links to it, copies the elements you need, and establishes monitoring so that any later edit triggers a coordination alert.

The source model on the left feeds copied, monitored elements into your model on the right. A dashed monitoring link watches for edits, and any mismatch routes into the Coordination Review dialog at the bottom.

Notice that the arrows move in two directions. The solid arrow represents the initial copy, while the dashed arrow represents the ongoing watch. This bidirectional awareness is what separates Copy/Monitor from a one-time import that would go stale the moment the source changed.

SECTION 4

How the Monitoring Relationship Works

Copy/Monitor is not a numerical formula but a rule-based relationship, so it helps to express its logic as a conditional statement. Revit stores, for each monitored element, a reference to its source and a snapshot of the source's key parameters—position, elevation, and identity.

MONITORING CONDITION

Alert = (P_source ≠ P_stored) ∨ (E_source deleted)

Here P_source is the current parameter set of the source element, P_stored is the snapshot Revit saved at copy time, and E_source is the element's existence. An alert fires whenever the source moves, changes, or disappears.

When the condition evaluates true, Revit does not silently update your copy. Instead it queues the discrepancy for review, respecting the principle that the downstream author owns the decision. This deliberate hand-off is what makes coordination trustworthy across independent teams.

RESOLUTION OUTCOMES

Resolve ∈ { Accept, Reject, Postpone }

Accept updates your copy to match the source; Reject keeps your version and breaks the specific monitor; Postpone leaves the flag open for a later decision without losing the relationship.

⚠

Why not auto-update?

Automatic updates would be dangerous—an engineer might have already designed a beam around a column's old position. Forcing review protects downstream work from being silently invalidated.

SECTION 5

Which Elements Can Be Copy/Monitored

Copy/Monitor is intentionally limited to a small set of coordination-critical element categories. These are the elements whose position multiple disciplines must agree upon. The table below classifies the supported categories and why each matters.

Element	Why It's Shared	Typical Owner
Levels	Define vertical stories every discipline references	Architect
Grids	Establish the horizontal locating system for columns	Architect / Structure
Columns	Structure and architecture must occupy identical positions	Structural engineer
Walls	Bearing walls affect both spatial and structural design	Architect
Floors	Slab locations coordinate finishes and structure	Structure
MEP Fixtures	Air terminals and equipment must align across systems	MEP engineer

Categories eligible for Copy/Monitor and their coordination rationale

Free-form geometry, detail lines, and annotation are deliberately excluded, because they are presentation choices local to one discipline rather than shared spatial facts. Just as a shared color palette governs a group mural while each artist's brushwork stays personal, Copy/Monitor governs only the elements that truly must match.

SECTION 6

Worked Example: Coordinating Structural Columns

Imagine you are the structural modeler receiving an architect's linked model. The architect has placed twelve columns on a grid. Your task is to bring those columns into your structural file and keep them coordinated as the design evolves.

Setting Up Copy/Monitor on Columns

1
Step 1 — Link the Architectural Model

Insert the architect's file as a Revit link and pin it in place so it cannot drift. The link appears as reference geometry you can see but not directly edit.

Architectural model visible and locked
2
Step 2 — Launch Copy/Monitor

On the Collaborate tab, choose Copy/Monitor, then select the linked model as the source. Revit enters a dedicated coordination mode.

Coordination mode active
3
Step 3 — Copy the Columns

Use the Copy tool with the multiple option, then window-select all twelve columns. Revit creates native structural columns at identical positions and quietly establishes a monitor on each.

12 native columns created and monitored
4
Step 4 — Finish and Verify

Click Finish to exit coordination mode. A small monitor icon confirms each column is now watched. Your structural columns are independent objects that still track their architectural origins.

Monitoring relationships confirmed
5
Step 5 — Handle a Change

When the architect later shifts one column 600 mm, reload the link and run Coordination Review. Revit lists the moved column; you Accept the change, and your structural column snaps to match.

Column realigned via Accept

✦

WHAT JUST HAPPENED

You never redrew a single column, yet your model stayed in perfect agreement with the architect's. The monitoring relationship did the vigilance for you, surfacing exactly one change for your approval instead of leaving you to hunt for it manually.

SECTION 7

Strengths and Limitations

Copy/Monitor is powerful but not universal. Understanding where it excels and where it falls short helps you choose it appropriately rather than forcing it onto every coordination problem.

Strength	Limitation
Catches source changes automatically, preventing silent drift	Only works on a fixed set of element categories
Keeps decision authority with the downstream author	Can generate warning clutter on large, volatile projects
Creates native, editable copies rather than static imports	Requires disciplined link management to stay reliable
Integrates with Coordination Review for a clear audit trail	Does not detect physical clashes—only monitored parameter changes

Balanced view of Copy/Monitor capabilities

✦

IN CONTEXT

Copy/Monitor is one instrument in a larger coordination orchestra. It handles parameter agreement, while separate tools like Interference Check handle physical collisions. Like a printmaker who registers each color plate before pulling a print, you use the right alignment tool for each stage rather than expecting one to do everything.

SECTION 8

Connection to Advanced BIM Coordination

Copy/Monitor is an entry point into the broader discipline of model-based coordination. As projects scale, teams layer additional tools and even external platforms on top of it. The table contrasts the introductory technique with its more advanced counterparts.

Copy/Monitor (Intro)	Advanced Coordination
Watches a fixed set of shared elements within Revit	Clash detection across all geometry via Navisworks
Change alerts through Coordination Review	Automated issue tracking through cloud platforms like BIM 360
One-to-one file relationships	Federated multi-model environments with many disciplines
Manual accept/reject decisions	Rule-based workflows and issue assignment to responsible parties

From introductory monitoring to enterprise coordination

Mastering Copy/Monitor first gives you the conceptual vocabulary—source, monitor, review, resolve—that scales directly into these professional workflows. The habits you build now, especially the discipline of deliberate change acceptance, remain the foundation of coordination at any project size.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

In your own words, explain the difference between simply copying a linked element and using Copy/Monitor on it.

Show answer

A plain copy creates a static, one-time duplicate that never changes when the source changes. Copy/Monitor also creates a native copy, but it additionally establishes a watching relationship. If the source element later moves, changes, or is deleted, Revit flags the discrepancy in Coordination Review. The essential difference is ongoing awareness: Copy/Monitor keeps the two models in a living dialogue rather than a frozen snapshot.

Question 2: BASIC

Name three element categories that support Copy/Monitor and identify which discipline typically owns each.

Show answer

Levels are typically owned by the architect, since they define the building's stories. Grids are owned jointly by the architect and structural engineer as the locating system. Columns are owned by the structural engineer, who must position them identically to the architectural intent. Other valid answers include walls, floors, and MEP fixtures, each shared because multiple disciplines depend on their agreed location.

Question 3: INTERMEDIATE

An architect deletes a monitored column from the source model. Walk through what Revit does and the options you have.

Show answer

According to the monitoring condition, the deletion of the source element (E_source deleted) evaluates the alert as true. Revit will not silently remove your copy; instead it queues the change for Coordination Review. There you may Accept, which deletes your corresponding column, or Reject, which keeps your column and breaks that specific monitor. You could also Postpone to defer the decision while preserving the flag for later resolution.

Question 4: APPLIED

You are the MEP engineer. The architect shifts an entire grid line, moving twelve associated columns. How does Copy/Monitor reduce your workload, and what must you do to see the change?

Show answer

Because you established monitors when copying the grid and columns, Revit already tracks all twelve relationships. You must first reload the architectural link so your file sees the updated source, then run Coordination Review. Revit reports every shifted element in one organized list. Accepting the changes realigns your copies automatically, sparing you from manually relocating twelve columns and re-verifying each position by hand.

Question 5: CRITICAL THINKING

Copy/Monitor does not detect physical clashes between geometry. Argue why this limitation is a reasonable design decision rather than a flaw, and describe what tool complements it.

Show answer

Copy/Monitor is scoped to parameter agreement on a defined set of shared elements, which keeps it fast, predictable, and low in false alarms. Extending it to detect every geometric collision would blur its purpose and flood users with warnings unrelated to coordination intent. This focused scope is a strength because it makes each tool's role clear. Physical collisions are instead the domain of Interference Check within Revit or Navisworks clash detection externally. Together they form a layered strategy: Copy/Monitor guarantees shared elements agree in position, while clash tools confirm that agreed geometry does not physically overlap.

SUMMARY

Summary

Copy/Monitor exists to keep independent Revit models in agreement about the elements they share. You link a source model, copy its coordination-critical elements—levels, grids, columns, walls, floors, and MEP fixtures—and monitor the originals. Whenever a monitored source moves, changes, or vanishes, Revit routes the discrepancy into Coordination Review, where you Accept, Reject, or Postpone rather than being forced into a silent update.

The genius of the tool is that it keeps decision authority with the downstream author while automating the vigilance. It handles parameter agreement, not physical clashes, so it pairs naturally with clash detection tools in a layered coordination strategy. Master this introductory workflow and you gain the vocabulary—source, monitor, review, resolve—that scales directly into professional, federated BIM coordination.