Turn meeting notes into decisions and action items
Read meeting notes through connected apps, check decisions against the transcript, and prepare follow-up tasks with source references.
Tuesday’s release review ends with a decision to hold an export feature and a promise to check a bug. The next morning, someone needs to know who owns that check and whether the release plan changed. The answer is in the discussion, not just the agenda.
Connect your calendar and the service that holds the meeting notes or transcript. Identify the meeting by its title, date, or link. Beeuni can locate the event, read its linked agenda, and retrieve the discussion from the connected source. Give it access to both the event and the meeting record so it can follow those references.
Find Tuesday’s release review in my connected calendar.
Read the linked agenda and the transcript available through my connected apps.
Prepare a short recap, decisions, actions, and unresolved questions.
Link each action to the relevant passage. Leave unagreed owners or dates blank.
Show me the task drafts before adding them to the project board.The agent can use the agenda to understand the topics, then check what participants actually agreed in the transcript. Ask it to list any source it could not open. If timestamps are absent, paragraph references still let you trace an action back to the discussion.
What should survive the summary?
This short, fictional exchange illustrates the difference between a suggestion, a commitment, and a decision:
[14:10] Product lead: Could we include CSV export in Friday’s release?
[14:22] Engineer: I can check the export bug tomorrow. I cannot commit to shipping it yet.
[14:40] Product lead: Then leave CSV export out of this release. We will decide after the bug check.
[14:55] Support lead: I will draft a note for the affected customers.| Type | Item | Owner | Due | Source |
|---|---|---|---|---|
| Decision | Exclude CSV export from Friday’s release | — | — | 14:40 |
| Action | Check the export bug | Engineer | Tomorrow; confirm date | 14:22 |
| Action | Draft a customer note | Support lead | Not agreed | 14:55 |
| Open question | When can CSV export ship? | Unassigned | Not agreed | 14:22–14:40 |
“Check the bug” is the commitment. “Ship CSV export” is not. The customer note has an owner but no agreed deadline. Keep those gaps visible instead of filling them with plausible dates.
Make the output easy to review
Ask Beeuni for a brief recap followed by separate decisions, actions, and open questions. Keep links to the meeting record and quote the sentence behind any uncertain assignment. Have the agent prepare each task with a description, owner, and due date for review in your connected project tool.
Before sharing the result, check each owner and deadline against the transcript. Resolve “tomorrow” using the meeting date and time zone, or leave it unresolved if either is missing. A later comment may also cancel an earlier action, so ask the agent to check the full discussion before finalizing the list.
Confirm the action list with the participants. If the connected task system exposes task creation and your agent has permission, ask it to add the approved items to the named board. Give it the destination, owners, and dates you confirmed. Keep the meeting link in each task so a teammate can check the agreement without searching the full recording.
More articles
Infrastructure for RSI research: running and evaluating self-improving agents
How Beeuni helps researchers run repeated agent-improvement experiments: edit code and instructions, execute tests, investigate failures, and compare versions.
Use Beeuni to run and evaluate a model fine-tuning experiment
Have an agent prepare training data, run a fine-tuning job on your connected training computer, inspect failures, and compare model outputs.