> For the complete documentation index, see [llms.txt](https://docs.wcrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcrobotics.org/team-handbook/handbook/team-travel.md). # Team Travel Students are required to attend all FIRST Robotics Competitions with the team. All meal expenses are paid by each student and adult traveling with the team. Travel itinerary and information will be provided mid-season. Student MUST attend the competitions (in their entirety) each year for two years to meet [lettering requirements](/team-handbook/handbook/membership-requirements.md#lettering-and-school-recognition). ### Expectations of students while traveling * Be a member in good standing (see Member Requirements). * Arrange ahead of time with their teachers to make-up any work missed (students will miss school on Thursday and Friday for regional competitions, plus Wednesday if we compete in the *FIRST* Championships). * Complete all necessary paperwork for travel (all [Final Forms](https://westcarrollton-oh.finalforms.com/), the Consent & Release in your online dashboard at [www.firstinspires.org](https://docs.wcrobotics.org/team-handbook/handbook/www.firstinspires.org), Pirate Robotics Handbook Acknowledgement Form, Safety Form, and any travel forms such as Permission Forms and the Student Behavior Expectation Form, etc). * Attends mandatory travel meeting(s). * Abide by all rules of conduct for traveling with the team (to be distributed prior to traveling). * Exhibit team spirit and “Gracious Professionalism” at all times while traveling. * Students must travel as a team. * Students will not be allowed to change travel arrangements or housing. * After each event, all team members must return with the team to help unload all equipment. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wcrobotics.org/team-handbook/handbook/team-travel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.