Summarize meetings with AI: decisions and action items

To summarize a meeting with AI, give the tool your notes and ask it to separate agreed decisions, action items, and open questions. Each action should include the person responsible, the deadline, and the relevant source passage; details missing from the notes should remain unresolved. Check the result against the notes before sharing it with your team.

This workflow helps when you need to turn a long meeting record into a clear answer to “Who does what next?” Start with text notes that you paste into a ChatGPT conversation.

Separate decisions from suggestions in your meeting summary

“We could try a new form” is a suggestion. “We agreed to use the new form in the pilot” describes a decision. Putting both in the same list can turn a discussed idea into an agreed next step.

Request three separate sections:

• Decisions: what was agreed, including any conditions.
• Action items: what needs doing, who will do it, and when.
• Open questions: what still needs a decision or clarification.

A short paragraph can describe the meeting overall. To continue the work, you still need a separate action list. “The team discussed testing” does not tell you whom to ask for the result.

Prepare notes that let you check the answer

First, read the names, dates, and important terms. If your text came from an audio recording, mark unclear phrases rather than leaving AI to fill them in. A misrecognized name can assign work to the wrong person.

Give paragraphs simple labels: S1, S2, S3. Then ask the tool to attach the relevant label to each conclusion. These are labels you add to make the source easier to check.

Keep only information you have permission to use in this tool. For work notes, follow your organization’s rules and remove unnecessary personal data. If sharing the notes is not allowed, prepare the summary yourself or work in an environment your organization permits.

If your source is a PDF, first make sure the relevant passages can be read correctly. The guide to summarizing PDFs and checking the source can help with that step.

Specify the output format and how to handle missing details

OpenAI’s prompting guide recommends a clear task, sufficient context, and refining the prompt based on the answer. For a meeting, that means specifying the format and what the tool should do with an unknown detail.

Adapt this prompt to your notes:

Create a working summary from the meeting notes below.
Use only information contained in these notes.

Divide the result into four sections:
1. A short summary, no more than three sentences.
2. Agreed decisions, preserving all conditions.
3. An action table: Action | Person responsible | Deadline | Source label.
4. Open questions and suggestions that were not agreed.

If a person or deadline is missing, write “Needs clarification”.
Do not invent names or dates.
Do not present a suggestion as a decision.
Do not turn a conditional date into an unconditional deadline.
Flag conflicting passages separately.
Attach S1, S2, or the appropriate source label to every decision and action.

Start of notes:
[Paste your labeled notes here]
End of notes.

Source labels help you check the answer, but a correct label does not guarantee a correct conclusion. Read the passage it points to yourself.

Example: three action items and one conditional date

The notes below are a fictional learning example. The names and dates are part of the exercise.

S1. Meeting: October 9, 2026. We agreed to use the new registration
form for the pilot test and invite five participants.

S2. Nino will prepare a draft of the form questions by October 12.
Giorgi will check the error in the existing form; the deadline
for his task was not discussed.

S3. Salome suggested adding an SMS reminder.
We did not make a decision on this issue.

S4. We will start the pilot on October 14 only if the error check
is completed by October 13.
Otherwise, we will reconsider the start date.

An action table consistent with this source looks like this:

The decisions should include using the new form and inviting five participants. Starting the pilot on October 14 must retain its condition: the check must finish by October 13; otherwise, the date will be reconsidered.

Giorgi’s task deadline still needs clarification. October 13 is tied to the condition for starting the pilot, while S2 explicitly says his task deadline was not discussed. Preserve that distinction in the summary and clarify the deadline with the participant.

The SMS reminder is an open suggestion. It has neither agreed status nor an assigned person. These notes do not establish an action for Salome to add it.

Check the AI meeting summary with four questions

OpenAI’s explanation of answer accuracy notes that ChatGPT can present incorrect information confidently. Check important details against the source even when the answer reads well.

Ask four questions about every decision and action:

1. Where does it say that? Does the cited passage actually contain this information?
2. Who will do it? Is the name in the notes, or did the tool infer it from someone’s role?
3. When? Was the deadline agreed, conditional, or never discussed?
4. What is its status? Is this a decision, a suggestion, or a question still awaiting an answer?

If you find an error, request a specific correction:

S2 says the deadline for Giorgi’s task was not discussed.
Change his deadline in the table to “Needs clarification”.
Keep October 13 only in the description of the condition in S4.
Preserve the other action details unchanged.
Then list which row you changed.

Check the corrected table again. A model reviewing its own answer is not independent confirmation.

When a manual summary or a standing template works better

If a meeting produced only two clear actions, writing them down yourself may be simpler. Processing a long record also requires time to check the AI output.

For recurring meetings, prepare a template in advance: decision, action, person responsible, deadline, and open question. Filling these fields during the meeting leaves fewer unclear details for a later summary.

For a long or contradictory record, extract and check decisions first, then move on to actions. This lets you verify each response separately. If the notes contain conflicting agreements, clarify the final answer with the participants.

Frequently asked questions about AI meeting summaries

Can AI choose a person when no one was assigned?

You can separately ask it to suggest a possible person, but that is an assumption. Include only an agreed name in the confirmed action list and leave the rest for clarification.

What if the notes say “next week”?

Before writing an exact date, check the meeting date and what the participant meant. If no specific day was agreed, preserve the original wording and mark the exact deadline as needing clarification.

Can I share the summary straight away?

First, check names, deadlines, and the status of decisions. In the text you share, clearly mark open questions and ask the relevant participant to answer them.

In this example, the first question to clarify is: who will invite the five participants, and by when? A question like this turns the meeting summary into a record you can use to continue the work.