Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Team Registration and Roster Requirements: Mel provided detailed instructions to coaches on preparing team rosters, ensuring all members and parents complete electronic consent forms, and registering teams with Adventist Robotics prior to the tournament.
  • Roster Preparation Process: Mel explained that coaches must prepare a printed team roster, which includes all team members and coaches, and ensure that parents complete the electronic consent and release forms. The roster must be brought to the tournament for check-in, and teams cannot compete without it.
  • Electronic Consent and Release: Mel emphasized that parents must complete the consent and release forms electronically via the FIRST Dashboard. Once completed, the team roster can be printed, and instructions for accessing and submitting these forms were reiterated.
  • Team Registration with Adventist Robotics: Mel instructed teams to register with Adventist Robotics and pay the event registration fee through the Adventistrobotics.net website, noting that this step should be completed before the tournament registration deadline.
• Dean’s List and Leadership Award Nomination Process: Mel and Fiona outlined the process for nominating 10th or 11th grade students for the Dean’s List (Leadership) Award, including eligibility, submission deadlines, and the interview process led by Fiona as judge advisor.
  • Award Eligibility and Purpose: Mel clarified that the Dean’s List (Leadership) Award is intended for 10th or 11th grade students, not seniors or freshmen, and is designed to recognize leadership within teams. Coaches may nominate up to two students per team.
  • Nomination and Submission Details: Mel stated that coaches are responsible for submitting nominations by mid-March, with the exact deadline to be confirmed in writing. There is no cost to submit, and coaches should carefully consider their written responses.
  • Interview and Selection Process: Fiona, as judge advisor, will contact coaches to arrange online interviews (via Zoom or Teams) with nominated students. The winner will be selected based on both the written submission and interview performance, and announced at the tournament.
  • Award Criteria and Preparation: Fiona highlighted that leadership and demonstration of FIRST core values are key criteria. Coaches and students should prepare examples and thoughtful responses, and translation accommodations will be provided if needed.
• Judging Process and Portfolio Submission: Fiona and Mel described the structure of judging sessions, portfolio submission procedures, and the importance of Section 6 of the manual for award criteria, advising teams to prepare and review materials thoroughly.
  • Structured Interview Format: Fiona explained that each team will participate in a 15-minute structured interview with judges, including a five-minute uninterrupted presentation followed by ten minutes of questions. Teams may bring their robot and portfolio, and one silent adult observer is permitted.
  • Portfolio Handling and Visuals: Fiona stated that portfolios should be handed to judges at the start of the interview, but judges will not review them during the session. Teams may bring an extra copy or specific visuals to reference during their presentation, and only one portfolio copy is retained by judges.
  • Judges’ Post-Interview Actions: After the interview, judges complete a feedback form, briefly review the portfolio, and nominate teams for awards based on their strengths. Feedback is returned to teams at the end of the day.
  • Importance of Section 6 and Award Criteria: Both Fiona and Mel stressed that all team members should read Section 6 of the manual, as it contains the official award criteria used by judges. Teams should ensure their presentations and portfolios address required and encouraged elements for each award.
• Awards Strategy and Team Development: Mel and Fiona encouraged teams, especially coaches, to review all award categories, explaining that pursuing multiple awards fosters student growth and enhances the overall FIRST Tech Challenge experience.
  • Benefits of Pursuing Awards: Mel explained that striving for various awards helps students develop skills relevant to future careers, such as presentations and teamwork, and that the process of preparing for awards is more valuable than winning them.
  • Strategic Focus for Teams: Teams are advised to review all award criteria, even if they are experienced, and to consider taking on additional award categories or assigning specific responsibilities to team members to maximize learning opportunities.
• Game Rules and Drive Team Roles: Fiona and Sam provided an in-depth review of drive team roles, human player responsibilities, and key game rules, including penalties, artifact handling, and alliance area storage limits, addressing questions from Reginald and others.
  • Drive Team Composition and Badges: Fiona clarified that the drive team consists of a drive coach (who may be an adult), drivers, and a human player, all of whom must wear appropriate badges. The human player role is not strictly differentiated from drivers, and responsibilities may rotate.
  • Drive Coach and Human Player Restrictions: Sam detailed that drive coaches may not operate controllers or interact with scoring elements, while human players and drivers may handle artifacts within the loading zone during teleop, following specific rules to avoid penalties.
  • Artifact Handling and Penalties: Sam emphasized that direct contact between a drive team member and a robot, or with an artifact in contact with a robot, results in major fouls and yellow cards. Artifacts must be dropped, not pushed, into robots to avoid violations.
  • Alliance Area Storage Limit: Sam explained rule G434, which limits each alliance to storing no more than six artifacts out of play during teleop. Exceeding this limit incurs minor fouls, and teams must promptly return excess artifacts to the field.
  • Clarifications on Artifact Removal: In response to Reginald’s question, Fiona confirmed that human players may remove artifacts from the field for strategic reasons, provided the six-artifact storage limit is not exceeded and no contact with robots occurs during removal.
• Field Layout, Protected Zones, and Scoring: Sam described the field layout, including alliance areas, loading zones, secret tunnels, and base zones, and explained rules for protected zones, scoring methods, and ranking points, addressing questions from Reginald and Dylan.
  • Field Zones and Common Fouls: Sam reviewed the locations and functions of alliance areas, loading zones, secret tunnels, and gate zones, noting that contacting the opposing alliance’s gate is a common major foul that awards a ranking point to the other alliance.
  • Protected Zone Rules: Sam clarified that in the secret tunnel, fouls are based on which robot is in the tunnel at the time of contact, while in loading and gate zones, fouls are assessed if a robot is touched while in its protected zone, regardless of the other robot’s position.
  • Base Zone Endgame Rules: During the last 20 seconds of a match, contact with a robot in its base zone results in a major foul and credits the touched robot with a full park, regardless of its actual location.
  • Scoring and Ranking Points: Sam explained that points are awarded for driving off launch lines in autonomous, parking in base zones, and matching artifact patterns on the ramp. Ranking points are determined by specific achievements, such as pattern completion and autonomous actions.
  • Artifact Pattern Scoring: Sam and Daniel clarified that while matching artifact patterns yields additional points, teams are not penalized for ignoring the pattern and may choose strategies that maximize overall scoring instead.
• Tournament Communications and Support: Mel reminded participants to regularly check emails for tournament updates, meal ordering information, and to reach out with questions or requests for assistance as the event approaches.
  • Ongoing Communications: Mel stated that emails with tournament details and logistical information will be sent every one to two weeks, including instructions for meal ordering and payment.
  • Support and Assistance: Mel encouraged teams to communicate any needs or questions, assuring that the organizing team will do their best to accommodate within their capabilities.

The post FTC Coach/Captain Call – February 12, 2026 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Tournament Preparation and Team Roster Requirements: Mel provided detailed instructions to all coaches on preparing for upcoming FIRST LEGO League tournaments, emphasizing the importance of team rosters, consent forms, and the process for ensuring all participants are properly registered, with Sam, Anne, and Roymond raising specific questions about deadlines, roles, and troubleshooting registration issues.
  • Team Roster Completion: Mel explained that each team must have a printed roster from the FIRST Dashboard, which includes all coaches and youth members, with parent/guardian consent forms completed online. Coaches must ensure there are no red marks on their dashboard, indicating all requirements are met. The roster must be brought to the tournament for participation.
  • Coach Screening and Roles: Mel clarified that two screened coaches are required per team, and additional adults can be added as mentors. The admin role is primarily for handling payments and does not allow for managing team rosters. Roymond’s question about dual roles was addressed, confirming that a person can be both coach and admin, but only coaches can manage rosters.
  • Registration Deadlines and Troubleshooting: Mel stated that while event registration deadlines are strict due to logistical needs like trophy ordering, the deadline for adding youth to the roster is up to the day before the tournament. Sam’s issue with a parent’s registration was discussed, with Mel advising to assist parents directly and to contact FIRST customer service if technical issues persist.
  • Event Registration Process: Mel walked through the process of registering for events via the Adventist Robotics website, emphasizing the need to select the correct event and complete payment. Coaches were reminded to check their event status and ensure all requirements are met for their teams to be event-ready.
