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

Tutorial: Using Meeting Notetaker and Console

Overview

Meeting Notetaker captures meetings into searchable notes.

Console queries Project content to surface decisions and next steps.

Key Concepts

  • Meeting Notetaker: capture and summary pipeline for meetings

  • Meeting summary: structured output used for follow-ups

  • Console: natural language search across Project content

How It’s Used

Use this tutorial during discovery and weekly governance.

Use it to turn meeting outcomes into requirements and tasks.

Benefits

  • Faster capture of decisions and action items

  • Cleaner traceability from meetings to requirements

  • Less time spent re-reading threads and notes

Setup Steps

1

Set up Meeting Notetaker

  1. Confirm Meeting Notetaker is enabled for the Account.

  2. Configure capture settings and permissions.

Related: Setting Up Meeting Notetaker

2

Capture a meeting

Capture one meeting to generate searchable content.

Related: Capturing Meetings Automatically

3

Review the summary

Review summary output for correctness.

Related: Reviewing Meeting Summaries

4

Convert key notes into requirements (optional)

Convert meeting notes into draft requirements when scope is discussed.

5

Query outcomes in Console

Run queries such as:

  • decisions made last week

  • blocked items

  • approved requirements

Troubleshooting

I don’t see Meeting Notetaker

This is usually a permissions or plan issue.

Ask an Account Admin to confirm Meeting Notetaker is enabled.

Best Practices

  • Capture governance meetings consistently.

  • Convert action items into tasks within 24 hours.

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

Summary

Next actions:

Console results are empty

Common causes:

  • No data exists in the project yet (capture a meeting first).

  • Project permissions do not allow access to the indexed content.

Last updated