Autodesk Revit Quiz: Coordination Review
10 questions · exam conditions
0:00
Coordination ReviewQuestion 1 of 10

After an architectural link is reloaded, Revit reports that a monitored grid has moved. The project team also suspects that several ducts physically intersect structural beams.

Which use of Coordination Review is appropriate in this situation?

Use it to evaluate the monitored grid change, but use Interference Check for the duct-beam intersections.
Use it to evaluate both the monitored grid movement and all physical duct-beam intersections.
Use it only for the duct-beam intersections because monitored grid movement is handled by Reload Latest.
Use it only after binding both linked models so that every element becomes native geometry.
← Back to quizzes

Autodesk Revit Quiz

Autodesk Revit Quiz: Coordination Review

Practice Coordination Review in Autodesk Revit with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Coordination Review, giving you a quick way to practice the rules, question types, and explanations that matter most for Autodesk Revit.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

After an architectural link is reloaded, Revit reports that a monitored grid has moved. The project team also suspects that several ducts physically intersect structural beams.

Which use of Coordination Review is appropriate in this situation?

  1. Use it to evaluate the monitored grid change, but use Interference Check for the duct-beam intersections. (correct answer)
  2. Use it to evaluate both the monitored grid movement and all physical duct-beam intersections.
  3. Use it only for the duct-beam intersections because monitored grid movement is handled by Reload Latest.
  4. Use it only after binding both linked models so that every element becomes native geometry.
Explanation: When working with linked models in Revit, it's essential to know which tool handles which type of coordination problem. Two tools often cause confusion: Coordination Review and Interference Check — and this question tests whether you know the boundary between them. Coordination Review is specifically designed to manage monitored elements — elements in a linked model that Revit is actively "watching" for changes. When an architectural link is reloaded and a monitored grid has shifted, Coordination Review is exactly the right tool. It surfaces that change, lets you review it, and allows you to accept, reject, or postpone action. This makes A the correct answer for the first half of the scenario. For the duct-beam intersections, however, Coordination Review is the wrong tool. Those ducts and beams are not in a monitoring relationship — they simply happen to physically overlap in 3D space. That type of conflict is precisely what Interference Check (found under Collaborate → Interference Check) is built to detect. It scans geometry for real physical clashes between selected categories across models. B is wrong because Coordination Review cannot detect arbitrary geometric intersections — it only tracks monitored element changes, not spatial conflicts. C flips the logic entirely, misidentifying which tool handles monitored elements; "Reload Latest" is just how you refresh the link, not how you review changes. D introduces a false requirement — binding linked models is never a prerequisite for running either Coordination Review or Interference Check. A helpful rule of thumb: Monitored = Coordination Review; Physical clash = Interference Check. Keep that distinction sharp and these questions become straightforward.

Question 2

Two monitored grids were originally aligned. During design development, the structural engineer intentionally offsets the structural grid from the linked architectural grid. Both teams approve the offset, but they want Revit to continue reporting any later changes to the monitored pair.

Which action should be applied to the current Coordination Review issue?

  1. Choose Accept Difference to approve the present offset and reset the monitored relationship at its current state. (correct answer)
  2. Choose Modify to preserve the offset while forcing both grids to share the original location.
  3. Choose Postpone to approve the offset permanently while suppressing later coordination messages.
  4. Choose Reject to record that the offset is incorrect and prompt the architect to restore the original grid location.