• Tournament Day Structure and Judging Procedures: Mel outlined the typical schedule and procedures for tournament day, including coaches meetings, judging sessions, practice rounds, and the structure of the robot game, with Anne and Adam asking about logistics and permissions for recording presentations.
  • Tournament Schedule Overview: Mel described that tournaments usually start between 8:00 and 9:00 AM, beginning with a coaches meeting, followed by judging sessions in the morning, a practice round, and then the main tournament rounds in the afternoon. The best score out of three robot matches is used for ranking.
  • Judging Session Details: Each team participates in a 30-minute judging session, including presentations on their innovation project and robot design, followed by Q&A with judges. Only one adult coach or mentor may observe, and coaches must not participate during the session.
  • Recording Permissions: Adam asked if presentations could be recorded, and Mel confirmed that coaches may record from their seat, but not move around the room. Daniel added that some tournaments may restrict recording of Q&A portions, which is at the discretion of the tournament or judges.
• Robot Game Rules and Technical Clarifications: Trever and Mel discussed specific robot game rules, including when robots can be touched, handling of equipment, and strategies for managing the field, with references to the official rulebook and practical advice for teams.
  • Robot Handling During Matches: Mel explained that robots and any attachments must be fully in the home area before being touched during a match. If a robot is interrupted outside of home, the team loses a precision token. Teams cannot hand robots across the field during matches, but may use interruption and relaunch strategies.
  • Match Setup and Inspection: At the start of a match, teams place all items in one launch area for inspection, with a bonus if everything fits within a 12-inch height. After inspection, items can be distributed between launch areas, but no items may be handed across during the match.
  • Field and Mission Model Interactions: Mel clarified that teams should not touch anything outside the home area during matches and must ask referees to check field setup if something appears incorrect. The process for scoring, referee review, and the finality of scores was also described.
  • Specific Mission Questions: Trever asked about the angler artifact mission and whether teams can request the gear be in a favorable position. Mel responded that this is at the referee’s discretion, and teams are encouraged to politely ask referees for adjustments.
• Upcoming Changes to FIRST LEGO League and Transition Plans: Mel provided an in-depth overview of the upcoming transition from the current Founders Edition to the new Future Edition of FIRST LEGO League, including new hardware, coding options, timelines, and the impact on teams, with extensive Q&A from Anne, Roymond, Ben Selby, Dave, Simon, and others.
  • Reason for Changes and New Hardware: Mel explained that LEGO is releasing a new Computer Science & AI kit, which will replace Spike Prime starting June 30. The new kit supports block and Python coding, and is designed to be more accessible for schools and scalable for larger participation.
  • Transition Timeline and Dual Games: For the next two seasons, both the Founders Edition (current system) and Future Edition (new system) will run in parallel, with separate games and registration. After two years, only the Future Edition will remain. Mel emphasized that the new robot cannot be used with the old game and vice versa.
  • Impact on Teams and Equipment: Mel discussed challenges for teams, especially regarding hardware availability and cost. Existing Spike Prime sets will be supported through 2031, but new teams will need the new kit. Mel encouraged networking to source used hardware and suggested grant opportunities for funding.
  • Competition Structure and Judging: The Future Edition will feature a new field format and may require two kits per team. Judging will remain similar, with rubrics for robot design, innovation project, and core values. The new kits are Bluetooth-enabled, with simplified pairing and no wires.
  • Q&A on Technical and Logistical Details: Participants asked about compatibility, cost, charging requirements, and training options. Mel confirmed that only LEGO parts (not motors/sensors) will be compatible, pricing is not finalized, and multiple devices will need charging. Spike Prime can still be used for training, but not for Future Edition competitions.
• Support Resources, Grants, and Alternative Robotics Options: Mel and participants discussed available support resources, grant opportunities, and alternative robotics platforms like XRP Robots for summer camps or as a bridge to FIRST programs, with Richard and Dwayne expressing interest in these options.
  • Grant Opportunities: Mel recommended applying for grants such as the Versa Care grant to help fund robotics equipment, and encouraged participants to seek sponsorships and support for their programs.
  • Alternative Robotics Platforms: Mel introduced XRP Robots as a low-cost, Python-based platform suitable for summer camps or as a preparatory tool for FIRST programs. Richard shared positive feedback about the platform and inquired about potential competitions, with Mel noting its value as a teaching tool.

The post FLL Coach Conference Call – February 12, 2026 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Team Registration and Event Preparation: Mel provided detailed instructions to all teams on completing dashboard registration, ensuring two screened coaches, managing express enrollment invitations for parents, and emphasized the necessity of a printed, signed roster for tournament participation.
  • Dashboard Registration Process: Mel explained that teams must access their dashboard on the event website, ensure there are no red flags, and confirm that two primary contacts (coaches) are listed and screened before proceeding with further steps.
  • Express Enrollment Invitations: Once two coaches are screened, the express enrollment invitation feature becomes active, allowing teams to generate a QR code or registration link to share with parents for youth member registration.
  • Roster Printing Requirement: Mel stressed that teams must print out their roster, which includes all team members and parent signatures, and bring it to the event as it serves as their entry ticket.
  • Resource and Documentation Review: Mel highlighted the importance of reviewing the resources, documentation, and blog updates available on the event website, including information about upcoming control system changes and new hardware.
• Judging Process and Awards Structure: Fiona and Mel outlined the judging process, emphasizing the importance of Section 6 of the game manual, described the structure of judged awards, and discussed strategies for teams to prepare for interviews and award eligibility.
  • Section 6 Manual Review: Fiona recommended that all teams, not just rookies, thoroughly read Section 6 of the game manual, especially section 6.3, which details team-judged awards, and suggested dividing the reading among team members for efficiency.
  • Award Categories Update: Fiona noted that the Motivate award has been discontinued and replaced by Reach and Sustain, resulting in three Team Attributes Awards and three Machine Creativity Innovation Awards.
  • Interview Preparation: Fiona explained that the structured interview consists of a five-minute uninterrupted team presentation followed by questions, and all team members are expected to participate unless exceptions are communicated to Mel.
  • Portfolio Submission: Teams are required to bring a paper copy of their portfolio to the interview, which judges will retain for the day and return with feedback.
  • Pit Interviews: Fiona and Mel described the importance of pit interviews, which occur during the event, and advised teams to designate members to interact with judges while others continue working on the robot.
• Safety Requirements and Practices: Fiona and Mel reiterated the necessity for all participants to wear closed-toed shoes and safety glasses in designated areas, provided guidance on selecting appropriate safety equipment, and encouraged teams to practice these habits before the event.
  • Footwear and Dress Code: Fiona emphasized that students must be accustomed to wearing closed-toed shoes at all times during the event, discouraging sandals, flip-flops, or Crocs, and suggested integrating this practice into regular meetings.
  • Safety Glasses Selection: Both Fiona and Mel advised teams to ensure every student, mentor, and potentially parents have comfortable, ANSI-approved safety glasses, including over-glasses for those with prescription eyewear.
  • Practice and Enforcement: Teams were encouraged to practice wearing safety glasses and closed-toed shoes during meetings to build the habit, and Mel noted that safety will be strictly enforced in the pit and competition areas.
