Autodesk Revit • Coordination and Collaboration

Coordination Review — Use coordination review conceptually (intro)

Understanding how Revit's coordination review tools detect, manage, and resolve conflicts across linked models in collaborative BIM workflows.

A building model with layered plans and dimension marks.
Inside this lesson 10 sections 5 questions 5 figures

SECTION 1

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.

1980s • Early CAD Coordination

Architectural firms begin using 2D CAD software such as AutoCAD. Coordination between disciplines relies on xref overlays — external reference files layered together — but conflict detection remains entirely manual.

2000 • Revit Launches as a BIM Platform

Revit Technology Corporation releases the first version of Revit, introducing parametric building components. The concept of linked models allows multiple discipline-specific files to coexist in a single project environment.

2004 • Autodesk Acquires Revit

Autodesk integrates Revit into its ecosystem, expanding collaboration features. Copy/Monitor and Coordination Review tools appear in subsequent releases, enabling teams to track changes across linked models systematically.

2012–Present • Cloud-Based Collaboration & Clash Detection

Autodesk introduces BIM 360 (now Autodesk Construction Cloud) for cloud-hosted coordination workflows. Coordination Review in Revit works alongside Navisworks clash detection, giving teams a layered system for identifying and resolving conflicts.

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.

SECTION 2

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.

1

Linked Models

In Revit, a linked model is an external Revit file (.rvt) that is referenced inside your host project. It allows teams to work on separate discipline files (architectural, structural, MEP) that come together visually and informationally in each team's view.
2

Copy/Monitor

The Copy/Monitor tool creates a local copy of elements from a linked model (such as levels, grids, columns, or walls) and establishes a monitoring relationship. When the original element changes in the linked file, Revit flags the discrepancy.
3

Coordination Review Alerts

When a monitored element diverges from its source, Revit generates a coordination review alert. Each alert describes the nature of the change — moved, deleted, or parameter-altered — and offers resolution actions.
4

Resolution Actions

For each alert, you can choose to accept the change (update your copy to match), reject it (keep your version), or postpone the decision for later review with the team.
5

Interference Check vs. Coordination Review

While Revit's Interference Check detects geometric clashes (two objects occupying the same space), Coordination Review tracks parametric and positional changes to monitored elements. Both tools complement each other in a robust coordination workflow.
✦

KEY TAKEAWAY

Think of Coordination Review as a change-tracking system similar to "Track Changes" in a word processor. When a collaborator edits a paragraph (an element in the linked model) that your chapter (your host model) references, you receive a notification showing exactly what changed. You then decide whether to incorporate the edit, ignore it, or flag it for a group discussion. In Revit, the "paragraph" might be a structural grid line, and your "chapter" might be the gallery layout that depends on that grid's position.

SECTION 3

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.

Coordination Review WorkflowLINKED MODEL(Structural Engineer's File)Grids, Levels, ColumnsHOST MODEL(Your Architectural File)Copied + Monitored ElementsLINKCOPY / MONITOREstablish monitoringrelationship on elementsCHANGE OCCURSEngineer moves Grid A by 300mmin the linked structural modelRELOADALERT GENERATEDRevit flags mismatch betweenyour copy and the source elementACCEPTUpdate your copyREJECTKeep your versionPOSTPONEDefer to team meetingCOORDINATION REVIEW DIALOGCollaborate → Coordination Review → Use Current Project (lists all pending alerts)Each alert maps to a specific monitored element and describes the change type
The workflow begins at the top left with a linked model. After Copy/Monitor establishes relationships, any change in the linked file triggers an alert when you reload the link. The Coordination Review dialog (bottom) lists all pending alerts, each offering three resolution paths: Accept, Reject, or Postpone.

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).

SECTION 4

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 TypeDescriptionExample Scenario
MovedThe 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.
DeletedThe 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 ChangedA 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 ElementA 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.

Types of changes that trigger Coordination Review alerts

💡

Visual Arts Context

In exhibition or gallery design, even minor shifts in structural grids can cascade into significant spatial changes. A 300mm column shift might push a display wall out of alignment with a lighting track, disrupt a carefully composed sight line, or violate an accessibility clearance requirement. Coordination Review ensures these changes surface before they reach construction.

SECTION 5

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.

