Skip to main content
Beech

Workspace vs Schedule vs Home

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

Three pages, one loop: Home surfaces attention, Schedule commits the week, Workspace is where status actually moves.

Intent: Explain workspace vs schedule vs home 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.

New teams bounce between the same three screens and wonder which one is “the work.” They are not competitors. Home is attention, Schedule is the commitment, Workspace is execution.

Home

Read-only command centre. Chips for Blocked, For review, and Vendors due (plus Hours for non-Admins). A sprint banner if one is running. A single Today's work list. Admins also see a Team hours card. Click through to act — you do not change status on Home.

Schedule

Plan the sprint: start it, pull from Available work, return a row, complete it when the window ends. Contributors see assigned sprint tasks only. Nothing here replaces the Kanban columns.

Workspace

The board. Move To-Do → In Progress → In Review → Done (plus Blocked and On Hold when work is waiting or paused). In-sprint work wears a green badge. Filter unscheduled work if you are hunting leftovers. Reviews and vendor requests sit on this board too.

Morning: Home. Planning meeting: Schedule. The rest of the day: Workspace. If a sheet is “in the sprint” but still To-Do, that is expected — membership is not progress.

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

Related guides: Logging time · Using Home as the command centre · Quick capture: notes and reminders

Next: explore related feature workflows.