Automations for M2 follow-ups

[sacha-l]

Idea dump:

1. Scheduling & Reminders

Weekly update reminders (every Monday)
Form submission deadlines
Check-in scheduling notifications
Payment processing reminders
Review deadline tracking (5 business days)

2. Status Tracking & Dashboards

Team status (🟢🟡🔴) based on defined criteria
Submission checklist progress per team
Mentor assignment matrix
Payment status tracking
Timeline milestone visualization

3. Document Management

Store Milestone 2 Agreements as reference docs
Collect and organize weekly updates
Track submission materials (code, video, docs links)
Version control on milestone plans
Centralized repository of all team artifacts

4. Workflow Automation

Trigger alerts when teams miss updates (auto-flag 🟡 or 🔴)
Notify mentors when reviews are needed
Route submissions through review pipeline
Escalate unresponsive teams after X days
Auto-calculate metrics (completion rate, review times)

5. Communication Templates

Pre-written message templates for common scenarios
Form generation and distribution
Standard check-in agendas
Review request formats
Approval/rejection notification templates

6. Data Collection & Reporting

Weekly update form submissions
Mentor feedback collection
Final metrics aggregation
Satisfaction surveys
Success story capture

[sacha-l]

Phase 2+ input for the Stadium revamp (docs/stadium-revamp-phase-1-spec.md §8.1).

Almost everything here — weekly update reminders, status tracking dashboards, mentor assignment matrix, escalations, notification templates, workflow automation — is out of Phase 1 scope. Notifications are explicitly deferred in the revamp spec (§3.2) and the context doc.

One related item: "Weekly update reminders" — project updates themselves land in Phase 1 (Issues 4–6). The reminder / notification side is Phase 2.

Staying open as a Phase 2 planning input. Revisit at the Phase 1 retro after we see what alpha users actually ask for.