AI Meeting Notes

Business

Chaos → decisions — action items with owners, open questions, and a narrative recap you can paste into Notion or email without inventing attendance.

Make meetings expensive to waste

If it is not written, it did not happen.

Paste rough notes, auto-transcripts, or Otter exports. Pick a meeting type so tone matches standup vs exec vs sales. The output foregrounds decisions and action items with explicit owners (when notes name them) and honest TBDs (when they do not). The model is instructed not to fabricate commitments, attendance, or numbers that do not appear in the raw notes — it surfaces ambiguity instead of papering over it. The result is a recap your team can paste into Linear, Asana, or email and act on without re-listening to the recording.

How to brief minutes that survive Monday

Six prep moves that beat re-watching the recording.

1. Paste the cleanest notes you have — auto-captions, scribbles, or transcript dumps all work.
2. Pick the meeting type honestly; standup vs decision vs sales each shape the recap structure differently.
3. Optionally hint attendees to bias action item language — but the model knows hints are not proof of attendance.
4. Choose detail level based on use — tight bullets for Slack, narrative for email summaries.
5. Verify owners and dates in the output before assigning tickets; TBDs are intentional, not bugs.
6. Pair with the AI Transcription tool when you only have audio and no rough notes.

Meeting types it understands

Each type shapes the output structure.

Standup

Status sweep

Round-the-room blockers and progress with emphasis on what changed since yesterday.

Planning

Scope + estimate

Story-grouped recap with capacity calls and parking-lot items for next planning cycle.

Decision review

Options + chosen path

Decision log format with rationale, alternatives considered, and follow-up owners.

1:1

Career + work

Two-axis recap separating personal growth threads from immediate work commitments.

Sales discovery

Pain + next step

BANT-shaped notes with named pain points, decision criteria, and committed follow-ups.

Exec update

Crisp, decision-ready

Top-line summary with risks and asks separated for executive readability.

Best for

Recurring meetings where structure compounds.

• Weekly leadership syncs that need a written record for absent partners
• Customer discovery interviews where action items drive product decisions
• Architecture reviews where decisions need traceable rationale months later
• Cross-functional planning where multiple owners need clear handoffs
• Board prep meetings where the recap becomes the next deck draft
• Vendor calls where you need a paper trail of commitments and timelines
• Internal mobility 1:1s that need consistent format across reporting chains

Why honest TBDs beat fake precision

Inventing owners is how trust dies in distributed teams.

The most damaging meeting-notes failure is not bad formatting — it is confidently assigning an action item to someone who never agreed to it. Generic AI summarizers love to fill in owners because the recap reads cleaner that way. This template inverts that incentive: when ownership is unclear in the raw notes, the output marks TBD loudly and surfaces it as a follow-up question. When dates are not stated, they stay blank instead of becoming "end of week." The recap reads slightly less polished than fabricated alternatives, but every commitment in it is real.

Pro tips for minutes that drive action

Habits that compound across recurring meetings.

1. Send the recap within an hour of the meeting; latency erodes accuracy of attendees' memories.
2. When TBDs appear in the action items, assign them in the next meeting — do not let them rot.
3. For sales discovery, paste customer quotes verbatim so the recap captures their language, not your paraphrase.
4. Use narrative detail for board prep; tight bullets for engineering standups.
5. Pair with the AI Email Writer to convert internal-format minutes into a customer-facing follow-up note.
6. Save outputs in a consistent location (Notion, Google Drive) so future searches surface decisions, not just summaries.

Meeting Notes FAQ

Will it assign blame for missed items?

It mirrors ownership language from your raw notes; if no owner is named, it writes TBD honestly. Blame is a human conversation, not a recap output.

Will it invent attendees, decisions, or commitments?

It is explicitly instructed not to. If something appears that you did not write, fix the raw notes input and regenerate.

Can it process audio directly?

Use the AI Transcription tool first to clean audio into text, then paste the transcript into this tool for structured minutes.

Does it work for non-English meetings?

Best in English today; other languages produce reasonable structure but ownership and date inference is weaker. Always verify.

Can the output integrate with Linear or Asana?

Not directly — but the action items table is shaped for easy copy-paste. Each row maps cleanly to a ticket.

Which models power it?

Default streaming text models work well for most meeting summaries. Use a deeper reasoning model for complex multi-decision strategy meetings.

How do I get crisper TL;DR bullets?

Paste richer raw notes — three bullets of context per topic produce better one-line summaries than a wall of unstructured text.

Close the loop on every conversation

Minutes only matter when linked to tickets.

This output is structured for the paste-into-PM-tool hop. Send the recap within an hour, assign the TBDs by the next meeting, and watch how much faster decisions stick when there is a written record of who agreed to what.