Meeting Minutes Template
For Next Trend Hub organizers: Use this template to document and publish notes from weekly check-in calls.
Purpose
Publishing meeting minutes:
- Provides transparency for participants
- Creates record of discussions and decisions
- Helps absent participants catch up
- Documents hackathon journey
Where to Publish
Add new entries to: /processes/cats-hackathon/meeting-minutes
Each entry should be added at the top of the page (most recent first).
Template Format
## [Date] - [Day] Check-in
**Date:** [Full date - e.g., November 13, 2024]
**Time:** [Start time - End time] WAT
**Attendance:** [X] participants / [Y] teams
**Facilitator:** [Name]
**Phase:** [Current hackathon phase]
### Key Discussion Points
[2-3 paragraphs summarizing main topics discussed]
- Main theme or focus of this check-in
- Important concepts or methodologies covered
- General progress updates across participants/teams
- Any announcements or policy clarifications
### Participant/Team Updates
**Phase 1-2 (Individual Reporting):**
[Summarize patterns across individuals, not individual reports unless noteworthy]
- Common problems being discovered: [list]
- Interview progress: [general statistics]
- Challenges many participants face: [list]
- Notable discoveries: [2-3 examples]
**Phase 3-8 (Team Reporting):**
[Summarize each team briefly or highlight notable teams]
**Team [Name]:**
- Status: [brief 1-sentence update]
- Blockers: [if any]
**Team [Name]:**
- Status: [brief 1-sentence update]
- Notable: [any standout progress or pivot]
[Continue for teams with significant updates]
### Mentor Guidance & Advice
[Capture key advice or guidance provided by mentors/facilitators]
**On [Topic]:**
- [Specific advice or recommendation]
**On [Topic]:**
- [Guidance provided]
**Common Pitfalls Discussed:**
- [Warning or mistake to avoid]
### Action Items
| Who | Action | Deadline |
|-----|--------|----------|
| All Participants/Teams | [Action required] | [Date] |
| [Specific team/person] | [Specific action] | [Date] |
| Next Trend Hub | [Organizer action] | [Date] |
### Resources Shared
- [Link or resource name]: [Brief description]
- [Link or resource name]: [Brief description]
### Questions & Answers
**Q:** [Question asked by participant]
**A:** [Answer provided by mentor/facilitator]
**Q:** [Another question]
**A:** [Answer]
[Include 3-5 most important or commonly asked questions]
### Next Meeting
**Date:** [Next check-in date]
**Time:** [Time] WAT
**Focus:** [What next meeting will cover]
**Preparation:** [What participants should do before next call]
---
Detailed Instructions
Writing Style
Tone: Professional but friendly, encouraging
Length: 500-800 words per entry
Perspective: Third person (“Participants discussed…” not “We discussed…”)
Balance: Specific enough to be useful, general enough to protect individual privacy
What to Include
✅ Include:
- Date, time, attendance statistics
- Phase context
- Main themes and topics discussed
- General progress patterns
- Specific advice from mentors
- Action items with deadlines
- Resources shared
- Important Q&A
- Next meeting details
❌ Don’t Include:
- Individual participant names (unless they achieved something notable and give permission)
- Private or sensitive team issues
- Detailed critiques of specific teams
- Off-topic discussions
- Internal organizer notes
Capturing Information
During the Call:
- Take real-time notes
- Record call if participants consent (for accuracy)
- Note timestamps for important topics
- Track who asks questions (anonymize in minutes)
After the Call:
- Write up within 24 hours while fresh
- Review with co-facilitator for accuracy
- Edit for clarity and conciseness
- Publish to meeting-minutes page
Examples
Example Entry (Short)
## November 6, 2024 - Wednesday Check-in
**Date:** November 6, 2024
**Time:** 6:00 PM - 7:15 PM WAT
**Attendance:** 42 participants
**Facilitator:** Abdulrahman
**Phase:** Phase 2 (Community Discovery)
### Key Discussion Points
Week 1 of community discovery showed strong engagement. Participants are conducting interviews and beginning to identify recurring problems in areas like waste management, transportation, and market efficiency. Emphasis placed on importance of voice notes as mandatory evidence.
Several participants expressed initial hesitation about approaching strangers for interviews. Facilitator demonstrated effective introduction techniques and consent scripts. Discussion on balancing structure (using interview template) with flexibility (following interesting tangents).
### Participant Updates
- **Interview Progress:** Most participants have completed 3-5 interviews so far (target: 10-15 by Nov 21)
- **Voice Notes:** All participants have set up recording systems and cloud backup
- **Common Problems Emerging:** Waste accumulation (8 participants), transportation gaps (6 participants), financial access (5 participants)
- **Notable:** One participant discovered unexpected insight about market traders' willingness to pay for services if coordination is simplified
### Mentor Guidance & Advice
**On Approaching Interviewees:**
- Be clear about purpose upfront: "I'm learning about community challenges"
- Build rapport before asking about problems
- Market areas, bus stops, and community centers are good starting points
**On Recording Quality:**
- Find quieter corners even in busy areas
- Hold phone 6-12 inches from speaker
- State context at beginning of recording (date, location, role)
**Common Pitfalls Discussed:**
- Interviewing only friends/family (not diverse enough)
- Asking leading questions ("Don't you think...?")
- Jumping to solutions during research phase
### Action Items
| Who | Action | Deadline |
|-----|--------|----------|
| All Participants | Complete minimum 10 interviews | Nov 21 |
| All Participants | Upload voice notes to cloud storage | Ongoing |
| Next Trend Hub | Share interview template in WhatsApp | Nov 7 |
### Resources Shared
- [Interview Template](/processes/templates/interview-template): Structured guide for community interviews
- [Voice Notes Guidelines](/processes/action-learning/voice-notes-guidelines): Recording standards
### Questions & Answers
**Q:** What if someone doesn't want to be recorded?
**A:** Respect their decision. Take detailed written notes and note in your documentation why no voice note exists for that interview.
**Q:** How long should each interview be?
**A:** 10-15 minutes is ideal. Quality over quantity—one deep interview better than three superficial ones.
**Q:** Can we interview in Yoruba or Pidgin?
**A:** Yes! Just provide English summary in your documentation.
### Next Meeting
**Date:** Saturday, November 9, 2024
**Time:** 1:00 PM WAT
**Focus:** Analyzing interview data, identifying patterns
**Preparation:** Complete 2-3 more interviews, begin noting recurring themes
---Publishing Process
Step 1: Write Minutes
Use template above, fill in details from call
Step 2: Review
- Check for accuracy
- Remove sensitive information
- Verify links work
- Proofread for typos
Step 3: Add to Page
- Open
/content/processes/cats-hackathon/meeting-minutes.mdx - Find the section after the intro/template
- Add new entry at the top (most recent first)
- Separate entries with
---horizontal rule
Step 4: Announce
Share in WhatsApp/Slack group:
”📝 Minutes from [Day]‘s check-in are now posted: [link to page]“
FAQ for Organizers
Q: How detailed should updates be?
A: Specific enough to be useful but not so detailed it takes hours to write. Aim for 30-45 minutes to write up minutes.
Q: Should we name participants?
A: Generally no, unless highlighting notable achievement with their permission.
Q: What if a team shares confidential business plans?
A: Don’t publish specifics. Summarize as “team discussed business model options.”
Q: How to handle team conflicts mentioned in call?
A: Don’t publish conflicts. Handle privately. Only mention if becomes action item: “Hub leadership will facilitate team collaboration discussion.”
Q: Should we transcribe everything said?
A: No, minutes are summaries, not transcripts. Capture key points, decisions, and action items.
Quality Checklist
Before publishing, ensure:
- Date, time, attendance accurate
- All action items have deadlines
- Resources have working links
- No sensitive information included
- Participant privacy protected
- Grammar and spelling checked
- Next meeting details included
- Published to meeting-minutes page
- Announced in group chat
Related Pages: