Meeting Outcomes and Commitments Summarizer
Turn raw meeting notes into four clear sections for decisions, commitments, and next-meeting details.
Customise & copy
Add the context you have. The prompt updates as you work.
Enter the external company discussed in the meeting.
Paste unedited notes, transcript excerpts, or bullet points.
List each attendee and their organization or role when known.
Enter the date of the meeting.
List the people on your team so internal commitments can be separated from external commitments.
Live prompt
5 fieldsSummarize the meeting notes below into exactly four sections. Use only information explicitly stated in the notes or inputs. Do not invent dates, commitments, decisions, attendees, or meeting details. If a date or status is missing, write "Not specified". Separate internal commitments from commitments made by the external company or its representatives. Preserve specific owners and dates when stated. Output only the following format: Section 1: Decisions Made - [Decision] - If none are explicitly stated: Not specified Section 2: Our Commitments with Dates - [Internal team member]: [Commitment] — Due: [date or Not specified] - If none are explicitly stated: Not specified Section 3: Their Commitments with Dates - [External owner or company]: [Commitment] — Due: [date or Not specified] - If none are explicitly stated: Not specified Section 4: Next Meeting Scheduled - Status: [Scheduled, Not scheduled, or Not specified] - Date/time: [Exact date and time or Not specified] - Purpose: [Purpose or Not specified] Company: {{company_name}} Meeting date: {{meeting_date}} Attendees: {{attendee_list}} Internal team members: {{internal_team_members}} Raw meeting notes: {{raw_meeting_notes}}
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"company_name": "Northstar Logistics",
"meeting_date": "2025-04-18",
"attendee_list": "Maya Chen — Northstar Logistics, VP Operations; Jordan Ellis — Northstar Logistics, Data Lead; Priya Shah — Acme Analytics, Product Manager; Luis Romero — Acme Analytics, Solutions Consultant",
"raw_meeting_notes": "Agreed to proceed with a 30-day warehouse analytics pilot covering the Denver and Phoenix sites. Northstar will provide shipment-volume data and confirm site contacts by April 24. Our team will send the security questionnaire by April 22 and a draft pilot plan by April 29. Priya to schedule a technical workshop. Follow-up discussed for May 2 at 10:00 AM Mountain Time, but calendar invitation has not yet been sent.",
"internal_team_members": "Priya Shah — Product Manager; Luis Romero — Solutions Consultant"
}A small ritual that works
How to use it
- 01Enter the company name and meeting date.
- 02List attendees and identify your internal team members.
- 03Paste the raw meeting notes.
- 04Review the four-section summary for accuracy.
Why it works
The prompt defines a narrow extraction task with four fixed sections: decisions, internal commitments, external commitments, and the next meeting. It establishes a clear evidence boundary by requiring the summary to use only information stated in the supplied inputs. Explicit fallback phrases such as "Not specified" provide a consistent way to represent missing information without encouraging invention. The internal team member list gives the prompt a basis for separating internal and external responsibilities, while the required owner-and-due-date format preserves accountability details when they are present. The fixed output template also makes the resulting summary easy to scan and compare across meetings.
Where it fails
The structure depends on the notes clearly identifying decisions, owners, organizational roles, dates, and meeting status. Ambiguous wording, incomplete attribution, conflicting details, or commitments that cannot be confidently classified as internal or external will be reduced to limited or unspecified entries because the prompt prohibits inference. The next-meeting section can also represent only the fields requested: status, date/time, and purpose.
Customisation tips
Add fields for risks, open questions, dependencies, action-item priority, or decision rationale if those are recurring parts of the meeting record. If ownership is frequently unclear, define an explicit convention for team names, departments, or unnamed participants. You can also replace the section labels with terminology used by your organization, add a required time zone for meeting details, or specify a date format such as ISO 8601. Keep the evidence rule and fallback language if factual traceability is important.
Watch-outs
- The prompt uses the internal team member list to distinguish internal commitments from external commitments, so that list should include every relevant internal person or team.
- A commitment with a named owner but no due date is retained with "Not specified" rather than receiving an inferred deadline.
- The prompt separates meeting status from date/time, so a date can be recorded independently from whether the meeting is described as scheduled.
- Attendees and the meeting date are supplied as inputs, but the required four-section format does not provide a dedicated section for them.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Three-Bullet Meeting Decision and Action Summary
Turn a meeting transcript into three concise, evidence-based decision and next-step bullets.
RevOpsActionable Meeting Log Extractor
Turn raw meeting notes into a precise log of decisions, actions, owners, deadlines, risks, and open questions.
RevOpsMeeting Action Record
Turn meeting notes into a factual JSON record of decisions, questions, actions, dependencies, and commitments.
Want to make AI useful across your team? Explore Atul's training.