Explanation: When working with Coordination Review in Revit, the key is understanding what each action does to the monitored relationship — not just to the geometry. The question hinges on one specific need: approve the current offset, but keep monitoring active for future changes. Accept Difference, choice A, is exactly designed for this scenario. It tells Revit: "acknowledge this deviation as intentional and accepted," resets the baseline of the monitored pair to its current state, and — critically — keeps the monitor relationship alive. Any future movement of either grid will trigger a new Coordination Review alert. This is precisely what both teams want. Choice B describes something Revit's Coordination Review cannot do — it does not force two elements to share a location while preserving an offset. That's a contradiction, and no such "Modify" behavior works this way in practice. Modify allows you to make a corrective change, not freeze two grids at different positions. Choice C is the most tempting distractor. Postpone sounds like a temporary approval, but it actually just defers the issue without resolving it — the alert remains open and unresolved. It does not permanently accept the offset, and it does not suppress future messages cleanly. It simply kicks the decision down the road. Choice D, Reject, signals that the change is wrong and needs correction. Choosing it here would misrepresent the teams' agreement and prompt unnecessary rework. A useful memory anchor: Accept Difference = approve + keep watching. Whenever a question describes an intentional deviation that still needs future monitoring, Accept Difference is almost always the right tool.

Question 3

A BIM coordinator reviews several Copy/Monitor issues and must send the design leads a record of the findings. The coordinator does not want the act of documenting the issues to move, delete, or approve any model elements.

Which approach best satisfies this requirement?

  1. Apply Accept Difference to each review item because report creation requires every issue to be resolved.
  2. Apply Modify to each review item and export the resulting element locations as a coordination report.
  3. Add comments to the review items and save or create a Coordination Review report for distribution. (correct answer)
  4. Bind the coordinated link and export the resulting groups as the formal review record.
Explanation: When working with Coordination Review in Revit, the key distinction to keep in mind is between reviewing issues and resolving them. The question specifically asks for an approach that documents findings without altering, moving, or approving any model elements — so you need a read-only, non-destructive workflow. Adding comments to review items and generating a Coordination Review report (C) is exactly that. You can annotate each issue with notes for the design leads and then save or print the report, all without touching the status of any monitored element. The elements remain unresolved and unchanged in the model, which is precisely what the coordinator needs. Choice A is a trap because Accept Difference is an action that resolves a discrepancy — it tells Revit "this difference is intentional, stop flagging it." Using it just to generate a report would permanently change the status of those issues, which violates the coordinator's requirement. Choice B is similarly problematic: Modify is a resolution action that updates element parameters or positions to bring them into alignment. Applying it for documentation purposes would actually alter model elements, the opposite of what's needed. Choice D introduces Binding a linked model, which converts the link into groups within the host model. This is a major, irreversible workflow change that has nothing to do with Coordination Review reporting and would significantly disrupt the project structure. As a study tip, remember that Revit's Coordination Review offers three resolution actions — Accept Difference, Reject, and Modify — each of which changes the issue's state. If a question asks for passive documentation without resolution, those actions are disqualifiers.

Question 4

A structural grid and an architectural grid were copied and monitored during early design. The teams now approve different permanent grid systems and do not want Revit to report future changes between this particular pair.

After resolving any current coordination issue, what should the user do to meet the long-term requirement?

  1. Choose Accept Difference once, because that permanently disables monitoring for the selected element pair.
  2. Use Copy/Monitor to stop monitoring the pair, because accepting the present difference does not end future monitoring. (correct answer)
  3. Choose Postpone repeatedly, because postponed issues suppress all later movement warnings for the pair.
  4. Choose Reject once, because rejection removes the Copy/Monitor relationship from both project files.
Explanation: Whenever you see a question about Copy/Monitor in Revit, think about two separate actions: resolving a current conflict and managing the ongoing monitoring relationship. These are not the same thing, and the exam loves to test whether you understand the difference. The key insight here is that Accept Difference is a one-time resolution tool — it tells Revit "I acknowledge this discrepancy right now," but it leaves the Copy/Monitor relationship fully intact. That means Revit will continue watching both elements and will flag any future changes between them. If the teams have permanently diverged and simply don't want this pair monitored anymore, accepting the difference does nothing to achieve that goal long-term. The correct approach, answer B, is to use the Copy/Monitor workflow to explicitly stop monitoring the pair. This severs the relationship entirely, so Revit will never again report coordination warnings between those two elements — which is exactly what the scenario requires. Answer A is the most tempting distractor because Accept Difference sounds permanent. It isn't — it clears the current warning but keeps monitoring active for future changes. Answer C is wrong because Postpone simply defers the warning to a later session; it does not suppress future movement alerts and will resurface every time you run Coordination Review. Answer D is wrong because Reject does not remove the Copy/Monitor link — it signals disagreement with a proposed change and keeps the relationship alive. Your study tip: memorize this distinction — Accept Difference resolves now, Stop Monitoring resolves forever. Any question asking about permanent or long-term removal of monitoring points to stopping the Copy/Monitor relationship, not just clearing the current alert.

