16 August 2026
Updated 16 August 2026 · Beech Product Education Team
Three places project writing can live — operational record, design documents, and visual reference — so minutes do not end up in a jot.
Intent: Explain studio vs log vs jot 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.
Teams lose files when every document type lands in one pile. Beech splits the job: Log is what happened, Jot is how you are thinking, Studio is the visual wall, and Vault holds the project files.
Log
Site visit MOMs and meeting notes. Chronological, numbered, attendee lists, actions that become tasks. Operational and defensible.
Jot (inside Studio)
Named documents: concept notes, material schedules, client briefs, issue notes. Headings, tables, checklists, @mentions, live work-item references, file embeds. Not minutes.
The rest of Studio
Freeform canvases and inspiration links. Contributors can view; only Admins and Managers add, edit, or delete Studio content. Project PDFs, CAD, and folders live on the Vault tab.
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: Studio in the user guide
Related guides: Deliverables issuance checklist · Site visits and MOMs · Meeting notes vs site visits