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.
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.
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
Copy
Monitor
Coordination Review
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.
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.
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.
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.
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 |
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.
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.
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 |
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 |
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.
Practice Problems
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.