Question 5

A monitored architectural grid was moved in the linked model. During review, the structural team determines that the move conflicts with an approved structural layout and believes the architect should reverse or revise the linked-model change.

Which Coordination Review response most accurately records the structural team's decision?

  1. Choose Postpone so Revit sends an automatic revision request to the owner of the architectural model.
  2. Choose Modify so Revit moves the grid in the architectural link back to its approved location.
  3. Choose Accept Difference so Revit marks the architectural movement as incorrect but leaves it visible.
  4. Choose Reject and communicate the reason, without expecting Revit to edit the linked architectural file automatically. (correct answer)
Explanation: When working with Coordination Review in Revit, it helps to understand what the tool actually does versus what it only records. Coordination Review tracks discrepancies between a host model and a monitored linked model — but it cannot directly edit the linked file. The linked model belongs to another discipline's project file, and Revit respects that boundary. When the structural team selects Reject, they are formally logging their disagreement with the architectural change and signaling that the architect needs to reverse or revise it. Revit marks the action in the coordination report, but the actual fix must happen in the architectural model by the architect. That's why D is correct — it accurately reflects both what the tool records and what communication must happen outside of Revit. A is wrong because Postpone simply defers the decision for a later review session; it does not send any automatic notification or revision request to anyone. Revit has no built-in messaging system that contacts the architectural team. B is wrong because Revit cannot use the Coordination Review workflow to move elements in a linked file. The Modify option refers to adjusting the host model's monitored element, not reaching into the linked model to undo the architect's change. C is wrong because Accept Difference does the opposite of flagging a problem — it tells Revit to stop tracking the discrepancy and treat the new position as acceptable. Choosing it would effectively approve the architectural move, not mark it as incorrect. A useful rule of thumb: Coordination Review is a communication and tracking tool, not a cross-model editing tool. Any actual geometry changes must be made by the team that owns that file.

Question 6

A structural model contains levels copied and monitored from a linked architectural model. The architect moves one monitored level and sends an updated RVT file. The structural model currently has the previous version of the link loaded.

Which workflow should the structural user follow to evaluate the level change through Coordination Review?

  1. Reload the architectural link, start Coordination Review, and select that link as the review source. (correct answer)
  2. Start Coordination Review before reloading, then select the structural model as the review source.
  3. Run Interference Check against the old link, then reload the architectural model after resolving clashes.
  4. Bind the architectural link into the structural model, then review the resulting model groups.
Explanation: Whenever you see a question about monitoring linked files in Revit, think about the order of operations: you cannot review changes you haven't yet received. The Copy/Monitor and Coordination Review workflow exists specifically to flag discrepancies between your model and a linked file after that link is updated. The correct path — choice A — follows this logic precisely. First, you reload the architectural link so Revit can detect that the monitored level has moved relative to your structural copy. Only after reloading does Revit have the data to flag a discrepancy. You then launch Coordination Review and select the architectural link as the review source, which surfaces the level change as an action item you can accept, reject, or postpone. Choice B reverses the required sequence. Starting Coordination Review before reloading means Revit compares your model against the old version of the link — no change is registered, so nothing appears to review. Selecting the structural model as the source is also incorrect; the source should be the linked file where the change originated. Choice C confuses two separate tools. Interference Check identifies geometric clashes between elements in 3D space — it has no awareness of Copy/Monitor relationships or level elevation changes. Running it against an outdated link compounds the error. Choice D — binding the link — permanently merges the architectural geometry into the structural model as model groups, eliminating the live link entirely. This destroys the collaborative workflow and provides no coordination review mechanism. Study tip: On Revit exam questions involving Copy/Monitor, always ask yourself: Has the updated data been loaded yet? The link must be current before Coordination Review can surface any discrepancies.