• Robot Inspection and Compliance: Fiona and Mel guided teams through the updated inspection checklist, clarified sizing rules and robot sign requirements, and explained the importance of early self-inspection to avoid event-day surprises.
  • Inspection Checklist Changes: Fiona explained that field inspection is no longer performed separately; instead, teams must use the updated inspection checklist, which now omits some previous field inspection elements.
  • Sizing and Mechanical Limits: Fiona detailed that robots must fit within an 18-inch cube at the start and cannot expand horizontally beyond this limit, which must be mechanically enforced rather than relying on software.
  • Robot Sign Requirements: Teams must create two alliance-colored robot signs with white numbers, using provided templates or their own methods, and affix them securely to opposite or adjacent sides of the robot for alliance identification.
  • Inspection Timing and Support: Mel described the inspection process, encouraging teams to complete inspection Saturday night to allow time for corrections, and noted that experienced teams will assist rookies as needed.
• Tournament Schedule and Match Procedures: Mel and Fiona described the event schedule, including inspection, judging, practice, and match timing, and provided detailed instructions on alliance assignment, sign switching, and pit area operations.
  • Event Timeline Overview: Mel outlined that team check-in and inspection begin Saturday night, with Vespers and continued inspections Sunday morning, followed by judging, practice, and pit area setup.
  • Alliance Assignment and Sign Switching: Teams receive their alliance assignments and match lists after the drivers meeting, and must be prepared to quickly switch robot signs between matches, with at least eight minutes provided for transitions.
  • Pit Area Operations: Teams are assigned pit areas as their home base for working on robots and storing tools, and must adhere to safety protocols, including wearing safety glasses and closed-toed shoes in designated areas.
• Robot Game Rules and Field Operations: Fiona and Mel provided an in-depth walkthrough of the robot game, covering field setup, artifact preloading, randomization procedures, match periods, and scoring mechanisms, including the new pattern points system.
  • Field Setup and Alliance Areas: Fiona described the layout of the field, including alliance areas, base zones, loading zones, and the placement of goals, noting the color assignments and their implications during autonomous and teleop periods.
  • Artifact Preloading and Placement: Teams must preload up to three artifacts per robot from their alliance’s designated tray, coordinate with alliance partners on artifact selection, and ensure correct placement to avoid confusion.
  • Randomization and Autonomous Procedures: After robots and driver stations are set up, the field is randomized using the obelisk motif, and teams must not touch their robots or controllers post-randomization except to start or stop autonomous mode, as violations result in fouls.
  • Match Periods and Scoring: Matches begin with a 30-second autonomous period, followed by a two-minute teleop period, with specific rules for when teams can interact with their controllers, and scoring includes pattern points based on artifact arrangement.
  • Stopping Autonomous for Strategy: Teams are now allowed to stop their robot during autonomous for any reason, including strategic purposes, which can be used to maximize scoring or prevent fouls.
• Awards Calculation and Inspire Award Criteria: Fiona and Mel clarified the evaluation process for awards, explaining that FTC uses seven award categories, the Inspire Award is based on overall strength across these areas, and robot game performance is considered separately from judged awards.
  • Award Category Structure: FTC evaluates teams across seven award categories, and the Inspire Award is given to the team demonstrating the strongest overall performance in these areas, not based on a fixed percentage or rubric.
  • Interview and Portfolio Role: The 15-minute interview and submitted portfolio are used by judges to assess teams for all awards, with teams encouraged to address both robot and outreach efforts during their presentation.
  • Robot Game and Advancement: Robot game results are tracked separately from judged awards and are used for advancement and alliance selection, but do not directly factor into the Inspire Award calculation.
• Field Mitigation Guide and Common Issues: Fiona introduced the recently released field mitigation guide, which outlines potential field element issues, their in-match solutions, and recommendations for teams to address these problems during practice and events.
  • Common Field Issues: The guide describes scenarios such as artifacts jamming the orc shway, gate malfunctions, and goal bracket dislodgement, and provides instructions for field staff and teams on how to resolve these without stopping matches.

The post FTC Coach/Captain Call – January 8, 2026 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Tournament Readiness and Participation Expectations: Mel addressed concerns about team readiness for the tournament, emphasizing that full preparedness is not required and encouraging all teams to participate for the experience, with input from coaches and examples of rookie teams performing well.
  • Defining Readiness: Mel clarified that being ‘ready’ for the tournament does not mean having completed all missions or achieving perfection, but rather being willing to participate and learn from the experience, regardless of the team’s current state.
  • Value of Participation: Mel highlighted that the primary value of the tournament is the learning experience, including presenting to judges, sharing ideas with other teams, and handling pressure, rather than focusing solely on winning.
  • Managing Expectations: Mel advised coaches to set realistic expectations to reduce stress on students, suggesting that approaching the event with a positive, growth-oriented mindset leads to a better experience for everyone involved.
  • Encouragement for New Teams: Mel shared that rookie teams have sometimes outperformed more experienced teams, reinforcing the message that all teams, regardless of experience, should commit to attending the tournament.
• Team Registration and Compliance Requirements: Mel provided detailed instructions on team registration, including the need for two cleared coaches, completion of the Youth Protection program, and specific requirements for California teams, as well as the importance of weekly status updates.
  • Weekly Status Updates: Mel explained that teams will receive weekly email updates regarding their registration status, including team numbers, names, event registration status, and coach compliance.
  • Coach Clearance Process: Mel outlined that each team must have two coaches who have completed the Youth Protection program, and for California teams, a live scan background check is also required for all volunteers.
  • Administrator Role: Mel clarified that administrators are only needed if someone other than the coach, such as a school treasurer, is handling payments and administrative tasks.
• Tournament Day Procedures and Judging Process: Mel described the step-by-step procedures for tournament day, including check-in, coaches’ meetings, judging sessions, practice matches, and the use of rubrics, with a focus on process over product.
  • Check-In and Roster Requirements: Teams must bring a printed roster from the FIRST dashboard, which serves as their entry ticket, and ensure all youth members have completed consent forms.
  • Coaches’ Meeting and Judging Flow: After check-in, one coach per team attends a meeting for last-minute updates, followed by judging sessions where teams present their innovation projects and answer judges’ questions.
  • Judging Session Structure: Judging sessions include a two-minute setup, five-minute project presentation, five-minute Q&A, robot discussion, and final feedback, with coaches observing but not participating.
  • Rubrics and Evaluation Criteria: Mel emphasized that teams are evaluated on process rather than product, using rubrics that cover areas such as design, innovation, iteration, and communication, with equal weighting for all four main areas.
• Robot Game Rules and Match Logistics: Mel explained the logistics of the robot game, including practice and official matches, pit area setup, field procedures, scoring, and the importance of understanding the rulebook and cycle time.
  • Practice and Official Matches: Teams participate in a morning practice match that does not count toward their score, followed by three official matches in the afternoon, with the best score counting.
  • Pit Area and Equipment: Each team is assigned a pit table for robot work and charging, with guidelines on what can be brought into the gym and field area.
  • Field Procedures and Referee Interaction: Teams must place all robot parts in the launch area, request referees to fix any field issues, and follow the rule that only two technicians are allowed at each side of the field at a time.
  • Scoring and Rulebook Familiarity: Scores are shown electronically for team approval, and Mel advised teams to thoroughly review the rulebook, especially regarding interruptions, restarts, and maximizing points.
  • Cycle Time Considerations: Mel encouraged teams to practice and optimize their robot’s cycle time for efficient mission completion within the 2.5-minute match duration.
