> For the complete documentation index, see [llms.txt](https://robonation.gitbook.io/robotx-2026-team-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robonation.gitbook.io/robotx-2026-team-handbook/section-2-design-documentation/2.4-design-strategy-presentation.md). # 2.4 Design Strategy Presentation Teams are required to give a design strategy presentation to a panel of subject matter expert judges. The goal of the presentation is to share the team’s System of Systems (SoS) design approach to the challenges presented in the Autonomy Challenge, specifically the capabilities required for each task. The presentation should include: * a concise description of the team's strategic vision, and * how the SoS design compliments the team’s goals. ## 2.4.1 **Deliverable** Requirements This presentation must be conducted in English and may include visual aids (i.e. digital slides, poster board). If digital slides are used, teams must provide their own computer and adapters for an HDMI connecter to use the presentation display monitor. Teams receive an assigned 30-minute presentation time. The presentation schedule can be found on the RobotX Challenge webpage: [robotx.org/2026](https://robotx.org/2026)*.* This presentation includes: * Team introduction video - 3 minutes * Team presentation – 20 minutes * Judges’ question and answer – 5 minutes ## **2.4.2 Scoring Metrics** The design strategy presentation is worth a total of 180 points. The scoring metrics include a scoring weight with guidance for scoring considerations that are provided to the judges during evaluations. #### **Competition Strategy** (30% of score)


Outstanding	Presentation includes a concise description of the team's strategic vision and how the system design compliments their goals. The team clearly explains how they developed their competition strategy.
Strong	Presentation describes their competition strategy and how their system design aligns with meeting their competition goals.
Average	Presentation includes a brief overview of how the system design aligns with the team’s competition strategy and goals.
Below Average	Team mentions a competition strategy but no additional details on how it was developed or how it led to their strategic vision.
Requirements Not Met	Team does not mention their competition strategy, vision or how their system design is aligned with vision.

#### **Design Rationale** (30% of score)


Outstanding	Team presents their design process and how their decisions relate to their overall competition strategy. Lessons learned from testing or previous competition experience are described, including application throughout the design process.
Strong	Presentation includes a description of the team’s design process and includes narrative on how testing or previous experience influenced system design.
Average	Team describes the rationale behind the system design process.
Below Average	Presentation includes mention of the design process, lacking a clear rationale of design choices.
Requirements Not Met	No mention of the team’s design process or the rationale behind the design process.

#### **Effective Communication & Professionalism** (20% of score)


Outstanding	Presentation materials and team members’ knowledge are effective and support the team's message. Team members are engaging, respectful, and professional, while interacting positively with the judges and each other.
Strong	Presentation materials are presented in a professional manner and support the team’s message. Presentation is well prepared and appears to be rehearsed in advance.
Average	Presentation materials are presented in a mostly professional manner and support the team’s message.
Below Average	Presentation materials and styles are adequate but less than engaging.
Requirements Not Met	The message was not effective, and the presentation was not organized.

#### **Judge Questions & Dialogue** (20% of score)


Outstanding	The team effectively uses evidence, experience, and research from their project to inform responses to all questions and discussion posed by the judges.
Strong	The team responded professionally and knowledgeably to judges’ questions.
Average	The team responded adequately to most or all of the judges’ questions, mostly interacting with courtesy and professionalism.
Below Average	The team did not provide sufficient answers to the judges’ questions and interacted with minimal courtesy and professionalism.
Requirements Not Met	Team members were not able to respond to many or all questions and did not take the initiative to engage in dialogue with the judges.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://robonation.gitbook.io/robotx-2026-team-handbook/section-2-design-documentation/2.4-design-strategy-presentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.