Skip to main content
Beech

Drawing tasks vs general tasks

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

When work should be a numbered drawing and when it should be a TSK — and why only drawings hit the review gate by default.

Intent: Explain drawing tasks vs general tasks 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.

Every drawing in Beech has a linked Kanban task. You can also create standalone general tasks for coordination, site follow-ups, and anything that is not a sheet. Mixing them up is the usual reason someone cannot get to Done, or cannot find a number in search.

Drawing tasks

Created automatically when you add a drawing from + Add work (choose Drawing). They share the drawing's reference (RV01-FLP-005), follow dependencies, and by default cannot be marked Done until an internal review is approved (unless the project turns that off). Revisions, file versions, and the drawing status lifecycle all live here. Review is not a type of work you add — it is a named step on the drawing.

General tasks

Created from + Add work → General, or from a site visit action point or meeting note. They get a TSK reference (RV01-TSK-007). Review is optional — Send for review from the task panel — and is never a gate. You can move a general task to Done at any time.

A simple rule

  • If it is a sheet the client or consultant will see, it is a drawing.
  • If it is a call, a chase, a site snag, or studio admin, it is a general task.
Both types appear on Workspace and can sit in a sprint. Only drawings auto-block from unfinished dependencies and vendor requests.

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: Tasks & Workspace in the user guide

Related guides: How drawing numbers work · Why a drawing is Blocked · Getting a drawing to Done

Next: explore related feature workflows.