• Parent Registration and Communication Challenges: David, Brian, Nicole, and Mel discussed challenges in getting parents to register their children, including language barriers, authentication issues, and shared strategies such as using QR codes, parent meetings, translators, and communication apps.
  • Parent Registration Process: Mel explained that after two coaches are registered, coaches can generate a QR code or link for parents to register their children, and suggested sending these home or via email.
  • In-Person Registration Support: Mel recommended holding parent meetings with available laptops to assist less tech-savvy parents in completing the registration process on-site.
  • Language and Translation Solutions: David raised the issue of needing a translator for non-English-speaking parents, and Mel suggested using Google Translate or seeking community members who can help, while Nicole mentioned that some registration platforms and communication apps offer language options.
  • Authentication and Technical Barriers: Brian noted that recent changes to the authentication protocol caused confusion among parents, with some systems being flagged as suspicious by home computers, and Mel acknowledged the process remains somewhat cumbersome due to legal requirements.
  • Communication Tools: Nicole shared that using the Team Snap app helps streamline communication with parents, allowing for reminders and direct messaging, and noted that it supports multiple languages.
• Tournament Schedule and Staffing Updates: Mel announced the upcoming tournament schedule, introduced Priscilla as a new tournament coordinator, and explained the increasing need for additional support due to scheduling challenges.
  • Upcoming Tournament Dates: Mel stated that the first tournament will be held on February 1 in Colorado, with several more to follow shortly after.
  • Staffing and Support: Mel introduced Priscilla as a new team member who will help coordinate tournaments, and assured teams that Mel will remain available for support via phone or video chat during events.

Follow-up tasks:

• Parent Registration Support: Identify and arrange for a translator or alternative language support (such as Google Translate or a community member) to assist non-English-speaking parents with the student registration process. (David)

The post FLL Coach Conference Call – January 8, 2026 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Administrative Reminders and Event Preparation: Mel provided essential reminders to coaches and captains regarding dashboard requirements, coach screening, express enrollment, printable rosters, and event registration, emphasizing the importance of early completion to ensure smooth tournament participation and planning.
  • Coach Screening and Dashboard: Mel instructed all teams to ensure that two coaches are screened and that all acknowledgment forms are completed on the dashboard, highlighting that any red indicators on the dashboard must be resolved to avoid last-minute issues.
  • Express Enrollment and Team Invitations: Teams were advised to use the express enrollment feature to manage invitations, including generating QR codes for parents, and to add team members as they enroll, ensuring all are properly registered before the competition.
  • Printable Roster Requirement: Mel emphasized the necessity of printing the official team roster from the dashboard and bringing it to the tournament, describing it as the ‘golden ticket’ required for competition entry and warning against the stress of last-minute completion.
  • Event Registration and Planning: Participants were reminded to complete FTC event registration and payment via adventistrobotics.net, as early confirmation aids in logistical planning such as ordering trophies and medals.
• Competition Manual Updates and Team Communication: Mel and Fiona discussed the importance of regularly reviewing the competition manual and staying updated with rule changes, encouraging coaches to sign up for team update notifications and to ensure teams are aware of the latest version and incorporated updates.
  • Manual Versioning and Updates: Mel explained that the competition manual is updated frequently, with new versions incorporating recent rule changes and clarifications, and advised teams to verify they are using the latest version (e.g., TU14 as of December 11).
  • Team Update Notifications: Coaches were encouraged to sign up for team update emails to receive timely notifications about rule changes, as only adults (18+) can register for these updates.
  • Resource Navigation: Mel demonstrated where to find the competition manual, team updates, and other resources on the main website, ensuring teams know how to access critical information.
• Judging Process and Section 6 Guidance: Fiona, serving as Judge Advisor, outlined the significance of Section 6 in the competition manual, detailed the judging process, and encouraged teams to prepare thoroughly for the awards criteria and judging sessions, with Mel providing logistical details for inspection and judging schedules.
  • Section 6 Importance: Fiona recommended that teams regularly study Section 6 of the manual, as it contains all information about awards, both new and existing, and suggested designating students to become familiar with its content.
  • Judging Session Structure: Mel described the judging process: robot inspection and portfolio submission occur Saturday night, followed by 15-minute judging sessions on Sunday morning, which include a 5-minute team presentation and 10 minutes for Q&A.
  • Preparation Strategies: Teams were advised to practice concise presentations that address all award areas and to ensure all team members participate, maximizing their opportunity to impress judges within the limited time.
  • Communication Channels for Questions: Fiona and Mel clarified that teams can submit judging questions via email or bring them to monthly conference calls, where dialogue can help clarify complex issues.
• Game-Specific Rules and Referee Guidance: Sam, the Head Referee, provided an in-depth overview of significant game rule changes for the season, including robot sizing, human player interactions, protected zones, ranking points, and the interpretation of intent in fouls, with Mel and Fiona supporting the discussion and addressing participant questions.
  • Robot Sizing and Expansion: Sam explained that the 18-inch sizing limit now applies horizontally for the entire match, requiring mechanical constraints rather than software, and advised teams to allow a small margin to ensure compliance with the official sizing cube.
  • Starter Robots and Design Resources: Starter robot designs from various manufacturers were highlighted as useful resources for teams, especially given the unique shooting game mechanics this season, with examples and code available for reference.
  • Human Player Rule Changes: The human player can now place artifacts directly into robots in the loading zone, provided there is no direct or transitive contact with the robot, marking a change from previous seasons.
  • Protected Zones and Gate Rule: Sam and Fiona reviewed rules regarding protected zones (e.g., gate, secret tunnel, loading zone, base), emphasizing that touching the opponent’s gate results in a major penalty and awards the opposing alliance a ranking point.
  • Ranking Points and Achievements: Ranking points can now be earned through in-game achievements (artifacts through the square, patent points, parking in base), not just match outcomes, and Mel noted that the event may use ‘all other events’ thresholds pending confirmation.
  • Field Layout and Gameplay Implications: The field layout places alliance stations and goals on opposite sides, increasing the risk of accidental gate contact and requiring teams to be mindful of their robot’s movements.
• Interpretation of Fouls, Intent, and Gameplay Strategy: Fiona and Sam addressed detailed questions from Daniel Plaisted regarding the interpretation of rule G210, intent in drawing fouls, and the distinction between standard gameplay and deliberate actions to force penalties, providing examples and clarifications on referee judgment.
  • Rule G210 and Intent: Fiona clarified that actions clearly aimed at forcing opponents to violate rules are not allowed and will result in penalties for the instigating alliance, while standard gameplay that incidentally results in fouls is permissible.
  • Referee Judgment and Examples: Examples were provided where explicit instructions to draw a foul (e.g., telling a driver to hit an opponent for a penalty) resulted in G210 violations, whereas actions consistent with normal gameplay, even if they result in fouls, are acceptable.
  • Guidance for Teams: Teams were advised to focus on playing the game rather than worrying about intent, as referees will assess whether actions are part of standard gameplay or deliberate attempts to exploit the rules.
  • Protected Zone Scenarios: Scenarios involving artifact control, pushing, and interactions in protected zones were discussed, with Fiona explaining how referees consider context and intent, and that actions like pushing artifacts while already at capacity are not allowed.
• Launching, Artifact Control, and Field Setup Clarifications: Fiona, Mel, and Daniel Plaisted discussed the definitions and practical implications of launching artifacts, controlling elements, and field setup details, addressing specific scenarios and promising further clarification after more event experience.
  • Definition of Launching: Launching is defined as shooting an artifact into the air or propelling it across the floor to a desired location or in a preferred direction, and is only allowed from the launch zone.
  • Artifact Ejection Scenarios: Questions about ejecting artifacts from robots (e.g., running intake in reverse) were discussed, with Fiona indicating that simply removing an artifact may not count as launching unless it is directed or forceful, but further clarification will be sought.
  • Pushing Artifacts and Control: Pushing artifacts across the field is considered control, not launching, unless the artifact is propelled away from the robot at speed and in a preferred direction, which may require further referee interpretation.
  • Field Setup and Tape Lines: Nicole inquired about field tape lines, and Mel and Fiona directed teams to the field setup guide in the playing field resources, which provides exact dimensions and recommended taping order.
  • Alliance Station Artifact Limits: Fiona reminded teams that only six artifacts are allowed in the alliance station box, and exceeding this limit results in fouls, requiring teams to manage artifact placement carefully during matches.
