Historical Context & Motivation
Before digital modeling tools existed, architects, engineers, and interior designers coordinated their drawings by literally overlaying transparent sheets on a light table — a painstaking process in which discrepancies between structural columns and partition walls, or ductwork and ceiling planes, were caught only if someone physically noticed the overlap. As building projects grew in complexity throughout the late twentieth century, this manual overlay method became a bottleneck responsible for costly errors discovered only during construction. The discipline known as Building Information Modeling (BIM) emerged to address this challenge, replacing flat drawings with intelligent three-dimensional databases where every wall, beam, and duct carries parametric data. Within Autodesk Revit, the Coordination Review feature was developed specifically to manage changes that occur when multiple linked models are updated independently, providing a systematic way to detect and respond to modifications that could compromise design intent across disciplines.
The central question that Coordination Review answers is deceptively simple: When another team member changes an element that your model depends on, how do you know about it, and how do you decide what to do? For visual arts students working in spatial design, exhibition architecture, or interior environments, this question is directly relevant — your ceiling grid, lighting layout, or gallery partition may rely on a structural grid that a structural engineer just shifted by 300 millimeters.
Core Principles & Definitions
Coordination Review operates within a broader framework of linked-model collaboration in Revit. Before diving into the workflow mechanics, it is essential to grasp the foundational concepts that make the feature meaningful. These principles apply whether you are coordinating a small gallery renovation or a large mixed-use cultural center.
Linked Models
Copy/Monitor
Coordination Review Alerts
Resolution Actions
Interference Check vs. Coordination Review
Visual Explanation — The Coordination Review Workflow
The following diagram illustrates the end-to-end conceptual workflow of Coordination Review in Revit. It traces the journey from establishing monitoring relationships through to resolving alerts, showing how information flows between the linked model and the host model.
Notice that the workflow is inherently asynchronous. The structural engineer does not need to notify you directly when they shift a grid line; Revit's monitoring relationship handles that communication automatically upon reloading the linked file. This is particularly valuable in studio-based visual arts programs where team members may be working on different schedules, or in professional settings where the architect and structural engineer occupy different offices entirely. The diagram above emphasizes three distinct phases: setup (establishing monitoring), detection (alerts generated upon reload), and resolution (choosing an action for each alert).
How Coordination Review Works in Practice
Coordination Review is not a mathematically driven tool in the traditional sense — there are no equations to solve. Instead, it operates through a logical mechanism rooted in element identity tracking and parametric comparison. Understanding this mechanism at a conceptual level is critical for using the tool effectively and for communicating coordination issues to project stakeholders.
Step-by-Step Mechanism
Every element in a Revit model has a unique Element ID — an internal identifier that Revit assigns automatically. When you use Copy/Monitor to copy a grid line from a linked structural model into your architectural model, Revit creates a new element in your file but stores a reference back to the original element's ID in the linked file. This ID pairing is the foundation of the monitoring relationship. Each time you reload the linked model, Revit compares the current state of each monitored source element against its last known state. If any parameter has changed — position, name, type, or if the element has been deleted — Revit adds an entry to the coordination review queue.
Types of Changes Detected
| Change Type | Description | Example Scenario |
|---|---|---|
| Moved | The source element's position has shifted in the linked model. | Structural grid line B moved 500mm east; your copied grid B is now out of alignment. |
| Deleted | The source element no longer exists in the linked model. | The engineer removed Level 4 from the structural model; your copy of Level 4 still exists. |
| Type Changed | A parameter or type property of the source element has been altered. | A column type changes from W14×22 to W14×30, affecting clearance dimensions in your gallery layout. |
| New Element | A new element has been added in the linked model that may need monitoring. | A new structural column appears where your design assumes open floor space. |
Alert Resolution — A Detailed Breakdown
Understanding the three resolution actions — Accept, Reject, and Postpone — is the conceptual heart of Coordination Review. Each action has distinct implications for your model and for your team's communication. The diagram below maps the decision logic that guides practitioners through the resolution process.
A common misconception among beginners is that rejecting an alert "fixes" the problem. In reality, rejection simply clears the alert from your queue while leaving the discrepancy between your model and the linked model intact. This means your grid line copy sits at position X while the linked structural grid now sits at position Y — a condition that could lead to construction errors if not formally communicated. In professional practice, the Postpone action is often the most diplomatically responsible choice when you are uncertain, as it preserves the alert for discussion at the next coordination meeting without unilaterally accepting or overriding a change.
Worked Example — Gallery Renovation Project
Imagine you are designing the interior layout for a contemporary art gallery. Your architectural Revit model links to the structural engineer's model, from which you have copied and monitored grid lines A through E and Levels 1 through 3. The engineer has just issued an updated structural model. When you reload the link, Revit generates three coordination review alerts. Here is how you would work through them.
Strengths, Limitations, and Comparisons
Coordination Review is a powerful but narrowly scoped tool. Understanding where it excels and where it falls short helps you build an effective coordination strategy that may incorporate additional tools and workflows.
| Aspect | Strengths | Limitations |
|---|---|---|
| Scope | Tracks changes to specific monitored elements (grids, levels, columns, walls) with precision. | Only monitors elements established via Copy/Monitor; does not detect arbitrary geometric clashes. |
| Automation | Alerts are generated automatically when a linked model is reloaded — no manual checking required. | You must manually reload the link; Revit does not push notifications in real time. |
| Resolution | Provides clear action options (Accept, Reject, Postpone) with descriptive context for each alert. | Rejecting an alert does not notify the other team; external communication is still essential. |
| Integration | Works natively within Revit, requiring no additional software licenses. | For comprehensive clash detection across disciplines (including MEP), Navisworks or BIM 360 Coordinate is often needed. |
| Learning Curve | Conceptually straightforward — three actions, clear alert descriptions. | Setting up Copy/Monitor relationships correctly requires familiarity with shared coordinates and project positioning. |
Connection to Advanced Coordination Workflows
Coordination Review is an entry-level coordination tool within a much larger BIM ecosystem. As projects scale in complexity, teams often layer multiple coordination strategies. Understanding where Coordination Review fits in this hierarchy will help you communicate effectively with engineers, contractors, and project managers who may reference more advanced tools.
| Feature | Coordination Review (Revit) | Navisworks Clash Detection | Autodesk Construction Cloud |
|---|---|---|---|
| What it detects | Changes to monitored elements (position, deletion, parameter shifts) | Hard clashes (geometry intersections), soft clashes (clearance violations), time-based (4D) clashes | Clashes across federated models in a cloud environment, with issue tracking and assignment |
| Data source | Revit linked models only | Any 3D model format (Revit, IFC, DWG, FBX, etc.) | Cloud-hosted Revit models, IFC files, point clouds |
| Best for | Small-to-medium projects; quick parametric checks during design development | Large multi-discipline projects requiring geometric collision analysis | Enterprise-scale projects with distributed teams requiring cloud-based issue management |
| Cost | Included with Revit license | Separate Navisworks license required | Subscription to Autodesk Construction Cloud |
For visual arts students, the practical takeaway is that Coordination Review is the tool you are most likely to encounter first in academic and early professional projects. It provides a manageable introduction to the broader discipline of BIM coordination without requiring additional software. As your projects grow in scope — perhaps into museum design, large-scale installations, or adaptive reuse — you will encounter Navisworks and cloud-based coordination as natural extensions of the same conceptual framework you are learning here.
Practice Problems
Lesson Summary
Coordination Review is Revit's built-in mechanism for tracking and resolving changes to elements that have been established through Copy/Monitor relationships between linked models. When a source element in a linked file is moved, deleted, or parametrically altered, Revit generates an alert upon reloading the link, providing a structured dialog for resolution.
Each alert offers three resolution paths: Accept (synchronize your copy with the source), Reject (keep your version while acknowledging a deliberate discrepancy), or Postpone (defer the decision for team discussion). While Coordination Review does not replace geometric clash detection tools like Interference Check or Navisworks, it provides an essential parametric layer of coordination that helps maintain design intent across disciplines — a capability especially valuable in spatial and exhibition design where visual precision and spatial relationships are paramount.