Add new file

This commit is contained in:
Aarthi Manivannan, Premanathan Aarthi Manivannan
2025-11-20 12:02:32 +01:00
parent 76129982c3
commit db2192dc30
+42
View File
@@ -0,0 +1,42 @@
# Best Practices for High-Quality Meeting Reports
## 1. Tone & Style
- Neutral, concise, factual
- No personal opinions
- Use consistent timestamps (HH:MM:SS)
## 2. Structure
- Start with a clear title page
- Include agenda, summary, decisions, and actions
- Sections must follow chronological order
## 3. Executive Summary
- 23 short sentences
- Should give a quick understanding of the meetings outcome
## 4. Key Points
- Max. 5 bullet points per section
- Use speaker labels if known
## 5. Decisions
- Every decision must have:
- Text
- Responsible person (owner)
- Due date
## 6. Action Items
- Should be structured in a table:
- ID
- Task
- Owner
- Due date
- Status
## 7. Handling Missing Information
- If unclear → use UNKLAR:<reason>
- If timestamps missing → estimate minimal timestamps
## 8. Output Format
- Markdown
- Clean sections
- No meta comments from the LLM