RoboCupJunior Soccer Award Criteria and Rubrics
These are the official award guidelines for the International RoboCupJunior Soccer League, issued by the RoboCupJunior Soccer League Committee. The English version takes precedence over all translations. For questions or suggestions, visit the RoboCupJunior Soccer Forum or RoboCupJunior Discord Server.
This Award Criteria and Rubrics Document is guaranteed to be used for the International Tournament only. Each Region may have different methods of awarding teams and determining team rankings. Regional Tournaments may use this as a guideline as is or with modifications for their own competitions. Check with the organizers of the tournaments you are participating in to find out which version they are using.
Change: | Date: |
Initial Document Creation for 2024 Season. | 2024-04-01 |
Rubric and Criteria Document rework for 2025 Season (draft 1) | 2025-05-08 |
Addition of 3 Bonus points mentioned in TDP Form | 2025-06-18 |
Corrected 3 bonus points for mention in TDP Form | 2025-07-02 |
1.1.1 Individual Gameplay Tournament
1.1.2 Technical Documentation Paper Form (TDP Form)
1.1.3 Poster Design & Presentation
1.1.5 Sportsmanship, Leadership and Outreach
1.2.1 Gameplay Tournament Podium Positions
1.2.2 Outstanding Design Certificate
1.2.3 Outstanding Innovation Certificate
1.2.4 Outstanding Documentation
1.2.5 Exemplary Team Certificate
2.1 Technical Description Paper Form (TDP Form)
2.4 Sportsmanship, Leadership and Outreach
Appendix A: Group Interview Questions
Two kinds of awards are given out at the international tournament: Trophy awards and certificate awards. Only one Team (or SuperTeam) can win each trophy award. Certificate awards will be awarded to every team that meets excellence criteria and can be won by any number of teams.
Teams will be evaluated based on the following criteria:
There are 3 Individual Team Trophies for 1st, 2nd and 3rd place overall, based on the results of the Individual Gameplay Tournament combined with the Award Criteria described in this document. The final score of a team will be the sum of the scores over all the Award Criteria. If there are any equal teams in scores, the order of teams in the Individual Gameplay Tournament will be the tie breaker.
The Community Award will be given to one team as voted by all other teams.
The winning SuperTeams will receive the SuperTeam Award that is separate from the individual team scoring (individual scores and SuperTeam scores do not affect each other).
Individual Gameplay Tournament place turns into overall ranking points as follows:
Individual Gameplay Tournament Scores - Example with 29 teams | ||||||||
1st | 2nd | 3rd | 4th | 5th | … | 27th | 28th | 29th |
30 Points | 27 Points | 25 Points | 24 Points | 23 Points | … | 1 Point | 0 Points | 0 Points |
The TDP Form is an online questionnaire to complete prior to the competition. It consists of a series of prompts designed to help create a structured document similar to a Technical Description Paper. Note there are three bonus points mentioned within the TDP Form.
TDP Form Scoring Values | |||
Developing | Satisfactory | Proficient | Excellent |
0 | 1 | 3 | 5 |
Before the competition, teams will create a poster about their robot and team. During the competition, there will be a poster session where teams will show their own and view each others’ posters and help explain parts of their robots to share their innovations and designs.
Click here to see the Awesome RCJ Soccer GitHub Repository past Team Posters!
Poster Design & Presentation Scoring Values | |||
Developing | Satisfactory | Proficient | Excellent |
0 | 1 | 3 | 5 |
In this challenge-based evaluation, teams will complete a small robot task to demonstrate their teamwork, problem-solving, and technical understanding. This task will occur alongside one to three other teams. Judges will assess collaboration, communication, and design knowledge.
Teams should bring their Robots, Laptops and programming equipment to the interviews and expect the interviews to contain these elements:
Judges have a standard list of questions they can ask with some modifications to help minimize translation issues. Please see Appendix A: Group Interview Questions.If your team needs language assistance please let us know as soon as possible (e.g. at check-in at the Soccer desk) and we will try to arrange someone to translate. Please be aware that this cannot be a mentor or guardian. Availability of translation unfortunately cannot be guaranteed.
Group Team Interview Scoring Values | |||
Developing | Satisfactory | Proficient | Excellent |
0 | 1 | 3 | 5 |
Sportsmanship is the cornerstone of any successful tournament. Therefore we don’t only ask teams to show respect for other teams, leagues, tournament officials, hosts and locations but we also reward it with points. To get these points, be on time for matches, meetings and interviews, be fair to your opponents, be polite to everyone, be open about sharing what you know and don’t accuse anyone of bad behavior without very good reason.
Sportsmanship Scoring Values | |||
Developing | Satisfactory | Proficient | Excellent |
0 | 1 | 2 | 3 |
RoboCup’s mission is to advance the field of robotics and to beat humans at playing Soccer by the year 2050. Nobody can do this alone, therefore we share our knowledge freely in the spirit of academic cooperation.
Teams that make their work available to others contribute to the ability of all future teams (including those not at the same events) to develop more advanced robots by building on top of their work. This can take any form but is often write-ups/papers, videos, test results, instructions how to do things, sometimes with source code, circuit diagrams or CAD files.
Doing this is required for an “Outstanding Documentation” award certificate.
Documentation and Community Contribution Scoring Values | |||
Developing | Satisfactory | Proficient | Excellent |
0 | 1 | 3 | 5 |
The community award is presented to the team that contributes the most to building and fostering a sense of community throughout the competition. Either through passing on their knowledge to other teams, helping others with any arising problems, or overall just being a pleasure to be around.
This award is voted for by the teams themselves. Each team votes for their top 3 teams in each of the following categories:
When you vote, the 1st team receives 3 points, 2nd 2 points and 3rd 1 point.
All teams HAVE to vote and are NOT allowed to vote for themselves. Voting for oneself will result in being excluded from this award and losing points on sportsmanship.
The team with the most voting points overall will receive the award and will receive an extra point on the overall ranking - not enough to get ahead of a better team but it may break a tie.
Certificates are a valuable award, offering recognition to teams who may not have earned a trophy but still demonstrate exceptional achievements and abilities. While trophies highlight the top overall performances, certificates ensure that every deserving team is acknowledged for their hard work, dedication, and the skills they've displayed throughout the competition.
Teams are able to earn Certificates based upon the following categories:
There are no physical or organisational limits to the number of certificates that may be awarded. All teams meeting the qualifications below will be awarded a certificate.
Teams who come 1st, 2nd or 3rd in the Individual Tournament will receive a certificate for their placing. This can be awarded in addition to overall 1st, 2nd or 3rd place Trophies.
To qualify, all of the follow must be met:
Teams recognized for outstanding design have fielded robots that are great examples of what can be done through the application of the engineering design process. To qualify, all of the follow must be met:
Teams recognized for an outstanding innovation created a design that is both novel and effective for others to learn from. To qualify, all of the follow must be met:
Teams recognized for outstanding documentation have demonstrated excellence in capturing and communicating their engineering process. To qualify, all of the following must be met:
Exemplary teams are the best examples of the effective application of soft and hard engineering skills. These teams are amongst the top performers, have outstanding designs or innovations, and serve as community leaders for their league by pushing the state of technology available to the community forward. To qualify, all of the follow must be met:
The SuperTeam Challenge is a side tournament run during the International Competition. It is typically organised as groups of 4 or 5 Teams merging together to form 1 SuperTeam. These SuperTeams will compete in a mini tournament on an expanded soccer field.
The SuperTeams are created based on the results of the Individual Gameplay Championship ranking, to best distribute the Teams into fair, balanced SuperTeams. Each team is allowed to have a maximum of 1 of their robots on the SuperTeam Field, with the lowest ranked teams allowed to have 2, only if another Team has no working robots.
Learn more about SuperTeams here!
The SuperTeam position rankings do not affect the Individual Championship scores. However, teams’ Sportsmanship during the SuperTeam games do affect that criteria. It is expected of SuperTeam member teams to work together, help each other out in case of technical difficulties, take care that all SuperTeam member teams show up to the games together and not to sideline weaker teams.
There is 1 Trophy to be won for being in the winning SuperTeam during the challenge. Each team within the winning SuperTeam will receive this Trophy.
A team’s Technical Description Paper should provide evidence of student centered work in electrical, mechanical, software, and strategy development and is a resource for everyone, including the publishing team and all future teams. The Soccer Committee has chosen to implement this through a Google Form document to simplify the process for teams & educators. The answers in these sheets will be compiled into TDP documents and published. There are 3 bonus points available through the TDP Form for Open-Sourcing the CAD files, PCB and Schematic files, and Software repositories.
Rubrics | Developing | Satisfactory | Proficient | Excellence |
Electrical | Team did not submit on time. Little to no original pictures, video, CAD renderings, schematics, sketches, or work. Elements of others’ work without proper accreditation (e.g., non-referenced previous team’s work). Documentation lacks a clear design process or visuals. Contains minimal mechanical diagrams or construction steps. May include reused content without context or credits. Software documentation is missing or unclear. Code snippets are unoriginal, unexplained, or lack context. No evidence of debugging or iteration. Disorganized or incomplete documentation. Poor formatting and navigation. No table of contents or labeling of sections. | Documentation provides basic details of electrical design. Includes some original visual artifacts. May have minor attribution issues or lack clarity. Includes basic steps of mechanical construction. Shows some original work (e.g., CAD, prototypes). Describes how components were built or assembled. Some code is explained with comments or screenshots. Includes a basic overview of programming languages, libraries, or platforms used. The document is readable and has a basic structure. Sections are labeled, but may lack clarity or polish. May be missing timestamps or team member attributions. | Documentation provides sufficient detail for a technical reader to replicate the design process. Includes original visual artifacts (e.g., wiring diagrams, schematics, photos). Design appears student-created. Clearly describes mechanical strategy and design iterations. Visuals support the narrative (e.g., annotated CAD, exploded views). Includes testing data or notes on how design was evaluated. Provides meaningful insight into code structure and function. Describes algorithmic logic and control schemes. Includes some discussion of testing and refinement. Well-organized and easy to navigate. Sections are clearly labeled and include context (e.g., team roles, dates). Shows collaboration across sub-teams. | Meets all Proficient criteria AND evaluates use of resources (e.g., budget, tools, components). Includes data-driven reasoning for design decisions. Reflects on failures and improvements. Demonstrates growth in electrical knowledge. Meets all Proficient criteria AND explains design trade-offs and constraints (e.g., weight, materials, mobility). Includes revisions based on performance. Demonstrates a cohesive mechanical strategy tied to the robot's goals. Meets all Proficient criteria AND includes version control usage, flowcharts, or pseudocode. Reflects on debugging, testing processes, and how code evolved. Demonstrates thoughtful programming choices tied to performance. Meets all Proficient criteria AND includes a clear narrative of the team’s journey. Demonstrates thoughtful storytelling, aesthetics, and professionalism. References all sources and includes team reflections. |
Mechanical | ||||
Software | ||||
Presentation |
A team’s poster is a way of sharing their robot’s design and discoveries to everyone during and after the event. RoboCupJunior will archive all posters after the event for future teams to study. During the competition there will be a Poster Presentation period (“Poster Session”) where teams will discuss each others' robots in an open format.
Example posters from previous years’ teams can be found here:
Awesome RCJ Soccer GitHub Repository
Rubrics | Developing | Satisfactory | Proficient | Excellence |
Abstract | Abstract is missing, unclear or wholly incomplete (i.e omits many critical elements of the poster). Very little to no information about production (i.e. design, construction, programming, component selection, and overall process). No data is displayed OR data analysis is not relevant to project development. Several photos and graphics of a poor quality OR are not relevant to the related section of the poster. The poster does not follow a logical layout OR contains many spelling or grammatical errors. Team not present during poster presentation session. Poster is outside the format specifications. | Abstract is somewhat incomplete (i.e. omits some critical aspects of the poster) OR repeats detailed information already in the poster. Some information about production (i.e. those listed in rubric 1) OR complete information is supplied but descriptions are not clear and concise. Minor data resulting from testing is displayed OR significant data resulting from testing is displayed but no major modifications based upon the testing are mentioned. Photos and graphics are relevant to the related section of the poster but some are not labeled or cited. The poster follows a somewhat, but not wholly, logical layout OR the poster contains a few spelling or grammatical errors. Team was absent for a significant portion of the poster session OR was not able to answer any questions adequately. | Abstract clearly summarizes each critical component AND uses appropriate scientific language. Complete information about production AND the information is clear and concise. Significant data resulting from testing is displayed AND major modifications were made on the robot as a result of testing AND data and results are displayed clearly (e.g. using graphs or tables). Photos and graphics are relevant AND excellent quality AND appropriately labeled and cited. The poster has a clear and logical layout (i.e.Information is easy to access for the viewer, with graphics, images and text appropriately positioned and font size consistent). Spelling and grammar are error free. Team was present during the poster session but was regularly absent OR did not actively engage OR did not adequately answer questions. | Rubric 3 is satisfied AND there is a clear intent to share actionable knowledge. Rubric 3 is satisfied AND there is a clear intent to share all actionable knowledge. Rubric 3 is satisfied AND the poster demonstrates a clear understanding of the link between testing, evaluation and modification based upon the testing AND method of testing is described so it may be repeated by others. Rubric 3 is satisfied AND the amount of images are appropriate to the content being presented. Rubric 3 under “Layout/ Design” AND has an original design that effectively highlights the team’s creativity and professionalism. Team present during the entire poster session AND actively engaged with judges, participants, and guests AND did their best to answer any/all questions. |
Method, Production & Design | ||||
Data, Results & Discussion | ||||
Photos & Graphics | ||||
Layout & Design | ||||
Presentation |
In this challenge-focused evaluation, teams will participate in a structured group task designed to assess teamwork, problem-solving, and technical understanding. Each team will be asked to complete a small robot-related challenge (for example, programming their robot to drive in a square) within a shared session alongside one to three other teams. Teams will demonstrate their approach, reflect on their collaboration, and engage in discussion with peers. Judges will assess how effectively teams work together, understand their robot systems, and communicate their design choices. Active participation, respectful peer interaction, and shared team involvement are key to scoring well.
Teams should bring their Robots, Laptops and programming equipment to the interviews and expect the interviews to contain these elements:
During the task, Judges may ask teams questions about their robot design, strategy or other items. These questions will only be from the list in Appendix A: Group Interview Questions. Extra consideration will be given to teams who have students that have difficulty speaking in English if judges are made aware.
Rubrics | Developing | Satisfactory | Proficient | Excellence |
Teamwork & Communication | Team was disorganized, one or more members disengaged or dominating. Poor communication or conflict was evident. Team struggled to explain or apply their design. Robot could not complete the task or had minimal function. Task was attempted with basic or partial functionality. Errors were not clearly diagnosed. | Team showed some coordination, but communication was inconsistent or relied heavily on one person. Team completed the task but with unclear or limited understanding of how their robot functioned. Task was completed or close to completion. Team adapted to challenges and explained decisions well. | Team worked together with clear roles. All members contributed meaningfully to the task. Team demonstrated a solid understanding of their design. Task was completed or attempted with logical reasoning and explanation. Task was completed efficiently with innovative approaches. Team handled problems with confidence and clear strategy. | Team showed seamless collaboration. Members supported each other and communicated effectively throughout. Team showed strong technical fluency and problem-solving. Explanation and execution were clear, creative, and insightful. Task was completed efficiently with innovative approaches. Team handled problems with confidence and clear strategy. |
Technical Understanding | ||||
Task Execution & Problem Solving |
Sportsmanship expectations include the behavior of students, mentors, parents, and anyone else associated with the team attending the event. Although everyone is competing, we’re all involved to learn and have fun; participants should not hinder the experience for others.
Attendance at each general match, Technical Challenge, SuperTeam match and interview will be taken. Teams should come on time and prepared to keep their robots functional for the entire event and should have a member in charge of keeping a schedule. If a team cannot participate in a match or activity, the referees should be notified.
We expect spirits to be high and conflicts between teams and/or volunteers will sometimes occur. It is critical these are handled in a respectful manner by not accusing anyone (team or referee) of willful wrongdoing without very good reason and giving everyone the benefit of the doubt for clearing up what is usually just a misunderstanding. Unless in extreme cases, participants will be given a warning before teams are penalized by tournament organizers.
Exemplary teams enhance their community or RoboCup Junior community in general by providing resources and encouragement for others. The organizing committee may be made aware of these efforts through their own observations, what is presented in any other criteria (e.g. team documentation), or by nomination from another team or volunteer through the community award voting process
Rubrics | Developing | Satisfactory | Proficient | Excellence |
Sportsmanship | Disrespectful behavior continued after warnings. Team missed over half of matches or key challenges. No participation in SuperTeam or technical challenges. Team lacked defined roles. Relied On adults. Little evidence of student ownership. Significantly negatively impacted other teams’ experience at the competition. | Team was occasionally uncooperative or late. Missed some matches or challenges. Behavior improved after reminders. Some student leadership evident, but roles unclear or inconsistent. Sometimes difficult situations were escalated but ended up resolving them fairly. | Team was consistently respectful and on time. Participated fully in matches, SuperTeam, and technical challenges. Contributed to a positive environment. Clear student-led roles and decision-making. Team showed independence and problem-solving. Handled difficult situations calmly and fairly when they arose. | All Proficient criteria plus: Team actively supported others (e.g., shared tools, cheered opponents, helped peers). Set an outstanding example of collaboration and kindness. All Proficient criteria plus: Students mentored peers, resolved issues constructively, and empowered all voices. Exhibited initiative and ownership. Prevented difficult situations from escalating early and behaved sportsmanlike at all times. |
Teams that make their work available to others in addition to building robots contribute to the ability of all future teams (including those not present at the same events) make it possible for more teams to develop more advanced robots and to build on top of their work. These contributions can come in any form but frequently take the shape of write-ups/papers, videos documenting and instructing how to replicate their work, sometimes accompanied with releases of source code, circuit diagrams or CAD files.
Rubrics | Developing | Satisfactory | Proficient | Excellence |
TDP | TDP was not filled, not nearly complete or not filled with any meaningful information. Poster was not created, poster session not attended or information was not shared during the interview. Nothing was shared publicly. Note: This alone will not result in a “developing” - although we expect things that can be of use to the community to be shared in the academic spirit. | TDP was filled with all required information. No or little care was taken to present information so it is easy to understand. A poster was created but lacked a lot of information poster session was attended, information was shared on request in the interview Nothing except the poster and TDP were shared publicly. | TDP was filled with all available information and presented in a helpful and easy to understand way. An informative poster was created and questions answered well during the poster session. Design highlights shown at interview on own initiative. At least one or two of Testing data, design drawings or -files, code, explanations or sources for materials were shared publicly for other teams to benefit from. All criteria of “Satisfactory” also met or exceeded | TDP was filled with all available info, presented well, supplemented with sources and links to more helpful material and easy to understand Poster was informative, detailed, well presented Design highlights shown in interview on own initiative. Both in a way that helps others replicate and build on their success. Everything needed for others to learn from the team's design published (see “Proficient” for examples), contact details for questions available (Forum or Discord name(s) encouraged). All criteria of “Satisfactory” and “Proficient” also met or exceeded |
Poster, Presentation & Interview | ||||
Open Source and published materials |
Judges may ask questions from the following list and may ask followup questions based upon responses. Judges should focus questions on items that may need clarification or were missing from a team’s presentation or design document. No more than one question from each category should be asked.
General:
Electrical:
Mechanical:
Strategy:
Software:
Development and Documentation: