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:

• 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:

• 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.

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.

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:

• Event Registration and Promo Video: Mel discussed the new promo video for Adventist Robotics, available on their YouTube channel, and emphasized the importance of registering for the event as soon as possible to help with planning.
• Team Registration and Profile: Mel explained the importance of team registration and ensuring that Adventist Robotics is listed as the region in the team profile. He also highlighted the need for two registered coaches who have passed the Youth Protection screening.
• Tournament Requirements: Mel outlined the necessary steps for participating in the tournament, including bringing a printed roster, having two registered coaches, and ensuring all team members are registered. He also mentioned the importance of following school or conference policies for overnight trips.
• Tournament Schedule: Mel provided an overview of the tournament schedule, including the Vespers on Saturday night, robot inspections, and practice sessions. He also explained the judging sessions and robot qualifying matches on Sunday.
• Judging Process: Fiona, the judge advisor, emphasized the importance of sending the entire team to the judging sessions and preparing a 5-minute uninterrupted presentation. She encouraged teams to practice and have different team members present various aspects of the team.
• Leadership Award: Fiona introduced the Leadership Award, an individual achievement award for sophomores or juniors. She explained the nomination process and the importance of providing specific examples of the student’s leadership and contributions to the team.
• Game Rules and Scoring: Sam, the head referee, provided an in-depth explanation of the game rules, scoring criteria, and the importance of autonomous programming. He also discussed the consequences of damaging opponent robots and the need for cooperation between alliance partners.
• Scouting and Alliance Coordination: Mel and Sam highlighted the importance of scouting and coordinating with alliance partners to optimize scoring strategies. They suggested having multiple autonomous options and using timers to aid cooperation during matches.

Follow-up tasks:

• Leadership Award Nomination: Send out the form and requirements for the Leadership Award to all teams registered for the event. (Mel)
• Team Registration: Ensure all teams complete their registration and payment for the event. (All teams)
• Portfolio Submission: Submit a paper copy of the portfolio during team registration on Saturday night. (All teams)
• March Meeting Reminder: Send out a reminder for the next conference call scheduled for March 18. (Mel)
• Scouting Preparation: Prepare scouting forms and strategies to gather information about other teams’ capabilities before the match schedule is released. (All teams)
• Autonomous Programming: Develop and test multiple autonomous options, including potential delays, to coordinate with alliance partners. (All teams)

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

Meeting notes

Meeting Introduction : Mel welcomed everyone to the meeting, mentioned the recording, and outlined the agenda, including key referee and judging items.

Registration and Screening : Mel emphasized the importance of completing team registration on the Adventist Robotics website, ensuring no outstanding tasks, and completing youth protection screening through Sterling Volunteers.

Event Registration Fee : Mel explained the process for paying the event registration fee on the Adventist Robotics website and mentioned the optional purchase protection.

Youth Member Registration : Mel highlighted the need for all youth members to be registered and the importance of completing tasks early to reduce stress on event day.

Competition Manual and Updates : Mel reviewed the competition manual, emphasizing the importance of staying updated with team updates and changes to the manual.

Judging Session Overview : Fiona and Mel discussed the judging session process, including the 15-minute interview with judges, the importance of the team portfolio, and the follow-up pit interviews.

Leadership Award : Mel introduced the Leadership Award, which is similar to the Dean’s List award, and explained the nomination process and criteria.

Robot Inspection : Sam discussed the importance of passing robot inspection, including the 18-inch cube size limit and the new horizontal expansion limit.

Human Player Rules : Sam explained the role of the human player in the competition, including their ability to manipulate scoring elements during the autonomous and teleoperated periods.

Safety Requirements : Mel and Sam emphasized the importance of wearing safety glasses and closed-toed, closed-heeled shoes in the competition and pit areas.

Team Registration Status : Mel provided a list of currently registered teams and encouraged teams to register as soon as possible.

Follow-up tasks

.Team Registration: Ensure all teams are registered on the Adventist Robotics website and have no outstanding tasks. (All Coaches)

.Youth Protection Screening: Complete the Youth Protection Screening for all coaches and ensure emails match between FIRST and Sterling Volunteers. (All Coaches)

.Event Registration Fee: Pay the event registration fee on the Adventist Robotics website. (All Teams)

.Team Roster: Complete all tasks and print the team roster from the FIRST dashboard. (All Coaches)

.Judging Session Preparation: Prepare a 5-minute uninterrupted presentation and a 15-page portfolio for the judging session. (All Teams)

.Leadership Award Nomination: Nominate up to two 10th or 11th graders for the Leadership Award and complete the required form. (All Coaches)

.Robot Inspection: Inspect the robot using the inspection checklist and ensure it meets all size and construction requirements. (All Teams)

.Safety Compliance: Ensure all team members and visitors wear safety glasses and closed-toed, closed-heeled shoes in the pit area. (All Teams)

.Human Player Coordination: Coordinate with alliance partners to determine the human player for each match. (All Teams)

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