Meeting Transcript to Decision Log and Owner-Dated Action Tracker

Converts raw meeting notes or a transcript into a decision log, an action tracker with owners and dates, and a list of open questions. It separates what was stated from what was inferred, so follow-up is unambiguous.

You get: Summary, decision log table and action tracker table

More like this

The prompt

meeting-transcript-to-decision-log-and-owner-dated-action-tracker.md
Role: You are an experienced chief of staff who writes precise meeting records.

Context: I attended a {meeting_type} with {attendees}. The job to be done is to leave with a reliable record of what was decided, who owns what, and what is still unresolved. The decision your answer supports: whether the group is aligned enough to proceed or needs a follow-up conversation.

Task: Turn the notes or transcript below into a decision log, action tracker, and follow-up message.

Inputs (ask for anything missing before producing output):
- Meeting purpose: {meeting_purpose}
- Attendees and roles: {attendees}
- Raw notes or transcript: {notes}
- Known deadlines or constraints: {deadlines}
- Audience for the summary: {audience}

Workflow:
1. Read the notes and list Assumptions separately (for example, unclear speaker names or ambiguous dates). Do not guess owners or dates; mark them as TBD.
2. Extract decisions. Classify each as Confirmed (explicitly agreed) or Tentative (discussed, not confirmed).
3. Extract action items. For each: task, owner, due date, dependency, and source quote or note fragment.
4. Identify open questions, disagreements, and risks.
5. Check for gaps: actions without owners, decisions without rationale, deadlines that conflict.
6. Draft a follow-up message for {audience}.

Constraints: Concise, professional tone. Do not add decisions that were not discussed. Do not include private data beyond what I pasted. Keep the summary under 150 words.

Output format:
1. Summary (max 150 words)
2. Decision log table: ID | Decision | Status (Confirmed/Tentative) | Rationale | Source fragment
3. Action tracker table: ID | Action | Owner | Due date | Dependency | Source fragment
4. Open questions and risks (bulleted, each with a suggested person to resolve it)
5. Missing information (what I should confirm with attendees)
6. Next actions for me (max 3)
7. Follow-up message draft

Acceptance criteria:
- Every action has an owner and due date or is explicitly marked TBD with a reason.
- Confirmed and Tentative decisions are never mixed.
- Every decision and action traces to a fragment of the provided notes.
- The follow-up message can be sent with at most light editing.

Quality checks (report as a short checklist at the end): no invented facts; owners match attendee list; dates are in a consistent format; nothing in the summary contradicts the tables; ambiguity is flagged, not resolved silently.

Tool-specific instructions: In Claude, long transcripts can be pasted whole; ask it to quote fragments exactly. In ChatGPT, if the transcript is a file upload, tell it to cite the section or timestamp for each source fragment. Use Markdown tables.

Example output

AI-written example

1. Summary
The team met to check readiness for the Mobile App 3.0 launch. A 10% staged rollout is confirmed. The launch date of 2025-06-17 is tentative until the payment retry bug is fixed. One action has no owner. Alignment is partial: proceed with preparation, but hold a 15-minute check-in on 2025-06-06 to confirm the date.

2. Decision log

IDDecisionStatusRationaleSource fragment
D1Roll out to 10% of users in week oneConfirmedLimit support load"Okay, 10% first week, everyone agreed?" / "Yes."
D2Launch on 2025-06-17TentativeDepends on payment fixMarcus: "June 17 works if the retry bug is fixed"

3. Action tracker

IDActionOwnerDue dateDependencySource fragment
A1Fix payment retry bugMarcus2025-06-06None"I'll have the retry bug fixed by the 6th"
A2Draft launch emailDanaTBD (said "next week"; meeting date not given)D2"I can draft the email next week"
A3Update help-center articlesTBD (no one volunteered)TBDD1"Someone needs to update the help articles"

4. Open questions and risks

  • Is 2025-06-17 acceptable for the store listing review? Suggested: Priya.
  • Who owns help-center updates? Suggested: Lee.
  • Risk: if A1 slips past 2025-06-06, D2 falls through and A2 is blocked. Suggested: Marcus.

5. Missing information

  • Exact meeting date, to convert "next week" into a calendar date.
  • Whether Lee's team has capacity for A3.
  • Assumption: "the 6th" means 2025-06-06.

6. Next actions for me

  1. Ask Lee or Priya to assign A3.
  2. Confirm Dana's date for A2.
    3.
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Remove sensitive or personal details before pasting. If the transcript has no speaker labels, say so in the notes so owners are marked TBD instead of guessed. Works for stand-ups, client calls, and planning sessions.

Questions about this prompt

More in Productivity

Meeting Notes to Decisions, Action Items and Follow-Up Email

Extracts decisions, owned and dated action items and open questions from meeting notes, then drafts a follow-up email.

Email Thread Summary and Forward-Moving Reply

Summarizes a long email thread into asks, agreements and pending items, then drafts a reply that moves it forward.

Brain Dump to Weekly Plan with Top 3 Outcomes

Turns a messy brain dump into a realistic weekly plan with three outcomes, time blocks and a drop or delegate list.

Brutally Honest Red Team for Your Plan or Idea

Stress-tests a plan with five strong objections, hidden assumptions, the likeliest failure path and the evidence that would change the verdict.

Doctor Appointment Prep Sheet: Symptom Timeline and Questions

Organizes rough symptom notes into a dated timeline and a prioritized question list for your appointment, without any diagnosis.

Productivity Tool Selection: Source Discovery, Evidence Review, and Citation Table

A research workflow to choose between candidate productivity or automation tools. It plans online source discovery, structures evidence review in a citation table, and ends in a decision memo without claiming live browsing took place.

Realistic Day-by-Day Trip Itinerary Grouped by Neighborhood

Builds a neighborhood-clustered itinerary with downtime and rainy-day backups that fits your budget and travel style.

Smart Packing Checklist: Carry-On vs Checked Bag

Creates a trip-specific packing checklist split between carry-on and checked bag, with commonly forgotten items flagged.

Weekly Capacity Plan with Commit, Defer, Delegate, Drop Table

Turns a messy task list, fixed commitments, and available hours into a realistic weekly plan. It also produces a trade-off table that supports the decision on what to commit to, defer, delegate, or drop.

Weekly Family Dinner Plan with Aisle-Sorted Grocery List

Plans seven budget-aware dinners with a grocery list sorted by aisle and a clear plan for using leftovers.

Weighted Decision Matrix with Pre-Mortem on the Winner

Guides you through criteria and weights, scores each option in a table, then runs a pre-mortem on the top choice.

AI Paper Explainer with Evidence Table and Practical Takeaways

Turns a pasted AI paper abstract or text into a plain-language explanation of what is new, how it was tested, its limits and what to do with it.