Choosing a first classroom robot kit

The first robot kit a school buys tends to shape its robotics for years. Teachers learn it, students get attached to it, and a cupboard fills up with its spare parts. That makes the first choice worth a little thought, even when the budget is small and the pressure is to just order something before the term starts.

This note does not recommend a single brand. Prices change too often to quote, and the right kit depends on who will use it. Instead, it sorts the common options into three families and explains what each is good and bad at.

Three families of kit

1. Micro:bit and add-on buggies

The BBC micro:bit is a small programmable board designed for schools. It already has buttons, a 5×5 LED display that can also measure light, a compass, an accelerometer and radio, and the newer version adds a microphone and speaker. On its own it is not a robot, but several makers sell motor "buggy" chassis that the micro:bit plugs into, turning it into a small wheeled robot.

Strengths: low cost per board, free browser-based editors, and a gentle path from blocks to Python. Weaknesses: the add-on chassis vary a lot in build quality, and each brand needs its own extension blocks, so check that the chassis you choose has current support in the editor you plan to use.

2. LEGO Education sets

LEGO's education sets combine bricks, motors, sensors and a programmable hub. The appeal is obvious: students can rebuild the robot endlessly without tools, and the mechanical side of robotics (gears, levers, sturdy frames) becomes something they can explore with their hands.

Strengths: very durable, quick to rebuild, good for mixed-ability groups. Weaknesses: the highest cost per set of the three families, and the many small pieces need a sorting system or they disappear by week three.

3. Arduino-style boards

Arduino boards are open-source microcontrollers widely used by hobbyists. The classic Arduino UNO is built around the ATmega328P chip and offers 14 digital input/output pins and 6 analog inputs. You add your own motors, motor driver, sensors and chassis, usually with jumper wires or a breadboard.

Strengths: cheap parts, a huge community, and real engineering skills such as wiring, power and soldering. Weaknesses: much more can go wrong. Loose wires, reversed batteries and missing libraries eat lesson time, so this family suits older students or a club with a confident adult.

Matching the kit to Year levels

New Zealand schools often run robotics across a wide age range, so it helps to think in bands rather than exact years.

1. Years 1–4: simple floor robots that follow arrow-key sequences are enough. The goal is sequencing and prediction, not sensors.
2. Years 5–8: micro:bit buggies or LEGO sets fit well. Students can read one sensor, make a decision, and see the result straight away.
3. Years 9–10: either keep LEGO and push into more complex mechanisms, or introduce Arduino with a pre-built chassis so wiring problems stay manageable.
4. Years 11–13: Arduino and other microcontrollers in typed languages, with students designing their own sensors and control code.

Questions to ask before you buy

1. How many students per kit? Three per robot is a common sweet spot: a builder, a coder and a tester who swap roles.
2. What runs the editor? Check that it works on the devices you actually have, such as Chromebooks, iPads or old Windows laptops, and whether it needs installing or runs in a browser.
3. What are the batteries? Disposable AA cells add up fast. Rechargeable packs cost more at the start but usually pay for themselves within a year of regular use.
4. What breaks, and can you replace it? Motors, wheels and cables wear out. A kit where spares are easy to buy is worth more than one that is cheaper on day one.
5. Who will look after it? If one teacher leaves and nobody else knows the kit, it often ends up in a cupboard. Pick something at least two staff members are willing to learn.

A sensible way to start small

Many schools do best by buying a small batch, enough for one class to work in groups of three, and running a single term with it before committing further. A term of real use tells you more than any catalogue: which parts break, which editor students prefer, and whether the kit suits your timetable.

It is also worth asking neighbouring schools what they use. Sharing a kit family across a local cluster makes it easier to swap spares, run joint practice days and support each other's teachers.

Whatever you choose, the kit matters less than the habit of building, testing and fixing. A modest kit used every week will teach more than an expensive one that only comes out for special occasions.

Sources: micro:bit features overview (Micro:bit Educational Foundation); Arduino UNO Rev3 documentation; LEGO Education.