16 August 2026
Updated 16 August 2026 · Beech Product Education Team
When a light MTG note is enough, and when the visit needs a full MOM with categories and action statuses.
Intent: Explain meeting notes vs site visits 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.
Log interleaves site visits and meeting notes, most recent first. They look similar in the list and they are not the same tool.
Site visit (MOM)
Use it when the record must stand up later: site inspection, structured minutes, categorised points, photos, attendees with companies. Actions convert cleanly to tasks.
Meeting note
Lighter: client call, internal catch-up, design review that does not need a full MOM. Title, date, meeting type (Client call, Internal, Design review, Site review, Other), names, freeform notes with basic formatting, optional photos. Numbered like MTG-RV01-004.
+ Create task on an expanded note pre-fills the meeting title. Click it more than once if several follow-ups came out of the same call.
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: Site visits & notes in the user guide
Related guides: Deliverables issuance checklist · Site visits and MOMs · Studio vs Log vs Jot