• Scrimmage Planning and Logistics: Daniel Plaisted asked about upcoming scrimmages, with Mel confirming tentative dates, the need for team rosters, and plans for local referees, while also outlining sign-up and fee procedures for these less formal events.
  • Scrimmage Scheduling: Mel indicated that February 15th is the likely date for the local scrimmage, pending finalization and coordination with other FTC events to avoid conflicts.
  • Referee Arrangements: Due to overlapping events, local referees will be used for the scrimmage, and Mel emphasized the importance of having experienced referees present.
  • Roster and Registration Requirements: Teams must prepare and submit rosters for scrimmages, and Mel will set up a sign-up process with a small fee to confirm participation and facilitate event scoring.
• Meeting Recordings and Ongoing Communication: Mel confirmed that meeting recordings are shared with all teams for transparency and encouraged participants to review them and bring further questions to future monthly calls.
  • Recording Access: Recordings of the meetings are posted and can be shared with all team members, allowing those who missed the session to catch up and prepare questions for subsequent meetings.
  • Encouragement of Dialogue: Mel encouraged teams to review the recordings and participate actively in future calls to address any emerging questions or clarifications.

Follow-up tasks:

• Coach and Team Compliance on Dashboard: Ensure that all teams have two screened coaches and all acknowledgment forms completed on the dashboard, with no outstanding red indicators. (All coaches)
• Team Roster Preparation: Print the official team roster from the dashboard and bring the physical copy to the tournament as required for participation. (All coaches)
• FTC Event Registration and Payment: Complete FTC event registration and submit payment to confirm participation and facilitate event planning. (All coaches)
• Team Update Notifications: Sign up for team update emails to receive notifications about rule changes and updates throughout the season. (All coaches)
• Judging Section Familiarization: Read Section 6 of the competition manual regularly and designate students to become familiar with its content for effective preparation. (All teams)
• Submission of Portfolio and Robot Inspection: Turn in the team portfolio and complete robot inspection during Saturday night check-in prior to the tournament. (All teams)
• Field Setup Guide Access: Access and review the field setup guide from the playing field resources to ensure correct field marking and tape placement. (All teams)

The post FTC Coach/Captain Call – December 11, 2025 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Model Fragility and Assembly Guidance: Mel provided detailed instructions to coaches and teams regarding the fragility of this year’s models, emphasizing the importance of careful assembly, double-checking construction, and not using glue, with Dashield and Daniel contributing questions and clarifications.
  • Model Fragility Issues: Mel explained that this year’s models are less robust than in previous seasons, making them more prone to coming apart during use. Coaches and teams were advised to handle the models with extra care and to expect more challenges in keeping them intact.
  • Field Setup and Instructional Videos: Mel directed participants to the official field setup and robot game videos, stressing the importance of watching these multiple times to catch nuances not found in written documentation. Teams were encouraged to study these videos carefully to ensure correct field and model setup.
  • Double-Checking Model Assembly: Mel recommended that someone meticulous, whether an adult or a student, should review the model building instructions and verify that all models are assembled correctly, as small errors can significantly affect performance during competition.
  • Prohibition of Gluing Models: In response to Dashield’s question, Mel clarified that gluing models is not allowed because competition models will not be glued, and glued models would behave differently, potentially disadvantaging teams during the event.
  • Specific Model Assembly Tips: Mel and Daniel discussed several models, including the surface brush, silo, tip the scales, angler artifacts, statue rebuild, and careful recovery, highlighting common assembly pitfalls and the need to check specific components (e.g., dual lock placement, lever connections, block positions) to ensure proper function.
• Competition Field Procedures and Rules: Mel outlined the procedures and rules for competition field setup, inspection, and gameplay, addressing questions from Courtney and others about handling field elements, inspection protocols, and the importance of following official guidelines.
  • Field Inspection and Model Verification: Mel described the pre-match inspection process, where teams can visually check all mission models for correct setup but should not touch them. Team members, not coaches, are responsible for requesting referees to verify or correct any issues with the models.
  • Technician Roles and Launch Areas: Mel explained that two technicians are allowed on each side of the table, and the robot must start completely within one of the designated launch areas. Once the match begins, items cannot be handed between sides, and the referee will enforce this rule.
  • Handling Field Elements During Matches: In response to Courtney’s question, Mel clarified that if the robot moves or displaces field elements, those elements remain where they come to rest, and teams are not permitted to touch or reset them during the match. Only intentional field damage is penalized.
  • Inspection Stacking and Attachments: Mel and Daniel addressed questions about fitting attachments into the 12-inch launch area during inspection, confirming that stacking and partial disassembly are allowed as long as all parts fit, but warned against excessive reassembly at the table.
  • Challenge Updates and Rule Changes: Mel emphasized the importance of regularly checking the official Challenge Updates document on the website, as these updates override previous documentation and may introduce new rules or clarifications.
• Tournament Day Structure and Logistics: Mel provided a comprehensive overview of the tournament day’s schedule, including check-in, pit setup, judging sessions, practice and official matches, and the award ceremony, with Daniel and others contributing clarifying questions.
  • Check-In and Team Rosters: Mel instructed teams to arrive early, complete their team rosters with all required consent forms, and bring a printed copy for check-in. Failure to provide a completed roster may prevent team participation.
  • Pit Area and Practice Fields: Teams will be assigned a pit area for robot adjustments and preparation. Practice fields are available in the pit area and must be shared with other teams, with Mel advising against bringing personal tables due to potential inconsistencies in floor surfaces.
  • Judging Sessions: Each team will have a 30-minute judging block, including setup, innovation project presentation, robot explanation, and Q&A. Only one adult coach or mentor may accompany the team as an observer, and strict time management is encouraged.
  • Competition Matches and Awards: After practice rounds in the morning, teams will participate in three official matches in the afternoon, with their best score counting. The day concludes with an award ceremony, during which teams pack up and return for final recognition.
• Team Registration, Rosters, and Participation Rules: Mel, Daniel, and Richard discussed team registration requirements, roster management, coach screening, and participation limits, addressing questions about team size, rearranging students, and coach roles.
  • Team Size and Composition: Mel clarified that a competitive team must have between two and ten members; teams with more than ten students must be split into multiple teams. Sharing a challenge set between teams is permitted.
  • Roster Management and Student Movement: Teams can rearrange students between teams before the competition, but rosters must match the actual team composition at the event. Richard noted that moving a student may require deleting and reapplying, and Mel advised completing rosters closer to competition if changes are anticipated.
  • Coach Screening and Roles: Coaches must complete youth protection screening (and live scan in California) before youth enrollment can proceed. While only two official coaches are required, additional mentors or specialists can be involved, provided they are screened.
  • Consent Forms and Parental Involvement: Parents must complete online consent forms for their children, and Mel recommended assisting parents as needed but ensuring they personally authorize participation for legal protection.
• Judging Criteria and Process: Mel explained the judging rubrics, session flow, and evaluation focus for the innovation project and robot design, emphasizing process over product and the importance of time management during presentations.
  • Rubrics and Evaluation Focus: Teams are evaluated using innovation project and robot design rubrics, with core values integrated throughout. Judges assess the process followed by the team rather than the final product, so teams should document and present their approach and learning.
  • Judging Session Structure: Each judging session includes setup, a five-minute innovation project presentation, five minutes for judge questions, a five-minute robot explanation, and additional time for judge questions and feedback, all within a 30-minute block.
  • Coach and Team Member Roles: Only one adult coach or mentor may observe the judging session without interacting with the team. Team members are responsible for all presentations and responses, and coaches should prepare teams for efficient setup and clear communication.

