> 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/managing-meeting-history.md).

# 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

{% stepper %}
{% step %}

### Find a prior meeting

1. Open Meeting Notetaker.
2. Filter or search for the meeting record.
   {% endstep %}

{% step %}

### Reuse outputs

1. Open the meeting summary.
2. Follow links to the related requirements and tasks.
3. Convert missed items when needed.
   {% endstep %}

{% step %}

### Archive patterns (optional)

When a delivery phase ends, standardize naming or grouping to keep history searchable.
{% endstep %}
{% endstepper %}

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


---

# 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/managing-meeting-history.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.