Using AI for Meeting Notes and Email

AI for meetings and email is not “send the transcript.” Lock a note structure (decisions, open items, actions), split email drafts by purpose and audience, and keep tone, facts, and promises as human gates. Paid meeting/mail AI prices are omitted.

Replace “summarize the meeting” with S04 job units applied to communication.

What structure should meeting notes use?

One-line answer: Lock a template first (attendees, agenda, decisions, open items, actions). The agent only fills those slots from the memo/transcript.

Inputs before the agent:

  • Source: transcript summary, handwritten notes, chat logs. Exclude HR, pay, unpublished figures.
  • Template: attendees, agenda, decisions, open items, actions (owner, due, source).
  • Banned: guessing speakers as certain; writing “agreed” when it was not.
  • Artifact: a filled Markdown/Doc, separate from the raw source.

Sample instruction: “Fill the template from the memo below only. Decisions may quote explicit lines. Ambiguity goes to open items. Missing owners → [needs check]. Do not invent agenda topics.”

A good note:

  1. Decisions not mixed with open items in one paragraph.
  2. Each action has a source line or timestamp.
  3. No vibe sentences (“great energy”) unless you have a separate Observations slot.

Take structure read-only, confirm action owners with attendees, then distribute.

How do you draft email?

One-line answer: Bundle recipient, purpose (inform/request/decline), length, and banned phrases. Do not over-generate subject and body in one sprawling ask.

Split the mail session:

  • Purpose one-liner: schedule ask, delay notice, send materials.
  • To/Cc: internal versus customer — tone changes.
  • Required facts: dates, links, numbers — pasted by a person; ban invention.
  • Banned phrases: endless apologies, legal certainty, unconfirmed discounts/dates.
  • Artifact: three subject candidates + one body draft. Signature and legal lines stay human.

Sample done-check: “Body ≤150 words, one request paragraph, only dates I supplied. No guessed schedules.”

Search-shaped “make it softer” adds adjectives. Job-shaped asks lock purpose, length, and facts.

How do you check tone and facts?

One-line answer: Cross-check facts line-by-line against the source. A person does a last read for tone against the relationship and company phrasing rules.

Human gates:

  • Facts: dates, amounts, product names, promises (“by Friday”) match the memo/ticket.
  • Ownership: action owners were not assigned without consent.
  • Tone: no internal blame, jokes, or unconfirmed roadmap leaking to customers.
  • Channel: full notes versus a link only; long logs go as attachment/Docs link.
  • Tool rights: generate drafts only — send stays human. Do not grant auto-send to the agent.

Vendor prices for meeting/mail assistants are not pinned here. Prefer products that stop before send/share and document whether source text is used for training.

Minimum path: (1) fill the template, (2) confirm action owners, (3) draft the mail/share text, (4) re-read facts and tone, then send. Speed does not remove 4.

Speech is not a search result. A wrong summary costs relationships.

Sources

  • S03/S04 applied to meeting and email artifacts.
  • Paid meeting/mail AI pricing: vendor pages (not pinned here).