Back to Prompts
SummarizationClaude Sonnet 4.5

Process Meeting Notes

Part of the Meeting Notes Processor template

Prompt
Process the following meeting notes into a structured summary with clear action items.

Meeting Notes:
{{meeting_notes}}

Meeting Context (optional):
{{meeting_context}}

Create a structured meeting summary:

## Meeting Summary
**Date:** [Extract from notes or state "Not specified"]
**Attendees:** [List all mentioned participants]
**Meeting Type:** [e.g., Project kickoff, Weekly sync, Client call, Planning session]
**Duration:** [If mentioned, otherwise omit]

## Key Discussion Points
[3-5 bullet points summarizing the main topics discussed, in order of importance]

## Decisions Made
- **[Decision topic]:** [What was decided] *(Owner: [Name if mentioned])*
[List all decisions made during the meeting. If no decisions were made, state "No formal decisions recorded"]

## Action Items
| Action | Owner | Due Date | Priority |
|--------|-------|----------|----------|
| [Specific task] | [Name] | [Date or "TBD"] | [High/Medium/Low] |

## Open Questions
- [Questions raised but not answered]
- [Items needing follow-up or clarification]

## Next Steps
- [What happens after this meeting]
- [Next meeting date/topic if mentioned]

## Parking Lot
[Topics mentioned but deferred for later discussion, or "None"]

---

Guidelines:
- Extract specific names for owners, never use "someone" or "the team"
- If an action has no clear owner, mark as "[Unassigned]"
- Infer priority from context (urgent language = High, mentioned deadlines = High/Medium)
- Convert relative dates ("next week", "by Friday") to specific dates if meeting date is known
- Capture direct quotes for important decisions or contentious points
- Flag any risks or blockers mentioned
Variables
Replace these placeholders with your specific values
{{meeting_notes}}

Raw meeting notes, transcript, or minutes

Example:

[Paste your meeting notes here]

{{meeting_context}}

Optional context about the meeting

Example:

Weekly product team sync, Jan 15 2024

Example

Input

Product sync 1/15. Present: Mike (PM), Lisa (Eng), Tom (Design). Discussed launch timeline - Lisa says API wont be ready until Feb 1 at earliest. Tom needs final copy by Friday for the landing page. Mike to check with legal on terms update. Should we do soft launch first? Decided yes, soft launch to beta users Feb 5, full launch Feb 15. Need to figure out who is doing launch blog post.

Output

## Meeting Summary
**Date:** January 15, 2024
**Attendees:** Mike (PM), Lisa (Engineering), Tom (Design)
**Meeting Type:** Weekly product sync

## Key Discussion Points
- Launch timeline adjusted due to API development status
- Decided on phased rollout strategy (soft launch then full launch)
- Landing page copy deadline established

## Decisions Made
- **Launch strategy:** Phased approach with soft launch to beta users first
- **Soft launch date:** February 5, 2024
- **Full launch date:** February 15, 2024

## Action Items
| Action | Owner | Due Date | Priority |
|--------|-------|----------|----------|
| Complete API development | Lisa | Feb 1, 2024 | High |
| Deliver final landing page copy | [Unassigned] | Jan 19, 2024 | High |
| Check with legal on terms update | Mike | TBD | Medium |
| Assign owner for launch blog post | Mike | TBD | Medium |

## Open Questions
- Who will write the landing page copy?
- Who will write the launch blog post?

## Next Steps
- Lisa to confirm API completion by Feb 1
- Soft launch to beta users Feb 5

## Parking Lot
None