Organize information

Turn meeting notes into decisions and actions

Separate what was decided from ideas, questions, and follow-up work

4 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Meeting notes or transcriptMeeting purpose

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Organize these meeting notes around the meeting purpose.

Purpose:
[purpose]

Notes:
[notes]

Use only information explicitly present in the notes. If an owner or date is missing, write “Unassigned” or “Not set”; do not guess. Produce:
1. Executive summary in three bullets or fewer
2. Decisions made, including rationale when recorded
3. Action items as a table: action, owner, due date, dependency
4. Open questions
5. Ideas discussed but not approved
6. Risks or contradictions that need confirmation

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Meeting notes or transcript: Maya: We can start the reporting beta with 10 customers on May 13. Leo: CSV export currently drops timezone information. My fix should be ready May 8. Priya: I can complete QA on May 9 if the test accounts exist by May 8. Evan: I will provision the test accounts by May 7. Noor: I will finish the support guide by May 10. Decision: Exclude SSO from this pilot. Two pilot customers requested it, but including it now would add about two weeks. Reconsider after the pilot. We discussed hosting a customer webinar, but did not approve it. Open question: Should success mean 70% activation or completion of the first reporting task? Risk: Sales has already promised SSO to one proposed pilot account.
Meeting purpose: Confirm the reporting beta scope, launch date, responsibilities, and unresolved launch questions.

Example output

1. Executive summary

The team plans to launch the reporting beta to 10 customers on May 13.
SSO is excluded because adding it now would delay the pilot by about two weeks; it will be reconsidered afterward.
Launch preparation has named owners, but the success metric and an SSO-related customer conflict remain unresolved.

2. Decisions made

Launch: Begin the beta with 10 customers on May 13.
Scope: Exclude SSO from this pilot. The recorded rationale is the estimated two-week delay; reconsider it after the pilot.

3. Action items

Action	Owner	Due date	Dependency
Provision test accounts	Evan	May 7	None recorded
Fix CSV timezone loss	Leo	May 8	None recorded
Complete QA	Priya	May 9	Test accounts by May 8; CSV fix is not explicitly a dependency
Finish support guide	Noor	May 10	None recorded
Choose the beta success metric	Unassigned	Not set	Agreement on activation versus first-task completion

4. Open questions

Should success be defined as 70% activation or completion of the first reporting task?

5. Ideas not approved

Host a customer webinar.

6. Risks or contradictions

Sales promised SSO to one proposed pilot account, but SSO is excluded. The affected account and response need confirmation.
The notes do not say whether Priya’s QA also depends on Leo’s CSV fix.