How do I turn meeting notes into checked action items?

Watch the briefing

Watch the full video on YouTube

The short answer

Extract action, owner, deadline and uncertainty; check against notes.

Worked example

FICTIONAL EXAMPLE; outputs ILLUSTRATIVE, not model-generated

What this does not establish

Original fictional inputs, mock outputs and editorial diagrams; no personal records, borrowed screenshots or actual model tests.

Full briefing transcript

Your meeting notes say someone should collect compost, and the planting morning might be October third. A polished action list says Joel will collect it by that date. That looks useful, but it contains two commitments the notes never made. The first check is simple: separate the action from its owner, its deadline, and what is still uncertain. Empty information should stay visibly unresolved.

Here are six invented garden club notes. Maya will count spare seed trays by September twenty second. Joel will ask the library about courtyard availability, with no deadline agreed. Compost needs collecting, but its owner is undecided. October third is a tentative planting date, pending courtyard confirmation. Priya will draft an invitation after that confirmation. Members also liked last year's sunflower display, without asking for follow up.

Ask for an action table with four fields: action, owner, deadline, and uncertainty. Add a source note identifier to each row. Request separate sections for planning decisions and background. Say explicitly: preserve tentative dates and dependencies; do not assign missing owners or deadlines. This instruction makes the intended result inspectable. It does not guarantee that a system will follow every rule, so the comparison with the notes still matters.

Our flawed table is an illustrative example written for this lesson, not output from a named AI tool. It assigns compost to Joel and gives the invitation an October third deadline. Trace those entries backward. Joel's name belongs to the courtyard enquiry, not compost collection. October third belongs to a possible event, not an agreed deadline. Remove both unsupported transfers instead of polishing their wording.

The corrected table keeps Maya's tray count and September twenty second deadline. Joel's courtyard enquiry has no agreed deadline. Compost collection has no assigned owner or agreed deadline. Priya's invitation has no agreed deadline and retains its dependency on courtyard confirmation. Put the tentative planting date in the planning section. Put the sunflower comment in background. All six notes are accounted for without making all six into tasks.

Review row by row rather than judging the list by how organized it looks. Can every action be traced to a note? Does each named owner belong to that action? Is a deadline explicitly agreed, or merely discussed elsewhere? Have words such as might and after survived? Then take unresolved assignments to the meeting organizer. A draft can expose the decision needed; it cannot appoint someone or confirm the courtyard.

Extract action, owner, deadline and uncertainty; check against notes. Keep the source identifiers until review is finished, because they make corrections easier to trace. The useful result is not a table with every box filled. It is a table that faithfully separates commitments from open decisions. Next, we will summarize a short policy without losing the exception that changes how its main rule applies.