Skip to main content
Beech

Setting up a project

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

How to create a client job in Beech: name, code, template, manager, members, and the settings that change how work runs.

Intent: Explain setting up a project 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.

A project is one client engagement — drawings, tasks, vendors, site visits, and studio material all hang off it. Getting the code and membership right on day one saves pain later, because the code becomes part of every drawing number.

Create the project

Admins and Managers click New project and fill in a name, client, short uppercase project code (for example RV01), priority, optional drawing-list template, and a team manager. Keep the code short and unique. It is hard to change once drawings exist.

The project list shows cards with phase, priority, and drawing completion (Approved or Final over the total). Contributors only see projects they are members of or have drawings on.

Five tabs, one job

  • Work — drawings, general tasks, vendor coordination, reviews.
  • Log — site visit MOMs and meeting notes.
  • Studio — canvases, Jot, inspiration links.
  • Vault — project files in the firm storage pool.
  • Info — status, team, site details, and project settings.

Membership and scope

Add contributors from Info → Project actions. Employee scope (also in Info) is Firm-wide by default — anyone in the firm can be assigned — or Project members only, which is better when different teams run different jobs.

If this job does not need a formal internal review before Done, turn off Require drawing reviews in Info → Project settings. Admins and Managers can still move drawings to Done either way.

When the job is over

Archive from Info → Project actions. Archived projects hide from the default list (use Show archived). Only Admins restore. Hand off the team manager from Info when someone else takes the job.

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: Projects in the user guide

Related guides: Signup and first login checklist · Troubleshooting Beech workflows · Your first week in Beech

Next: explore related feature workflows.