Copy/Monitor Setup: Stop Losing Coordination When Architects Move Levels

Our MEP model setup checklist flagged Copy/Monitor as the most-skipped item — usually because “the architect never moves levels.” They do, and it’s almost always the week before a milestone, silently, with no notification unless you set one up.

What Copy/Monitor actually does

Copy/Monitor is not “linking a level.” It creates a monitored copy of an element from a linked model into your model, and Revit tracks whether the original in the link ever changes. If it does — level elevation shifts, a grid moves, a column relocates — you get a coordination warning the next time you open or reload the link. Without Copy/Monitor, that same change happens invisibly; your MEP model just silently becomes wrong relative to the architecture.

Setting it up correctly

1. Load the architectural link, then go to Collaborate → Copy/Monitor → Select Link.
2. Copy levels first, monitor after — use the “Copy” tool inside Copy/Monitor mode for every level the architect has defined, not just the levels your MEP model currently uses. Skipping a level now means adding it later requires re-running Copy/Monitor from scratch on that element.
3. Grids: copy, don’t recreate manually. A grid drawn by hand in your MEP model with the same name as the architectural grid looks identical but has zero relationship to the original — it will never warn you of a move, and it invites a second silent-failure mode: two grids with the same label, one monitored, one not, confusing everyone in a coordination meeting.
4. Check the Coordination Review tool periodically — Copy/Monitor generates warnings automatically, but they surface in the Coordination Review dialog, not as a popup. If nobody has looked at Coordination Review in three weeks, warnings are stacking up unseen.

Why teams skip this

Copy/Monitor setup takes 10-15 minutes on a model that already has levels and grids drawn manually — which is most models, because someone modeled fast before coordination started. Redoing this properly means deleting manually-drawn grids and levels and replacing them with monitored copies, which feels like backward progress on a deadline. It isn’t: it’s the only mechanism that converts “the architect moved something” from a discovery you make during a clash review three weeks later into a warning you see the next time you open the file.

What breaks without it

• A level elevation shift of even 50mm can misalign every duct/pipe hanger height calculation done relative to that level, silently, across the entire floor.
• A grid shift changes column locations, which changes clearance calculations for anything routed near a column — exactly the kind of soft clash that headroom checks are built to catch, except this time the root cause is upstream of MEP entirely.
• Without monitored grids, “align to grid” workflows in scheduling and coordinate exports silently reference stale positions.

Common mistake

Teams monitor levels but skip grids, assuming “grids don’t change that often.” Grids change less often than levels, but when they do — during a structural bay resizing, for instance — the impact is wider (every column-adjacent element) and harder to spot visually than a level shift, because grid lines look the same at a glance whether they moved 200mm or not at all.