Turn meeting notes into Planner tasks with owners, due dates, and review checks.

1. Lock the task contract

The first pass defines the meeting-summary source, accepted task fields, owner rules, date rules, duplicate key, Planner buckets, source-link format, and review states. That keeps the handoff stable even when meeting notes arrive in different formats.

2. Use one canonical task shape

{
  "meeting_id": "mtg_client_onboarding_001",
  "action_item_id": "a2",
  "title": "Send source-file request list",
  "owner": "Nemo",
  "due_date": "2026-05-25",
  "priority": "normal",
  "status": "ready_for_planner",
  "source_link": "mailbox://sample/client-onboarding-001-update"
}

3. Build the first paid slice

• Read one approved meeting-summary source or export.
• Extract action item, owner, due date, priority, source link, and acceptance check.
• Merge repeated meeting items into the same task record.
• Route missing owner or due date to review instead of guessing.
• Return Planner-ready rows plus a run log and handoff note.

4. Acceptance checks

• The same meeting item updates the same task instead of duplicating it.
• Missing owners and due dates create review rows.
• Every ready task has an owner, due date, source link, and acceptance check.
• The run log shows created, updated, and review-required states.

5. Buyer route

A narrow first milestone can start when the meeting-summary source, Planner bucket structure, owner list, and sample notes are clear. The first deliverable is the task contract, import-ready rows, run log, and handoff note.

• $95 form dashboard handoff
• $500 workflow build or repair