Follow-up tasks:

• Team Roster Completion: Ensure all team members’ consent forms are completed and the printable roster is ready for tournament check-in.
• Team Size Compliance: Verify that each competitive team does not exceed the maximum of 10 members and, if necessary, split into multiple teams.
• Coach Screening: Complete youth protection screening (and live scan for California) for all coaches before starting youth enrollment.

The post FLL Coach Conference Call – December 11, 2025 first appeared on Adventist Robotics.

AI-generated content may be incorrect

Meeting notes

Updated Resources and Compliance Requirements: Mel provided an overview of the updated FIRST website resources, emphasized the importance of reviewing team updates, and detailed compliance requirements such as the inspection checklist and youth protection screening for coaches and team members.

• FIRST Website Updates: Mel explained that the FIRST website has been redesigned, but previous resources remain valid. They highlighted the ‘game in season’ section under programs, which contains essential materials and updates for teams.
• Team Updates and Manuals: Mel stressed the importance of regularly checking for biweekly team updates, as these may include rule changes and clarifications not present in the original competition manual.
• Inspection Checklist: Mel emphasized the necessity of using the self-inspection checklist early and throughout the season to ensure robots are compliant, as non-compliant robots cannot compete.
• Youth Protection Screening: Mel outlined that two coaches must complete the Youth Protection 3 screening (with additional fingerprinting for California), and only after both are cleared can youth members be registered and participate.
• Printable Roster and Consent: Mel described the process for generating a printable team roster, which confirms parental consent and is required at competitions, and clarified that this consent is separate from school field trip permissions.

Key Rule Clarifications and Referee Insights: Mel and Daniel discussed recent rule clarifications from referees, focusing on human-robot contact, protected zones, gate violations, and the importance of understanding and adapting to these rules during practice and competition.

• Human-Robot Contact Rules: Mel relayed that humans may not directly or transitively contact robots with scoring elements during matches, referencing Rule Q19 and G431B, which define such contact as a major foul.
• Artifact Handling Procedures: Daniel and Mel clarified that artifacts should be dropped or placed into the robot without imparting motion or rolling, and any contact while holding a game element is prohibited; teams are advised to review the latest rules for specifics.
• Protected Zones and Robot Contact: Mel highlighted the importance of understanding rules around protected zones (G420), noting that repeated bumping is allowed, but teams must design robust robots and be aware of scenarios where being pushed into a zone can still result in a major foul.
• Gate Violations and Fouls: Mel warned that touching the opposing alliance’s gate, directly or through a scoring element, results in immediate major fouls and ranking points for the opponent, with additional fouls for each artifact de-scored from the ramp.

Professional Development and Training Opportunities: Mel described available professional development options for coaches and interested parties, including FIRST Certified Professional Development sessions and the in-depth First Tech Challenge Academy, with details on scheduling, costs, and locations.

• Training Session Formats: Mel outlined that professional development is available both remotely and in-person, with options ranging from two-day compressed courses to a week-long, 40-hour First Tech Challenge Academy, which covers theory and practical aspects.
• Locations and Costs: Mel noted that the Academy is offered in Orlando, Fresno, and occasionally other locations, with the two-day course costing $600 and the week-long course being more expensive; these sessions are open to new and experienced coaches.

Game Play Questions and Q&A Resources: Phillip and Daniel raised questions about game play scenarios, such as penalties for launching balls out of the arena and requirements for legal robot signs, with Mel and Daniel providing guidance and referencing the official Q&A forum for further clarification.

• Artifact Launching and Penalties: Phillip asked about penalties for balls launched out of the arena; Daniel responded that intentional launching is penalized, but unintentional launches are handled at the judge’s discretion, with balls typically returned to the field by staff.
• Q&A Forum Utilization: Mel demonstrated how to use the official Game Q&A system to search for clarifications on artifact launching, rolling, and pushing, encouraging teams to consult this resource for answers to common and complex rule questions.
• Robot Sign Requirements: Daniel inquired about legal robot signs; Mel explained that printable resources are available, and while teams can make their own, signs should be sturdy and compliant with official specifications, with commercial options also available.

Scrimmage Organization and Referee Availability: Daniel requested assistance arranging practice scrimmages with other Florida teams, and Mel committed to coordinating such events, emphasizing the need for experienced referees and mentioning upcoming scrimmages in North Carolina and Texas.

• Scrimmage Scheduling: Mel stated they would work to organize a scrimmage in Orlando or elsewhere in Florida, considering the regular season schedule and the availability of other teams.
• Referee Coordination: Mel highlighted the importance of securing experienced referees for scrimmages and noted that their own refereeing experience is outdated, so they prefer to rely on current officials.
• Open Scrimmages: Mel mentioned that scrimmages in North Carolina and Texas are open to all teams, with registration details forthcoming, and encouraged teams to participate as these are not full tournaments.

Refereeing Standards and Defensive Play Strategies: Daniel and Mel discussed the consistency of refereeing, the learning curve for officials, and strategic considerations for offensive and defensive play, including the importance of understanding protected zones and the risks of certain defensive maneuvers.

• Referee Experience and Consistency: Daniel expressed concerns about missed calls in early season matches; Mel assured that their region employs experienced referees, especially later in the season, but acknowledged variability across regions.
• Offensive Versus Defensive Focus: Mel advised teams to prioritize offensive strategies, as effective scoring reduces the need for defense, and cautioned that some defensive actions, such as blocking, may result in major fouls depending on the rules.
• Protected Zones and Foul Risks: Daniel and Mel discussed the complexity of protected zones, the potential for drawing fouls, and the importance of drivers thoroughly learning the rules to avoid unintentional violations.
• Upcoming Referee Q&A Sessions: Mel announced plans to have the head referee join future meetings to address detailed rule questions and provide practical insights based on observed issues during competitions.

Event Registration and Refund Policy: Mel explained the process for registering for FIRST Tech Challenge events, highlighted the option for purchase protection, and clarified that refunds are not issued by the organizers, advising teams to review third-party protection terms.

• Registration Process: Mel directed teams to the online event registration system, noting that it is ready for use and includes an option for purchase protection.
• Refund and Protection Policy: Mel clarified that the organizers do not issue refunds for cancellations, but teams may opt for third-party purchase protection at an additional cost, and should review the terms before purchasing.

Follow-up tasks

Rule Clarifications from Referee: Arrange for the head referee to join an upcoming session to answer detailed questions about rules, fouls, and gameplay strategies. (Mel)

Scrimmage Organization: Coordinate with local teams and experienced referees to schedule a practice scrimmage in the Florida area, aiming for January if possible. (Mel)

Rule Clarification on Drawing Fouls: Contact the head referee to clarify the rule regarding intentionally drawing fouls by forcing an opponent to violate a rule during gameplay. (Mel)

Event Calendar Update: Add the upcoming Texas scrimmage to the Adventist Robotics event calendar and ensure registration information is available. (Mel)

The post FTC Coach/Captain Conference Call – November 2025 first appeared on Adventist Robotics.

AI-generated content may be incorrect

Meeting notes

Tournament Registration and Event Updates: Mel provided updates on finalized tournament dates, including the addition of the North Pacific qualifier at Columbia Adventist Academy, and explained the registration process for teams, emphasizing the importance of early sign-up and the availability of purchase protection.

FIRST Website Resources and Updates: Mel guided participants through the updated FIRST website, highlighting new resources such as electronic guidebooks, challenge updates, judging rubrics, score calculators, and innovation project materials, and explained how to access and utilize these tools.

Judging Process and Team Evaluation: Mel explained the judging process for tournaments, detailing the evaluation criteria based on process rather than product, the structure of judging sessions, and the roles of coaches and team members during evaluations.