Question 7

The architectural team adds a new level to its model after the MEP team established Copy/Monitor relationships for the existing levels. The new level has never been copied or monitored in the MEP model.

Which expectation about Coordination Review is most accurate?

  1. It automatically creates a corresponding MEP level each time the architectural link is reloaded and a review is started.
  2. It should not be relied on as proof that every new unmonitored level has been incorporated into the MEP model. (correct answer)
  3. It treats any newly added linked level as a resolved issue, because no earlier host-model elevation exists for comparison.
  4. It converts the new linked level into a monitored host level as soon as any other existing coordination issue is accepted.
Explanation: When working with Copy/Monitor and Coordination Review in Revit, it's important to understand what these tools actually detect versus what they automate. Coordination Review flags changes to elements that are already part of an established monitoring relationship — it compares the current state of a monitored element against its linked counterpart. It does not scan for entirely new elements that were never part of that relationship. This is why B is correct. If the architectural team adds a brand-new level after the MEP team set up Copy/Monitor, that level has no monitoring relationship in the MEP model. Coordination Review will never raise a flag about it, because there's nothing to compare. The MEP team could reload the architectural link repeatedly and run Coordination Review without ever being alerted to the new level's existence. Relying solely on Coordination Review as a completeness check would give you a false sense of security. A is incorrect because Coordination Review is not an automation tool — it does not create new MEP levels on reload. Manual action is always required to copy and monitor new elements. C is wrong because Coordination Review doesn't treat unmonitored elements as "resolved"; they simply fall outside its scope entirely and generate no notification at all. D is incorrect because accepting other coordination issues has no effect on unmonitored elements — there is no mechanism that converts a new linked level into a monitored host level passively. As a study tip, remember that Copy/Monitor and Coordination Review only work on established pairs. Any element added to the linked model after the monitoring relationship is set up requires a fresh, manual Copy/Monitor action — it won't be caught automatically.

Question 8

A coordination issue indicates that a monitored column moved in the linked structural model. The architectural team cannot decide whether its corresponding column should move until the structural engineer confirms the change.

What is the most appropriate immediate action in Coordination Review?

  1. Choose Reject, because uncertainty alone means the linked-model change has been determined to be incorrect.
  2. Choose Accept Difference, because any unresolved change can be reconsidered automatically during the next review.
  3. Choose Modify, then undo the column movement if the structural engineer later rejects the change.
  4. Choose Postpone, add a comment if needed, and leave the issue available for a later decision. (correct answer)
Explanation: When working with Coordination Review in Revit, the key concept to keep in mind is that each action — Accept, Reject, Postpone, or Modify — carries a specific meaning and has real consequences for your model and your team's workflow. Questions like this test whether you understand that Coordination Review is a decision-making tool, not just a notification system, and that unresolved decisions should be handled deliberately. Postpone is the correct choice here (D) because the architectural team genuinely cannot make an informed decision yet. Postponing preserves the flagged issue in Coordination Review without dismissing it or acting prematurely. You can attach a comment to document the pending confirmation, and the issue remains visible for follow-up once the structural engineer responds. A is wrong because Reject means you are actively asserting that the linked change is incorrect and should not be incorporated. That is a substantive determination — not an appropriate response to simple uncertainty. Using Reject as a placeholder misrepresents your intent and could mislead collaborators. B is wrong because Accept Difference tells Revit to treat the current discrepancy as resolved — the two elements are now "officially" different, and Revit stops flagging it. There is no automatic reconsideration; you would have to re-establish monitoring to catch the issue again. This option effectively hides the problem rather than deferring it. C is wrong because Modify means you are moving your architectural column now to match the structural change. If the engineer later reverses course, you have made an unnecessary model change that must be manually undone — creating rework and potential coordination errors. Study tip: Remember that Postpone is your "hold" button in Coordination Review — it signals "we know about this, but we're not ready to decide." Never Reject or Accept just to clear the queue.

