WORKED EXAMPLE / MEETING NOTES

Who actually owns that task?

A tidy action list can turn a suggestion into a commitment. Use this small example to inspect the evidence behind each owner and deadline.

1. Start with the source

S1 — Maya: I will compare the two landing-page drafts by 2026-10-02.
S2 — Leo: We should ask support about recurring questions.
S3 — Maya: Launch on 2026-10-05 is tentative; we have not decided yet.

2. Catch the unsupported assignment

Hand-written bad example: “Leo will collect support questions by 2026-10-02.”

S2 does not establish an owner or a deadline. The speaker is not automatically the assignee, and the date from S1 belongs to a different task. Keep the suggestion, label it PROPOSED, and ask for an owner and date before moving it into a confirmed task list.

3. Keep a reviewable action table

Review of the fictional source above
Candidate actionOwner / dateStatusEvidence
Compare two landing-page draftsMaya
2026-10-02
CONFIRMEDS1: explicit commitment
Ask support about recurring questionsUNKNOWN
UNKNOWN
PROPOSEDS2: suggestion only
Launch on 2026-10-05UNKNOWN
UNKNOWN
NOT DECIDEDS3: tentative, not approved

The status labels are our editorial convention. A source ID makes a row traceable; it does not prove the interpretation is correct. Read the referenced line and its context.

4. Copy a more reviewable prompt

Extract candidate actions from the source below.
Return: item_id, candidate_action, owner, due_date, status, source_id, review_note.
Use CONFIRMED only for explicit commitments.
Label suggestions PROPOSED and unresolved decisions NOT DECIDED.
Use UNKNOWN when the source does not establish an owner or date.
Do not treat the speaker as the owner by default.
Do not borrow a deadline from another action.
Preserve tentative or conditional language.
If the source has no stable IDs, retain a short supporting quote.
Do not create tasks or send messages. Return a review table only.

SOURCE: [paste material you are authorized to use]

This prompt has not been benchmarked. Inspect its output against your source before relying on it.

5. Review before the handoff

  1. Check every owner and date against the cited source. A populated cell is not proof.
  2. Keep suggestions and unresolved decisions separate from confirmed tasks.
  3. Ask for missing commitments instead of filling them from context.
  4. Approve the rows before importing into a task manager or sending reminders.
  5. After editing the prompt, rerun this example and your own permitted cases. Keep the first output and corrections.

Download the worksheet

The CSV uses UTF-8. Import date fields deliberately; spreadsheet apps may reformat them. UNKNOWN is a missing value marker, not a person or date.

Blank review CSVCompleted example CSV

Limits

Three fictional lines illustrate a review problem; they do not estimate model accuracy. Real meetings can contain corrections, ambiguous pronouns and conflicting commitments. This worksheet does not resolve those automatically. Do not put private meeting material into a service unless you are authorized to do so.