Youth Protection Program and Team Member Registration: Mel detailed the requirements for coach screening through the Youth Protection Program, the process for registering youth team members, and the use of express enrollment links and QR codes, addressing related questions from Jeremy and David.

Professional Development Opportunities for Coaches: Mel introduced available professional development sessions for coaches, including both remote and in-person options, and provided details on upcoming events and registration procedures.

Background Screening Requirements by Location: Mel answered a chat question regarding background screening, specifying that Sterling is required for FIRST, but additional requirements such as fingerprinting may apply in California due to state law.

Student Participation and Team Behavior Management: Laurie raised a question about managing student participation and behavior, to which Mel responded that decisions regarding attendance, commitment, and gracious professionalism are left to individual teams, offering suggestions for handling such situations.

Upcoming Championship and Summer Event Plans: Mel announced that top teams from each region will qualify for the championship in May and shared that plans are underway for a summer event, with details still being finalized.

Follow-up tasks

Tournament Registration and Team Compliance: Ensure all teams register for tournaments, complete Youth Protection Program screening for two coaches, and have all youth members signed up with parental consent prior to participation. (All coaches)

California Volunteer Screening Requirements: Verify and complete additional background screening (including fingerprinting/live scan) for volunteers in California as required by recent state law. (California-based coaches)

The post FLL Challenge Coach Conference Call – November 2025 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• Team Registration and Compliance Requirements: Mel provided detailed instructions to all participants on the necessary steps for team registration, including the need for two youth protection-cleared coaches, completion of acknowledgement forms, and ensuring the team profile is set to Adventist Robotics, with additional requirements for California teams.
  • Coach and Youth Protection Screening: Mel emphasized that each team must have two primary contacts or coaches who have completed the Youth Protection Program screening, and highlighted that California teams require additional fingerprinting due to state law.
  • Team Profile and Region Settings: Participants were instructed to verify that their team profile region is set to Adventist Robotics, and to contact FIRST directly if they encounter issues changing this setting, as Mel cannot assist with backend changes.
  • Youth Member Enrollment Process: Mel explained the express enrollment process for youth members, which generates a QR code for parents to sign consent forms, and clarified that this must be completed before teams can compete, though members can be added or removed as needed.
  • Compliance Deadlines and Consequences: Mel warned that all compliance steps must be completed before competition day to avoid last-minute stress and the risk of being unable to compete, noting that incomplete compliance has caused issues for teams in past events.
• Competition Resources and Award Structure: Mel guided the group through the updated FIRST website and FTC Docs, highlighting essential resources such as the competition manual, programming materials, and the new award categories for the season, and encouraged teams to understand the awards to maximize their experience.
  • Accessing Competition Materials: Mel demonstrated how to find programming resources, game materials, and the competition manual on the FIRST website, noting that the manual is updated throughout the season and recommending electronic distribution for easier searching.
  • Overview of Award Categories: Mel described the various awards, including the Inspire, Think, Connect, Reach (new), and Sustain (new) awards, and explained their significance in encouraging broader team development beyond just robot performance.
  • Importance of Awards Understanding: Mel stressed that understanding the awards helps teams get the most out of their participation, as the awards reflect the full scope of what it means to be a FIRST Tech Challenge team, including research, networking, and sustainability.
  • Additional Online Resources: Mel introduced FTC Docs as a comprehensive resource hub, and mentioned unofficial sites like Game Manual 0 for design tutorials, while cautioning that only official sources are authoritative for rules.
• Tournament Preparation and Inspection Procedures: Mel outlined the tournament schedule, emphasizing the importance of passing both robot and field inspections on Saturday night to ensure teams are eligible to compete in the action-packed Sunday event, and provided guidance on inspection checklists and livestreaming details.
  • Tournament Schedule Overview: Mel explained that the tournament begins with robot and field inspections on Saturday night, followed by a full day of competition on Sunday from 8:00 AM to 5:00 or 6:00 PM, with live streaming available for remote viewers.
  • Inspection Checklist Requirements: Teams must complete both robot and field inspection checklists before competing, and Mel advised teams to familiarize themselves with these checklists and practice self-inspection to avoid last-minute issues.
  • Consequences of Failing Inspection: Mel cautioned that teams cannot compete if they do not pass inspection, and that conducting inspections only on Sunday morning leaves little time for troubleshooting, so Saturday night inspections are strongly encouraged.
• Robot Design, Parts, and Programming Guidance: Mel provided technical advice on legal robot parts, recommended suppliers, CAD resources, and programming tools, and discussed the upcoming transition to a new control system, with Dillon and Daniel contributing additional programming and hardware insights.
  • Legal Parts and Sourcing: Mel clarified that teams may use commercial off-the-shelf parts with no more than one degree of freedom, and recommended Go Builda as a preferred supplier, while noting that electronics support is available upon request.
  • CAD and Design Resources: Mel highlighted free educational access to Onshape for CAD design, and mentioned other professional CAD programs and parts libraries, encouraging teams to utilize these resources for robot design and teaching.
  • Programming Tools and Tutorials: Dillon shared a YouTube playlist for FTC blocks programming and driver hub setup, and Mel discussed the availability of FTC Sim and XRP for programming practice, as well as the importance of subscribing to FTC Docs updates.
  • Upcoming Control System Changes: Mel informed teams of a new control system expected in two years, which will support multiple programming languages and a more flexible blocks-to-code workflow, and advised teams to plan for a transition period.
• Tournament Participation, Scrimmages, and Regional Events: Denise and Daniel raised questions about participating in other FTC tournaments and local scrimmages, to which Mel explained the rules for out-of-region play, discussed current and planned scrimmages, and offered to help connect teams with regional contacts and facilitate local events.
  • Out-of-Region Tournament Participation: Mel clarified that teams may participate in tournaments outside their home region for additional gameplay, but are not eligible for advancement or awards at those events, and that acceptance depends on the host region’s capacity.
  • Organizing and Attending Scrimmages: Mel described existing and planned scrimmages in North Carolina, Texas, and potentially Florida, and encouraged teams to help organize local scrimmages, noting that these events are informal and focus on practice and collaboration.
  • Connecting with Regional Teams: Daniel requested contact information for Florida regional organizers, and Mel agreed to reach out and provide details, noting that some regions may only host Saturday events and that local scrimmages can supplement official tournaments.
• Robot Maintenance and Match Preparation Strategies: Daniel and Phillip discussed issues with robot reliability during tournaments, prompting Mel to recommend regular maintenance checks, use of Loctite, and proactive repairs throughout the event to prevent mechanical failures.
  • Preventing Mechanical Failures: Mel advised teams to perform thorough checks and repairs on their robots during the tournament, especially at lunchtime, and to use temporary Loctite on bolts to prevent loosening, sharing past experiences of parts coming loose during critical matches.
• Match Scheduling, Alliance Selection, and Scouting: Daniel inquired about alliance partner assignments and match schedules, and Mel explained the process, including the importance of pre-match scouting and relationship-building with other teams to enable quick strategy adjustments.
  • Alliance and Match Schedule Process: Mel explained that alliance partners and match schedules are distributed at the drivers meeting on Sunday morning, leaving little time for in-depth strategy, so teams are encouraged to conduct scouting and information gathering during inspection and judging sessions.
• Hardware Availability and Mecanum Wheel Considerations: Daniel raised concerns about the availability of expansion hubs for Mecanum wheels, and Mel, Dillon, and Daniel discussed current stock status, purchasing tips, and considerations for wheel size and cost.
  • Expansion Hub Availability: Daniel noted recent shortages of the Rev expansion hub, but Mel and Dillon confirmed that stock has improved and provided guidance on purchasing quickly when available.
  • Mecanum Wheel Selection: Mel advised teams to consider wheel size and cost when purchasing Mecanum wheels, noting that different sizes have different advantages and that the wheels are a significant investment.
