Weekly Report Template

Use this template to prepare for weekly check-in calls (Wed 6PM, Sat 1PM WAT). Clear reporting helps mentors provide better guidance and keeps teams accountable.

Quick Reference

Check-in Schedule:

Wednesday 6:00 PM WAT
Saturday 1:00 PM WAT

Report Timing:

Prepare 1-2 hours before call
Share in group chat or verbally during call
Keep brief: 2-3 minutes per team

Phase 1-2: Individual Reporting (Nov 1-21)

During community discovery phase, individuals report weekly

Individual Weekly Report

Name: _________________
Date: _________________
Week: ___ of Phase 1-2

1. Research Progress

Interviews Completed This Week:

Number of interviews: ___
Diverse profiles? (ages, occupations, locations): Yes / No
Voice notes recorded? Yes / No
Voice notes uploaded and backed up? Yes / No

Problem Areas Explored:

2. Key Findings

Most Recurring Problems:

_________________ (mentioned by ___ people)
_________________ (mentioned by ___ people)

Surprising Discovery:

Notable Quote:

”_________________“

3. Challenges Faced

What’s blocking you?

Specific Help Needed:

4. Next Week Plan

This coming week I will:

Target: ___ total interviews by Nov 21

Phase 3-8: Team Reporting (Nov 23 - Jan 9)

After team formation, teams report collectively

Team Weekly Report

Team Name: _________________
Date: _________________
Phase: ___ (specify: Phase 3, 4, 5, 6, 7, or 8)
Reporting Member: _________________

1. Progress This Week

Phase-Specific Accomplishments:

If Phase 3-4 (Idea Development):

If Phase 5 (Prototyping Workshop):

If Phase 6 (Build Sprint):

Core functionality: ___% complete
Features completed:
Testing completed: Yes / No / Partial
Deployed: Yes / No / In Progress
Documentation updated: Yes / No

If Phase 7-8 (Presentation & Wrap-up):

2. Team Documentation Status

Which pages are complete?

Team Overview (/team/[your-team])
Ground Truth (/team/[your-team]/ground-truth)
Formulate Insight (/team/[your-team]/formulate-insight)
Formulate Hypothesis (/team/[your-team]/formulate-hypothesis)
Define Opportunity (/team/[your-team]/define-opportunity)
Journey (/team/[your-team]/journey)
Final Solution (/team/[your-team]/final-solution)

What needs work?

3. Prototype/Solution Status

What’s working?

What’s broken or incomplete?

Demo-ready? Yes / No / Almost

Deployment URL: _________________

GitHub Repo: _________________

4. Blockers & Challenges

What’s preventing progress?

Technical Blockers:

Team Collaboration Issues:

Resource Constraints:

Other Challenges:

Urgency Level: 🔴 Critical / 🟡 Important / 🟢 Minor

5. Decisions & Pivots

Did you change direction this week?

Original plan: _________________
New approach: _________________
Reason for change: _________________

Key decisions made:

6. Help Needed

What do you need from mentors/organizers?

Technical guidance on: _________________
Feedback on: _________________
Connection to: _________________
Resources: _________________
Other: _________________

Specific questions for this call:

7. Next Week Goals

By next check-in, we will:

Milestone Target: _________________

Who’s responsible for what?

Reporting Best Practices

Do:

✅ Prepare report before call (don’t wing it)
✅ Be honest about challenges and delays
✅ Share specific numbers (interviews, % complete, etc.)
✅ Ask for help when stuck
✅ Update team pages before reporting
✅ Bring questions for mentors

Don’t:

❌ Wait until call starts to think about report
❌ Hide problems or fake progress
❌ Give vague updates (“working on stuff”)
❌ Skip blockers section
❌ Report without team alignment
❌ Blame teammates publicly

Quick Status Indicators

Use these to quickly communicate status:

Progress:

🟢 On track
🟡 Behind schedule but manageable
🔴 Significantly behind, need help

Team Health:

🟢 Collaborating well
🟡 Minor coordination issues
🔴 Major team conflicts

Blockers:

🟢 No major blockers
🟡 Some challenges, working through them
🔴 Critical blocker, can’t proceed without help

Example: Good vs. Bad Reports

❌ Bad Report Example

“We’re working on stuff. Making progress. Will have something next week. No questions.”

Problems: Vague, no specifics, doesn’t help mentors provide guidance

✅ Good Report Example

“Team Catalyst reporting. Week 4 of Phase 6 (Build Sprint).

Progress: Core functionality 80% complete. Implemented user registration, waste collection scheduling, and payment tracking. Deployed test version at [URL].

Blockers: 🟡 Integration with payment API failing (rate limit issues). Need recommendation for alternative or workaround.

Documentation: 5 of 7 pages complete. Journey and Final Solution pages need updates this weekend.

Next Week: Fix payment integration, complete all documentation pages, prepare 10-min presentation.

Question: For payment issues, should we use test data for demo or delay deployment?”

Strengths: Specific progress, clear blocker, honest status, actionable question

Option 1: Pre-Call (Recommended)

Post in WhatsApp/Slack group 1-2 hours before call
Allows mentors to prepare targeted advice
Saves time during call

Option 2: During Call

Verbal summary using this template
2-3 minutes maximum per team
Share screen if showing prototype

Option 3: Async (If You Can’t Attend)

Share written report in group
Tag organizers for visibility
Request specific feedback needed

Tip: Copy this template into your team’s shared document (Google Doc, Notion, etc.) and fill it out collaboratively before each check-in call.