Skip to main content
Beech

Internal review in Beech

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

How to request a review, where reviewers find the work, and what happens when everyone approves — or one person asks for a revision.

Intent: Explain internal review in beech 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.

There is no Reviews item in the top nav. Reviews live on Workspace, Home (For review chip and Today's work), and the project Work tab. Opening one goes to a dedicated page: Approve, Request revision, or Reject.

Send for review

Use Send for review on the task detail panel, or move the Kanban card to In-Review. Reviews are not created from Add work — they are a named step on an existing drawing or general task. The picker lists people allowed by the project's employee scope. Everyone you pick is notified, and the drawing moves to Internal Review. The task panel shows a Review cycle checklist of each reviewer's decision.

How decisions combine

  • All approve — the drawing moves to Approved. The assignee is notified.
  • Anyone requests a revision — Revision Needed at once, regardless of other votes. An orange Revision needed badge appears. Fix the sheet and choose Resubmit for review (previous reviewers are pre-filled).
  • Reject — comments are required; the work must restart or be re-scoped.

Every decision is stored on the drawing and cannot be edited. Open the task panel's Review cycle block for the trail. General tasks can have optional peer review via Send for review, but it never blocks Done.

The old /reviews URL redirects to Workspace. Filter or search by drawing number to find what is waiting on you.

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.

Full reference: Reviews & Approvals in the user guide

Related guides: Drawing tasks vs general tasks · How drawing numbers work · Why a drawing is Blocked

Next: explore related feature workflows.