Skip to main content
Beech

Firm-wide vs project-wide planning

A practical guide for architecture studio workflows in Beech.

All guides

16 August 2026

Updated 16 August 2026 · Beech Product Education Team

One shared studio sprint, or a sprint per project — how to choose, what “one active sprint” means, and how to switch modes safely.

Intent: Explain firm-wide vs project-wide planning 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 does not run both planning modes at once. The whole firm is either planning together, or each project (or team) is planning on its own. New firms default to firm-wide; change it in Firm settings → Scheduling.

Firm-wide

One sprint across every project. Schedule has no project rail — just Past sprints and the firm sprint. Available work is grouped by project, then section. Best for a small studio that staffs as one team.

Project-wide

Each project has its own sprint. The sidebar lists projects, then Past sprints. Click a project to plan that job. Best when different managers own different buildings.

The hard rules

  • One active sprint for the current mode: one firm sprint, or one active sprint per project.
  • A task can only be in one active sprint at a time.
  • To switch modes, complete any active sprint of the other type first.
If you are unsure, start firm-wide. Split to project-wide when two jobs genuinely cannot share a week. The Using sprints guide covers starting, filling, and completing a sprint.

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: Schedule & Sprints in the user guide

Related guides: Using sprints in Beech

Next: explore related feature workflows.