A clear plan, clear owners and no surprises.
This is how a BotClub programme runs in a school, from the first syllabus map to the end-of-year review. Every step has an owner, a record and a date.
Seven steps, repeated every term
The same model applies to Luminary, BOTCLUB Labs and Solve'D. Only the details change.
- 1Before the term
Onboarding
We meet school leadership, agree goals and name a BotClub programme lead and a school coordinator. We collect textbooks, the academic calendar, exam dates and the classroom set-up.
- 2Week 1–2
Syllabus mapping
Every model, lab or question bank is mapped to grade and chapter. Gaps and open questions are listed for the school to confirm, and nothing is assumed silently.
- 3Before each month
Term-wise schedule
Sessions are placed in the month each chapter is taught. Each session is marked live, revision or enrichment, and hands-on sessions are paired with visualisation. Exam dates are kept free.
- 4Start of term
Teacher training
Hands-on training on your own equipment, then support in the first sessions until teachers are confident running them on their own.
- 5Every week
In-class delivery
Teachers lead sessions within the month's plan and choose section-level timing. BotClub supports with set-up, troubleshooting and co-delivery where agreed.
- 6Every month
Monitoring & reporting
Sessions delivered are recorded against the plan, and Labs usage comes from its analytics. Leadership gets a short monthly summary: what ran, what slipped and what's next.
- 7Every term
Review meeting
We review delivery, usage and teacher feedback with leadership, agree any changes and update the plan for the next term.
Leaders see what actually happened in class
For BOTCLUB Labs, monitoring isn't a form someone fills in. Every session is logged automatically, by class, section and chapter, and that's what our monthly summary and term review are built on.
- Usage by class and section, with the date each was last used
- Chapters opened against the plan
- Time in each chapter, across all screens
- Exportable for your own records
A sample term-wise plan
An illustrative excerpt of how Luminary sessions are spread across one academic year. Your school's plan is built from your own calendar and exam dates.
| Month | Grade & chapter | Session | Models used | When it happens |
|---|---|---|---|---|
| Month 1 | Grade 7 · Heat transfer in nature | live | Heat Transfer | Any free period before mid-term |
| Month 1 | Grade 9 · Describing motion around us | revision | Motion Conversion 1, ATDG 1 | First week, before half-yearly exams |
| Month 2 | Grade 9 · Work, energy and simple machines | live + visualisation | Power Gen, Power Factor, PE and KE | As the new chapter begins |
| Month 2 | Grade 8 · Resistors in series and parallel | live | Circuit Construction 4 | While the chapter is taught |
| Month 3 | Grade 8 · Reflection, mirrors and lenses | live + visualisation | Law of Reflection, Concave/Convex Mirror & Lens | Chapter is new this month |
| Month 3 | Grade 7 · Images in a plane mirror | live | Imagine IT | Any free period |
| Month 4 | Grades 6–8 · Post-mid-term syllabus | revision | Heat Transfer, ATDG 2, Peltier | Post-mid-term revision block |
| Month 5 | Grade 6 · Types of motion | enrichment | Motion Conversion 1 & 2 | Enrichment top-up |
| Month 6–7 | Grades 6–9 · Full syllabus | revision + visualisation | Selected per grade | Before final exams; exam dates kept free |
Every model accounted for
The plan lists every model and each month it's used. Models used only once are flagged so they can be reused.
Gaps written down
Anything we couldn't map with confidence goes on a short list of questions for the school, and it's resolved before it affects a lesson.
Exams respected
We don't schedule sessions during exams. Revision sessions are timed to finish before them.
Who does what
One table, agreed at onboarding, so everyone knows who owns each step.
| Activity | BotClub team | School leadership | School coordinator | Teachers |
|---|---|---|---|---|
| Share calendar, exam dates, textbooks and timetable | I | A | R | C |
| Syllabus mapping and gap list | R | I | A | C |
| Monthly session plan | R | A | C | I |
| Section-level timing within the month | I | I | A | R |
| Kits, Labs access and screen set-up | R | I | C | I |
| Teacher training and in-class support | R | I | A | C |
| Delivering sessions in class | C | I | A | R |
| Session records and usage monitoring | R | I | C | C |
| Monthly summary to leadership | R | I | I | I |
| Equipment faults and access issues | R | I | C | C |
| Term review and plan changes | R | A | C | C |
Where no school role is accountable, BotClub is accountable for its own deliverables.
Commitments we make to every school
Safe by design
Hands-on models are built for supervised classroom use. Experiments with flames, heat or chemicals are run in BOTCLUB Labs on screen, with safety notes built into each step.
Teachers stay in charge
Our tools support the teacher. They don't replace the teacher. Sessions follow the teacher's lesson, and every activity can be paused, slowed or repeated.
Careful with information
We collect only what we need to run the programme and report to your school. Your school's information isn't used for anything else.
Honest reporting
Monthly summaries show what was planned and what actually happened, including sessions that slipped and why.
Respect for school time
Sessions use free periods and chapter time agreed with the school. Nothing is scheduled during exams.
Always improving
Teacher feedback goes back to our product teams, and fixes and new activities reach classrooms through the year.
Let's plan your school's year
Tell us your grades and products of interest. We'll come back with a syllabus map and a first-term plan for you to review.