FIRST LEGO League Coach Call – November 2, 2026 BioGlow

FIRST LEGO League Coach Q_A-20261102_190231-Meeting Recording.mp4

Generated by AI. Be sure to check for accuracy.

Meeting notes:

  • FIRST Registration and Team Setup: Mel walked coaches through the updated FIRST registration process, emphasizing the Adventist Robotics League region, Founders Edition selection, required organizational information, storefront payment, and completion of two coach clearances before youth enrollment.
    • Required Documents: Teams may need to upload a school W-9 and, where applicable, a tax-exempt certificate. Mel explained that the W-9 identifies the organization and is not itself a request for tax-exempt status; David was advised to check whether the requirement applies to their organization or storefront purchase.
    • Region Selection: Teams should verify that their profile lists Adventist Robotics League rather than the automatically assigned geographic region. Mel highlighted this as a required profile check after registration.
    • Program Selection: Teams must register for the BioGlow Founders Edition. The Future Edition uses a different robot and is not supported by the league; teams that selected the wrong edition should create a new team if they have not paid or contact Mel for help.
    • Roster Requirements: Each team must have two coaches with required consent, release, and youth-protection clearances. Youth members cannot be enrolled through express enrollment until the registration fee is paid and the required coach clearances are complete.
    • Storefront Payment: The FIRST Storefront is used to pay the team registration fee and purchase the BioGlow challenge set. Teams may need their financial information approved before purchase, and those experiencing problems should contact Mel or FIRST headquarters.
  • BioGlow Judging And Innovation Project: Mel explained that Robot Game, Robot Design, Innovation Project, and Core Values each account for 25% of event performance, then detailed the biodiversity-focused innovation process and the judging expectations for identifying, designing, creating, iterating, and communicating.
    • Scoring Structure: The four equally weighted areas are Robot Game, Robot Design, Innovation Project, and Core Values. Teams may earn recognition in an individual area, while the Champion’s Award considers all four; Core Values are demonstrated across the team’s work and event experience.
    • Innovation Prompt: Teams must identify a problem that puts biodiversity at risk and design an innovative solution. Each team should pursue its own independent project, research why the problem matters, and ensure the project directly relates to the prompt.
    • Design Process: The project process consists of Identify, Design, Create, Iterate, and Communicate. Teams define and research a problem, create a project plan, develop an original idea or improve an existing one, produce a prototype model or drawing, gather feedback, make improvements, and present the solution in a live presentation.
    • Iteration And Evidence: Teams should share their solution with multiple people or mentors, preferably those with relevant expertise, record the feedback, and show how the solution changed as a result. Sharing is intended to test whether the idea is viable and identify specific improvements.
    • Rubric Expectations: The judging rubric evaluates each of the five project stages. Mel advised teams to study the rubric early and aim for clear definitions, detailed research from varied sources, an effective plan, participation by all members, a meaningful prototype, documented feedback-based improvements, and an effective presentation.
  • Robot Design And Team Participation: Mel connected the robot-design rubric to planning, testing, mission strategy, and Core Values, while advising coaches to rotate responsibilities so every student learns programming, building, robot strategy, and project work.
    • Mission Strategy: Teams should identify which missions to attempt and explain why they selected them, rather than simply choosing whatever seems easiest. A strategy can begin with an accessible mission to build confidence and then sequence additional missions based on the team’s plan.
    • Testing And Improvement: The robot-design rubric looks for collaborative design, building and coding skills across the team, repeated testing of the robot and code, and documented improvements based on test results.
    • Shared Responsibilities: Although students may develop areas of strength, every member should learn to program, build, contribute to the innovation project, and understand the team’s overall work. Mel cautioned against permanently dividing a team into isolated programmers, builders, and project members.
    • Coach Role: Coaches should facilitate rather than do the work. They should guide students through planning, research, construction, programming, and reflection without programming or building the robot for them.
    • Team Roles: The materials provide possible roles such as coder, builder, material manager, mission strategist, team captain, and researcher. Amber raised the challenge of engaging ten students; Mel recommended using roles while still giving members opportunities to try every area.
  • Robot Game Rules And Field Requirements: Mel reviewed autonomous robot-game operation, permitted equipment, mission interpretation, field-handling rules, and table construction requirements, including the need to read the wording literally and check official updates.
    • Autonomous Operation: At competition, the robot must operate autonomously. Students cannot drive or remotely control it, start it from a computer or tablet, or keep it tethered by Bluetooth; the robot must be launched by pressing its button at the field.
    • Permitted Equipment: Teams may use LEGO equipment in original factory condition, one controller, up to four motors, and permitted touch/force, color, distance/ultrasonic, and gyro sensors. SPIKE Prime, SPIKE Essential, EV3, Robot Inventor, Powered Up, NXT, and RCX are allowed, and teams may use any software or programming language.
    • Mission Interpretation: For Mission 3, the research flag must be down for the base points, and the rock must first be flipped and then returned to its starting position for the bonus. Leaving the rock in place does not qualify because the flag would not have been activated. Mel advised teams to follow the exact wording and not assume that a visible red mechanism is the only permitted method unless the rule says so.
    • Field Handling: The robot must start in a launch area, complete missions autonomously, and return as required. Teams may not hand the robot or loose pieces from one side of the table to the other; technicians must work within the permitted sides.
    • Table Construction: Tables should use smooth, sanded plywood or another smooth board, with clean surfaces and no visible knots, sawdust, dirt, or particles under the mat. Unevenness can affect robot performance; coaches with concerns about rough tournament tables should contact Mel.
    • Rule Updates: FIRST-issued Challenge Updates supersede the original rule book and mission descriptions. Mel noted that the online rule book itself is not automatically rewritten for FIRST LEGO League, so teams must monitor the separate Challenge Updates page.
  • Software And Season Resources: Mel directed coaches to the BioGlow season materials, engineering notebook, team meeting guide, judging resources, rule book, scoring tools, and optional Pybricks software as resources for planning and preparation.
    • Season Materials: The FIRST Programs and BioGlow Founders Edition pages contain the team meeting guide, engineering notebook, building instructions, videos, judging rubrics, robot-game rule book, interactive rule book, score calculator, and challenge updates.
    • Planning Guides: The team meeting guide provides a coach-oriented sequence of twelve two-hour sessions, while the engineering notebook provides student activities, project sparks, reflection prompts, and possible role structures. Mel said teams may use the student notebook according to their needs.
    • Scoring Tools: Mel plans to send teams the score calculator that the league will use and asked teams to test it and report discrepancies. Coaches should also use the latest official scoring materials after updates.
    • Pybricks Option: Pybricks is an optional third-party platform supporting Python and block programming for LEGO hubs. It requires a firmware change, so teams cannot mix programs from Pybricks and the standard LEGO environment without re-flashing the hub; Python is free, while block coding requires a paid license or supporter access.
  • Costs And Equipment Planning: Mel outlined expected costs for registration, the event, robots, tables, challenge materials, and travel, while noting that grants may help teams obtain robots and that the Founders Edition does not use the separate Science and AI kits.
    • Current Costs: Teams should budget for the FIRST team registration fee, the league event fee, a robot if needed, a competition table, the challenge set, and travel. The storefront showed a $285 season registration product and a $105 BioGlow challenge set.
    • Excluded Kits: The LEGO Science and AI kits are associated with the Future Edition and are not required for the Founders Edition. Current teams should use the capabilities available through supported platforms such as SPIKE Prime or EV3.
    • Grant Support: Mel said the organization has provided grants to help teams obtain robots and has distributed available equipment so teams can participate without immediately repurchasing equipment.
    • Team Size: Teams may have up to ten members, although Mel said four to six is often easier to organize and keep engaged. Larger teams require deliberate role management and opportunities for all members to participate.
  • Future Program Transition: Mel shared limited, NDA-constrained information about the post-FIRST LEGO League program, stating that the competition structure and existing tables are expected to remain similar while new partnerships and a new robot platform are announced publicly.
    • Pending Announcements: Mel said they had attended a FIRST call under a nondisclosure agreement and could not provide detailed information. Public announcements about partnerships and the next platform were expected within the following weeks.
    • Competition Continuity: The future program is expected to retain Core Values, an innovation project, and a robot game. The existing 4-by-8-foot table is expected to remain usable, although the field and robot platform may change.
    • Robot Transition: Teams will still be able to use LEGO robots for at least the next year and should not need to replace equipment immediately. Mel advised teams to begin budgeting for a future robot and game, with an expected price in a range similar to SPIKE Prime, approximately $600, although the final amount was not confirmed.
    • Current Equipment Availability: SPIKE Prime has been discontinued at retail, which is one reason the organization distributed available robots as grants. The future program will have a different name and will not be tied to LEGO, but further timeline details were not yet available.
  • Coach Support And Season Approach: Mel announced recurring coach calls and encouraged teams to focus on learning, discovery, and participation rather than trying to complete every mission or achieve perfection in their first season.
    • Ongoing Support: Coach conference calls will occur monthly, with recordings available for coaches who cannot attend. Mel also offered to connect newer coaches with experienced coaches and said future calls will include a referee to explain common rules and competition pitfalls.
    • Realistic Goals: Mel explained that teams rarely complete all roughly fifteen or sixteen missions, so attempting only a subset does not mean a team is unprepared. Teams should choose a manageable strategy and prioritize learning through the process.
    • Team Experience: In response to Amber’s concern about managing ten students and providing a complete first-year experience, Mel advised allowing students to learn through the process without letting perfection prevent progress. The stated approach was to maintain fun, discovery, and participation while improving over time.

