> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genieforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tutorial: Meeting notes intelligence

> Capture audio or notes, let AI structure them, then track action items and people in one searchable app.

# Tutorial: Meeting notes intelligence

Outcome: messy meeting input becomes searchable structured notes with action items and a people directory. Swap "meeting" for field notes, interviews, or any capture → structure → act loop.

## What you will assemble

| Piece      | Role in the app                                              |
| ---------- | ------------------------------------------------------------ |
| Roles      | `member` (and optional `admin`)                              |
| Data       | Meetings, participants, action items                         |
| Forms      | Add / edit participant                                       |
| Pages      | Meetings list; meeting detail; contacts                      |
| Tools      | Start transcription, run summary, save meeting, toggle items |
| Agents     | Optional participant helper that only edits contacts         |
| Background | Long transcription / summary jobs so chat stays responsive   |

## Step 1 | Prompt in Build mode

> Build a meeting notes app. Users upload an audio recording (or paste rough notes). The app transcribes when needed, then generates structured notes: headline, summary, action items, agreements, and key quotes. Meetings are listed and searchable. Each meeting has a detail page with checkable action items. Maintain a participants directory and link people to meetings. Roles: member can create and edit their meetings; admin can see everything.

Approve the plan when action items are real rows (not only prose in a summary blob).

## Step 2 | Capture → structure path

**Upload or paste → process tool (background) → save structured meeting → open detail page**

Ask Build to keep transcription and summarization in a background task so the chat does not hang. Confirm status under project **Executions**.

## Step 3 | Action items and people

Wire **toggle action item**, **add participant**, and **link participant to meeting**. Prove the contacts page and meeting detail stay in sync after edits.

## Step 4 | Access and Preview

1. **App Blueprint → Access**: members should not delete other people's meetings unless you intend that.
2. **Preview as** member: upload a short sample, wait for processing, check an action item.
3. Optional: add an event hook that notifies assignees when an action item is created with their name.

## Step 5 | Soft launch

Invite a small team under **End-Users**, then use [Launch checklist](/getting-started/launch-checklist).

## Related

* [Background tasks](/logic/background-tasks)
* [Agents](/primitives/agents)
* [Forms](/primitives/forms)
* [Troubleshooting](/getting-started/troubleshooting)