Business Ops & Client Comms

Verified against ChatGPT · 2026-08-09

Extract action items from raw meeting notes that name a real owner instead of a vague "team will follow up"

Pastes messy meeting notes or a transcript and gets back a clean action item list where every task has a specific owner, a real deadline, and a note on what happens if it's not tracked.

ChatGPT (GPT-5.1)4 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are extracting action items from meeting notes I'm pasting below. My recurring problem is that action items come out of meetings vague — "team will follow up," no date, no name — and then nothing happens because nobody actually owns them.

RAW MEETING NOTES OR TRANSCRIPT
Rough bullet notes from a 30-minute product sync, mixing decisions and casual asides.

ATTENDEES AND THEIR ROLES
Priya (eng lead), Marco (design), Sam (PM, me).

EXISTING TRACKING SYSTEM
Linear tickets under the 'Q3-launch' project.

DEFAULT DEADLINE IF NONE WAS STATED
One week from the meeting date unless otherwise specified.

Read through the notes and pull out every action item, whether it was stated explicitly ("John will send the deck") or only implied (someone said they'd "look into" something without a formal commitment). For each one, assign a specific named owner using the attendee list — never write "team" or "someone" as an owner; if the notes genuinely don't make clear who owns it, flag that explicitly as "owner unclear" rather than guessing a name, and list it separately so it doesn't get silently lost among properly-owned items. If a deadline was stated, use it; if not, apply the default deadline rule and say you did so. For each action item, add a one-line note on the actual dependency or blocker mentioned in the notes, if any was mentioned — this is often the difference between an item that will get done and one that's quietly waiting on something else. Flag any action item that sounds like a repeat of something from a previous meeting (implied by phrasing like "still need to" or "following up again on") since a recurring undone item is a signal worth surfacing on its own, not just another row in the list.

WHAT NOT TO DO
Do not summarize the meeting's discussion or decisions in prose — only extract action items. Do not merge two distinct action items into one line even if they were mentioned in the same sentence.

OUTPUT FORMAT
A table: Action item, Owner, Deadline, Dependency/blocker, Repeat flag (yes/no). Then a separate short list of any "owner unclear" items needing my attention before they can be assigned.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

The single biggest reason action items from meetings don't get done is that they were never assigned to an actual person in the first place, and a model asked generically to "extract action items" will faithfully reproduce whatever ambiguity was in the source notes — if the notes say "team will follow up," the naive extraction just repeats that phrase, preserving the exact ambiguity that caused the problem. Explicitly forbidding "team" or "someone" as an owner and requiring either a real name from the attendee list or an explicit "owner unclear" flag forces a binary check GPT-5.1 handles reliably (is there a name attached, yes or no) rather than a fuzzier judgment call about whether an owner is "clear enough," and separating unclear items into their own list means they can't hide inside a table that otherwise looks fully actionable. Explicitly including implied commitments ("look into" phrasing) alongside stated ones matters because meeting notes rarely record commitments in a uniform grammatical form, and a model that only pattern-matches on explicit "X will do Y" phrasing will systematically miss the softer, hedged commitments that are often the ones most likely to be forgotten precisely because they were never stated forcefully. The repeat-flag instruction gives the model a genuinely useful signal to surface: an item phrased as "still need to" or "following up again" indicates the same task survived at least one previous meeting undone, which is exactly the kind of pattern a busy person skimming a flat action-item list would miss but that changes how the item should be handled — it needs a harder deadline or an escalation, not just another polite restatement.

What you get back

| Action item | Owner | Deadline | Dependency | Repeat | |---|---|---|---|---| | Send updated onboarding deck to sales | Priya | Aug 22 | Waiting on final design assets from Marco | No | | Follow up on API rate-limit issue | Owner unclear | Aug 22 (default) | None mentioned | Yes — flagged "again" in notes |

Owner unclear: API rate-limit follow-up — notes don't say who raised or owns this.

Verified against

ChatGPT GPT-5.1 · 2026-08-09

Changelog

  • 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.

EXPLORE CUSTOM SOFTWARE
All Business Ops & Client Comms prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY