> 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/converting-meeting-notes-to-requirements.md).

# Converting Meeting Notes to Requirements

### Overview

Meeting Notetaker can extract requirements-like statements from discussions.

Convert them into requirements so they become trackable scope.

{% hint style="info" %}
Screenshot placeholder: meeting summary with “Convert to requirement” actions.
{% endhint %}

### Key Concepts

* **Candidate requirement**: scope statement that can become a requirement
* **Draft requirement**: first-pass requirement created from notes
* **Source link**: meeting record link preserved for traceability

### How It’s Used

Convert meeting notes after summary review.

Use conversion to preserve scope before details are lost.

### Benefits

* Faster conversion from meeting outcomes to requirements
* Better traceability from requirement to source discussion
* Reduced manual copy/paste work

### Setup Steps

Prerequisites:

* Meeting Notetaker enabled at Account scope
* Access to the destination Project
* Permission to create requirements

{% stepper %}
{% step %}

### Open the meeting summary

1. Open **Meeting Notetaker**.
2. Select a meeting.
3. Review the generated summary and action items.
   {% endstep %}

{% step %}

### Select candidate requirements

Look for:

* “The system must…”
* acceptance criteria
* rules, constraints, or approvals

Avoid:

* pure discussion points
* open questions without a decision
  {% endstep %}

{% step %}

### Convert and route to the right place

1. Click **Convert to requirement** (or similar).
2. Choose the destination Project (if prompted).
3. Confirm the requirement is created.

{% hint style="info" %}
GIF placeholder: convert a note → requirement appears in Requirements list.
{% endhint %}
{% endstep %}

{% step %}

### Clean up the draft

Do a fast polish pass:

* rewrite as a single “must” statement
* split multi-part notes into multiple requirements
* add tags such as Process or System (when used)
* add acceptance criteria bullets
  {% endstep %}
  {% endstepper %}

### Best Practices

{% hint style="info" %}

* Convert quickly. Edit later. Preserve context.
* Keep the meeting link in the requirement description.
* Add a short “Decision” line when the requirement comes from approval.
  {% endhint %}

### Troubleshooting

<details>

<summary>I don’t see a convert option</summary>

Possible causes:

* Meeting Notetaker is not enabled for the Account.
* Viewer access does not include requirement creation.
* The meeting summary is still processing.

Try refreshing, then confirm access and feature enablement.

</details>

<details>

<summary>Converted requirements land in the wrong project</summary>

If the Account has a default Project assignment:

* change the Project during conversion (if prompted)
* or move/copy the requirement after creation (if supported)

If move/copy is not available, request support from an Account Admin.

</details>

### Summary

Meeting note conversion accelerates scope capture.

It also preserves traceability from requirements back to the meeting record.

Related:

* [Meeting Notetaker](/ai/meeting-notetaker.md)
* [Reviewing Meeting Summaries](/ai/reviewing-meeting-summaries.md)
* [Requirements](/transformations/requirements.md)


---

# 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/converting-meeting-notes-to-requirements.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.