Run a Design Review

A practical workflow for assembling evidence, capturing feedback, and carrying decisions into the next revision.

1. Choose the Drawing Mode

Start with a remote drawing when the work must be shared, reviewed in a browser, or edited with live collaborators. Use a local drawing when the project should remain on the current device or must be available offline. A local drawing can be moved to the cloud later with its external files and version history.

Both modes use the same Scopture canvas and .duc project state.


2. State the Review Intent

Open the charter before arranging the review material. Record only the context that determines how the work should be evaluated:

  • the objective and current phase;
  • requirements and their acceptance criteria;
  • hard or soft constraints;
  • responsible stakeholders; and
  • decisions that have already been made.

The charter is the stable project brief. It prevents reviewers from having to reconstruct intent from annotations, messages, or filenames.


3. Assemble the Evidence

Bring only the material needed to understand the review. Scopture can combine 2D geometry and annotations with PDFs, documents, images, links, and engineering models such as IFC, STEP, STL, DXF, and DWG.

Use frames to establish visual sections, plots to define deliberate output regions, layers to control visibility, and blocks for content that should be reused consistently. Keep source artifacts near the references and explanations that qualify them.


4. Inspect in Context

Review the drawing at the level appropriate to the question. The canvas supports measurement, snapping, search, layers, and multiple unit scopes. Model elements can be opened in an interactive viewer for selection, hierarchy inspection, measurement, sectioning, material and display controls, and saved viewpoints.

The canvas view explains how an artifact relates to the project. Model Open mode provides the detailed 3D inspection environment for the artifact itself.


5. Capture Issues at the Source

Create an issue where the question occurs. An issue can point to:

  • a position on the canvas;
  • a particular element and a local position on that element; or
  • a point in a 3D model, including its orientation, model identity, and viewer state.

Give the issue a clear outcome to resolve, then use its thread for evidence, replies, attachments, assignments, followers, and timing. Anchoring the discussion removes ambiguity when the canvas or model is revisited later.


6. Resolve and Preserve

Close or dismiss issues deliberately. When an outcome changes the project direction, record it as a charter decision with its rationale and link the issues that informed it.

Create a named checkpoint before a formal review, handoff, or major revision. Checkpoints preserve complete project states; the version graph also records incremental changes between them. Preview a historical state before restoring it.


7. Share the Right Surface

For remote drawings, grant direct or organization access when participants need an ongoing role. Use a public link for a bounded review, with the appropriate view or edit permission. Public links can also require a password and independently control export, 3D access, and discoverability.

The review is complete when its intent, evidence, unresolved issues, resolved decisions, and accepted state can be understood without reconstructing them from another system.

Last updated on