Prompier
ApprovedProductivitymeetingstranscriptnotes

Meeting transcript to structured notes

PL by Prompier Library ☆☆☆☆☆ New Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.

About this prompt

Converts a raw meeting or interview transcript into a clean page with summary, decisions, action items and open questions. Use after calls when you need shareable notes quickly.

Prompt text

You are an expert note-taker. Goal: convert a raw transcript into a well-organized page that someone who missed the meeting can use. Inputs: - Transcript text: {{transcript}} - Meeting purpose and attendees: {{purpose_and_attendees}} - Audience for the notes: {{audience}} - Anything to leave out (private or off-topic): {{exclusions}} Steps: 1. Skim the transcript to find the topics, speakers and the order of discussion. Transcripts often have errors; where a name or term looks wrong, mark it with a question mark rather than silently correcting it. Ask at most 3 questions only if the purpose is unclear. 2. Write a 3-5 sentence summary of what the meeting was about and what was concluded. 3. Group the discussion by topic with brief bullets that capture positions and reasons. 4. Pull out decisions exactly as made. If something sounded like a decision but was not confirmed, put it under open questions. 5. List action items with owner, task and due date. Use "unassigned" or "no date given" when the transcript does not say. 6. Remove filler, small talk and anything listed in the exclusions. 7. Keep a clear visual hierarchy: headings, short bullets, a table for actions. Output format: - Title and date placeholders - Summary - Discussion by topic - Decisions - Action items table: owner | task | due - Open questions and risks Quality bar: never invent decisions, owners or dates; keep quotes short and only when exact; use neutral wording for disagreements; keep the whole page under one screen where possible.

Variables

4 variables
VariableWhat to enterExampleDefault
{{transcript}}Paste the meeting transcript[00:02] Priya: Thanks all. First item is the Q3 hiring plan. [00:04] Tom: We need two...—
{{purpose_and_attendees}}What the meeting was for and who attendedMonthly ops review; Priya (ops lead), Tom (finance), Lena (HR)—
{{audience}}Who the notes are forThe wider ops team who missed the call—
{{exclusions}}Anything to leave outLeave out the salary discussion and the small talk—

Try it

Live preview
Paste the meeting transcript
What the meeting was for and who attended
Who the notes are for
Anything to leave out
Your finished prompt
You are an expert note-taker. Goal: convert a raw transcript into a well-organized page that someone who missed the meeting can use. Inputs: - Transcript text: {{transcript}} - Meeting purpose and attendees: {{purpose_and_attendees}} - Audience for the notes: {{audience}} - Anything to leave out (private or off-topic): {{exclusions}} Steps: 1. Skim the transcript to find the topics, speakers and the order of discussion. Transcripts often have errors; where a name or term looks wrong, mark it with a question mark rather than silently correcting it. Ask at most 3 questions only if the purpose is unclear. 2. Write a 3-5 sentence summary of what the meeting was about and what was concluded. 3. Group the discussion by topic with brief bullets that capture positions and reasons. 4. Pull out decisions exactly as made. If something sounded like a decision but was not confirmed, put it under open questions. 5. List action items with owner, task and due date. Use "unassigned" or "no date given" when the transcript does not say. 6. Remove filler, small talk and anything listed in the exclusions. 7. Keep a clear visual hierarchy: headings, short bullets, a table for actions. Output format: - Title and date placeholders - Summary - Discussion by topic - Decisions - Action items table: owner | task | due - Open questions and risks Quality bar: never invent decisions, owners or dates; keep quotes short and only when exact; use neutral wording for disagreements; keep the whole page under one screen where possible.

Sample output

Summary: The team reviewed the launch timeline and agreed to move the release by one week to finish testing. Pricing was not decided. Discussion - Launch: testing found two blocking issues; fix estimated at 3 days (per Priya) - Pricing: two options discussed, no agreement Decisions - Release moves from 12 June to 19 June | Owner | Task | Due | | Priya | Fix the two blocking issues | no date given | | unassigned | Draft customer notice | before release | Open questions: Which pricing option will be proposed? "Marcus" or "Marcos" (transcript unclear)?

An example the author shared. Your result will differ.

Reviews

No written reviews yet. If you have used this prompt, tell others how it went.