Skip to content

Pilot protocol (Phase 4)

Goal: learn whether teachers can run units with only this repo, and whether students learn and enjoy it.

Schools (3–5)

Mix: urban/rural, public/private, with/without reliable internet. Record school type and resources, not names, in public files.

What each pilot teacher does

  1. Attend the one-day training (docs/for-teachers/README.md).
  2. Teach one unit per term (suggest G8 U1 and G9 U3 first); keep the time log.
  3. Give the pre/post concept check (10 items drawn from the unit's quiz.yml), the student feedback form, and return results.

Instruments (copy into pilots/<school-code>/)

  • Teacher time log: lesson, planned vs actual minutes, what was cut, what confused students.
  • Pre/post check: same 10 questions before and after; mark with the answer key; record anonymously by student code.
  • Student feedback (3 questions): What did you enjoy? What was confusing? Would you do it again? (1–5 smile scale + comment.)
  • Technical log: devices, connectivity, problems running notebooks offline.

Guardian/school consent before collecting any student feedback; anonymous codes; no photos of students; publish only aggregated results.

Analysis plan

Report school-level means for pre/post change (with n), teacher time vs plan, and common issues. Do not claim causal effects from a small pilot.

Report template (pilots/TEMPLATE-report.md)

School type · grade · unit · n students · n teachers · pre/post summary · time use · technical issues · what we changed · quotes (consented) · recommendations.

Pilot results are published in this folder and summarised in docs/for-cdc/.