Decision Tree for Coordination Review AlertsALERT RECEIVEDIs the linked change correct?YESNOUNSUREACCEPTYour copied element updatesto match the linked source.Alert is cleared.POSTPONEAlert remains in queue.Discuss with the team,then resolve later.REJECTYour copy stays as-is.Alert is cleared, but adiscrepancy now exists.✓ Models are synchronizedDownstream views update⏳ Re-appears next time youopen Coordination Review⚠ Manual reconciliationneeded — communicate reasonBest practice: resolve all alerts promptly; postpone only when team input is required.
This decision tree shows the logic behind resolving each Coordination Review alert. The key question — Is the linked change correct? — branches into three paths. Note that Reject does not revert the linked model; it only maintains your local copy, creating a deliberate discrepancy that must be communicated to the other team.

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.

SECTION 6

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.

Resolving Coordination Review Alerts in a Gallery Project

  1. 1

    Step 1 — Reload the Linked Model

    Navigate to the Manage tab and click Manage Links. In the Revit Links tab, select the structural model file and click Reload. Revit processes the updated file and compares all monitored elements against their source counterparts. A notification appears indicating that coordination review alerts are pending.
  2. 2

    Step 2 — Open the Coordination Review Dialog

    Go to Collaborate → Coordination Review → Use Current Project. A dialog opens listing three alerts: (1) Grid C — Moved, (2) Level 3 — Elevation Changed, (3) Grid E — Deleted. Each alert displays the element category, the element name, and the type of change.
  3. 3

    Step 3 — Evaluate Alert 1: Grid C Moved

    The alert states that Grid C has moved 450mm to the north. You check your floor plan and see that your main gallery partition wall aligns to Grid C. Moving it would shift the wall into the sculpture installation zone. After consulting the structural engineer's updated drawings, you confirm the move is intentional due to a foundation constraint.
    Action: Accept. Your copy of Grid C updates to the new position. You make a note to adjust the partition wall and sculpture placement accordingly.
  4. 4

    Step 4 — Evaluate Alert 2: Level 3 Elevation Changed

    Level 3 (the roof level) has been raised by 600mm. This would increase your upper gallery's ceiling height, which is actually beneficial for hanging large-format works. However, you need to verify that the HVAC team's ductwork model can accommodate the revised height before committing.
    Action: Postpone. The alert remains in the queue. You add this item to the agenda for the next cross-discipline coordination meeting.
  5. 5

    Step 5 — Evaluate Alert 3: Grid E Deleted

    Grid E has been deleted from the structural model. Your model still has a copy of Grid E, and two partition walls reference it. You contact the engineer, who explains that Grid E was redundant and has been consolidated with Grid D. Your partitions do not actually depend on Grid E structurally, so you can safely remove your copy.
    Action: Accept. Your copy of Grid E is flagged for deletion. You manually remove the partition wall references that depended on it and reassign them to Grid D.

SECTION 7

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.

AspectStrengthsLimitations
ScopeTracks changes to specific monitored elements (grids, levels, columns, walls) with precision.Only monitors elements established via Copy/Monitor; does not detect arbitrary geometric clashes.
AutomationAlerts 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.
ResolutionProvides 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.
IntegrationWorks 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 CurveConceptually straightforward — three actions, clear alert descriptions.Setting up Copy/Monitor relationships correctly requires familiarity with shared coordinates and project positioning.

Strengths and limitations of Coordination Review in Revit

✦

KEY TAKEAWAY

Coordination Review is like a curator's condition report for a traveling exhibition. When artworks arrive from another institution (the linked model), you inspect each piece (element) against the original loan agreement (the monitoring relationship). If something has changed — a frame has been replaced, dimensions differ — you decide whether to accept the change, flag it for the lending institution, or hold off until you can discuss it. But you would not rely on the condition report alone to verify that the gallery layout has no spatial conflicts; for that, you need a physical walkthrough (Interference Check or Navisworks). Both processes serve coordination, but at different levels.

SECTION 8

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.

FeatureCoordination Review (Revit)Navisworks Clash DetectionAutodesk Construction Cloud
What it detectsChanges to monitored elements (position, deletion, parameter shifts)Hard clashes (geometry intersections), soft clashes (clearance violations), time-based (4D) clashesClashes across federated models in a cloud environment, with issue tracking and assignment
Data sourceRevit linked models onlyAny 3D model format (Revit, IFC, DWG, FBX, etc.)Cloud-hosted Revit models, IFC files, point clouds
Best forSmall-to-medium projects; quick parametric checks during design developmentLarge multi-discipline projects requiring geometric collision analysisEnterprise-scale projects with distributed teams requiring cloud-based issue management
CostIncluded with Revit licenseSeparate Navisworks license requiredSubscription to Autodesk Construction Cloud

Coordination Review compared with advanced coordination tools

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.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

