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

Managing Meeting History

Overview

Meeting history provides continuity across time and team changes.

It supports audits, onboarding, and decision retrieval.

Key Concepts

  • Meeting record: stored notes, summary, and linked outputs

  • Retention: how long meeting records remain available (plan dependent)

  • Traceability: links from meetings to requirements, tasks, and Artifacts

How It’s Used

Use meeting history during onboarding to recover context quickly.

Use it during governance to confirm prior approvals and rationale.

Benefits

  • Faster continuity for new delivery teams

  • Reduced repeated discussions and rework

  • Stronger evidence for decisions and approvals

Setup Steps

1

Find a prior meeting

  1. Open Meeting Notetaker.

  2. Filter or search for the meeting record.

2

Reuse outputs

  1. Open the meeting summary.

  2. Follow links to the related requirements and tasks.

  3. Convert missed items when needed.

3

Archive patterns (optional)

When a delivery phase ends, standardize naming or grouping to keep history searchable.

Best Practices

  • Keep meeting titles stable and searchable.

  • Convert action items into tasks within 24 hours.

  • Use meeting links in requirements to preserve origin context.

Summary

Meeting history is a continuity layer for decisions and follow-through.

Last updated