16 August 2026
Updated 16 August 2026 · Beech Product Education Team
How to start from a template, use mentions and live work links, and let Jot auto-save while you think on the project.
Intent: Explain writing in 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.
Jot is the wide document editor on a project's Studio tab. Open a new jot and you are in the editor immediately — title, optional emoji and cover, then the page.
Start faster
Empty documents offer template chips (Design concept, Site and context, Material and finish, Client brief) and an All templates gallery. Pick one if you do not want a blank page.
What the editor can do
- Headings, tables, and checklists.
- @mentions for people on the firm.
- Live references to work items so the jot stays tied to drawings and tasks.
- Embeds of Vault files so the reference image sits in the prose.
Jots auto-save. Download as plain text if you need a copy outside Beech.
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