Turn meeting notes into actions: owners, deadlines and completion evidence

01Paste four lines and preserve their original gaps

Set the meeting date to 2026-10-19 and use a demonstration title such as Delivery coordination. This complete fictional input deliberately omits the supplier task’s owner and gives a discussion a bullet. Do not silently repair either gap before extraction.

1. 1
   Open Meeting actions, create a demonstration record and enter the date and notes. Keep the Decision sentence in the source and separately record the stated scope decision in the decisions field.
2. 2
   Run local extraction and compare the three candidates below. If using AI assistance, distinguish its suggestions and review them against the source rather than combining methods into assumed commitments.
3. 3
   Remove the Discuss whether… candidate first. Then review each task, owner and deadline; keep disputed or unanswered fields explicitly unresolved.

Decision: keep the current launch scope.
Action: @Lin reconcile the attendee list by 2026-10-23
Action: ask the supplier for a revised quote next week
- Discuss whether the launch date needs to move

02Review three candidates into two actions with explicit status

1. 1
   For A1, retain Lin and 2026-10-23 in the owner/date fields, and add its ID, acceptance rule and evidence location to the task. Confirmation is an explicit assumption of this exercise; real tasks require actual agreement.
2. 2
   Do not invent A2’s owner or turn next week into Monday. The meeting was 2026-10-19; only an explicit agreement on next Monday supports 2026-10-26. Also agree a timezone and time when needed.
3. 3
   Export the action CSV and meeting notes. Reopen the CSV and check exactly two actions, an owner that remains blank where unresolved, unchanged dates and long descriptions in the correct cells. Preserve agenda and decision provenance.
4. 4
   Use Project status if you need to draft a weekly update from the reviewed records. Continuing a draft does not confirm ownership or accept a deliverable.

[A1] Reconcile attendee list. Confirmed owner: Lin. Due: 2026-10-23. Acceptance: compare stable attendee IDs; retain unresolved conflicts. Evidence: reviewed-list-v1.csv; still awaiting review.
[A2] Request revised quote. Owner: awaiting confirmation. Due: next week, exact date unresolved. Evidence: no revised quote received.

03Why was a discussion extracted but a decision was not?

Current local rules work line by line, recognize cues such as Action and also admit bullet-prefixed lines. That yields three candidates: Decision stays out, but the discussion becomes a false positive. Extracting text cannot establish agreement, an approved budget or a decision by the meeting.

• Three candidates are not three recognized commitments. Removing the discussion leaves two actions needing confirmation.
• Tasks without a cue or bullet may be missed. Reread the original notes after reviewing candidates.
• Extracted owners and dates come from text matching. Duplicate names, multiple dates and cross-timezone deadlines still need human review.

04Interpret “next week” against the meeting date

Suppose the illustrative meeting happened on 2026-10-19. If the team confirms that “next Monday” means the following Monday, record 2026-10-26. If the source only says “next week,” do not invent Monday. Confirm the day with the owner, write that definite date in the due field and retain the original wording or confirmation in the task notes. The tool does not automatically turn relative language into an agreed schedule.

A deadline and a review reminder can differ: delivery on October 23 and a blocker check on October 22 are two arrangements. When a cross-region task needs a time and timezone, state the agreement in the task description. A date alone does not communicate those additional conditions to the recipient.

05From 0/2 to 1/2: evidence before a completion checkbox

In these demonstration descriptions, A1’s list awaits review and A2 has an unresolved owner, date and acceptance rule: start at 0/2 complete. Suppose the list is later checked using stable IDs and accepted. Only then mark A1 complete: 1/2, or 50%. This is progress across two registered actions, including an unresolved one, not a completion rate for confirmed commitments or a business outcome measurement.

A2 originally says to request a quote. Agree whether completion means a request was sent or a revised quote was received and accepted. An unconfirmed task cannot become done because a request draft exists. The tool has task, owner, due date and completion fields; put evidence and blockers in task descriptions or notes rather than assuming automatic approval fields.

06Optional tools for a different input or next step

• Extract meeting actions: Separate decisions from open questions, confirm owners and deadlines, and review the exported task list with the participants.
• Prepare a project status report: Support status labels with progress evidence, blockers and next steps; do not turn an optimistic draft into a completed milestone.
• Write a project or product brief: Define the user problem, scope boundaries, milestones and measurable acceptance conditions before listing proposed features.
• Plan a customer follow-up: Record the verified need and agreed next step, then set a due date; a scheduled follow-up is not proof that contact occurred.
• Draft a support response: Use known facts, distinguish proposed remedies from approved ones and check any promise, amount or deadline before sending outside the tool.
• Build a content schedule: Record channel, owner, intended publication time and review status; inspect CSV or calendar timezone behavior before importing elsewhere.
• Prepare a quote or invoice draft: Verify line items, quantity, currency, discounts and any supplied tax rate, then check totals and document labels before delivery.
• Compare cash-flow scenarios: Enter the opening balance and expected receipt and payment timing, inspect negative months and label estimates; a forecast is not a bank balance or professional financial advice.

07Accept against completion evidence before handing off the list

Hand off A1’s review status separately from A2’s unresolved details. Generation, export and completion are different events. Exclude the removed discussion from the denominator and do not present an unconfirmed action as an accepted commitment.

RFC 4180 describes CSV quoting and record structure. Reopen exported action lists to ensure multiline notes remain in their intended cells.

Define an explicit meeting-action template before using automation. Check schedule overlaps, endpoints and buffers separately.