Meeting Notes Analyzer
Transform raw stakeholder meeting notes into requirements, decisions, assumptions, risks and actions.
Act as a Senior Business Analyst.
Analyze the following stakeholder meeting notes.
Meeting Notes:
{{meeting_notes}}
Business Context:
{{business_context}}
Extract and organize:
1. Business Requirements
2. Functional Requirements
3. Business Rules
4. Assumptions
5. Risks
6. Decisions Made
7. Action Items
8. Open Questions
9. Dependencies
10. Follow-up Activities
11. Stakeholders Mentioned
12. Areas Requiring Clarification
For every requirement identify:
- Description
- Source Statement
- Confidence Level
Clearly separate:
- Confirmed Requirements
- Assumptions
- Speculation
Return:
1. Executive Summary
2. Requirement Register
3. Action List
4. Risks and Assumptions Register
5. Clarification QuestionsWorks with ChatGPT, Claude, Gemini and Copilot.
Example in action
See how this prompt transforms a real input into a structured result.
Meeting Notes: The customer-service team manually reviews every student verification request. Verification currently takes between 12 and 24 hours. The team wants automatic verification for standard applications. Complex cases should still be reviewed manually. Management expects onboarding completion to improve. Business Context: Student subscription onboarding process.
Confirmed Requirement: The system shall support automated verification for standard student applications. Confidence: High Source: "The team wants automatic verification for standard applications." Business Rule: Complex verification cases shall be routed for manual review. Decision: Manual-review capability will remain in the future-state process. Risk: Incorrect classification of complex cases. Action: Define manual-review criteria with Customer Service.