AI Field Manual
FM-PM-01 · Guide

Project Management  ·  Fundamentals

Turn meeting notes into decisions, actions and owners

The meeting ran fifty minutes. Eleven people spoke, three topics went sideways, and somebody said "let's take that offline" four times. Tomorrow, two attendees will remember a decision differently and a third won't remember it at all. This guide turns notes or a transcript into a record people can act on, and makes AI show its uncertainty instead of papering over it.

Status
Published
Reading time
About 13 minutes
You'll need
Your notes or a meeting transcript, the attendee list, the agenda, and an AI assistant your organization approves for meeting content
Last reviewed
November 2026
Before you start

What AI is for here, and what it isn't

A meeting record has one job: to let people who were there, and people who weren't, act on the same understanding. AI is good at the clerical part of that: pulling statements about decisions and tasks out of a long, messy transcript, grouping them by topic, and noticing when an action has no owner or no date. It's bad at the part that matters most, which is knowing what was actually decided. People hedge, agree tentatively, change their minds two topics later, and nod without committing. A transcript records words, not agreement.

So the AI drafts and you confirm. Nothing it labels a "decision" goes out until you've checked it against your own memory of the room, and anything ambiguous goes back to the people involved as a question, not into the record as a fact.

Step 1

Decide what the record is for

Different meetings need different records. Before you open the transcript, write down:

  1. The meeting type. A steering committee needs decisions and escalations. A working session needs tasks and open questions. A status meeting needs changes since last time. A kickoff needs agreements about scope, roles and ways of working.
  2. The audience. Attendees only, or also people who weren't there? A record for absentees needs more context and fewer shorthand references.
  3. What already exists. The previous meeting's open items, the current action log, the risk register. A record that ignores last week's open items quietly drops them.

"Steering committee, 18 Nov. Audience: attendees plus the CFO, who missed it. Carry forward three open items from 4 Nov. Focus on decisions and budget-related actions." That sentence becomes the context block of your prompt.

Step 2

Prepare the source material

A transcript and a set of notes are different raw materials.

  • Transcripts are complete but noisy: crosstalk, filler, misattributed speakers, words the transcription got wrong. Product names, acronyms and people's names are the most common errors. Fix the ones you notice before you send it; the model will otherwise faithfully repeat them.
  • Your own notes are selective but already filtered by judgment. They're often the better source for decisions, while the transcript is better for exact wording and who said what.

If you have both, give the model both and say which one wins when they conflict. Usually it's your notes for decisions, the transcript for wording.

Trim the material to the meeting itself. Remove the five minutes of waiting for people to join, side conversations that weren't part of the meeting, and any sensitive segment you excluded under the data-handling note. Keep timestamps if you have them; they make checking much faster.

Step 3

Separate decisions, actions and discussion

The most useful record keeps four kinds of content apart, because people treat them differently:

Type What it is Test
Decision Something the group with authority agreed, which changes what happens next. Could someone act on it without asking again? Did the person who owns the decision agree?
Action A specific task with one owner and a date. Is there exactly one name? Is the deliverable clear enough that you'd know when it's done?
Open question Something raised but not resolved. Does it have an owner who'll bring an answer back, and when?
Discussion Context, options considered, concerns raised. Does anyone need this to understand a decision? If not, leave it out.

Most bad meeting records fail by mixing these. "We discussed moving the go-live" isn't a decision. "Marketing to look into it" isn't an action: it has a team instead of a person, and no date.

Step 4

Ask for a record, and for its uncertainty

The meeting record prompt
You are helping a project manager produce a meeting record from the
notes and transcript below. I will confirm everything before it is
sent. Your job is to extract and organize, not to decide.

MEETING: [type, date, time zone]
PURPOSE OF THIS RECORD: [what readers need to do with it]
ATTENDEES: [names and roles]
OPEN ITEMS CARRIED FORWARD: [from the previous record]
SOURCES: [my notes] and [transcript]. If they conflict, my notes win
for decisions; the transcript wins for exact wording.

PRODUCE:
1. DECISIONS: each with who made or approved it, the exact words that
   support it (quote with timestamp if available), and its effect.
2. ACTIONS: one owner, a due date, and a definition of done. If any of
   those is missing, include the action anyway and mark the gap.
3. OPEN QUESTIONS: with who raised them and who should answer.
4. CARRIED-FORWARD ITEMS: status of each one from the previous record.
5. NEEDS CONFIRMATION: anything that sounded like agreement but may
   not have been: tentative language, objections not resolved,
   decisions reopened later in the meeting, owners who didn't accept.

RULES: Do not invent owners, dates or decisions. "Someone should" is
not an owner. Do not resolve contradictions; show both statements.
Keep discussion summaries to one line per topic. Use plain language.

The "needs confirmation" list is the most valuable part of the output. It's where the model shows you the places your memory of the meeting should overrule its reading of the words.

Step 5

Confirm before you send

Check the draft against your own understanding, item by item:

  • Every decision: was it actually agreed by the person with authority? A tentative "I think that works" from a junior attendee isn't a sponsor's decision.
  • Every action: did the named owner accept it in the meeting? Assigning someone in the minutes who wasn't there to agree is how actions get ignored.
  • Every date: was it stated, or did the model infer "next week"? Replace inferred dates with questions.
  • Every "needs confirmation" item: resolve it yourself, or send it as a question to the people involved before the record goes out.

When you're unsure, ask. A short message ("I've recorded that we're moving go-live to 3 March, pending Priya's confirmation of the vendor date. Correct?") costs less than a week of people working from different assumptions.

Step 6

Worked example: the steering committee that almost decided

Fictional meeting. A steering committee for a CRM migration discusses whether to delay go-live. The transcript includes these lines:

Dana (sponsor): I'm not comfortable going live before the data cleanup is done.

Marcus (vendor lead): We could push to March 3, but that affects our February resourcing.

Dana: Let's plan on March 3, then. Marcus, can you confirm the resourcing?

Priya (PM): I'll update the plan.

(Twenty minutes later)

Raj (finance): If we slip to March, we're into the next quarter's budget. Has anyone checked that?

Dana: Good point. Let's not lock anything until Raj has looked at it.

A careless AI draft: "Decision: go-live moved to March 3. Action: Priya to update the plan."

That record is wrong in a way that matters. The sponsor's later remark reopened the decision. The draft also misses two actions: Marcus confirming resourcing, and Raj checking the budget impact.

A good draft:

Needs confirmation: Go-live move to 3 March. The sponsor proposed it (12:14) but later said not to lock anything until finance confirms the budget impact (12:36). Recorded as proposed, not decided.

Actions:

  • Marcus: confirm vendor resourcing for a 3 March go-live. Due: not stated, confirm.
  • Raj: assess the budget impact of moving go-live into Q2. Due: not stated, confirm.
  • Priya: update the plan once the date is confirmed. Due: after the two actions above.

Open question: Who makes the final call on the date once finance reports back, and by when?

The good draft is less satisfying to read, because it admits the meeting didn't finish its job. That's exactly what a project manager needs to know.

Step 7

Send it, and close the loop

Send the record within a day, while people still remember the meeting. Put decisions and actions first; most readers stop after those. Then move every action into your tracker, so the record isn't the only place it lives.

Meeting record template
[Meeting name] — [date, time zone]
Attendees: [names]          Absent: [names]
Purpose: [one line]

DECISIONS
1. [decision] — decided by [name]. Effect: [what changes]

ACTIONS
ID     Action                        Owner     Due        Done when
[ID]   [action]                      [name]    [date]     [definition]

NEEDS CONFIRMATION (reply by [date])
- [item] — [what's unclear] — [who needs to confirm]

OPEN QUESTIONS
- [question] — raised by [name] — answer owed by [name], [date]

CARRIED FORWARD FROM [previous date]
- [item] — [status]

AI assistance: draft prepared from notes/transcript with [tool];
decisions and actions confirmed by [your name].

What stays with you: what was actually decided, which ambiguities you resolve yourself and which you send back as questions, and who you'll chase when an action slips.

Esc

Saved in this browser

Reading list

Contents

Reference

Keyboard shortcuts

/ or Ctrl K
Search the manual
↑ ↓
Move through search results and index entries
Enter
Open the selected result
← →
Switch discipline tabs; previous / next entry in a workflow card
Esc
Close any dialog
?
Show this list