How to Prepare
Your Child for WRO
Competition Season

For families new to it, the World Robot Olympiad can feel like a big unknown. Your child has been loving their weekly robotics class, and now there's talk of a "season", a "category", a regional event and possibly a national final. What does preparing actually involve — and what's your role as a parent?

The good news: the heavy lifting happens in class, with their coach. Your job is mostly to support, not to engineer. But the children who arrive at a WRO event calm and ready almost always have a few things in common — and most of them are things any parent can help with. Here's the full picture for the South African season.

First, Understand the Season

WRO runs on an annual cycle. Each year a fresh challenge and game mat are released, and teams spend the months that follow designing, building and programming a robot to complete missions on that mat. In South Africa the season builds toward regional events through winter and spring, with the strongest teams progressing to the national final and, ultimately, the international final.

For Gauteng families, the regional events are the dates that matter first. This season, Robotics League teams are preparing for:

• 31 July 2026 — Curro Aurora: Explorer Prime & Explorer Lite
• 22 August 2026 — Curro Krugersdorp: RoboMission Elementary & Junior

Knowing the date your child is working toward changes everything about preparation. It turns a vague "we're doing robotics" into a concrete countdown — and children respond remarkably well to a real deadline with a real goal at the end of it.

Make Sure They're in the Right Category

WRO is organised by age and experience, so children compete against genuine peers. Your child's coach will place them in the appropriate category, but it helps to understand the broad shape of it so you can talk to your child about what they're aiming at.

The Build Should Be Theirs

This is the single most important principle of WRO, and the one parents most often get wrong with the best intentions: the robot and the code must be the child's own work. WRO is judged on what the students can do, not what a coach or parent can do for them.

That's not just a rule — it's the entire point. The learning happens in the struggle: the failed runs, the sensor that won't behave, the turn that's two degrees off. A child who has personally debugged their robot fifty times walks onto the competition floor with a quiet, unshakeable confidence. A child whose robot was "fixed" for them does not.

What Good Preparation Actually Looks Like

Practise the Pressure, Not Just the Robot

Many children can run a flawless mission at home and then freeze when there's a clock, a judge and an audience. This is normal — and it's trainable. The way to build composure is to rehearse the conditions, not just the code.

In the final weeks, good coaches run mock rounds: a timer counting down, a few people watching, and the expectation that the robot runs first time. The first few are messy. By the fifth, the nerves have somewhere familiar to go. By competition day, the event feels like just another practice round — which is exactly the goal.

What Parents Can Do (and What to Avoid)

Your influence on competition day is bigger than you'd think — and almost all of it is emotional, not technical. The most helpful things parents do:

• Protect sleep and food. A tired, hungry competitor makes careless mistakes. A good night's rest and a proper breakfast matter more than one last practice run.
• Keep the stakes in perspective. Children take their emotional cue from you. If you're relaxed and proud, they compete relaxed. If you're anxious about the result, they feel it.
• Celebrate the process. Ask about the problem they solved, the bug they finally cracked — not just the score. That's where the real growth is.
• Let the team own the day. Cheer loudly, then step back. The robot, the strategy and the recovery from a bad run all belong to them.

And the one thing to avoid: never touch the robot or the code at the event. Beyond breaking the rules, it sends a child the message that you didn't believe they could handle it themselves — which is the opposite of everything WRO is meant to build.

A Simple Season Timeline

If you'd like a mental model of how the months ahead unfold, it looks roughly like this:

1. Early season: understand the challenge, study the game mat, sketch a strategy.
2. Mid season: build the robot, get a first version of every mission working — however roughly.
3. Late season: refine, test relentlessly, and chase consistency over cleverness.
4. Final fortnight: mock rounds under pressure, finalise the code, and rest.
5. Event day: arrive early, stay calm, and let them compete.

New to All This? Start Here

You don't need to understand WRO to get your child into it — you just need to get them started, and the pathway takes care of the rest. Competition isn't compulsory either: plenty of children do robotics purely for the love of it, and step up to a team only when they're ready and keen.

If your child has shown a spark for building, coding or solving problems, a free trial class is the easiest way to see where it leads. Many of the children now preparing for this season's WRO events started exactly there — with a single trial class and a robot that didn't quite work yet.