<G4>
All work must represent the skill level of the Students on the Team. The Team’s design, Robot, coding, strategy, and ongoing work must represent the skill level of the Students currently on the Team.
• Teams must avoid academic dishonesty and should not copy a Robot or mechanism that has been provided for them. This includes, but is not limited to, the use of instructions, pictures & videos, notebooks, CAD designs, and/or any other documentation useful to the design process provided by anyone that is not a Student on the Team (including Students on another Team).
• Teams may be inspired by designs by other Teams, and use an idea from someone else to spark innovation, but are expected to document and demonstrate this in their engineering notebook alongside evidence of iteration. Teams are required to present this evidence if asked to do so by a Robot inspector, Head Referee, Event Partner, or Judge. Using elements of another design as a starting point is acceptable if the Team is capable of demonstrating evidence of iteration, innovation, and/or modification that makes the design uniquely their own. Documentation should clearly demonstrate the idea that was used for inspiration, and how it was changed for the final implementation on the Team’s Robot. It should be clear that this final implementation is not an exact copy of ANY other original design. Failure to demonstrate evidence of iteration, innovation, and/or modification will result in a Violation.
• Teams may use Robot plans and code (e.g., the annual Hero Bot, VEXcode configurations, etc.) provided by VEX Robotics or the RECF, but are encouraged to use these Robots, mechanisms, and code only as a starting point that Students modify, improve, or replace as their skills increase. Plans provided by VEX Robotics or the RECF are the only legal plans available for use in competition.
• This rule still applies to Teams within the same school, organization, or club. Robots and/or code sets that are identical or substantially similar to one another across Teams within the same school/organization/club will be considered in Violation of this rule, regardless of whether they compete in the same or different events. Clause D does not apply in situations where both/all Teams are using the unmodified Hero Bot design, as allowed by clause C of this rule. For more information, including acceptable and unacceptable examples of mechanical design, construction, coding, and strategy solutions, please refer to the Student Centered Policy in the RECF Library. The VEX Robotics Competition and the Robotics Education & Competition Foundation (RECF) recognize that many third-party individuals and organizations produce and distribute robot designs, instructions, and/or other materials that are not under our direct control. We cannot legally regulate or restrict the activities of these external entities. However, when Teams use these resources in ways that violate the spirit and letter of the VEX Robotics Game Manual—particularly Rules<G2> and <G4>—they undermine the core mission of the program: to provide Students with hands-on opportunities to learn, design, and innovate. While it is never our intent to punish Students, we can legally regulate and restrict the activities of the Teams in our competitions, and we must preserve the fairness, educational value, and integrity of the competition. Therefore, Teams found to be in Violation of these rules will be held accountable to the strictest interpretations of <G2> and <G4>. It is the responsibility of each Team to be able to explain and defend the design, construction, and programming of their Robot if questioned by referees, inspectors, Event Partners, or judges. Teams should be prepared to describe their design process, justify design decisions, and demonstrate a full understanding of how their Robot and code function. If a Team is unable, for any reason, to provide reasonable evidence (when requested by event staff) that their Robot and code are the result of their own work, it is appropriate to assume that the Team is in violation of <G2> and/or <G4>. Event organizers cannot reasonably know the origins of every design or independently verify whether a Robot was created from scratch, purchased online, or copied from pictures of another Team’s design. When questions of authenticity arise, the only direct and fair approach is to require Students to explain and defend their work. This is not unlike academic honesty concerns in schools, and intellectual property concerns in business. By requiring Students to defend their designs, we ensure that they are developing not only technical skills, but effective communication skills and accountability, as well. Consequences may include disqualification from Matches, removal from events, and/or escalation of the investigation to VEX Robotics and the RECF for further disciplinary action, which may include sanctions up to and including removal from the program. Event staff should bear in mind <G3>, and use common sense when enforcing this rule. It is not the intent to actively hunt for Violations of this rule, compare every Robot at an event to all other known Robot designs, or closely question every team at an event about their Robot’s code. This rule is a set of tools for use if potential Violations are noted by or reported to event staff, and it is expected that most Teams will never be required to defend their Robot design or code. Teams or individuals who deliberately weaponize, manipulate, or falsely report <G4> Violations for competitive gain or to harass another Team may be subject to a separate RECF Code of Conduct investigation. Misuse of this rule is considered a serious Violation.
Violation Notes:
• Teams believed to be in Violation of this rule should be reported to the Judge Advisor, Head Referee, or Event Partner for further investigation in coordination with the RSM. Based on the investigation the Team may be removed from further Matches, have their Robot Skills Challenge scores removed, and/or be removed from consideration from judged awards.
• Violations of this rule will be evaluated on a case-by-case basis, in tandem with the RECF Student Centered Policy as noted in <G2>, and the REC Foundation Code of Conduct as noted in <G1>. All reported and/or suspected <G4> Violations should be reported to the Event Partners during the event, and should be reported to the RECF Rules and Conduct Committee following the event.
Significant Q&As:
• Q&A 2677 - Teams may only use custom parts that were designed and created by the Students on that Team
• Q&A 2823 - Excerpts from the Student-Centered Policy about code, templates, and libraries
• Q&A 2834 - Specific G4 scenarios and clarifications
• Q&A 2843 - Ownership of ideas when students legally change teams
• Q&A 2850 - Holecounting a design is not the same as being inspired by it
Game Rules Index