Mediori
For students aged 9 to 12 who want a more serious technical challenge. The team develops a robot or robotic system with autonomous behaviour, sensors and a clear explanation of the solution in front of the judges.
Who is the Mediori
category for?
They have a technical grounding
For secondary-school students who already know the basics of programming, electronics or robotics and want to apply that knowledge to a harder task.
They work as a development team
The team divides the roles: build, programming, testing and presentation. The mentor helps with preparation and with organising the process.
They are ready for the final
The Mediori format introduces clearer technical criteria, a public presentation and a direct comparison of solutions before an expert panel.
The 2026 challenge
The team prepares a robot or a system that reacts to its surroundings on its own. The focus is on sensors, decision-making, reliable movement and the team’s ability to explain the technical logic behind it.
The 2026 theme is a robot that learns from its environment: the system recognises markers, obstacles or conditions on the course and chooses its next step from that.
This competition asks for more testing and clearer documentation than the younger categories. The judges assess both the result and the development process: how the team reached its decisions, what was tested and what was improved.
Detailed rules and course specifications will be published in the PDF rulebook. The information here is general guidance for your preparation.
Examples of task types
- Autonomous movement through a changing course
- Using sensors to recognise obstacles
- Decisions made in code from the readings collected
- Optimising movement and mission time
- Presenting the technical approach to the judges
What do you need to prepare?
A working prototype
A robot or system that can complete the basic mission and be tested repeatedly under similar conditions.
Programme logic
A clear structure to the code: read the sensors, decide, act. The team should understand the logic, not simply run the code.
Testing
Keep notes on what you tested, what did not work and how you arrived at a more stable solution.
Division of roles
Who leads the mechanics, who the code, who the testing and who presents. A well-organised team answers the judges’ questions more easily.
Mentor and entry
Have the details of the team, the school and the mentor ready. The mentor is the contact person and looks after the team’s organisational side.
Brief documentation
We recommend a block diagram of the programme, a sensor schematic and a short description of your approach. It helps during the presentation.
Key dates
Frequently asked questions
Is previous experience required?
Some basic experience in programming, electronics or robotics is recommended. Mediori is not a beginners’ category, but professional-level knowledge is not expected.
Does the mentor have to be a teacher?
The mentor can be a teacher, an instructor or another adult who supports the team organisationally. The detailed conditions will be set out in the rulebook.
Can we use our own robot?
Yes, if it meets the conditions in the rulebook. Permitted platforms, dimensions and limits will be published before the event.
Is documentation assessed?
Brief documentation is not always formally required, but it helps the team explain its solution. The judges may ask how the system was designed and tested.
When do the course specifications arrive?
The specifications and rules will be published before the event, together with guidance on preparing your team.
Who do we send questions to?
Send your questions through the contact form. The organisers will pass the enquiry on to the person responsible for the competitions.