Business prompt · Built for Apollo

Extract decisions and owners from a meeting

Pulls the decisions and their owners out of a raw transcript, and separately lists what was discussed at length but never actually decided.

The prompt

You are reading the raw transcript of a work meeting. It is unedited, people talk over each other, and not everything said was agreed.

Transcript:
[PASTE THE TRANSCRIPT]

Meeting was about: [ONE LINE OF CONTEXT]
People in the room and their roles: [NAMES AND ROLES, OR "UNKNOWN"]

Produce three sections, in this order.

1. DECISIONS
Only things that were actually settled. For each: the decision in one sentence, who owns it, and the date or deadline if one was said. If no owner was named, write "no owner named" rather than guessing one.

2. OPEN — DISCUSSED BUT NOT DECIDED
Anything that took real time and ended without a decision. For each: what the disagreement or gap was, and what would have to be known or agreed to close it. This section matters more than the first one, so do not compress it.

3. STATED AS FACT, NOT VERIFIED
Any number, date, commitment, or claim about another team that someone asserted and nobody checked in the room.

Rules: quote or closely paraphrase the transcript rather than smoothing it. Do not invent an action item that nobody proposed. If the transcript is too garbled in a place to tell whether something was decided, say so and put it under OPEN.
Try in Rekdan

Replace the outlined parts before running

  • [PASTE THE TRANSCRIPT]
  • [ONE LINE OF CONTEXT]
  • [NAMES AND ROLES, OR "UNKNOWN"]

When to use this

The reason meeting notes are painful is not summarising — it is that the useful information is the part the meeting did not resolve. Ask plainly for a summary and you get a tidy narrative of what was said, which reads well and tells you nothing you can act on. Everyone in the room already knows what was said.

This prompt splits the transcript three ways. Decisions with owners are the part you circulate. The open items are the part you actually work from, and they are the part a plain summary silently folds into the narrative — an argument that ran fifteen minutes and ended in "let's come back to it" gets one neutral sentence and vanishes. The third section catches the numbers people say out loud with confidence and nobody checks, which is where a surprising share of bad decisions start.

How to use it

  1. Paste the transcript raw

    Do not tidy it first. Interruptions, half-sentences, and someone changing their mind mid-paragraph are signal — the difference between a decision and a suggestion is usually in exactly that mess.

  2. Give the roles if you have them

    Ownership is the field that goes wrong most often. Without roles the model assigns an action to whoever spoke last about it, which is frequently the person least able to do it.

  3. Read section two first

    Section one is the record. Section two is the work. If section two is empty in a meeting that ran an hour, either the meeting was unusually decisive or the transcript is incomplete.

  4. Send it back for what it missed, not for a rewrite

    If a decision is misattributed, say so and ask it to recheck that one item against the transcript. Asking for the whole thing again tends to produce a differently-wrong version.

Variations

For a call with a client or vendor

Read this transcript of an external call and separate what we committed to from what they committed to.

Transcript: [PASTE THE TRANSCRIPT]
Our side: [NAMES]
Their side: [NAMES]

Produce:
1. WHAT WE COMMITTED TO — including anything phrased loosely ("we can probably have that by Friday") that they could reasonably hear as a commitment.
2. WHAT THEY COMMITTED TO — same standard.
3. ASSUMED, NOT AGREED — anything either side spoke about as settled that was never actually confirmed by the other.
4. WHAT I SHOULD PUT IN THE FOLLOW-UP EMAIL to make 1–3 unambiguous.

Flag anything in section 1 that was said casually but would be expensive to honour.

For a long recurring meeting you were not in

I missed this meeting and need to know what changed, not what was discussed.

Transcript: [PASTE THE TRANSCRIPT]
What I own: [YOUR AREA]

Produce, in this order:
1. WHAT CHANGED FOR MY AREA — decisions that alter what I am doing, with the reasoning given.
2. WHAT I AM NOW EXPECTED TO DO, and by when, and who thinks so.
3. DECIDED WITHOUT ME — anything settled that touches my area where nobody from it spoke.
4. Everything else, in under five lines total.

If section 3 is not empty, quote the passage so I can see how it happened.

Where it falls short

  • When the transcript is auto-generated and speakers are unlabelledOwner attribution becomes guesswork, and a confident wrong owner is worse than none. Either label the speakers first, or run it and treat every owner as unverified.
  • When the meeting was mostly a decision made before it startedSome meetings exist to announce, not to decide. The open-items section will be thin and that is accurate — do not read the thinness as the prompt failing.
  • For anything that will be relied on as a formal recordBoard minutes, disciplinary meetings, and regulated processes have their own rules about what a record is and who approves it. This produces working notes, not minutes.
Extract decisions and owners from a meeting — AI Prompt · Rekdan