Camps
A full week of robotics during a school break, ending with a robot the learner built from nothing.
- Who
- 7–15
- Format
- Full-day / week-long
- Level
- Intro → Intermediate
A weekly robotics class that keeps going: the same learner moves up through levels rather than repeating an introduction.
A long-term, level-based track where learners move from first mechanical builds through electronics, code, autonomy and competition robots.
Tracks are the spine of the progression. Everything else in the programs list either feeds into a track, compresses one, or specialises out of it, so the level structure gets tested here first and week after week.
Capabilities, and how far this program takes each one.
Frames, drivetrains, tolerances and why a part that fits in CAD binds in aluminium.
Power, signal and ground; motor drivers and sensors wired so faults are findable.
Control logic and structure, then reading what the robot actually did.
Sensor-driven behaviour, feedback and calibration.
Designing and printing the parts a kit does not contain.
Join at the level a short placement build puts you at.
The same level structure installed as a school program, with the delivery split decided by the engagement model.
Tracks are the version most schools install, because a level structure is what turns a robotics club into a program somebody else can run next year.
Which of these lands on your staff depends on the engagement model: we run it, we run it with you, or you run it.
See how a school program worksOne session, in the order it happens.
Work continues from where it stopped, so problems carry over instead of being reset each week. That is what makes the progression cumulative rather than a series of activities.
It moves, it senses, or it fails in a way that tells you why, which is the part that gets debugged next week.
Moving up depends on what a learner can design, wire, program or debug, not on how long they have attended.
A short build and conversation places the learner at the right level.
Every session ends with something that moves, senses or fails informatively.
Progress is reviewed against engineering outcomes, not attendance.
Tracks are where a level structure gets tested week after week. If a progression does not hold here, it does not ship to a school.
Level-based progressions written against the hardware, not adapted to it.
A full week of robotics during a school break, ending with a robot the learner built from nothing.
Two minutes of questions tells us whether this program fits, or whether something else in the ecosystem fits better.