¶ Running Weekly Sessions
¶ Session Commencement
Session Commencement refers to kickstarting sessions with all children and youth in the chapter. This process is curated to ensure children are supported & can get the maximum number of sessions in a year.
This is where your chapter comes alive. Before a single session happens, the right systems, people, and energy need to be in place. That's what this project is about ❤️
¶ 🎯 Objective
Transform weekly sessions into consistent mentoring spaces where volunteers lead as mentors and children eagerly show up week after week.
¶ 🏆 What Winning Looks Like
¶ 🗺️ Phases of This Project
| Phase | What's happening |
|---|---|
| Phase 1 — Tech Setup | Before anyone walks into a classroom, your systems need to be ready — child data, MOUs, allocations, Campus Cloud and Platform Commons. |
| Phase 2 — Kickstarting Classes | Continuing volunteers restart priority classes. New volunteers are onboarded, trained, and running their first session. TR is set up and running. |
| Phase 3 — Driving Consistency | Sessions are running. Now the work is keeping them stable — strong Zero Hours, Debriefs, and data habits week after week. |
¶ 🔒 Project Boundaries
🔴 These are non-negotiable. The project cannot succeed without them.
| # | Non-negotiable |
|---|---|
| 1 | All Chapter Fellows & Volunteers know how to use Campus Cloud before the First Class |
| 2 | All Volunteer allocations & setup is completed on Platform Commons prior to the First Class |
| 3 | MOU is signed before the First Session |
| 4 | All session and volunteer data is marked on Campus Cloud on the same day of the class, within the Debrief |
Explore the phases →
- Phase 1- Tech Setup
- Phase 2- — Kickstarting Classes
- Phase 3- Driving Consistency