Meeting Summaries: What Good Automatic Summaries Actually Capture

It's tempting to think of an automatic summary as just a compressed transcript, but a genuinely useful one does something different: it extracts the handful of sentences in an hour-long conversation that actually matter later, and discards the rest — including the small talk, the repeated points, and the parts of the conversation that were exploratory rather than conclusive.

A summary that's just a shorter transcript still requires the reader to figure out what was actually decided; a good summary does that work already.

Decisions: what was actually agreed, stated as a fact rather than a discussion ("the launch date moved to the 12th," not "there was a discussion about the launch date"). Owners: which specific person is responsible for a follow-up, not just that a follow-up exists. Next steps: concrete actions with enough detail that someone reading the summary a week later, who wasn't on the call, understands what to do.

Everything else — the reasoning behind a decision, side conversations, context that only mattered in the moment — belongs in the full transcript, not the summary. A summary that tries to capture everything stops being useful precisely because it stops being short.

In a meeting that happened across two languages, a summary is often more valuable than the transcript itself — reading back a full bilingual transcript is slow, but a short bilingual summary of decisions and owners is something every participant can actually use afterward, regardless of which language they follow the meeting in. This is the thinking behind A6 Relay's Meeting Mode, which is built to produce exactly this kind of summary automatically.