Turning meeting notes into a task list with ChatGPT

Where meeting notes lose agreements

After a meeting, one list may contain a promise to send a design, a discount idea and a question nobody took ownership of. Simply asking for a plan makes all three easy to read as agreed tasks, especially when the answer already has names and tidy deadlines.

ChatGPT can analyze existing meeting notes. We need two distinct parts: what has been agreed and what remains to clarify. Each task retains a short source reference showing where its action, owner and deadline came from.

Keep statements that change the meaning

Consider a work meeting about updating a product card. In the notes below, both 'decided' and the qualification at the end matter. Reducing everything to 'layout — Ira — Thursday' before analysis loses the final clarification.

• [01] We decided to update the card without a new filter system.
• [02] Ira: 'I will send the card layout by Thursday.'
• [03] Lev: 'I will check the mobile layout once I receive the design.'
• [04] The card needs a size chart. We have not decided who will compile it.
• [05] Oleg suggested a bundle discount. The decision was postponed.
• [06] Ira clarified at the end: 'I cannot confirm the layout deadline yet.'
• [07] We are keeping the old photographs.

Prompt for analyzing meeting notes

Number your note excerpts as in the example. Numbers are easier to locate than long summaries. Preserve statement order, speakers and words such as 'if', 'after' and 'possibly'. If the notes contain internal information, first check whether you may send it to the chosen service.

Paste the assignment into ChatGPT first, then the numbered notes. Do not demand that every cell be filled at any cost: 'not specified' is more useful here than a plausible guess.

Analyze the meeting notes. Use only text after the line 'NOTES'.

First list the decisions made. Then create a table of agreed tasks: action | owner | deadline | dependency | source evidence | clarification needed. For evidence, give the excerpt number and a short exact quote.

Do not turn discussion or a suggestion into an assignment. Assign an owner only from an explicit assignment or the participant's own promise; being the author of an idea does not itself imply responsibility. If information is missing, write 'not specified'. Keep deadlines as written in the notes; do not calculate them from dependencies. Consider later clarifications together with earlier statements; explicitly flag contradictions or unconfirmed deadlines.

Separately list open questions and proposals without a decision. For each question, state what needs clarification. Do not propose your own deadlines or owners.

NOTES
[paste notes with numbered excerpts]

What should remain from our example

Check disputed details rather than the table's appearance. Each row should retain the same degree of certainty as the conversation.

• Excerpts [01] and [07] record decisions about the scope of the update. They do not establish who will perform all the work.
• The layout remains Ira's task because she explicitly promised to send it. But Thursday cannot be presented as confirmed after clarification [06]. The row needs a deadline question and references to both statements.
• Lev has a task to check the mobile layout. 'Once I receive the design' is a dependency on other work, not a calendar deadline. The notes give no date for the check.
• No owner was selected for the size chart in [04]. Ask who will prepare it and by when; do not automatically assign it to Ira because she owns the layout.
• The discount in [05] remains a proposal without an agreed decision. There is no basis for assigning Oleg a task to 'launch the discount'.

Cross-check in both directions

First trace the answer back to the notes. For each task, locate the cited quote and verify that it exists. Then check action, name and deadline separately. A quote may confirm work on the layout without confirming the date placed beside it in the table.

Now open the source and work in reverse: did every explicit promise and decision reach the answer? This catches omissions. Reread negations, conditions and final clarifications separately. They are often shorter than the main discussion, but determine whether a task can enter work.

If you find an error, identify the exact row. 'Check more carefully' does not explain what went wrong. Return the excerpts whose connection the model lost.

The layout row lists Thursday as an agreed deadline. Compare [02] and [06]. Correct only this row: preserve Ira's promise to prepare the layout, mark the deadline as unconfirmed and add a clarification question. Do not assign a new date. Then check other deadlines for the same substitution.

Add to the tracker after clarifying the gaps

Send participants short questions: 'Ira, what layout deadline are we recording?', 'Who is taking the size chart?', 'Lev, when can you finish checking after receiving the design?'. Do not phrase a question as if its answer were agreed: 'Confirm Thursday' pushes the earlier version that Ira withdrew.

Add the answers to the original notes in a separate block. Ask for only affected rows to be updated and for the changes to be shown. Keep the old Thursday statement in the history, but do not copy it into the current deadline field.

In a tracker, use a short action-and-object title: 'Check the product card's mobile layout'. Include the dependency on the design and a link to the notes in the description. If the owner or deadline is unconfirmed, leave that field blank or use the team's waiting status. A guessed date looks like a commitment and soon takes on a life separate from the conversation.