Skip to main content

Getting a drawing to Done

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

Why drawing tasks wait on an approved review, when a manager can override, and how to turn the gate off for a project.

Intent: Explain getting a drawing to done in a way that a new team member can follow without prior Beech context.

Who this helps: Architecture studio admins, managers, and contributors who need a repeatable operational workflow.

By default a drawing cannot sit in Done until internal review has approved it. That is the studio gate before a sheet goes to a client or vendor. General tasks skip this — they can be Done whenever the work is finished.

The usual path

  1. 1
    Finish the sheet

    Move the task through To-Do and In-Progress. Attach the file from the task panel if you keep versions in Beech.

  2. 2
    Send for review

    From the task panel, or by moving the card to In-Review. Pick one or more reviewers. Confirm with Send for review.

  3. 3
    Wait for Approved

    When every reviewer approves, the drawing can reach Approved and the task can go to Done.

If you do not use formal review

Turn off Require drawing reviews in the project Info tab. Drawings can then be moved to Done directly. Admins and Managers can always move a drawing to Done, even when the gate is on.

A revision request from any reviewer sends the drawing to Revision Needed immediately, even if someone else already approved. The drawing shows an orange Revision needed badge. Choose Resubmit for review to start a new cycle — previous reviewers are pre-filled.

Prerequisites

  • Confirm you can access the project and the page referenced in this workflow.
  • Collect any drawing references, due dates, and ownership details before you start.

Expected outcome

By the end of this workflow, your team has one visible, repeatable process and cleaner handovers.

Common mistakes and prevention

  • Mistake 1: Skipping context fields (owner, due date, status notes), which makes follow-up harder.

  • Mistake 2: Treating chat updates as source of truth instead of recording the update in Beech.

Troubleshooting checklist

  1. 1
    Troubleshooting step 1

    If a control is missing, verify your role has permission for the action.

  2. 2
    Troubleshooting step 2

    If results look wrong, check filters and refresh to confirm latest synced data.