Sense, think, act

Most classroom robots follow the same pattern. Sensors collect information, such as distance, light, colour or touch. A small computer, the controller, runs a program that decides what to do with that information. Motors, lights or speakers then carry out the result.

Explaining robots this way helps pupils see that a floor robot for five-year-olds and a competition machine for teenagers work on the same principle. The difference lies in how many sensors are used, how complex the program is and how precisely the parts are built.

Why schools teach it

Robotics makes abstract ideas visible. A loop in a program becomes a robot turning four times to draw a square. A measurement error becomes a robot stopping short of its target. Pupils get immediate feedback and can test a change within seconds.

It also links subjects. Mathematics appears in angles and distances, science in forces and sensors, design and technology in structures, and computing in algorithms. Group work, planning and explaining decisions come in naturally.

For school leaders, robotics can also be a visible way to show parents what computing and design lessons involve, through open afternoons or short displays of pupil projects.

Choosing a starting point

Match the equipment to the age group and to the time you can realistically give. Simple floor robots such as Bee-Bot suit early years and lower primary. Block-based kits, including LEGO Education sets and micro:bit with add-on buggies, work well from about age eight. Older pupils can move to Arduino boards or text-based programming in Python.

Before buying, borrow a kit or ask a nearby school to show theirs in use. Check how the software runs on your school devices, whether it needs installing, and how pupils will save their work.

• Start with one year group and one unit of four to six lessons.

• Buy enough kits for groups of two or three, not one per class.

• Plan storage and battery charging before the first lesson.

• Train at least two members of staff so the work survives a staff change.

A first lesson to try

For pupils aged 7 to 9, allow 45 minutes. You need one floor robot or micro:bit buggy per group, masking tape and a set of instruction cards. Mark a simple route on the floor with tape. Groups first write the route as a list of arrow instructions on paper, then program the robot and run it. When it misses the route, they find the step that went wrong and fix it. Finish by asking each group to explain one mistake and how they found it.

Key points

• Teach robotics as a cycle: sense, decide, act.

• Choose kits by age group and available lesson time.

• Start small with one unit and one year group.

• Value debugging as much as a working robot.

Photos: Cedric Folliot, Keerthan DM / Unsplash