Meeting notes into actions you can verify.
Fictional starter — replace with your own material.
Source: https://clankercloud.ai/templates/meeting-action-tracker

Copy into Workspace yourself:

Create a meeting action tracker and decision log using only the fictional notes below. Save meeting-actions.md in this Project for review. Do not send messages, create calendar events, or update any external task system.

Use action columns: ID, action, owner, stated due date or timing rule, dependency, source markers. Distinguish actions from decisions, open questions, and suggestions. Merge repeated commitments and retain all supporting markers. Do not infer missing owners, approval, completion, or launch dates. Keep relative timing relative. Add a short list of questions for the meeting owner.

# Fictional meeting notes: Orchard launch review
Date: 2026-09-10
Attendees: Mina, Leo, Priya

[N1] Decision: use the existing onboarding page for the pilot; redesign is out of scope.
[N2] Mina: I will send the revised welcome copy to Priya by 2026-09-14.
[N3] Leo: Analytics event names need review. I will investigate, but I cannot commit to a date yet.
[N4] Priya: I will approve or return the welcome copy within two working days of receiving it.
[N5] Open question: who owns the pilot support inbox? No owner was agreed.
[N6] Mina suggested adding a tutorial video after the pilot; no decision was made.
[N7] The pilot launch date remains unconfirmed until welcome copy is approved.
[N8] Follow-up note: Mina repeated that the revised welcome copy is due 2026-09-14.

Illustrative result:
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.

Review checklist:
- 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.