Make an Action List From Meeting Notes Without Reassigning the Work

To make an action list from meeting notes, keep the speaker and exact commitment beside each item. Separate accepted work from suggestions and conditional offers. When a speaker or deadline is missing, leave that part unresolved until someone supplies it. A meeting role is not evidence that a person accepted a task.

The result should tell a colleague what was actually agreed, who accepted it and what still needs an answer. It should not turn a useful suggestion into assigned work or make a tidy list look like proof that the work was completed.

A public meeting-note complaint describes action ownership being swapped and corrections not surviving a rewrite. Another reply reports no such problem, and one reply comes from a competing tool's founder. These are limited accounts, with exact posting dates unverified; they do not establish a product's present reliability or a technical fix.

The complete transcript, participant key, ledgers and clarification below are original fiction. They were written for this exercise, not recorded, transcribed or captured from an AI system. No meeting software or model was tested, and no participant was contacted. The date 2030-04-11 belongs only to the invented case.

Start with the whole meeting record and participant key

A plain document is enough for a small meeting. If your own notes already make the actions clear, you can prepare the list manually. The same source checks apply if you ask an assistant to organize it.

Here is the entire M-1 record. A and B are mapped by the fictional author; U deliberately is not. Host and guest describe their meeting roles, not a rule for allocating work.

M-1 — Leaflet review, original fictional teaching transcript
This is the entire authored meeting record, not an audio recording or a
transcription result. The date 2030-04-11 is an invented case deadline,
not this article's publication date. No meeting date or clock time is supplied.

Participant key supplied by the fictional meeting author:
A = Rowan, host and leaflet coordinator.
B = Casey, guest and layout reviewer.
U = unidentified speaker; the supplied record does not map this turn to A or B.
These are supplied labels, not identities inferred from voices or meeting roles.

T01 [A / Rowan]: I'll draft a new opening paragraph for the leaflet by 2030-04-11. That is a text draft for review, not permission to distribute the leaflet.
T02 [B / Casey]: I'll check the print layout. I have not set a due date for that check.
T03 [A / Rowan]: Could we send the revised leaflet to everyone on Friday?
T04 [B / Casey]: I have not agreed to send it, and we are not planning a send now. I suggest reviewing one paper copy first.
T05 [A / Rowan]: Agreed: we will review one paper copy before deciding about any distribution. There is no distribution decision today.
T06 [B / Casey]: If the room names are final, I can add a small route diagram.
T07 [A / Rowan]: The room names are not final. I have not asked you to start the diagram.
T08 [B / Casey]: Then the diagram stays an offer. I am not starting it.
T09 [U / unidentified]: I'll bring a paper copy of the current leaflet to the review.
T10 [A / Rowan]: Record those items for review. Do not assign the unidentified turn to either of us from the host or guest role. Casey's print-layout due date is still open.

T01 and T02 contain explicit first-person commitments. T03 is a question proposing distribution. T06 is an offer whose condition is contradicted in T07 and kept inactive in T08. T09 has commitment wording, but M-1 does not identify its speaker. Those distinctions should survive the conversion to a table.

Reject a complete list that assigns more than the source supports

WRONG-0 — deliberately wrong full ledger

This six-row list is an authored counterexample, not captured AI output. Reject it; it is not a source of assignments.

The problems are concrete, not stylistic:

A polished summary such as “Casey will finish and distribute the leaflet” would conceal several of these errors in one sentence. Keeping row IDs and turn references makes each claim easier to inspect.

Build the first full ledger without resolving unknowns yourself

LEDGER-1 — checked against M-1, before clarification

Actions record what was said, not completed work. A01/A02 have known owners; A03 has commitment wording but its attribution is unresolved. O01/P01 are parked, and D01 records an explicit decision without assigning new work.

The ledger contains different kinds of items on purpose. Only A01–A03 have explicit commitment statements. A03 still needs an owner before it can serve as a reliable assigned follow-up. The diagram offer and distribution proposal remain visible without joining the active-action list. D01 records the decision but does not silently make Rowan responsible for bringing the paper copy.

An unknown date is also different from a rejected commitment. Casey accepted the layout check while leaving its timing open. Keep the accepted action and ask about its date; do not replace the missing value with A01's deadline.

Ask the specific clarification the ledger needs

The document author cannot identify U from this record. Ask a participant who can confirm the attribution, and keep the later answer separate from the transcript. Here is the complete authored exchange for the example:

Q-1 / Complete authored clarification request

In M-1, T09 says, "I'll bring a paper copy of the current leaflet to the
review," but its speaker label is U. Who said T09 and accepted that action?
Please confirm from your knowledge of this fictional meeting rather than
assigning it from the host/guest role. Was any calendar date for that review
stated? Has Casey supplied a due date for the print-layout check in T02?
We will keep the existing commitments and offers unchanged while asking.

C-1 / Complete authored reply from Casey

T09 was me, Casey. I accepted bringing a paper copy of the current leaflet
to the review; it is not Rowan's action. The review has no calendar date yet.
I have not supplied a due date for my print-layout check. This reply
clarifies T09's owner and those missing dates; it does not change any
other action or turn the diagram offer or distribution proposal into work.

C-1 supplies the missing identity for T09. It also confirms that the two calendar dates remain absent. Do not rewrite T09's original label from U to B: the original record and later clarification are different sources, and the ledger can cite both.

Correct that attribution and return the entire ledger

Use this complete correction instruction with LEDGER-1 and C-1:

Update LEDGER-1 using the complete supplied Casey reply C-1.

