Skip to content
BIMpedia
Chapter 3 · Lesson 1 of 2Topic: Designing with the model

Design reviews in the model

A design review in the model is only useful if every comment ends up somewhere it can be found, owned and closed. Review against a purpose, capture comments as issues with a viewpoint, and close them in the next model.

3 min read3 quiz questions
Skip to the quiz
  • Watch out
  • What it costs
  • Experienced readers
  • Remember
  • In BIMpedia
Nadiaarchitect and design lead
Even if you do this every day, watch for this: Review purpose. Reviews without a stated purpose turn into general walk-throughs; name the question and invite the people who can answer it.

Design reviews happen on every project: the client, the fire engineer, the contractor, the operator, all looking at the design at a stage gate. In a model they can see far more than on drawings. But a review is only as good as what happens to its comments afterwards.

Story · Forty comments, three answered
How it goes wrong

A stage 3 review walks through the model for two hours with eight people. Forty comments are made; the minutes list "stairs, plant access, door widths discussed". Four weeks later, three have been looked at. At stage 4 the same comments come back, more expensive.

How it goes right

The review has one purpose: maintenance access. The facilities manager and the mechanical engineer are invited. Each comment is saved as a BCF issue with a viewpoint, an owner and a due date. The next model is checked against the list; 37 are closed, three are carried to the next review with a reason.

A review in four steps

Issues travel between tools with BCF
Your BIM toolSolibri, Revizto, Navisworks…
.bcfzipTopics, comments, snapshots
  1. Purpose: one question per review (fire, access, maintenance, cost, buildability).
  2. People: those who can judge it, including the operator and the contractor where they're appointed.
  3. Capture: each comment as an issue with a viewpoint, owner, due date and status.
  4. Close: check the next shared model against the list.
Basics

BCF (BIM Collaboration Format) is an open format for issues: a title, a viewpoint (camera position and the selected elements), comments and a status. Most BIM tools can read and write it, so a comment made in a viewer opens at the same spot in the designer's authoring tool.

Nadiaarchitect and design lead
Your turn. Give it about 10 min and work it out on your own before you open the model answer: that is where it sticks.
Exercise: Turn comments into issues 10 min

From a review walk-through you have these notes: (a) "AHU on roof: how is it replaced?", (b) "nice entrance", (c) "check door widths on level 2 corridor", (d) "riser 3 looks tight for the ductwork". Which become issues, with what owner, and what would the viewpoint show?

Key takeaways

  • Every review has a purpose (fire, access, maintenance, cost) and invites the people who can judge it.
  • Comments become issues: a viewpoint in the model, an owner, a due date, a status.
  • BCF carries issues between software, so comments stay attached to the place in the model.
  • An issue is closed when the next model shows the fix, not when someone says it's done.

Your notes

Related tool

Open a .bcfzip to review topics and snapshots, import them as issues, or export your issue log as BCF.

Open BCF Viewer & Exporter →

Check yourself

3 questions · 2 right to complete
  1. 1. The client's facilities manager joins a stage 3 review. What is the most useful thing to review with them?
  2. 2. During a review someone says 'that stair core looks tight'. What should happen to the comment?
  3. 3. When is a design review issue closed?
0 of 3 answered