Run the Progression Test
Most school robotics is a sequence of enjoyable one-off activities rather than a curriculum. The difference is whether year three assumes and builds on year two.
The Bot Scout progression test asks a department to state, for each year group, what students can do that they could not do the previous year, and which assessable evidence shows it. If that table cannot be filled in, the programme is a collection of activities and should be scheduled honestly as enrichment.
Platform ladders help because they make progression concrete. Sphero publishes bands from ages 4+ through 14+, and buildable options such as Makeblock mBot and lab-grade platforms including ROBOTIS kits and ROS-based systems extend the top end.
| Stage | New capability | Assessable evidence | Platform level |
|---|---|---|---|
| Early primary | Sequencing and direction | A planned route executed | Screen-free sequencing robot |
| Upper primary | Loops, conditions, sensors | A program responding to input | Coding robot |
| Lower secondary | Data, variables, debugging | A logged experiment and fix | Sensor-capable robot |
| Upper secondary | Design and iteration | A student-designed mechanism | Buildable kit or rover |
| Advanced | Engineering and autonomy | An open-ended project | Lab-grade platform |
Assessment Without Killing the Subject
Robotics assesses badly when it is graded on whether the robot worked. It assesses well when it is graded on the reasoning: the plan, the prediction, the test, the diagnosis, and the fix.
Debugging is the most assessable and most transferable skill in the subject. A student who can explain why a program did the wrong thing has demonstrated more than one whose robot completed the course first time.
Keep the outcome ahead of the platform, as set out in the educational robots guide, and check that the coding environment supports a block-to-text path using the coding robots guide.
- State what each year adds that the previous year did not.
- Assess reasoning and debugging rather than whether it worked.
- Choose a platform ladder that spans the bands you teach.
- Store lessons where a second teacher can run them unchanged.
- Name the owner of the library and the rota for next year.
Making It Survive Staff Turnover
The single strongest predictor of a programme still running in three years is whether a second teacher can deliver a colleague's lesson without help. Test that deliberately rather than assuming it.
The classroom logistics that make delivery possible — charging, storage, pairing, and reset time — are covered in the robotics classroom guide, and the fleet budget in the education robots guide.
Budget for continuity rather than launch: spares, replacement small parts, and time for a second teacher to learn the platform. Programmes rarely die from bad curriculum; they die when the person who built it leaves.
Bottom Line
A robotics curriculum needs a stated year-to-year progression, assessment focused on reasoning, and a library any teacher can run. Budget for continuity, not just for launch.
Fill in what each year group can do that the previous one could not, then choose the platform ladder.
FAQs
What makes a robotics curriculum rather than activities?
A stated progression where each year assumes and builds on the last, with assessable evidence for the new capability. Without that table it is enrichment, which is fine if scheduled honestly.
How should robotics be assessed?
On reasoning rather than results. The plan, prediction, test, diagnosis, and fix show more learning than whether the robot completed the course first time.
Should a school standardise on one robot platform?
A platform ladder spanning the taught bands helps make progression concrete, but confirm that the next band exists and that lessons transfer between teachers before committing.
Why do school robotics programmes end?
Usually staff turnover rather than curriculum quality. If a second teacher cannot run a colleague's lesson unchanged, the programme depends on one person.