“We should update the help page” does not tell you who agreed to do it or when. Yet an AI-generated action list can turn that sentence into “Maya: update the help page by Friday.” It looks useful because every cell is filled. The problem is that the meeting never made those decisions.
A useful meeting workflow preserves missing information. It separates what somebody committed to from what the group merely discussed, then asks for the decisions that remain open.
Classify the notes before extracting tasks
Begin with four categories:
- Explicit commitment: somebody agreed to perform an action.
- Unassigned proposal: somebody suggested an action without an owner.
- Status update: a statement about what has already happened.
- Unresolved decision: an option discussed without agreement.
Consider this fictional note: “Priya says the patch is in staging. She will run regression tomorrow. Someone suggested announcing it to customers, but we did not decide.” The regression check is a commitment. Staging is a status. The announcement is unresolved. None establishes that a production release is complete.
Require evidence for owners and deadlines
Use this prompt with your notes:
Extract explicit commitments into a table: action, owner, deadline as
stated, dependency, and supporting quote. Put proposals without an
owner in a separate table. Use [NO DEADLINE] where none was agreed.
Separate status updates and unresolved decisions. Do not assign a task
to someone merely because they discussed it.
The evidence column makes errors easier to inspect. If an owner has no supporting commitment, the row needs clarification. If the notes say “after Maya sends the draft,” preserve that dependency instead of inventing a calendar deadline.
Handle relative dates explicitly
Supply the meeting date when it is known. If the notes say “tomorrow” but the meeting date is missing, leave the relative date unresolved. Do not ask the model to infer it from the current day: you may be processing notes days or weeks later.
Where notes provide both a weekday and date, check they are consistent. If two people stated conflicting deadlines, keep that conflict visible and ask for confirmation rather than silently selecting the more convenient one.
Review the output against a small answer key
For an illustrative meeting, the correct treatment could be:
| Note | Correct treatment |
|---|---|
| “I'll send the draft by 9 October” | Named commitment with stated date |
| “I can review it after the draft arrives” | Review commitment, dependency, no invented date |
| “We should update the help page” | Unassigned proposal |
| “The patch is in staging” | Status, not a completed production release |
| “Maybe announce it to customers” | Unresolved proposal |
Check both errors of addition and omission. An accurate-looking list can still drop an awkward unresolved item. Keep a separate loose-ends section so uncertainty does not disappear simply because it does not fit the task table.
Ask for a follow-up, not an invented decision
The next draft can say, “Who will own the help-page update?” It should not announce, “Maya will update the help page,” unless Maya agreed. Keep follow-up messages as drafts until someone has checked the notes and chosen the recipients.
Before moving tasks into a tracker, confirm that repeated imports will not create duplicates and that source notes remain accessible. For a small meeting, manually reviewing the few proposed tasks may be simpler than building an automated handoff.
Try the complete exercise free
Our free meeting-notes task pack includes fictional notes, staged prompts, a blank intake form, an authored answer key, and repair steps. No email is required. Run it, compare the result with the checks, then change one commitment into a suggestion and see whether the output changes appropriately.
The complete Claude Work Kit adds the same set of materials for proposals, factual editing, decision memos and bug tickets. The method above is usable without buying anything; the kit packages the reusable files.
FAQ
Should every action have an owner and deadline?
Those fields should be resolved before people rely on them, but extraction must not invent the answers. Mark missing information and ask the people involved to decide.
Can I process old notes with relative dates?
Supply the actual meeting date if known. Otherwise preserve relative dates as unresolved instead of calculating them from today.