Best Practices: Meeting Capture

Best Practices: Meeting Capture

Meetings are where most institutional memory is made and most of it is lost. A little discipline in how you capture them turns fleeting conversation into lasting, searchable memory. Here is how to do it well.

---

The zero-effort path: Google Meet

If your meeting runs on Google Meet with recording and notes enabled, you are essentially done. The recording, transcript, and AI-generated notes are emailed out automatically, and if the capture inbox is on the invite, Sera picks them up on her own. This is the lowest-effort, highest-reliability path. Prefer it whenever you can.

---

Using external note-takers

Many teams use tools like Granola, Otter, or Fireflies. These work beautifully with Sera, you just need to hand off the notes:

1. Export the meeting notes as a .docx or .txt file. Word format is especially reliable.
2. Email the file to your capture inbox.
3. Put the meeting name in the subject line and a short note in the body.

A short body plus a substantial attachment routes the content to a Knowledge Base Draft, filed cleanly as meeting reference material.

---

The one habit that matters: add capture as a guest on the recurring invite

If you do only one thing, do this: add the capture address as a guest on your recurring meeting invite series. Set it once, and every future occurrence is captured automatically — no remembering, no forwarding, no per-meeting effort.

Here is why it works, because understanding the mechanism saves you a lot of unnecessary work. When the capture address is a guest on the meeting, Google itself emails the post-meeting recording and transcript to it — the same "your transcript is ready" email it sends every attendee. Sera reads that email and pulls in the transcript. So:

• You do not need to send transcripts to attendees yourself. Being a guest is what triggers Google's notification; a courtesy email to the team adds nothing for capture. If you have been manually forwarding transcripts "when you remember," you can stop — put capture on the recurring invite instead and it becomes automatic.
• You do not need to be the organizer. Any meeting the capture address is invited to gets captured.

For one-off meetings (not part of a recurring series), you have two easy options: add the capture address as a guest when you create the event, or — if you forgot — forward Google's "transcript is ready" email to the capture inbox once. Either works.

---

What makes extraction better

Sera reads for meaning, and certain kinds of language give her far more to work with. Whether you are writing notes or reviewing a transcript, these signals dramatically improve the quality of what gets extracted:

• Named participants — who was actually in the room. Names let Sera attribute decisions and tasks correctly.
• Decision language — phrases like "we decided," "we agreed," or "consent was reached" clearly mark a decision worth recording.
• Action language — "will," "by [date]," and "responsible:" turn a vague intention into a concrete, ownable task with a deadline.
• Risk language — "concern about," "the risk is," or "we are worried that" flag risks so they can be tracked, not forgotten.
• Role and circle references — mentioning the role or circle involved lets Sera anchor accountability correctly.

Here is the key insight: a rough summary with these signals beats polished prose with no governance cues. You do not need beautiful writing. You need names, decisions, owners, dates, and risks stated plainly. Sera will do the rest.

---

Recovering a meeting that shows Needs Access

Sometimes a meeting's transcript lives behind a permission Sera cannot reach. When that happens, the Meeting record shows Needs Access. This is not a failure; it is a prompt for a quick human assist. You have two easy ways to recover it:

1. Forward the document link — send the transcript or notes doc link to the capture inbox from an account that can see it, and Sera will pull it in.
2. Paste the text into the dashboard — open the Extract box on your dashboard, paste the transcript text, and submit it directly.

Either path gets the content into memory in under a minute. A Needs Access flag is simply Sera raising her hand for the one thing she genuinely cannot do on her own: reach content she has not been given permission to see.

---

The habit that pays off

The organizations that get the most from their living memory do one simple thing consistently: they put the capture address on their recurring invites and then forget about it. Automate it once on the calendar, forward the rare one-off, and stop doing anything by hand. Do that, and your memory fills itself.

Key points

The single solid habit: add the capture address as a GUEST on your recurring calendar invite series, once. Being a guest is what makes Google auto-email the post-meeting recording and transcript to the capture inbox — every occurrence, forever, with nothing to remember. You do NOT need to forward transcripts to attendees or send anything manually; that is extra work with no capture benefit. For one-off meetings, add the capture address as a guest when you create the event, or forward Google's "transcript is ready" email to the capture inbox once. For external tools (Granola, Otter, Fireflies), export notes as .docx or .txt and email them to the capture inbox with the meeting name as the subject. Extraction quality improves with named participants, decision language, action language with dates and owners, risk language, and role plus circle references. If a transcript is inaccessible the Meeting shows Needs Access; recover by forwarding the doc link or pasting the text into the dashboard Extract box.