Explain the difference between Coordination Review and Interference Check in Revit. Why might a project team need both tools simultaneously?
Show answer
Coordination Review monitors parametric and positional changes to specific elements that have been established through a Copy/Monitor relationship between linked models. It detects when a source element is moved, deleted, or altered. Interference Check, by contrast, detects geometric collisions — situations where two physical objects occupy the same space (for example, a duct passing through a beam). A team needs both because Coordination Review catches design-intent changes that may not cause physical overlaps, while Interference Check catches spatial conflicts that may arise independently of monitored relationships. Together, they provide both parametric and geometric layers of coordination.

Question 2: BASIC CALCULATION

You have Copy/Monitored 5 grid lines and 3 levels from a structural model. The structural engineer updates their model: 2 grid lines are moved, 1 level is deleted, and 1 grid line is renamed. How many Coordination Review alerts will Revit generate when you reload the link?
Show answer
Revit will generate 4 alerts. Each change to a monitored element produces one alert: 2 alerts for the moved grid lines, 1 alert for the deleted level, and 1 alert for the renamed grid line (parameter change). The remaining 2 grid lines and 2 levels that were not modified will not trigger alerts. The total count is straightforward: every monitored element that changes relative to its last known state generates exactly one alert entry in the Coordination Review dialog.

Question 3: INTERMEDIATE

You are designing an exhibition space and have accepted a Coordination Review alert that moved Grid B by 600mm to the east. After accepting, you realize that three partition walls in your model were constrained to Grid B. Describe the downstream effects in your model and the steps you should take to verify that the design remains intact.
Show answer
When you accept the alert, your local copy of Grid B shifts 600mm east. Any partition walls that were dimensionally constrained or aligned to Grid B will attempt to move with it, depending on how their constraints were set up. If walls were locked to the grid, they move automatically — which could create unintended spatial consequences such as reduced circulation width, misalignment with lighting tracks, or encroachment on adjacent gallery zones. To verify, you should: (1) open relevant floor plan views and check wall positions, (2) review any dimensions or constraints that reference Grid B, (3) verify that accessibility clearances (typically 900mm minimum for wheelchair passage) are still maintained, and (4) check section views to confirm floor-to-ceiling elements still align properly. If any issues are found, you adjust the dependent elements manually.

Question 4: APPLIED

You are collaborating on a museum project with separate architectural, structural, and MEP Revit models. The MEP engineer adds a large mechanical shaft that requires a structural opening, but the structural engineer has not yet updated their model. Your architectural model has Copy/Monitored elements from the structural model only. Will Coordination Review alert you to the new mechanical shaft? If not, what coordination strategy would you recommend to catch this issue?
Show answer
No, Coordination Review will not alert you to the new mechanical shaft. The tool only monitors elements that have been established through a Copy/Monitor relationship with a linked model. Since the shaft exists in the MEP model and you monitor elements from the structural model, there is no monitoring relationship that would detect this change. Furthermore, even if the structural model eventually adds an opening, Coordination Review would only flag it if you had specifically copied and monitored that opening element. To catch this type of cross-discipline issue, the team should implement either Revit's Interference Check between the MEP and structural links, use Navisworks for comprehensive clash detection across all three models, or establish a regular coordination meeting where teams visually overlay all models and review new elements. A layered approach — Coordination Review for tracked elements, Interference Check for geometric overlaps, and periodic visual reviews — provides the most robust coverage.

Question 5: CRITICAL THINKING

Consider a scenario where a team member consistently uses "Reject" on Coordination Review alerts without communicating the rejections to the linked model's author. Analyze the risks this practice introduces to the project, and propose a protocol that uses all three resolution actions (Accept, Reject, Postpone) in a way that maintains model integrity and team communication.
Show answer
Systematically rejecting alerts without communication creates a dangerous divergence between models. The host model retains outdated element positions or properties while the linked model reflects the latest design intent, meaning that construction documents generated from each model will contradict each other. For instance, the architectural drawings might show a column at one location while structural drawings show it 500mm away — a discrepancy that could lead to rework costing tens of thousands of dollars on site. A responsible protocol would designate Accept as the default action when the change is verified and beneficial, Reject as an action reserved for situations where formal written communication (such as an RFI or design change request) accompanies the rejection and documents the reason, and Postpone as the action for any ambiguous change, with the requirement that all postponed items are reviewed within a defined time frame (e.g., at weekly coordination meetings). The protocol should also require that rejected alerts be logged in a shared coordination tracker — a spreadsheet or issue management platform — so that both teams have visibility into unresolved discrepancies. This transforms Coordination Review from a unilateral tool into a bilateral communication framework.

SUMMARY

Lesson Summary

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.

Varsity Tutors • Autodesk Revit • Coordination Review — Use coordination review conceptually (intro)