C-1 explicitly identifies Casey as the speaker and owner of T09.
Change A03's owner from Unknown to Casey, its state from attribution
unresolved to owner clarified, and its source references to include C-1.
Keep A03's action and timing wording unchanged: bring a paper copy of
the current leaflet to the review; the calendar date is not supplied.

Return the entire ledger as LEDGER-2, including the parked items.
Keep A01, A02, O01, P01 and D01 exactly as in LEDGER-1. In particular,
do not copy A01's 2030-04-11 deadline into any other row, invent the
layout-check due date, start the diagram, or approve distribution.

After the full ledger, list only the fields changed in A03 and their
sources. Leave the original transcript unchanged and keep U/T09 visible
as its original label. C-1 is a later clarification, not a rewritten turn.

Prepare text only. Do not create tasks, contact participants, schedule
anything, send the leaflet or claim that any action has been performed.

The resulting complete authored ledger is:

LEDGER-2 — full ledger after C-1

C-1 identifies Casey as T09's owner. It does not supply either missing calendar date, start the diagram, approve distribution or report completed work. The earlier U label remains in M-1.

Remaining questions

• U1 — A02 due date: What due date, if any, should Casey's accepted print-layout check have? Casey explicitly says none has been supplied. Keep Unknown until an actual answer is given.
• U2 — review date: What calendar date will the review use? C-1 says none is set. A03 retains the event-relative timing, and D01 retains the agreed sequence; neither becomes a dated appointment.

O01's room-name condition remains unmet, and P01 remains a proposal. Those are parked states, not gaps the document author may solve by scheduling or assigning work.

The permitted change is limited to A03's attribution fields: its owner becomes Casey, its state no longer describes unresolved ownership, and C-1 joins its sources. Its kind, action, event-relative timing and condition stay the same. A01, A02, O01, P01 and D01 are unchanged in the complete structured companion.

That is a different step from fixing WRONG-0. The first pass repaired unsupported content against the transcript. The second pass uses a new clarification to resolve one attribution. Keeping those passes separate makes it visible which source supported each change.

Give an assistant a bounded extraction request

Use the following with the complete M-1 record above. The companion complete-extraction-request file combines the request and all source turns, so no earlier chat or recording access is assumed.

Prepare a meeting action ledger from the complete supplied M-1 transcript.
Return a document only; do not create tasks, contact anyone, schedule work,
distribute the leaflet or perform the recorded actions.

Use only M-1 and its explicitly supplied participant key. A is Rowan;
B is Casey; U remains unidentified. These labels are supplied information,
not voice recognition. No meeting date or clock time is supplied, and
2030-04-11 is a fictional case deadline, not a publication date.

Return the full ledger with stable row IDs and these fields:
- Kind: accepted action, conditional offer, proposal or decision.
- Action or item wording, preserving what was actually accepted.
- Owner, or Unknown when an action's speaker is unidentified.
- Due/timing exactly as supplied, with missing dates visibly Unknown.
- State and any unmet condition.
- The exact supporting turn IDs.

Keep the three accepted-action statements separate from the diagram offer,
the distribution proposal and the review-before-distribution decision.
A suggestion is not an assignment. An offer with an unmet condition is
not active work. An agreed review step does not approve distribution.

Do not assign T09 from the host/guest role or borrow a deadline from
another row. Preserve T02's missing deadline. Keep the Friday in T03 as
proposed timing only, not an accepted due date or an invented calendar day.

After the full ledger, identify the specific questions needed to resolve
T09's attribution and the missing dates. Do not answer them yourself.
State which items are known commitments, which remain parked and which
facts the packet does not establish. Do not report task completion.

For another meeting, adapt this reusable request and include the actual authorized source material:

Source packet:
[Complete meeting notes/transcript and revision label.]
[Participant-label key that the meeting participants can verify.]
[Any later clarification, separately labeled with who supplied it.]

Task:
Prepare a full action ledger for review. Do not operate a task system,
contact participants, schedule work or perform the actions.

For every row, return a stable ID, kind, action/item wording, owner,
due/timing as stated, commitment state, condition and source locator.
Separate accepted actions from conditional offers, unaccepted proposals
and explicit decisions. Mark unsupported ownership or dates Unknown.
Do not infer agreement from silence or identity from a meeting role.

If correcting an existing ledger:
[Attach the complete baseline ledger and label its version.]
[Name the specific row/fields and supply the complete clarification.]
Return the entire corrected ledger, then the changed fields and sources.
Preserve every unaffected row. Keep the original transcript and the later
clarification separate; do not rewrite the source to make the ledger fit.

End with the exact remaining questions and who can answer them, where
that responsibility is actually known. Do not invent missing information
or say that producing this document completed the recorded work.

Check whether another reader can use the ledger

Give a colleague the complete M-1 record, its participant key, LEDGER-1 and the Q-1/C-1 exchange. Ask them to identify the next supported document change and the questions that remain. They should not need to infer an owner from the host or guest role.

The following are proposed checks, with expectations derived from the authored sources. No second reader has performed them; actual observations and outcomes remain empty. These checks concern the document, not whether Rowan or Casey completed real work.

If a reader cannot find a source for an assigned owner, date or decision, revise the document or ask a specific clarification question. Record what the reader actually did only after a real check; do not turn these expected distinctions into pass results.

A useful meeting action ledger preserves distinctions that change the next step: who committed, what was only suggested, which condition has not been met and which question still needs an answer. Keep those distinctions in the finished document even when a shorter summary sounds more decisive.