> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/tutorial-using-meeting-notetaker-and-console.md).

# 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

{% stepper %}
{% step %}

### Set up Meeting Notetaker

1. Confirm Meeting Notetaker is enabled for the Account.
2. Configure capture settings and permissions.

Related: [Setting Up Meeting Notetaker](/ai/setting-up-meeting-notetaker.md)
{% endstep %}

{% step %}

### Capture a meeting

Capture one meeting to generate searchable content.

Related: [Capturing Meetings Automatically](/ai/capturing-meetings-automatically.md)
{% endstep %}

{% step %}

### Review the summary

Review summary output for correctness.

Related: [Reviewing Meeting Summaries](/ai/reviewing-meeting-summaries.md)
{% endstep %}

{% step %}

### Convert key notes into requirements (optional)

Convert meeting notes into draft requirements when scope is discussed.

Related: [Converting Meeting Notes to Requirements](/ai/converting-meeting-notes-to-requirements.md)
{% endstep %}

{% step %}

### Query outcomes in Console

Run queries such as:

* `decisions made last week`
* `blocked items`
* `approved requirements`

Related: [Using Console for Natural Language Search](/ai/using-console-for-natural-language-search.md)\
Related: [Finding Decisions and Approvals](/ai/finding-decisions-and-approvals.md)
{% endstep %}
{% endstepper %}

### Troubleshooting

<details>

<summary>I don’t see Meeting Notetaker</summary>

This is usually a permissions or plan issue.

Ask an Account Admin to confirm Meeting Notetaker is enabled.

</details>

### 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:

* [Managing Meeting History](/ai/managing-meeting-history.md)
* [Console Search Tips and Examples](/ai/console-search-tips-and-examples.md)

<details>

<summary>Console results are empty</summary>

Common causes:

* No data exists in the project yet (capture a meeting first).
* Project permissions do not allow access to the indexed content.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/getting-started/tutorial-using-meeting-notetaker-and-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.