In schools

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.

Implementation model

Seven steps, repeated every term

The same model applies to Luminary, BOTCLUB Labs and Solve'D. Only the details change.

If we can't get something from the school, such as a timetable, we don't guess. We plan by month, write the assumption down and confirm it with your coordinator.
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 7Every term

    Review meeting

    We review delivery, usage and teacher feedback with leadership, agree any changes and update the plan for the next term.

Proof, not promises

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
What a year looks like

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.

Illustrative month-by-month session plan
MonthGrade & chapterSessionModels usedWhen it happens
Month 1Grade 7 · Heat transfer in natureliveHeat TransferAny free period before mid-term
Month 1Grade 9 · Describing motion around usrevisionMotion Conversion 1, ATDG 1First week, before half-yearly exams
Month 2Grade 9 · Work, energy and simple machineslive + visualisationPower Gen, Power Factor, PE and KEAs the new chapter begins
Month 2Grade 8 · Resistors in series and parallelliveCircuit Construction 4While the chapter is taught
Month 3Grade 8 · Reflection, mirrors and lenseslive + visualisationLaw of Reflection, Concave/Convex Mirror & LensChapter is new this month
Month 3Grade 7 · Images in a plane mirrorliveImagine ITAny free period
Month 4Grades 6–8 · Post-mid-term syllabusrevisionHeat Transfer, ATDG 2, PeltierPost-mid-term revision block
Month 5Grade 6 · Types of motionenrichmentMotion Conversion 1 & 2Enrichment top-up
Month 6–7Grades 6–9 · Full syllabusrevision + visualisationSelected per gradeBefore 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.

Accountability

Who does what

One table, agreed at onboarding, so everyone knows who owns each step.

R Responsible: does the work A Accountable: signs off C Consulted I Informed
Responsibility matrix between BotClub and the school
ActivityBotClub teamSchool leadershipSchool coordinatorTeachers
Share calendar, exam dates, textbooks and timetableIARC
Syllabus mapping and gap listRIAC
Monthly session planRACI
Section-level timing within the monthIIAR
Kits, Labs access and screen set-upRICI
Teacher training and in-class supportRIAC
Delivering sessions in classCIAR
Session records and usage monitoringRICC
Monthly summary to leadershipRIII
Equipment faults and access issuesRICC
Term review and plan changesRACC

Where no school role is accountable, BotClub is accountable for its own deliverables.

Safety & care

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.