Files
video2document/docs new/meeting_report_best_practices.md
T
Aarthi Manivannan, Premanathan Aarthi Manivannan db2192dc30 Add new file
2025-11-20 12:02:32 +01:00

43 lines
952 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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