Meeting Projects: File the Client Call, Then Record
Hero photo by cgreiter on Unsplash
Meeting projects group calls, notes, and follow-up on one client or one piece of work in Vemoir. You create a project, name it, assign a client or group, add a short description, and pick an icon. In the menu bar you select that project before you record, so the meeting is filed there from the first second.
If you forget, the call can land in Local Recordings. Drag it into a project later. Filing first is calmer because the project glossary and context are in scope while the record is built.
What a meeting project holds
A project contains date-grouped meetings, generated records, actions, decisions, documents, exports, and project context. The dashboard shows a recap, open work, recent decisions, pinned documents, and recent meetings. Search inside the project covers meetings, transcripts, artifacts, actions, and decisions on the Mac.
- StorageOn this Mac
Nothing uploads because you named a client.
- GlossaryPer project
Terms do not leak across clients.
- DeletePermanent
Removes meetings and folders here.
Edits to actions at project level change the same records you see on the meeting. A task does not fork because you opened it from the client page. New project-level actions and decisions attach to a source meeting you pick.
Archive, restore, and delete exist for projects and meetings with local cleanup. Deleting a project removes its meetings, transcripts, generated records, actions, decisions, speaker data in scope, and recording folders. Export anything you still need before you confirm.
File the call before you record
- Create
One project per client or workstream, with the name you want on the dashboard.
- Prepare
Add glossary terms and, if you use Notes, set the export folder in the project.
- Select
Choose the project in the menu bar recorder, then start capture.
- Review
Open the project dashboard for recap and open work across meetings.
Microphone and system audio remain the two local tracks. The project only decides where the meeting is filed. Imported files use the same local pipeline as a live recording. A file is not split into mic and system audio unless it already was.
What a project is not
It is not a shared team workspace. Colleagues do not see your project by signing in. It is not a cloud folder. Voice profiles, if you opt in, stay on the Mac and can be deleted in Privacy settings. Unknown speakers stay anonymous until you remember them.
It is not a substitute for the meeting vendor’s official recording. If the client requires Teams or Zoom’s archive, use that control as well. Vemoir is your local record with no bot in the participant list.
Browser tools have no projects. /tools/transcribe-recording turns a short file into text after the call, up to 15 minutes, three successful runs a week, with no speaker labels. Ongoing client work belongs in the Mac app.
One client, one or two projects
Use one project when one name on the invoice matches one glossary and one Notes folder. Open a second project for the same customer when the mandate, spelling rules, or export destination truly differ, for example client work versus an internal retrospective.
A project name only you understand becomes a problem in six months. Use the name that matches billing. Two mandates with different spellings for the same company are two projects, not two glossaries fighting in one pile.
Where leaving calls unfiled is better
Meeting projects fit when you will have more than one call with the same client and you want glossary, actions, and documents in one place. Local Recordings is enough for a single call you will export and forget. A project you never open is clutter, and deleting a project takes its meetings with it.
Several people editing one task list in a browser need the cloud workspace they already pay for. You can still keep audio on the Mac and paste the minutes you choose to share.
Before you delete a project to clean up, export notes you must keep, including an Apple Notes folder if that is your archive.
Ask Vemoir can scope to one meeting, one project, or the active library. Ask from a project starts a scoped conversation. Archived projects are excluded. That helps when the question is what this client decided, less when you wanted every meeting on the Mac including archived ones.
Archive versus delete
Archiving hides a project or individual meetings from the active dashboard and from Ask’s default scope. Files stay on the Mac until you delete them or remove the whole project. That helps when a mandate is quiet but you want recordings for a later review.
Delete is permanent on this device. If you are unsure, export minutes first or use export to Apple Notes, then archive. Many teams archive closed years and delete only when the client no longer wants a local copy.
A week of calls on one client
Monday you create Northwind and set the client name. You add three glossary terms before the kickoff and select Northwind in the menu bar. The recording files there. Wednesday you join from a different meeting app. The project is the same because filing does not depend on Teams versus Meet. You type two manual notes during the call. They stay on that meeting with their own provenance and appear when the dashboard lists open work.
Friday a colleague forwards an old M4A. You import it into Northwind. It is processed locally and sits in the date list with the other meetings. Ask, opened from the project, can look across active meetings in that project, not archived ones.
When the engagement ends, export what you must keep, then delete the project only if you want the local meetings gone. Cloud text, if you enable it later, is a separate activation and stays text-only.
Frequently asked questions
Can I pick a meeting project before I hit record?
Yes. The menu bar recorder includes project selection so the call is filed before capture starts.
Can I move a meeting later?
Yes. Drag meetings between Local Recordings and projects.
Does each project have its own glossary?
Yes. Preferred terms, aliases, and definitions live on that project. The original transcript stays the evidence.
What does delete do?
Deleting a project removes its meetings, transcripts, generated records, actions, decisions, speaker data in scope, and recording folders on this Mac.
Will my colleagues see the project?
No. It is local. Sharing is a separate step through export or macOS sharing of the parts you choose.
Do actions edited on the project change the meeting?
Yes. Project-level edits update the same source records shown in the meeting.
Is there a project in the browser tools?
No. The free tools transcribe a file you already have. They do not file live calls under a client.
What Mac is required?
Apple silicon, macOS Sonoma 14.2 or later, at least 8 GB of memory and 10 GB of free storage. 16 GB is recommended for long meetings. Intel Macs are not supported.
Create the client as a project once, select it in the menu bar, and record. Open work afterward shows on the project dashboard under the record.
Written by
Vemoir TeamMac meeting records by Aurum Avis Labs · Oberägeri, Switzerland
We build Vemoir, a Mac app for local-first meeting records: capture from the menu bar, transcribe on your Mac, and turn calls into minutes and action items.
Related Articles
You might also be interested in these articles
Take Notes While Recording and Keep Their Provenance
Notes while recording become part of the minutes and keep their own provenance. They are not rewritten as transcript quotes.
Set a Project Glossary for Names, Products, Jargon
A project glossary keeps preferred terms and aliases in meeting notes. The original transcript stays the evidence. Hints stay on your Mac.
Consultant meeting notes you can share without audio
Consultant meeting notes should capture the decision and the owner. Share the note, not the recording, unless the client asked.