Meeting Notes Summarizer
1. Overview
The Meeting Notes Summarizer takes a transcript of a meeting, reads the content, and produces two deliverables: a concise written summary of the discussion and a list of actionable items with owners and any due dates.
2. Business Value
- Rapid distribution – Stakeholders receive a quick recap without rereading the full transcript.
- Clear accountability – Action items are extracted with responsible owners, ensuring follow‑up.
- Consistent documentation – Every meeting is captured in a standard format that supports audit trails and knowledge bases.
3. Operational Context
| When should it run | Who uses it | How often |
|---|
| After any meeting where a transcript is created (e.g., staff meetings, project updates, client calls) | Operations Professionals, Team Leads, Project Managers | Each time a meeting transcript is available, typically once per meeting. |
4. Inputs
4.1 Meeting Transcript (PDF)
- Name/Label: Meeting Transcript
- Type: PDF document
- Details Provided: The complete, readable transcript of a single meeting. The document should contain speaker names (or initials), timestamps if available, and any spoken content. No additional files are required.
4.2 Meeting Metadata (Optional)
- Name/Label: Meeting Metadata
- Type: List of single‑level fields (provided as a simple list)
- Details Provided: Information that gives context to the transcript. If any field is not supplied, it will be marked “Not provided” in the final output.
| Field | Description | Example |
|---|
| Meeting Title | The name of the meeting or event | “Quarterly Marketing Review” |
| Meeting Date | Date the meeting took place (YYYY‑MM‑DD) | 2025‑08‑02 |
| Participants | List of attendees, separated by commas | “Alice Smith, Bob Lee, Carla Gomez” |
| Meeting Owner | Person who organized the meeting | “Alice Smith” |
| Meeting Objective | Brief purpose of the meeting | “Review Q3 marketing performance and plan Q4 activities” |
If the Metadata is not supplied, the process proceeds with the transcript alone. Missing fields will be noted as “Not provided.”
5. Outputs
5.1 Meeting Summary
- Name/Label: Meeting Summary
- Contents: A concise paragraph (3‑5 sentences) summarizing the key discussion points, decisions made, and any overall conclusions.
- Formatting Rules:
- Use present‑tense, professional tone.
- Each sentence starts with a capital letter and ends with a period.
- No bullet points or numbered lists.
5.2 Action Items
- Name/Label: Action Items
- Contents: A table of all actionable items identified in the transcript, each with a description, the owner responsible for completing it, and any due date.
- Formatting Rules:
- The table must contain the columns: Action Description, Owner, Due Date (optional), Additional Notes (optional).
- If an owner is not mentioned, write “Unknown.”
- If no date is mentioned, leave the Due Date cell blank.
- Use a short verb phrase to start each action description (e.g., “Prepare quarterly report”).
| Action Description | Owner | Due Date (optional) | Additional Notes (optional) |
|---|
| example | | | |
If no actionable items are found, the “Action Items” section will contain the sentence “No action items identified.”
6. Detailed Plan & Execution Steps
-
Confirm Input Availability
- Verify a PDF file is present and can be opened.
- If a PDF cannot be opened or is empty, stop the process and generate an error message indicating “Transcript not readable.”
-
Extract Transcript Text
- Read the entire PDF content, preserving speaker names and any timestamps.
-
Identify Main Topics
- Scan the transcript for repeated key terms, headings, or speaker cues that indicate major discussion points.
-
Compose Summary
- Draft a paragraph of 3‑5 sentences that:
a. States the meeting purpose (from Metadata if available).
b. Highlights the top 2‑3 discussion points or decisions.
c. Mentions any agreed‑upon next steps.
- Use present tense, formal and professional tone.
-
Extract Action Items
- Search the transcript for sentences that contain:
a. An action verb (e.g., “prepare,” “review,” “schedule”).
b. A named individual or group responsible for the action.
c. An optional deadline (e.g., “by Friday,” “by 2025‑09‑01”).
- For each identified action:
- Record the Action Description (the core task).
- Capture the Owner (the speaker or person mentioned). If unclear, set to “Unknown.”
- Capture Due Date if a specific date or clear timeframe is present; otherwise leave blank.
- Add any extra clarification in Additional Notes (e.g., “see attached slide”).
-
Validate Content
- Ensure the summary contains at least three distinct points.
- Verify each action item has a non‑empty description and an owner.
- Remove duplicate action entries.
-
Format Outputs
- Write the Meeting Summary as plain text.
- Assemble the Action Items table as shown in section 5.2.
-
Deliver Results
- Provide the Meeting Summary followed by the Action Items table.
7. Validation & Quality Checks
- Transcript Readability – Confirm all text is extracted; if any portion is missing, flag the missing segment.
- Summary Coverage – Check the summary includes: (1) purpose, (2) key points, (3) decisions or next steps.
- Action Item Completeness – Each row must have an Action Description and an Owner.
- Date Format – Dates, if provided, must be in YYYY‑MM‑DD format.
- Duplicate Check – No two rows should have identical Action Description and Owner combinations.
- Empty‑Result Handling – If no action items are found, output the sentence “No action items identified” and skip the Action Items table.
- Error Reporting – If the PDF cannot be read or is empty, output an error message and produce no summary or action items.
8. Special Rules / Edge Cases
- Missing Speaker – If the transcript line does not indicate a speaker, set the Owner as “Unknown.”
- No Date Specified – Leave the Due Date cell blank; do not invent a date.
- Multiple Owners – If more than one person is named for an action, list them separated by commas (e.g., “Alice Smith, Bob Lee”).
- Partial Metadata – Missing fields in the Metadata input will appear as “Not provided” in the summary (e.g., “Meeting Date: Not provided”).
- Long Transcript – If the transcript exceeds 15,000 words, the process should still run, but a note “Long transcript – summary may be high‑level” is added to the summary.
- Non‑English Content – The process works only on the dominant language of the transcript; any portion in a different language is ignored.
9. Example
Input
1. Meeting Transcript (PDF) – A PDF containing the following excerpt (illustrated as plain text for illustration):
Alice: “Welcome everyone, let’s start with the Q3 performance review.
Bob: “We saw a 5% increase in web traffic, but conversion rates dropped to 2.1%.”
Carol: “I’ll prepare a detailed report on the conversion funnel by next Friday.”
Alice: “Great, Bob, can you send the raw data to Carol by Wednesday?”
Bob: “Sure, I’ll email the data by end‑of‑day tomorrow.”
Alice: “The next steps are: Carol will draft the report, Bob will deliver the data, and I will schedule the next review for 2025‑09‑01.”
2. Metadata (Optional)
| Field | Description | Example |
|---|
| Meeting Title | Quarterly Review | “Quarterly Review” |
| Meeting Date | 2025‑08‑02 | “2025‑08‑02” |
| Participants | List of attendees | “Alice, Bob, Carol” |
| Meeting Owner | Who organized | “Alice” |
| Objective | Meeting purpose | “Review Q3 performance and plan Q4 actions” |
Expected Output
Meeting Summary
The team reviewed Q3 performance, noting a 5 % rise in web traffic but a decline in conversion rates to 2.1 %. Carol will prepare a detailed conversion‑funnel report by next Friday. Bob will send the raw data to Carol by tomorrow, and the next review meeting is scheduled for 2025‑09‑01.
Action Items
| Action Description | Owner | Due Date (optional) | Additional Notes |
|---|
| Prepare detailed report on conversion funnel | Carol | 2025‑08‑09 | Draft to be shared with the team |
| Send raw data to Carol | Bob | 2025‑08-03 | Email delivery |
| Schedule next review meeting | Alice | 2025‑09-01 | Calendar invite |
Note: Dates were extracted from the transcript text. Where no exact date was given, the nearest relative date was used and converted to an absolute date based on the meeting date.
Appendix A – FAQ
Q1: What if the transcript contains multiple languages?
A: Only the dominant language will be processed. Any sections in a different language are ignored.
Q2: What if the transcript is very long?
A: The process still works, but the summary may be high‑level. A note indicating “Long transcript – summary may be high‑level” is added to the summary.
Q3: How are duplicate action items handled?
A: Duplicate rows (identical description and owner) are removed during the validation step.
Q4: What if a speaker is not identified for an action?
A: The Owner field will be filled with “Unknown.”
Q5: What format should the due date be?
A: Use the ISO format YYYY‑MM‑DD. If the transcript only provides a relative date (e.g., “next Friday”), convert it to an absolute date based on the meeting date.
Q6: Can the process be used for non‑meeting transcripts, like webinars?
A: Yes, provided the transcript follows the same speaker‑based format.
Q7: What if no action items appear in the transcript?
A: The “Action Items” section will contain the sentence “No action items identified.”
Q8: What if the PDF is unreadable or corrupted?
A: The process will stop and return an error message: “Transcript not readable.” No summary or action items will be generated.
Q9: Does the process add any personal data?
A: No new identifiers are created. All identifiers come directly from the transcript (e.g., speaker names).
Appendix B – Glossary
| Term | Definition |
|---|
| Meeting Summary | A brief paragraph (3‑5 sentences) that captures the core discussion points and decisions of a meeting. |
| Action Item | A task or responsibility that originates from the meeting, assigned to a specific person, and often includes a deadline. |
| Owner | The individual (or group) who is responsible for completing an action item. |
| Due Date | The calendar date by which the action item should be completed. |
| Metadata | Supporting information about the meeting (title, date, participants, etc.) that provides context for the transcript. |
| Transcript | The written record of a spoken meeting, typically containing speaker names and timestamps. |
| Present Tense | Verb form describing current or ongoing actions (e.g., “prepare,” not “prepared”). |
| Professional Tone | Language that is formal, clear, and free of slang or informal expressions. |
Appendix C – Reference Material
C.1 Style Guide for Summary and Action Items
General Tone
- Use a formal and professional voice.
- Keep sentences short (no more than 20 words each).
- Write in present tense (e.g., “We discuss” → “We discuss”).
Summary
- Start with the purpose: “The team discussed …”.
- List key points: Use one sentence per major point.
- Mention decisions and next steps (e.g., “A follow‑up meeting will be held …”).
- Avoid filler words (“basically”, “just”).
- Do not use bullet points; keep it as a paragraph.
Action Items Table
- Action Description: Begin with a strong verb (“Prepare,” “Send,” “Schedule”).
- Owner: Use the name as it appears in the transcript; if multiple names, separate by commas.
- Due Date: Use ISO format (YYYY‑MM‑DD). If only “next Friday” is mentioned, calculate the date based on the meeting date.
- Additional Notes: Use only when extra context is needed (e.g., “see attachment”).
Formatting
- Paragraphs – no indentation, one line per paragraph.
- Tables – plain text, columns separated by “|”. Use a header row, then a row for each action.
- Missing Data – Insert “Not provided” or “Unknown” where appropriate.
C.2 Prohibited Items
- No generation of new IDs (e.g., no “User ID 12345”).
- No external references – only use information from the transcript and the supplied metadata.
C.3 Classification List for Action Items
| Category | Description |
|---|
| Data Request | Action requires delivering data or files. |
| Report Creation | Action involves preparing a report, document, or presentation. |
| Meeting Scheduling | Action involves arranging a meeting or event. |
| Decision Implementation | Action implements a decision made in the meeting (e.g., “launch campaign”). |
| Follow‑up | Action is a follow‑up to a prior task or meeting. |
| Review | Action involves reviewing a document, data, or process. |
C.4 Example Workflows
-
Standard Meeting
- Transcript provided.
- Summary generated in 30 seconds.
- 4 action items extracted, each with owner and due date.
-
No Action Items
- Transcript contains only discussion.
- Summary created.
- “No action items identified.” displayed.
-
Missing Owner
- Action “Prepare budget” spoken without naming who.
- Owner set to “Unknown”.
These reference materials are intended to be copied and refined as needed for specific organizational use cases.
