> 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/ai/meeting-notetaker.md).

# Meeting Notetaker

### Overview

Meeting Notetaker turns meeting discussion into structured Project context.

It reduces manual note taking. It also improves traceability to delivery work.

### Key Concepts

* **Capture**: meeting recording and transcription (when enabled)
* **Summary**: structured notes, decisions, and action items
* **Outputs**: meeting records that can be linked to requirements and tasks
* **Permissions**: visibility follows Account, Organization, and Project access

### How It’s Used

Use Meeting Notetaker during discovery to capture early scope.

Use it during governance to record decisions and approvals.

### Benefits

* Faster conversion from discussion to delivery artifacts
* Reduced loss of context across teams and time
* Clearer governance through searchable decisions

### Setup Steps

Use the following sequence.

1. Configure the feature: [Setting Up Meeting Notetaker](/ai/setting-up-meeting-notetaker.md)
2. Capture meetings: [Capturing Meetings Automatically](/ai/capturing-meetings-automatically.md)
3. Review summaries: [Reviewing Meeting Summaries](/ai/reviewing-meeting-summaries.md)
4. Convert notes into requirements: [Converting Meeting Notes to Requirements](/ai/converting-meeting-notes-to-requirements.md)
5. Manage history: [Managing Meeting History](/ai/managing-meeting-history.md)

### Best Practices

* Capture governance meetings consistently.
* Convert action items into tasks within 24 hours.
* Keep decision statements in one comment for scanability.

### Summary

Meeting Notetaker creates structured context that can be linked to requirements and tasks.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/ai/meeting-notetaker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.