• Robot Expansion and Sizing Rules: Dillon and Daniel discussed the stricter robot expansion rules for the current season, and Mel confirmed the need to mechanically limit expansion and comply with the 18-inch cube requirement.
  • Expansion Rule Clarifications: Daniel explained that robots must be mechanically limited to the 18-inch cube except during the final 20 seconds, and Mel advised teams to plan for these restrictions to avoid disqualification at competition.
• Team Growth, Equipment Distribution, and Support: Daniel and Denise asked about equipment availability, and Mel explained the policy of providing control and driver hubs to newly registered teams to help bridge the gap until the new control system is released, with the condition that teams must be officially registered and attend the competition.
  • Equipment Distribution Policy: Mel stated that new teams without control systems can receive a control hub and driver hub upon registration, and clarified that these are given to help teams avoid unnecessary expenses before the upcoming control system transition.
• Future Meetings and Communication: Mel concluded the meeting by announcing that these sessions will be held monthly on the second Thursday, with recordings distributed to all teams, and encouraged participants to review past tournament recordings on YouTube.
  • Monthly Meeting Schedule: Mel confirmed that meetings will occur on the second Thursday of each month, with recordings made available to accommodate varying schedules, and referenced the YouTube channel for past tournament footage.

Follow-up tasks:

• Florida FTC Region Contact: Reach out to the appropriate contacts to identify the FTC league and event opportunities in the Florida region for Daniel’s team. (Mel)
• Spring Scrimmage Planning: Coordinate with local teams and volunteers to organize a spring scrimmage in the area, including confirming dates and logistics. (Mel, Daniel)
• Texas Scrimmage Date Update: Check the date for the Texas scrimmage and update the schedule to include it. (Mel)
• Distribution of Control and Driver Hubs: Provide control hub and driver hub to newly registered teams who contact Mel with their team number and ensure they plan to attend the competition. (Mel)

The post FTC Coach / Captain Call – October 2025 first appeared on Adventist Robotics.

Generated by AI. Be sure to check for accuracy.

Meeting notes:

• FIRST LEGO League Resources and Rule Structure: Mel provided an overview of essential resources for coaches, including the FIRST LEGO League website, the structure of the rule book, challenge updates, and the importance of understanding rule precedence for successful team participation.
  • Resource Overview: Mel directed participants to firstlegoleague.org, highlighting the importance of accessing the season page for guidebooks, engineering notebooks, rule books, and challenge updates, and explained how these resources form the foundation for team preparation.
  • Rule Book and Challenge Updates: Mel explained the structure of the Robot Game Rule Book, emphasizing that missions can override general rules, and that challenge updates take precedence over both, with updates issued based on team feedback and clarifications.
  • Mission Scoring and Equipment Constraints: Mel detailed how mission descriptions and scoring work, including the significance of the ‘no equipment constraint’ symbol, which means a mission model cannot earn points if touching equipment at the end of the match.
  • Field Setup and Technician Roles: Mel described the field setup, launch areas, and technician rules, clarifying that two student technicians are allowed per side, and that robots cannot be handed across the field after the match starts.
• Team Meeting Guide, Engineering Notebook, and Program Structure: Mel reviewed the team meeting guide and engineering notebook, outlining the four core areas of the program—core values, innovation project, robot design, and robot game—and explained their equal weighting in team evaluation.
  • Team Meeting Guide Usage: Mel described the team meeting guide as a coach’s resource for planning 12 two-hour sessions, adaptable for both beginner and advanced teams, and emphasized its role in structuring team preparation.
  • Core Values and Program Areas: Mel explained the importance of core values, gracious professionalism, and ‘cooperatition,’ and outlined the four program areas: core values, innovation project, robot design, and robot game, each weighted equally in rankings.
  • Engineering Notebook Purpose: Mel introduced the engineering notebook as a student-focused resource, detailing the design process steps—identify, design, create, iterate, communicate—and its use in brainstorming and documenting the innovation project.
  • Innovation Project Prompt: Mel highlighted this year’s innovation project prompt, which challenges teams to identify and solve a problem faced by archaeologists, encouraging outreach to local experts and use of available resources.
• Judging Rubrics and Competition Preparation: Mel explained the judging rubrics, session flow, and the importance of understanding evaluation criteria, providing guidance on how teams are assessed and how to prepare for competition judging sessions.
  • Rubric Structure and Scoring: Mel described the rubrics used for core values, innovation project, and robot design, explaining the scoring system, the meaning of gear symbols for dual-weighted criteria, and the need for clear evidence to achieve top scores.
  • Judging Session Flow: Mel outlined the 30-minute judging session, including time allocations for team introductions, innovation project presentations, Q&A, robot explanations, and judge feedback, and emphasized the importance of reviewing rubrics in advance.
  • Awards and Feedback: Mel noted that judges provide feedback sheets covering core values, innovation project, and robot design, and described the different awards available, encouraging teams to review award descriptions and prepare accordingly.
• Team Registration, Dashboard Management, and Compliance: Mel guided coaches through the team registration process on firstinspires.org, emphasizing the need for two cleared coaches, correct region selection, and parent consent for youth members, and addressed common dashboard issues raised by David and Tarkyshia.
  • Coach Clearance and Youth Protection: Mel explained that each team must have two primary contacts who are cleared through the Youth Protection program, clarifying that the second coach can be any adult and that clearance is separate from school-based background checks.
  • Region Selection and Team Profile: Mel instructed teams to ensure their region is set to ‘Adventist Robotics League’ in the team profile, explaining the implications of incorrect region selection and how to request changes if the field is grayed out.
  • Youth Member Registration and Parent Consent: Mel described the express enrollment process for youth team members, including generating QR codes for parent consent, and stressed that all youth must be registered and consented before competition participation.
  • Troubleshooting Dashboard Issues: Mel addressed David’s and Tarkyshia’s questions about dashboard errors, clarifying that both coaches need to log in for clearance, that event registration is handled separately, and that unresolved technical issues should be directed to FIRST support.
• Event Registration and Local Competition Logistics: Mel provided updates on event registration timelines, described the locations of upcoming competitions, and clarified procedures for local and Explorer events in response to questions from Ria.
  • Event Registration Status: Mel announced that event registration is slightly delayed but expected to open soon, listed competition locations including a new event in Tennessee, and explained that teams can choose any event to attend.
  • Local and Explorer Events: In response to Ria, Mel clarified that local Explorer events are not managed through the main dashboard, offered support for organizing local events, and described Explorer events as shorter, science fair-style gatherings.
  • Region and Communication: Mel explained the importance of selecting ‘Adventist Robotics League’ for communication and support, and provided background on the league’s history and structure, especially for teams in states with multiple regions.
• Technical Support and Missing Parts Resolution: Mel and Daniel addressed questions about missing LEGO model parts, advising teams to contact LEGO Education for support and to check for unnumbered bags, with Daniel providing additional clarification.
  • Contacting LEGO Education: Mel recommended contacting LEGO Education directly for missing parts, provided their website and support options, and offered to assist if teams do not receive a response.
  • Unnumbered Bags Clarification: Daniel explained that some parts may be in unnumbered bags, which are often overlooked, and Mel reiterated the importance of checking all packaging before requesting replacements.

Follow-up tasks:

• Coach Clearance Issue Resolution: Contact FIRST support to resolve issues with coach clearance and dashboard access for the second coach if problems persist after following standard procedures. (David)
• Missing Model Parts Resolution: Contact LEGO Education support directly to resolve missing parts for the model, and follow up if no response is received. (the team)

The post FLL Coach Call – October 2025 first appeared on Adventist Robotics.