Starting a school robotics program that survives year two

First-year robotics programs almost always look successful. The kits are new, the teacher is enthusiastic, the photos are good, and nothing has broken yet. Year two is the real test, and the things that end programs are rarely the things schools plan for.

We have installed and supported enough of these to know what the failure modes look like. None of them are about curriculum quality. All four are logistical.

1. Storage decides whether builds continue

A robotics session is roughly fifteen minutes of setup and fifteen minutes of teardown wrapped around the actual work. If a partly-built robot cannot survive until next week, every session restarts from zero, and learners never get past the first third of any project.

The fix is unglamorous: shelving deep enough to hold a chassis without disassembly, one labelled bin per team, and a rule that bins are never emptied between sessions. Programs that share a room with three other subjects need this most and get it least.

2. Spares are a running cost, not a one-time purchase

Motors burn out. Connectors fatigue. Wheels lose grip. A learner will strip a gear the week before a demo. In a healthy program this is normal wear, not a crisis, but only if the spares drawer is stocked.

Schools that budget hardware once and never again spend year two cannibalising kits: one working robot assembled from three broken ones, and two teams with nothing to do. Build a small recurring consumables line into the budget from the start and the program never has to beg for it.

3. One trained teacher is a single point of failure

The most common way a school robotics program ends is that the teacher running it moves schools. If the knowledge lived entirely in that person, the kits go into a cupboard and stay there.

Two people trained is meaningfully more robust than one, even if the second person only co-teaches occasionally. Written session plans matter for the same reason: a program that can only be run from memory cannot be handed over.

4. Pacing is what actually breaks learners

A robotics curriculum that moves too fast produces learners who can follow instructions but cannot diagnose anything. Too slow, and the strongest learners disengage before the interesting work starts.

Pacing should be set against outcomes, not weeks. A learner moves on when they can wire a sensor and explain why it reads what it reads, not when the calendar says so. That requires a level structure, and it requires the honesty to hold a group back a level.

What a second-year program looks like

• Work in progress survives between sessions, in labelled team storage.
• A consumables budget exists and is spent without a special request.
• At least two staff can run a session unaided.
• Learners are grouped by demonstrated level, not by year group.
• Something in the room is visibly harder than it was last year.

None of this is about buying better robots. It is about treating a robotics program as infrastructure with a running cost, rather than an event with a launch date.