> 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/reviewing-meeting-summaries.md).

# 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

{% stepper %}
{% step %}

### Open the meeting record

1. Navigate to Meeting Notetaker.
2. Open the meeting record to review.
   {% endstep %}

{% step %}

### 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.
   {% endstep %}

{% step %}

### Convert high-signal items

Convert scope statements into requirements.

Convert action items into tasks when execution work is defined.

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

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


---

# 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/reviewing-meeting-summaries.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.