Question 9

A level copied and monitored into an MEP model is at the old elevation. The corresponding level in the linked architectural model was intentionally raised, and the MEP team has confirmed that its copied level must match the new architectural elevation.

Which Coordination Review action best implements the confirmed decision?

  1. Choose Modify so the MEP level is changed to match the corresponding architectural level. (correct answer)
  2. Choose Accept Difference so the MEP level remains at its existing elevation without modification.
  3. Choose Reject so the architectural level is automatically restored to its previous elevation.
  4. Choose Postpone so Revit temporarily moves the MEP level but retains the open warning.
Explanation: When working with linked models in Revit, the Coordination Review tool monitors changes between a host model and its linked files. The key to answering this type of question is understanding what each action actually does to the elements involved — not just what the names suggest. When an architectural team intentionally raises a level and the MEP team has confirmed they want their copied level updated to match, the correct workflow is to select Modify (Answer A). This action tells Revit to apply the detected change — updating the MEP level's elevation to align with the new architectural value. It resolves the discrepancy by synchronizing the two models, which is exactly what the confirmed decision requires. Answer B, Accept Difference, does the opposite: it acknowledges the mismatch and leaves the MEP level at its current elevation, essentially telling Revit "we know they differ, and that's intentional." This would be appropriate if the MEP team wanted to deliberately maintain a different elevation — not the scenario described. Answer C, Reject, is a common trap. It does not force the architectural model to revert. Revit cannot push changes back into a linked file through Coordination Review. Reject simply dismisses the alert without applying any change to the MEP model. Answer D, Postpone, defers the decision and keeps the warning active for future review — it neither moves the MEP level nor resolves anything permanently. A useful rule of thumb: Modify = apply the change, Accept Difference = keep the gap, Postpone = decide later. Memorizing these three distinct outcomes will help you navigate Coordination Review questions quickly on the exam.

Question 10

An MEP model contains copied and monitored levels from an architectural link and copied and monitored grids from a structural link. Both links have recently been reloaded, but the user needs to review only issues originating from the structural model.

How should the user limit the Coordination Review to the relevant source?

  1. Unload the architectural link, then select the MEP host model as the source of all structural issues.
  2. Select one structural grid first, then review every linked model associated with that element category.
  3. Start Coordination Review and select the structural link whose monitored relationships need evaluation. (correct answer)
  4. Run Coordination Review on the architectural link because link selection filters by host-model discipline.
Explanation: Whenever you see a question about Coordination Review in Revit, focus on how the tool is scoped: Coordination Review is always initiated against a specific linked file, and that selection determines which monitored relationships are surfaced for review. It doesn't operate globally across all links at once. When you launch Coordination Review (Collaborate tab → Coordinate panel → Coordination Review), Revit prompts you to choose a linked model. Selecting the structural link tells Revit to evaluate only the monitored elements copied from that specific file — in this case, the structural grids. This is exactly what answer C describes, and it's the correct, built-in workflow for isolating issues by source. Answer A is wrong because unloading the architectural link is a disruptive workaround that affects the entire project environment and could break other workflows. It's also unnecessary — Coordination Review's link-selection prompt already handles this filtering. Answer B misrepresents how Coordination Review works; you don't pre-select individual elements to scope the review. The tool works at the linked-file level, not the element level. Answer D is incorrect because selecting the architectural link would surface issues from the architectural model, not the structural one. Discipline doesn't automatically reroute which link is being reviewed — the link you explicitly choose determines the scope. The key study tip here: Coordination Review = choose your link, then review. On the exam, watch for distractors that suggest element-level filtering or workarounds like unloading links. The correct answer almost always reflects Revit's actual dialog-driven workflow.