Step-by-step workflow
AI Meeting Notes Workflow
A workflow that turns meetings into executable outcomes, covering recording, transcription, summaries, and action-item follow-through.
- Difficulty
- Beginner
- Estimated time
- 30 minutes
- Steps
- 4
- Best for
- Remote teams with heavy meeting loads and project managers; leads who need conversations to end in executable conclusions.
This workflow is rated "Beginner" and takes about 30 minutes, with 4 steps across 3 tools. Steps are editorial suggestions — add or drop stages to fit your project, and confirm each tool's account, quota, and platform requirements before starting to avoid interruptions.
Required tools
Steps
- 01
Record the Meeting
Obtain consent and confirm language support; unsupported languages require a manual transcript or suitable alternative.
Suggested tool: Otter.ai
- 02
Check Audio
Listen and reduce noise if useful; transcription accuracy still requires comparison with the recording.
Suggested tool: Krisp
- 03
Generate Notes
Extract actions from verified text; owners and dates require spoken evidence, not guesses.
Suggested tool: Notion AI
- 04
Follow Through
Sync action items into your project tool and review them before the next meeting.
Executable exercise and acceptance
This is an editorial procedure based on official documentation, not a completed product test. Inputs and numbers are exercise targets; expected results are acceptance criteria, not observed performance. Listed durations are planning estimates. Record actual versions and settings; cloud outputs can vary.
Prepare inputs
Input: a consented ten-minute mock meeting, three speaker names, and an agenda. Include one unresolved question and one confirmed task.
Environment, versions, and prerequisites
Check Otter's current transcription languages first; Korean is not on the reviewed list, so use a Korean-capable service or a manual transcript. Krisp does not guarantee transcription accuracy; send verified text to Notion.
Run in this order
- Confirm consent, language, and input device; check names on a 30-second sample and retain the recording.
- Compare transcript with audio and separate actual decisions from suggestions.
- List owner, due date, and source timestamp for each action. Mark unspecified dates as unresolved and ask participants to confirm.
Copyable English exercise fixture
Mock transcript: 02:10 Mina proposes Friday; 03:20 Tao says the deadline is undecided; 07:40 Mina accepts drafting a checklist. Output confirmed actions separately from suggestions; never infer a Friday deadline.Expected delivery and pass criteria
- Timestamped notes, an action table, and unresolved questions. Owners and dates require spoken evidence; participant confirmation must be recorded or pending.
Failure conditions and fallback
- Do not auto-create tasks with unsupported language, overlapping audio, guessed owners, or suggestions presented as decisions. Replay or confirm first.
Official references and review date
· Sources support tool capabilities and limits. Fixtures, sequence, and acceptance targets are our editorial design, not vendor performance promises.
Common mistakes to avoid
These are typical pitfalls our editors hit when assembling similar tool chains — check against them before you start and save yourself rework:
- Keeping recordings without distilling notes, making review expensive
- Action items without owners and deadlines
- Notes disconnected from the task system across tools