Skip to main content
Beech

Your first week in Beech

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

Where to click after you log in, what the four main pages are for, and how to find your own work without learning the whole product at once.

Intent: Explain your first week 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.

Beech is built for architecture studios: drawings with real numbers, a board for the work, sprints for the week, and a Home page that surfaces what needs your attention. You do not need every setting on day one. You need a loop you can repeat.

The four places you will live

  • Home — blocked work, reviews waiting on you, vendors due, and today's work list.
  • Projects — one client job. Open a project for Work, Log, Studio, Vault, Deliverables, and Info.
  • Workspace — your board across every project you can see, including reviews and vendor requests.
  • Schedule — the sprint. Managers plan it; contributors see their assigned sprint work.

More hides Firm board, Activity, Vendors, Library, Reports, Team Hours (Managers and Admins), and Firm settings. On a phone, those four destinations sit in a bottom tab bar.

What to do in the first few days

  1. 1
    Open Home

    Click a summary chip (Blocked, For review, Vendors due) or an item in Today's work. That is usually faster than hunting through Projects.

  2. 2
    Find your tasks in Workspace

    Filter by assignee (you) if the board is busy. Green In-sprint badges are this week's commitment.

  3. 3
    Learn one drawing number

    Press Cmd+K (Mac) or Ctrl+K (Windows) and type a reference like RV01-FLP-005. Search is the fastest way back to a sheet.

The question mark in the top bar opens Help. Guides are short how-tos; Docs is the full reference. Press Cmd+J / Ctrl+J for a private scratchpad and reminders.

If you cannot see a project

Only Admins see every project. Managers and Contributors see projects they are members of (or have work on). Ask a manager to add you on the project's Info tab, and check you accepted the invite with the same email you log in with.

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: Welcome to Beech in the user guide

Related guides: Signup and first login checklist · Troubleshooting Beech workflows · Setting up a project

Next: explore related feature workflows.