Follow-up tasks:

  • Team Registration: Verify that the registered team uses the Adventist Robotics League region and correct it if necessary. (Coaches)
  • Program Edition: Confirm that each team is registered for the BioGlow Founders Edition rather than the Future Edition, and contact Mel if the edition cannot be corrected. (Coaches)
  • Registration Documents: Upload the organization’s W-9 and, where required, tax-exempt certificate to complete registration and purchasing requirements. (Coaches)
  • Coach Roster: Add at least two coaches to each team roster and complete their required consent and release forms. (Coaches)
  • Team Enrollment: Complete team-fee payment and coach clearances so that team-member enrollment can be activated, then add the team members. (Coaches)
  • Season Resources: Review the BioGlow Founders Edition materials, including the team meeting guide, engineering notebook, judging rubrics, and robot-game rule book. (Coaches)
  • Judging Preparation: Teach teams to use the five judging areas—identify, design, create, iterate, and communicate—across both the robot design and innovation project. (Coaches)
  • Innovation Project: Develop an independent project addressing a biodiversity-risk problem, including research, a project plan, a prototype or drawing, feedback-based iteration, and a presentation. (Teams)
  • Team Skill Development: Ensure every team member participates in and gains experience with programming, building, and the innovation project rather than remaining assigned to only one specialty. (Coaches)
  • Robot Strategy: Define and document a deliberate robot mission strategy instead of selecting missions solely because they are easiest. (Teams)
  • Game Rules: Review the robot-game rules and missions, including autonomous operation, robot-button launches, launch-area requirements, and the prohibition on handing robots or pieces between field sides. (Teams)
  • Challenge Updates: Monitor FIRST challenge updates throughout the season and apply any rulings or corrections that supersede the rule book. (Coaches)
  • Practice Field: Build or obtain a clean, smooth, sanded-plywood competition table and ensure the field surface is free of debris that could affect robot performance. (Coaches)