Meeting notes into actions you can verify.

Keep the record before interpreting it

Create a Project for the work and keep the original notes alongside the tracker. Paste the complete example below into a Session, or upload the sample file. The source markers N1–N8 make every extracted item easy to check. They are ordinary text labels, so the method also works with your own numbered paragraphs.

For real notes, include the meeting date, participants, and any follow-up corrections. A transcript may contain tentative proposals, interruptions, or a speaker changing their mind. Ask the Agent to retain a short supporting quote or source marker rather than deciding that every future-tense sentence is a commitment.

Separate four kinds of information

An action states work someone has committed to do. A decision records an agreed choice. An open question needs an answer. A suggestion may be useful without having an owner or approval. Mixing these categories makes a tidy tracker look more certain than the meeting actually was.

In the fictional record, the onboarding-page choice is a decision, the tutorial video is a suggestion, and support-inbox ownership is an open question. Mina’s welcome copy is a committed action. Leo’s investigation has an owner but no promised due date. Preserve these differences instead of completing every empty cell.

Represent dependencies without inventing deadlines

Priya’s review is due within two working days of receiving the copy. That is a relative commitment, not a fixed date. Keep the rule and dependency together until receipt is confirmed. Even a seemingly simple conversion depends on weekends, holidays, and what counts as receipt.

Use separate fields for a stated date, a relative timing rule, and an unknown date. Do not infer a pilot launch date from Mina’s copy deadline. If notes say “next Friday,” ask which calendar date was intended before replacing the phrase in the final register.

Reconcile repeated and conflicting commitments

The final note repeats Mina’s existing action. Keep one action row with both supporting markers instead of counting two deliverables. Give each resulting action a stable ID so a later review can change its status without making a new task merely because the wording differs.

If a later note changes an owner or date, show the conflict and identify the later source. A newer timestamp alone does not prove approval. Ask the meeting owner to resolve conflicting commitments; retain the superseded detail in the review notes when it matters to the record.

Review the tracker with the original beside it

Open the saved file through Project Files or Session Preview. Check each action against its source marker, then scan the separate decision, question, and suggestion lists. A missing unassigned question can matter as much as a wrongly assigned action. Review actual file contents before treating the work as finished.

Use this register as a draft for the people responsible. Creating it does not assign tasks in your team’s task manager or obtain anyone’s agreement. If you later request an external update, name the destination, exact records, and authorized change; review the available access separately.

Update the record without rewriting history

For the next meeting, keep the approved tracker and add dated notes rather than replacing the old evidence. Ask for proposed status changes supported by the new record. “Discussed again” is not evidence of completion, and an overdue date does not prove a task failed.

Store a stable output format in Project instructions once it works. When a source is unreadable or missing, return an incomplete extraction with the missing sections identified. That gives the reviewer a clear next step and prevents an attractive but partial tracker from becoming the assumed full record.

Try it with a small example.

An illustrative result.

Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.

Fictional expected extraction

A1: Send revised welcome copy | Mina | 2026-09-14 | None stated | N2, N8
A2: Investigate analytics event names | Leo | No committed date | None stated | N3
A3: Approve or return welcome copy | Priya | Within two working days of receipt | Receive copy | N4

Decision: existing onboarding page; redesign out of scope (N1).
Open questions: support-inbox owner (N5); pilot launch date after copy approval (N7).
Suggestion: tutorial video after the pilot; not approved (N6).
Reviewer questions: confirm Leo’s timing and the receipt date that starts Priya’s review window.

Before you use the result.

• Exactly three actions are extracted; the repeated copy commitment is one row.
• Every action has its correct source markers and only stated ownership.
• Priya’s relative deadline stays relative and the pilot date stays unconfirmed.
• The tutorial video is a suggestion, not a committed deliverable.
• The saved tracker opens and no external tasks or messages were created.