Project ideas by age
Pitch the challenge so that most groups can reach a working version and stronger groups can extend it.
Ages 5 to 7: program a floor robot to deliver a 'letter' to houses on a town mat.
Ages 8 to 10: build a buggy that follows a black line using a light sensor.
Ages 10 to 12: design a sorting machine that separates objects by colour.
Ages 12 to 14: make an automatic plant-watering alarm with a moisture sensor.
Ages 14 and over: build a robot arm from card or 3D-printed parts driven by servo motors.
A model brief: the rescue robot
This project suits pupils aged 11 to 13 across four 50-minute lessons. Each group of three needs a programmable robot kit with at least two motors and one sensor, card, tape, and a laptop. The task: move a small 'casualty' (a cardboard tube) from one zone of a taped arena to a safe zone without crossing a marked hazard.
Lesson one covers planning and sketching. Lesson two is building and a first drive test. Lesson three focuses on programming and sensor use. In lesson four, groups run timed attempts and present one design change they made and why.
Running the sessions
Give each pupil a role, such as builder, programmer or tester, and swap roles each lesson so everyone does every part. Keep a simple design log where groups note what they tried, what happened and what they changed. The log is often more useful for assessment than the final robot.
Short progress check-ins help too. At the start of each lesson, ask every group to state one goal for the session; at the end, ask whether they met it and what stopped them if not. This keeps groups focused and shows the teacher where extra support is needed.
Set up a test area that stays in place between lessons, and leave ten minutes at the end for tidying and sorting parts. Missing pieces cause more lost time than any technical problem.

Materials on a budget
Many projects need fewer parts than a full kit. Recycled card, bottle tops and elastic bands are useful for grippers and bodies. A micro:bit with a few motors and sensors can support most primary projects, and the MakeCode simulator lets pupils test code before the hardware is free.
Ask families for clean packaging and small household items at the start of term, and keep them sorted in labelled trays. Pupils often design more inventive mechanisms when they cannot rely on ready-made parts.
Key points
Set a problem to solve, not just a model to copy.
Rotate builder, programmer and tester roles.
Assess the design log alongside the finished robot.
Plan time for tidying and parts checks every lesson.
Photos: Marília Castelli, Robin Glauser / Unsplash
Hands-On Robotics Projects
Robotics projects work best when pupils solve a real problem rather than follow a build guide to the end. A clear brief, limited materials and time to test and improve give better learning than a large kit used once. Below are project ideas by age, a model brief, and advice on running the sessions.
Edutech
/
/
Hands-On Robotics Projects
