For the complete documentation index, see llms.txt. This page is also available as Markdown.

Reviewing Meeting Summaries

Overview

Meeting summaries turn captured discussion into structured notes.

Review ensures accuracy before converting notes into delivery work.

Key Concepts

  • Summary: structured narrative of topics, decisions, and action items

  • Decision signal: explicit approval or direction captured in text

  • Action item: follow-up that can become a task

How It’s Used

Review summaries after capture and processing.

Use review output to create or refine requirements and tasks.

Benefits

  • Fewer incorrect requirements created from misheard context

  • Cleaner audit trail for decisions

  • Better follow-through on action items

Setup Steps

1

Open the meeting record

  1. Navigate to Meeting Notetaker.

  2. Open the meeting record to review.

2

Validate decisions and action items

  1. Confirm decisions match meeting intent.

  2. Confirm action items have a clear owner and outcome.

  3. Add clarifying comments when needed.

3

Convert high-signal items

Convert scope statements into requirements.

Convert action items into tasks when execution work is defined.

Best Practices

  • Review governance meetings first.

  • Capture approvals in a consistent Decision: pattern.

  • Keep requirement statements in the requirement record, not only in notes.

Summary

Summary review protects accuracy and keeps follow-through consistent.

Last updated