16 August 2026
Updated 16 August 2026 · Beech Product Education Team
The default Intake-to-Completed catalog, how to rename or add statuses, and who moves a project along.
Intent: Explain project statuses your firm actually uses 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.
Project status is the job's chapter, not the drawing's. The team manager or an Admin moves it by hand. Your firm can rename, archive, or add statuses in Firm settings → Project status labels. At least one status must stay active. Keys stay fixed; display names are what people see.
The defaults
- Intake — brief in, team not assigned.
- Design — concept and presentation drawings.
- Client Revision — feedback rounds.
- Confirmed — client signed off; work in earnest.
- Sanction — permits and authority sets.
- Construction — construction drawings and structure.
- Parallel — MEP (and similar) running alongside.
- Closing — snags and site coordination.
- Completed — closed.
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
- 1Troubleshooting step 1
If a control is missing, verify your role has permission for the action.
- 2Troubleshooting step 2
If results look wrong, check filters and refresh to confirm latest synced data.
Full reference: Projects in the user guide
Related guides: Roles and permissions playbook · Security controls for admins · Exporting data for audit or handover