This AI prompt coaches you from your meeting transcript. It picks a moment where you could have done better and gives you something else you could have said instead.
It also gives you a summary, the tasks with real due dates, what was left open and a follow-up message ready to send.
Use it after a sales call, a client meeting or a call with your boss.
Why have AI coach you on your own meeting
A prospect asked me how long a past website took to develop, start to finish. I went through my email and rambled on about the dates for a full minute. The answer should have been 2 sentences, stated in 7 seconds.
The person you’re in a meeting with won’t tell you that you rambled. This prompt will.
How to use this meeting transcript prompt
Paste the prompt into a new chat. It asks you 3 questions, one at a time:
- What was the meeting for, and what date was it?
- Which speaker in the transcript is you?
- Paste the transcript.
This prompt is not about getting ready for the meeting. The meeting prep prompt does that. No transcript, just your memory? Use the voice note summary instead.
Where to get the transcript
I’ve partnered with Granola. Download it on your computer through my link and sign up with your work email. Have your first meeting on your computer, and you get the Business plan free for a month.
At the time of this writing, the free plan gives you a transcript of every meeting and keeps 30 days of history. No bot joins your call.
Business is $14 a month. It sends your notes to Notion, HubSpot, Attio and Zapier, and uses more advanced AI models. Before a client meeting, it builds a short brief from your past notes with that person or company, ready when you open or join the meeting.
Sign up for Granola and keep the free plan in your back pocket. You don’t have to use it, but maybe you’ll use it later.
The prompt that coaches you, summarizes your meeting and lists your tasks
I just had a meeting and I want a clear write-up of it. Ask me these 3 questions one at a time, and wait for my answer before you ask the next one:
1. What was the meeting for, and what date was it?
2. Which speaker in the transcript is me?
3. Paste the transcript.
If I skip a question or only answer part of it, ask that part once more. If I still don't answer, write "Not said" wherever you needed it. Never guess a date.
Then give me the write-up below. Use only what someone said in the transcript. Don't add your own reading of it, and don't make a task, a deliverable or a number bigger or more specific than the words the speaker used. If something wasn't said, write "Not said".
Your answer starts with "## 1. Summary". Write nothing before it: no notes, no drafts, no copy of the transcript.
Layout rules for the whole write-up:
- Use the 6 headings below, numbered, in this order.
- Short lines. No paragraph longer than 3 sentences.
- Put a blank line between every item so it is easy to scan.
## 1. Summary
4 sentences at most. What was decided, what changed, and what is stuck. Every sentence has to match something a speaker said. Don't add describing words they didn't use.
## 2. Tasks
First line: the meeting date and its weekday, for example "Meeting: Monday, October 19, 2026". If I gave no date, write "Meeting date: Not said" and put "Not said" in every Due cell.
Then a table with these columns: Task | Owner | Due | Notes
- Task: describe it in the words the speaker used.
- Owner: the person who agreed to do it. If nobody clearly took it, write "Unclear".
- Due: turn the speaker's words into a date, counted from the meeting date. "By Thursday" becomes the next Thursday after the meeting. If they said "soon" or "ASAP" or gave no time, count 3 business days after the meeting, Monday to Friday only, and mark it "(my guess)".
- Notes: leave it blank unless there is something worth adding. If you quote a speaker here, the quote must be about this task.
- One row per task. Leave out anything that was only discussed and never agreed.
## 3. Left open
Things someone asked or raised that never got an answer or a decision anywhere in the meeting. Up to 3.
Before you list one, read the rest of the transcript after it. If it gets answered or settled later, even many minutes later, it is not left open. Leave it out.
For each one:
Moment: the quote, word for word, with who said it and the timestamp of the turn it is in.
What's missing: 1 sentence.
If nothing was left open, write "Nothing left open."
## 4. What was said that matters
2 or 3 quotes. For each one, use this layout:
> "The quote, copied word for word."
> (Who said it, timestamp)
Why it matters: 1 sentence.
## 5. How I did
Only about me, the speaker I named.
**What I did well**
Moment: the quote from the transcript, with the timestamp.
Why it worked: 1 sentence.
**What I could do better** (1 or 2 of these)
Moment: the quote from the transcript, with the timestamp.
Better line: what I could have said instead.
What it gets me: 1 sentence.
If a better line uses a number, a date or a fact, it has to come from something said in the meeting. Put where it came from in brackets after it, for example (from 44:50).
## 6. Follow-up message
If anyone is waiting on something from me, write them a short follow-up, under 100 words. Include every task from the Tasks table, with the same date as the table.
Write each task as a normal sentence from me, not the speaker's exact phrase. For example, if the task is "let me do one page for you for your parent website", write "I'll put together one sample page for your parent website."
If nobody is waiting, write "No follow-up needed" and stop.
Before you send the write-up, check each of these. Fix anything that fails, then send:
- The answer starts with "## 1. Summary", with nothing before it.
- Every quote matches the transcript word for word, and every timestamp is the one on that turn.
- Every sentence in the Summary matches something a speaker said, with no added describing words.
- Every date in the Tasks table is counted from the meeting date I gave, with the weekday checked.
- Nothing in Left open gets answered later in the transcript.
- Every task in the Tasks table is in the follow-up, with the same date, written as a normal sentence.
- Every number in "How I did" says where it came from.
Why it works: Every coaching note has to quote a real moment from your meeting, with its timestamp. That stops it from handing you advice that would fit any meeting. The better line can only use facts someone said on the call.
One gap: It coaches you from the words alone, so it doesn’t read sarcasm very well. It might also miss a timestamp.
Simple fix: Check the timestamp in the transcript before you quote it back to anyone.
Prompt writing tips you can use anywhere
Each tip is a line from the prompt above. Copy the line into your own prompts, then read why it’s there.
1. Make every number show where it came from
If a better line uses a number, a date or a fact, it has to come from something said in the meeting. Put where it came from in brackets after it, for example (from 44:50).
An earlier version of this prompt scored how much each person talked. My goal was to see each person’s share of the talk time. The fast models made up the word counts, so I cut that part out.
This line keeps every number tied to the transcript. Add a line like it whenever you ask AI to pull numbers from a report, a contract or a spreadsheet, so each number shows where it came from.
2. Stop it from adding to what was said
Don't add your own reading of it, and don't make a task, a deliverable or a number bigger or more specific than the words the speaker used.
Someone says “I’ll take a look at it,” and AI can write that up as “Review the full proposal by Friday.” This line makes AI write each task the way the person said it, with nothing added. Use it whenever you ask AI to sum up a call, an email thread or your notes.
3. Give vague deadlines a rule
If they said "soon" or "ASAP" or gave no time, count 3 business days after the meeting, Monday to Friday only, and mark it "(my guess)".
Without a rule, “soon” becomes whatever date AI picks. With one, you get the same answer every time, and “(my guess)” shows you which dates to confirm. Use it whenever AI has to turn loose words into a number.
4. End with a checklist
Before you send the write-up, check each of these. Fix anything that fails, then send:
The checklist makes AI go back over its answer before you see it. Each line names one mistake to look for, so it knows what to fix. Add one to the end of any long prompt.
Related prompt: the reminder prompt finds the files you promised to send and forgot.