Session by session
- Session 41 · Ask & understandWeek 21
Proximity and audible feedback
Evidence: a question, sketch or new vocabulary
- Session 42 · Build & designWeek 21
Map distance bands to buzzer behaviour
Evidence: a design draft, dataset or build
- Session 43 · ImplementWeek 22
Add LCD status messages
Evidence: a working version, explained once
- Session 44 · Test & improveWeek 22
Test near, far and invalid readings
Evidence: a test log with at least one failure
- Session 45 · Explain & reflectWeek 23
Document a useful range
Evidence: an individual explanation
- UNO
- HC-SR04
- buzzer
- LCD
Five distances; missing echo must not indicate safe travel.
A physical circuit, sensor or mechanism, built and tested on the bench.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG07-P09
Parking Assistant
A model parking aid with defined alert bands.
Sessions 41-45Innovation only - RoboticsG07-P10
Event Counter
A tabletop object counter with recorded limitations.
Sessions 46-50Innovation only - AIG07-P11
Reusable Evidence Checker
A structured AI-output review workflow with evidence references.
Sessions 51-55Innovation only - IntegratedG07-P12
AI Status Interpreter
An AI-assisted status display with an operator-controlled hardware link.
Sessions 56-60Innovation only
For school leadersChoose a starting point.
Build from evidence.
Pick the classes and a plan. We map the timetable, kit and safety checks with you, then pilot one class first.
- Prospectus and class-wise plan
- Kit and readiness check
- Pilot one class first
- Evidence at every milestone
Let's plan your pilot.
Share a few details and we will send the right plan for your classes.