All Tournaments Edition

©2017 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group.
Used by special permission. All rights reserved.
 Robot Design Judge
Preparation Pack
Table of Contents
 FIRST® LEGO® League Core Values
 10 Things to Know as a FIRST LEGO League Judge
 Robot Design Judging Primer
 Robot Design Rubric
 What to Expect as a Judge: Day of the Event
 Judging Process
 FIRST LEGO League Awards
 Robot Design Sample Questions
 Comment Starters
 The Challenge and Challenge Guide

FIRST LEGO League Core Values

 We are a team.
 We do the work to find solutions with guidance from our
Coaches and Mentors.
 We know our Coaches and Mentors don’t have all the
answers; we learn together.
 We honor the spirit of friendly competition.
 What we discover is more important than what we win. We
share our experiences with others.
 We display Gracious Professionalism in everything we do.
 We have fun.
 10 Things to Know as a FIRST LEGO League Judge
Please be sure to check out www.firstlegoleague.org for additional information, including Judging
Q & A from throughout the season:
FIRST LEGO League Challenge: www.firstlegoleague.org/challenge
Judging Questions: flljudge@firstinspires.org
Thank you for agreeing to be a Judge with FIRST LEGO League. The information in this packet is designed to help you prepare as a
Judge this season. It is intended to offer background information that will be useful to review prior to your tournament. You should
also participate in training sessions that may be offered through your local tournament organizer and/or FIRST LEGO League. We
hope your experience as a Judge is rewarding and enjoyable!
10. Have fun – you and the kids
The most important thing to know about a FIRST LEGO
League tournament is that it is supposed to be FUN. The
mission of FIRST is to get kids excited about science and
technology. A competition is a celebration of what the
children have accomplished throughout the season. It should
be serious and competitive, but not so much that the fun is lost.
9. Exhibit Gracious Professionalism and honor FIRST
LEGO League Core Values
These are the basic foundations of FIRST LEGO League, and
should always be at the forefront in everyone’s minds.
We offer specific awards to recognize Core Values
excellence, but a significant concern can impact team
eligibility in any award category.
8. Be a good role model for technology and
engineering careers
Give the kids a chance to see what makes engineers,
scientists, computer programmers and educators special.
Share your experiences without sharing your agendas. Be
professional – show the kids that what they have
accomplished is appreciated and valuable. Show interest in
their presentations and discussions, and be personable.
7. Respect the children
Please keep negative comments to yourself, away from the
ears of the kids, parents, and coaches. All teams should be
given the benefit of the doubt when questions arise about
adult involvement. If you suspect the kids did not do the
work, it is your job to probe further to prove it, rather than
assuming that the kids did not do the work. Remember that
these are kids who worked hard all season to make it to the
tournament. Treat their accomplishments with respect, and be
sure that other Judges do so as well. One negative
comment from a Judge can have a devastating effect on
teams. Make it your goal as a Judge to ensure that the
teams know what they did well, and that they have a positive
experience showcasing their achievements.
6. Respect the judging process
Stay on schedule. The kids have a more challenging
schedule than you do. Remember the FIRST LEGO League
awards philosophy. Remember that the whole judging process
is subjective. Concentrate on providing a great experience for
the kids and try not to get caught up in the mechanics of the
process. Do not share scores or awards discussions with the
kids, coaches or parents.
5. Evaluate teams completely and fairly
Each rubric is designed to evaluate many areas of a team’s
performance, and gives equal weighting to several factors tied to
specific awards. All Core Awards are of equal importance,
except for our Champion’s Award that recognizes all-around
excellence. Be objective, both on a team-by-team basis and
a total rubric evaluation basis. Familiarize yourself with the
levels of achievement. Identify any conflicts of interest you
have before the competition, and refrain from involving yourself
in discussions about any team when you have a conflict.
4. Consider age appropriateness and experience
Consider age when evaluating teams. Certain skills,
knowledge, and capabilities are more likely to be exhibited by
the kids as they get older and more experienced in general and
in FIRST LEGO League in particular. You may also see
rookie teams that are more polished and understand FIRST
LEGO League better than experienced teams.
3. Reward excellence and celebrate achievement
For a team to be considered for an award, they should be
evaluated at an Exemplary level of achievement in that
category whenever possible. Award distribution is spread as
equitably as possible among the teams, with the goal of no
team winning more than one judged award.
2. Provide specific and constructive feedback
Please be specific when providing feedback comments to
teams. This will also help when it comes to awards
deliberations – specific examples are very helpful when
differentiating between teams. “This team’s willingness to help
other teams (by providing programming mentorship, for
example) is exemplary” is more descriptive and helpful than
“that team was so nice and polite and exhibited gracious
professionalism.” Take lots of notes if you need to!
1. See #10 again!
 Robot Design Judging Primer

Robot Design judging in FIRST LEGO League can be compared to an engineering design review in the “real
world.” Design teams present their robots to panels tasked with selecting the robots that best meet the
requirements (completion of missions) given constraints like size, parts usage and software. The natural
inclination for engineers and technical people is to say, “There is an easy test to see which robots are best –
the competition!” However, in FIRST LEGO League, and often in the “real world,” decisions are made based
on how well a team can explain their design and all the things they considered while developing it. The FIRST
LEGO League Robot Design rubric represents a set of criteria that we feel are important “takeaways” from
participating in the design of a FIRST LEGO League competition robot. They are analogous to evaluation
criteria used when selecting between competing designs. Judges gather information about teams’ mechanical
design, programming and overall design process to evaluate a team and its robot.
As a Judge, here are some overall things to consider:
 The Robot Design judging session is more about the team's ability to present the robot and all the
thoughts and considerations that went into their final product than it is about its performance. The
performance is covered under the Robot Performance Award. The judging session is the time for the
Judges to learn from the teams the design processes they used to make decisions and gain
understanding; it also allows discussion so that Judges can be sure that the teams did the work.
 You may ask teams to perform missions with their robot on the judging table. Give teams the benefit of
the doubt should these missions not work successfully all the time. Judging tables and field setup kits
are not usually built or maintained to the same standards as competition ones. There is also a
tendency for Murphy’s Law to rule in these sessions and for teams to be nervous and mistake prone
when running missions in a judging setting.
 Teams may bring additional prototypes of their robot or attachments into a judging session.
Sometimes these prototypes utilize additional electrical parts beyond those allowable in competition.
Remember that electrical parts and software rules apply only to the robot used in the competition itself,
and that extra parts or software used by teams to demonstrate designs are perfectly allowable.
 Simpler is usually better. Don’t be overly impressed with complicated robots. The complication must be
used for a purpose.
 Remember that this is an engineering challenge for autonomous robots. Small imperfections in the
field, mission models and environmental variations must be considered by Accomplished and
Exemplary teams.

Mechanical Design
Durability – The robot should be able to withstand the rigors of the competition, for example it should be able
to contact walls or mission models without pieces falling off or breaking. Attachments should be similarly
robust. Long arms that delicately grip a lever aren’t very effective if they don’t stay attached to the robot.

Mechanical Efficiency – Here the Judges are looking for robot structures and attachments which show a
judicious use of parts. For example, using six pins to tie two beams together is not as efficient as using one at
each end. One note here: don’t over penalize the teams for adding small bits of “flair” or pieces that are fun for
them to use to express their creativity. Remember the Core Value “We have fun!”

© 2017 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
Mechanization – Judges look here for how the robot moves and operates. They look to see whether the
robot balances speed and power.

Programming
Just as with Mechanical Design, simplicity is desired when it comes to programs. Teams can develop
amazing programs that aren’t necessarily better than simple programs that perform the same purpose.

Programming Quality – The robot’s programs should work consistently, producing the same results every
time. Examples of quality code could include audible checks or a simplified menu system that teams use to
make sure they are running the appropriate section of code for a particular mission. Be careful to attempt to
assess how the robot’s programs would operate independent of mechanical faults.

Programming Efficiency – The goal here is to encourage teams to develop code that is modular, portable
and flexible, so that it can be used in multiple situations. This criterion also addresses readability and
documentation of code, both of which are good programming practices.

Automation/Navigation – Autonomy in FIRST LEGO League means that the robot operates with minimal
driver intervention. Retrieving a robot and taking a touch penalty may be part of an acceptable strategy for a
team, but it is still driver intervention. So for this instance, a team might have an Accomplished Mission
Strategy, but only score Developing for Automation. This criterion also doesn’t distinguish between sensor
use/feedback and mechanical feedback. For example, it is valid for a team to use an aligning jig in base
followed by a robot using the wall or a mission model to align itself before activating an attachment. It is also
just as valid for a team to use a light sensor to follow a line to the same mission model. Teams should try to
avoid just using driver aiming, motor rotations and timing to navigate the field, as these methods often
become unreliable under variations in field or environmental conditions. Remember that lack of sensors isn’t
necessarily a bad thing. Lack of Automation, however, should be considered.

Strategy & Innovation

Remember that Strategy and Innovation can be seen in Mechanical Design or Programming, as well as the
integration of both.

Design Process – Accomplished teams move beyond a trial and error approach to robot improvements to
utilize testing cycles where systematic processes are used. Frequently you will hear teams say, “We tried a lot
of different things and this one was the best.” You are looking for more details and more organization to their
process than that for teams who are Accomplished or Exemplary.

Mission Strategy – This is fairly straightforward. Judges can ask teams, “What is your strategy to complete
the missions?” and “How did you make decisions to support that strategy when designing your robot?”

Innovation – This is often a hard area for Judges to judge. Things to be on the lookout for here include
creativity, uniqueness, a cool attachment or programming trick, or something similar. Most competitions will
have one or more robots that will have some feature that captures the Judges’ attention. Remember that
Innovation implies added benefit, so make sure that the team can state the benefits of their cool feature.
 Robot Design Team Number _____________
Judging Room _____________
Directions: For each skill area, clearly mark the box that best describes the team's accomplishments. If the
team does not demonstrate skill in a particular area, then put an 'X' in the first box for Not Demonstrated
(ND). Please provide as many written comments as you can to acknowledge each team’s hard work and to
help teams improve. When you have completed the evaluation, please circle the team’s areas of strength.
Beginning Developing Accomplished Exemplary
Durability Evidence of structural integrity; ability to withstand rigors of competition
Mechanical Design

N frequent or significant sound construction; no

quite fragile; breaks a lot
D faults/repairs
Mechanical Efficiency
N excessive parts or time to
D repair/modify
Mechanization
imbalance of speed,
N strength and accuracy on
D most tasks
Comments:
rare faults/repairs
repairs
Economic use of parts and time; easy to repair and modify
inefficient parts or time to appropriate use of parts streamlined use of parts
repair/modify and time to repair/modify and time to repair/modify
Ability of robot mechanisms to move or act with appropriate speed, strength and
accuracy for intended tasks (propulsion and execution)
imbalance of speed, appropriate balance of appropriate balance of
strength and accuracy on speed, strength and speed, strength and
some tasks accuracy on most tasks accuracy on every task

Programming Quality
N would not achieve purpose
D AND would be inconsistent
Programming
Programs are appropriate for the intended purpose and would achieve consistent
results, assuming no mechanical faults
would not achieve purpose should achieve purpose should achieve purpose
OR would be inconsistent repeatedly every time

Programming Efficiency Programs are modular, streamlined, and understandable

N excessive code and difficult inefficient code and appropriate code and easy streamlined code and easy
D to understand challenge to understand to understand for anyone to understand
Automation/Navigation Ability of the robot to move or act as intended using mechanical and/or sensor
feedback (with minimal reliance on driver intervention and/or program timing)
robot moves/acts as intended robot moves/acts as
N frequent driver intervention frequent driver intervention repeatedly w/ occasional intended every time with no
D to aim AND retrieve robot to aim OR retrieve robot driver intervention driver intervention
Comments:

Design Process Ability to develop and explain improvement cycles where alternatives are considered and
narrowed, selections tested, designs improved (applies to programming as well as
Strategy & Innovation

mechanical design)
N organization AND explanation
D need improvement
Mission Strategy
N no clear goals AND no
D clear strategy
Innovation
N original feature(s) with no
D added value or potential
Comments:
organization OR explanation systematic and well- systematic, well-explained
need improvement explained and well-documented
Ability to clearly define and describe the team's game strategy
no clear goals OR no clear clear strategy to accomplish clear strategy to accomplish
strategy the team's well defined goals most/all game missions
Creation of new, unique, or unexpected feature(s) (e.g. designs, programs, strategies
or applications) that are beneficial in performing the specified tasks
original feature(s) with some original feature(s) with the potential original feature(s) that add
added value or potential to add significant value significant value

Strengths: Mechanical Design Programming Strategy & Innovation

© 2017 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
What to Expect as a Judge

Day of the Event

Before Judging During Team During During the Awards
Sessions Evaluations Deliberations Ceremony

• Meeting with the • Interview teams • Submit award • Attend the Awards
Judge Advisor to • Make sure sessions nominations and Ceremony (if
review stay on schedule rankings by your possible)
• Event schedule • Evaluate each team judging pair • Help distribute
• Judging according to rubric • Participate with all medals, awards and
procedures criteria and note area Judges to other team
• Judging constructive determine award recognition
Deliverables comments candidates/merged • Join the high-five line,
• Last minute items • Keep additional notes preliminary ranking congratulate all teams
• Meet your judging of team specifics if • Work with Judges of and have fun!
partner(s) and the rest needed other areas to
of the panel • Note and report: determine the
• Attend the Opening • cases of adult Champion’s Award
Ceremonies intervention winner(s)
• demonstrations • Work with all Judges
of GP & Core to finalize remaining
Values awards and prepare
scripts
 The Judging Process

Judging Sessions
Evaluate teams; Provide feedback
Judging
You will work
Pairs
Nominate and Rank Teams
with other
Judges Determine top teams seen by each pair
throughout the
tournament
using FIRST Call-Backs and Additional Information
LEGO League’s
Review and discuss top teams
process to Three
evaluate teams
and determine Judging
awards Areas Initial Deliberations
Determine preliminary rankings for each area award
Note that you
may work with
different Judges Final Deliberations
at different times
Determine Champion’s then all other award winners
All
Judges
Awards Ceremony
Develop script & distribute awards
The Judging Process

Judging Sessions

Team Evaluation
During Team

and Feedback
Evaluate teams; Provide feedback
Evaluation and
Feedback, the
Judges focus on Nominate and Rank Teams
evaluating each
team and Determine top teams seen by each pair
providing them
with constructive
Call-Backs and Additional Information
feedback
Review and discuss top teams

Initial Deliberations
During Awards Determine preliminary rankings for each area award
Deliberations,
Deliberations

the Judges focus

Final Deliberations
Awards

on determining
the teams Determine Champion’s then all other award winners
worthy of awards
and recognition
Awards Ceremony
Develop script & distribute awards
The Judging Process

1 2 3

Judge Advisor &

Judging Pairs

Nominate

Head Judges
Select
Judging Sessions & Rank Champion’s
Teams Candidates

Individual Award Nominations Champion’s Candidates

Completed Rubrics + – ~2 per room Selected by JA/HJ
Comments – 1 per
1-N Ranking for Overall Number dependent on
room
Area – 1 per room tournament size
Head Judges Facilitate
Individual Judging

4 6
5 Initial
Areas

Deliberations
Call Backs Discuss Award
Candidates
1-N Ranking for Each
Optional
Award in Each Area
Judge Advisor Facilitates

7 8 9 10
All Judges

Vote for Finalize Finalize

Discuss Champion’s
Champion’s Remaining Optional
Candidates Award Core Awards Awards

Scripts for All Awards

4
Written Feedback to
All Teams
 FIRST® LEGO® League
Awards
Full Structure
Champion’s Award
This award recognizes a team that embodies the FIRST LEGO League experience, by fully embracing our
Core Values while achieving excellence and innovation in both the Robot Game and Project.

Robot Awards
Mechanical Design
This award recognizes a team that designs and develops a mechanically sound robot that is durable,
efficient and highly capable of performing challenge missions.

Programming
This award recognizes a team that utilizes outstanding programming principles, including clear,
concise and reusable code that allows their robot to perform challenge missions autonomously and
consistently.

Strategy & Innovation

This award recognizes a team that uses solid engineering practices and a well-developed strategy to
design and build an innovative, high performing robot.

Robot Performance
This award recognizes a team that scores the most points during the Robot Game. Teams have a
chance to compete in at least three 2.5 minute matches and their highest score counts.

Project Awards
Research
This award recognizes a team that utilizes diverse resources to formulate an in-depth and
comprehensive understanding of the problem they have identified.

Innovative Solution
This award recognizes a team’s solution that is exceptionally well-considered and creative, with good
potential to solve the problem researched.

Presentation
This award recognizes a team that effectively communicates the problem they have identified and their
proposed solution to both the judges and other potential supporters.

© 2017 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
Core Values Awards
Inspiration
This award celebrates a team that is empowered by their FIRST LEGO League experience and
displays extraordinary enthusiasm and spirit.

Teamwork
This award recognizes a team that is able to accomplish more together than they could as individuals
through shared goals, strong communication, effective problem solving and excellent time
management.

Gracious Professionalism®
This award recognizes a team whose members show each other and other teams respect at all times.
They recognize that both friendly competition and mutual gain are possible, on and off the playing
field.

Judges Awards
During the course of competition the judges may encounter teams whose unique efforts, performance or
dynamics merit recognition. Some teams have a story that sets them apart in a noteworthy way. Sometimes a
team is so close to winning an award that the judges choose to give special recognition to the team. Judges
Awards allow the freedom to recognize remarkable teams that stand out for reasons other than the Core
Award categories. Examples include:

Against All Odds or Overcoming Adversity or Perseverance

This award goes to the team that improvises and overcomes a difficult situation while still making a
respectable showing, with an attitude that shows, “We can overcome incredible odds if we never give up, no
matter what!”

Rising Star
This award recognizes a team that the judges notice and expect great things from in the future.

Special Recognition Awards

Outstanding Volunteer Award
The FIRST LEGO League program would not exist without its volunteers. This award honors an extraordinary
volunteer(s) whose dedication to FIRST LEGO League has a positive impact on the team experience.

Coach/Mentor Award
Coaches and mentors inspire their teams to do their best, both as individuals and together. This award goes
to the coach or mentor whose leadership and guidance is clearly evident and best exemplifies the FIRST
LEGO League Core Values.
 FIRST® LEGO® League
Awards
Consolidated Structure

Champion’s Award
This award recognizes a team that embodies the FIRST LEGO League experience, by fully
embracing our Core Values while achieving excellence and innovation in both the Robot Game and
Project.

Project Award
This award recognizes a team that excels across the Research, Innovative Solution and
Presentation categories. This team utilized diverse resources for their Project to help them gain a
comprehensive understanding of the problem they identified, develop a creative, well-researched
solution and effectively communicate their findings to judges and the community.

Core Values Award

This award recognizes a team that excels across the Inspiration, Teamwork and Gracious
Professionalism® categories. This team displays extraordinary enthusiasm and spirit, knows they
can accomplish more together than they could as individuals, and shows each other and other teams
respect at all times.

Robot Design Award

This award recognizes a team that excels across the Mechanical Design, Programming and Strategy
& Innovation categories. This team uses outstanding programming principles and solid engineering
practices to develop a robot that is mechanically sound, durable, efficient and highly capable of
performing challenge missions.

Robot Performance Award

This award recognizes a team that scores the most points during the Robot Game. Teams have a chance to
compete in at least three 2.5 minute matches and their highest score counts.

© 2017 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
 Robot Design
Sample Questions
Durability
 How did you get your robot to stay together?
 How often does your robot fall apart? What happens and have you thought about ways to fix
this?

Mechanical Efficiency
 Would it be possible to use fewer pieces or components for your robot and still accomplish the
same missions?
 If your robot has attachments, tell us about them.

Mechanization
 Tell us about how your robot uses attachments or other mechanisms to complete missions.
 Describe how your robot moves from place to place, or overcomes obstacles, and balances
speed and power.

Programming Quality
 What program do you feel is your best? Why?
 Do your robot’s programs achieve the same result every time? If not, why do you think this
might happen?

Programming Efficiency
 What did you do to make your programs more understandable and easier to use?
 What mission is your favorite? Explain the steps in the program for that mission.

Automation/Navigation
 Would you explain how your robot turns (or travels a specific distance, or goes from base to a
specific destination)? How satisfied are you with this?
 As your robot moves around the field, was there one area that was more difficult to navigate
than another? If so, what did your team do to overcome this challenge?
 Would you explain which sensors you used, and how and why you used them?
 Would you explain how your robot knows where it is on the field? Note: Sensing includes not
only touch and rotation sensors, but time (timers in the RCX) and passive sensing such as
referencing to walls or other objects, etc.
Design Process
 What was the greatest design or programming difficulty you encountered? How did you solve
that problem?
 How did you test your designs?
 Describe one way your robot got better over the course of the season.

Mission Strategy
 How did your team decide which missions to tackle?
 How many of the missions has this robot completed successfully in a single match (includes a
tournament match, a tournament practice, or home practice)?
 We want to consider the overall strategy behind your robot’s design. Tell us about your robot,
its attachments and sensors and the missions the robot attempts so that we will understand
your team’s design strategy.
 Which attachments are most difficult to put on and/or take off?

Innovation
 What part of your design, program or strategy do you think is unique to your team?
 How did you come up with the idea?

Look For:
 Unusual strategy, programming or design.
 Propulsion or steering methods or functional aspects that no one else has or you are
surprised someone would try.
 Robot is able to effectively perform the same task over and over.
 Parts or functional aspects that make something difficult look very easy.
 Parts or mechanisms that perform several functions.
 Propulsion, steering methods or functional aspects that work, but children have no
understanding how.
 Children can describe what the robot will do based on the program.
 Does the team look to the coach for answers or are they focused on the robot and Judges?
 Noteworthy observations about Core Values to share with the judging team.
 Comment Starters
The best comments on FIRST LEGO League rubrics include at least one item the team did well and
one challenge or item for improvement.

Use these starters and key words to help you write meaningful comments appropriate for FIRST
LEGO League teams. Be sure cite evidence or examples and explain to teams why they
received the levels you marked (Beginning, Developing, Accomplished, Exemplary).

Positive Improvement Needed

Include at least one positive in each comment Include at least one item to improve in each
box. comment box.
 We liked how you…  We would have liked to hear more
 Excellent job on… about…
 Thanks for telling us about…  Your (project/robot/etc.) could be even
 ________ was an innovative way to better if you…
accomplish…  How could you change your design to
 Your (diagram/poster/etc.) helped us improve…?
understand your …  It seemed like your team struggled with…
 We appreciated that you…  We were still a little confused by…
 ________ was an effective way to…  Consider changing…
 ________ showed us how your team…  Think about…
 Your approach to…  Maybe you could add…
 _______ was an example of how your  One suggestion would be…
team…  We noticed that…
 Your team worked through…  We weren’t sure how…
 Your ______ process helped your team…  _________ could have been clearer.

Some words to inspire your comment writing:

 Challenging  Especially  Solve

 Consistent  Example  Specifically
 Demonstrate  Explain  Strategy
 Decide / decision  In particular  Strength
 Describe  Process  Thorough
 Disciplined  Resourceful  Try
 Display  Show  Wonder
 FIRST LEGO League
Challenge Documents

Challenge – This four-page color document includes

the essential information about what the teams need to do to
be successful in the Project and Robot Game. It includes the
Core Values that should guide the experience.

Challenge Guide – This document serves to

provide guidance and tools to help support teams in their
process of working on the Project, Robot Game and using the
Core Values.

Challenge Updates – This document serves to

communicate any clarifications or changes to the content of
the Challenge that happen after Challenge release. It is largely
driven by the frequently asked questions we receive from
teams.

All Challenge documents are available at http://www.firstlegoleague.org/challenge#block-block-19

 Solve problems in:
The Robot Game
• Read the Robot Game Rules in the Challenge Guide:
http://www.firstlegoleague.org/challenge
• Identify one or more Missions to solve
• Design a robot using LEGO® MINDSTORMS®
that can solve the Mission(s)
Missions as written below are only an overview.
For full details, read the Challenge Guide.
Note: *Asterisks tell you a specific METHOD is required,
and must be observed by the referee. Underlined
conditions must be visible at the END of the match.
M01 - PIPE REMOVAL
*Move the Broken Pipe so it is completely in Base.
20 Points
M02 – FLOW
*Move a Big Water (one time maximum) to the
other team’s field *only by turning the Pump System’s
valve(s). 25 Points
M03 – PUMP ADDITION
Move the Pump Addition so it has contact with
the mat and that contact is completely in the Pump
Addition target. 20 Points
M04 – RAIN
Make at least one Rain come out of the Rain Cloud.
20 Points
M05 - FILTER
Move the Filter north until the lock latch drops.
30 Points
M06 – WATER TREATMENT
Make the Water Treatment model eject its Big Water,
*only by moving the Toilet’s lever. 20 Points
M07 – FOUNTAIN
Make the Fountain’s middle layer rise some obvious
height and stay there, due only to a Big Water in the
gray tub. 20 Points
Have you ever wondered how you get the water you use in your
daily life? Whether it’s to brush your teeth, quench your thirst,
cook your food, or even take a swim – all of us need water! Does
it come from the ground, a river or a lake? How do you make
sure it’s safe to drink, and what happens when it goes down a
drain? In this season’s HYDRO DYNAMICSSM Robot Game,
you’ll explore these questions and many more, and you’ll
get to learn about the amazing engineering
used to protect your most precious liquid
asset – water!!
M08 – MANHOLE COVERS
Flip Manhole cover(s) over, obviously past vertical
*without it/them ever reaching Base. 15 Points EACH
FOR BONUS: Score 30 Manhole Cover points as
described above WITH both covers completely in
separate Tripod targets. 30 Points Added
M09 – TRIPOD
Move the inspection camera Tripod so it is
FOR PARTIAL SCORE: partly in either
Tripod target, with all of its feet touching
the mat. 15 Points
FOR FULL SCORE: completely in either Tripod
target, with all of its feet touching the mat.
20 Points
M10 – PIPE REPLACEMENT
(Install the Optional Loop first, in Base, if you
wish.) Move a New Pipe so it is where the
broken one started, in full/flat contact with
the mat. 20 Points
M11 – PIPE CONSTRUCTION
(Install the Optional Loop first, in Base,
if you wish.) Move a New Pipe so it is
FOR PARTIAL SCORE: partly in its target, in
full/flat contact with the mat. 15 Points
FOR FULL SCORE: completely in its target,
in full/flat contact with the mat. 20 Points
M12 – SLUDGE
Move the Sludge so it is touching
the visible wood of any of the six
drawn garden boxes. 30 Points
M13 – FLOWER
Make the Flower rise some obvious
height and stay there, due only to a
Big Water in the brown pot. 30 Points
FOR BONUS: Score Flower Points as described
above WITH at least one Rain in the purple part,
touching nothing but the Flower model.
30 Points Added
M14 – WATER WELL M16 – WATER COLLECTION
Move the Water Well so it has Move or catch Big Water and/or Rain water (one
contact with the mat and that contact is Rain maximum; no Dirty Water) so it is touching
FOR PARTIAL SCORE: partly in the the mat in the Water Target, *without the target ever
Water Well target. 15 Points reaching the white Off-Limits Line shown below.
FOR FULL SCORE: completely Water may be touching the target, and/or other
in the Water Well target. 25 Points water, but not be touching nor guided by anything
else. Each water model is scored as an individual.
— At least one Rain: 10 Points
— Big Water: 10 Points EACH
FOR BONUS: Score at least one Large Water in
M15 – FIRE its target as described above WITH one on top,
Make the fire drop *only by making the Firetruck
which is touching nothing but other water. 30 Points
apply direct force to the House’s lever. 25 Points
(Maximum only one Bonus can score)
M02 M11
M03
M04 M15
M16
M05 M08
M13
M14
M06
M10
M12
M17
M09
M01
M18
M07
M17 – SLINGSHOT M18 – FAUCET
Move the Slingshot so it is Make the water level obviously more
completely in its target. 20 Points blue than white as seen from above the
FOR BONUS: Score Slingshot cup, *only by turning the Faucet handle.
points as described above WITH the 25 Points
Dirty Water and a Rain completely
in the Slingshot target. 15 Points Added
PENALTIES: Before the match starts, the Ref
removes the six red Penalty discs from the Field,
and holds on to them. If you Interrupt the Robot,
the Ref places one of the removed Samples in the
The Robot Game Missions can provide real-world
white triangle, in the southeast, as a permanent/
examples for your Project research. Learn about the untouchable Interruption Penalty. You can get up
stories behind the Missions in the Challenge Guide:
to six such penalties, worth -5 Points EACH
http://www.firstlegoleague.org/challenge
 The Robot Game
2017/2018 Robot Game Rules
Guiding Principles
GP1 - GRACIOUS PROFESSIONALISM®
You are “Gracious Professionals.” You
compete hard against problems, while
treating all people with respect and kindness.
If you joined FIRST LEGO League with a main
goal of “winning a Robotics competition,”
you’re in the wrong place!
GP2 - INTERPRETATION
• If a detail isn’t mentioned, then it doesn’t
matter.
• Robot Game text means exactly and only
what it plainly says.
• If a word isn’t given a game definition, use
its common conversational meaning.
GP3 - BENEFIT OF THE DOUBT - If the
Referee (Ref) feels something is a “very tough
call,” and no one can point to strong text in
any particular direction, you get the Benefit
Of The Doubt. This good-faith courtesy is not
to be used as a strategy.
GP4 - VARIABILITY - Our suppliers and
volunteers try hard to make all Fields correct
and identical, but you should always expect
little defects and differences. Top teams
design with these in mind. Examples include
Border Wall splinters, lighting changes, and
Field Mat wrinkles.
GP5 - INFORMATION SUPERIORITY - If two
official facts disagree, or confuse you when
read together, here’s the order of their authority
(with #1 being the strongest):
#1 = Current Robot Game UPDATES
#2 = MISSIONS and FIELD SETUP
#3 = RULES
#4 = LOCAL HEAD REF - In unclear
situations, local Head Referees may make
good-faith decisions after discussion, with
Rule GP3 in mind.
• 
Pictures and video have no authority,
except when talked about in #1, #2, or #3.
• 
Emails and Forum comments have no
authority.
Definitions
D01 - MATCH - A “Match” is when two teams
play opposite each other on two Fields placed
north to north.
• Your Robot LAUNCHES one or more times
from Base and tries as many Missions as
possible.
• Matches last 2-1/2 minutes, and the timer
never pauses.
D02 - MISSION - A “Mission” is an opportunity
for the Robot to earn points. Missions are writ-
ten in the form of requirements.
• Most requirements are RESULTS that must
be visible to the Ref at the END OF THE
MATCH.
• Some requirements are METHODS that
must be observed by the Ref AS THEY
HAPPEN.
D03 - EQUIPMENT - “Equipment” is
everything YOU BRING to a Match for
Mission-related activity.
D04 - ROBOT - Your “Robot” is your
LEGO MINDSTORMS controller and all the
Equipment you’ve combined with it by hand
which is not intended to separate from it,
except by hand.
D05 - MISSION MODEL - A “Mission Model”
is any LEGO element or structure ALREADY
AT THE FIELD when you get there.
D06 - FIELD - The “Field” is the Robot’s game
environment, consisting of Mission Models
on a Mat, surrounded by Border Walls, all on a
Table. “Base” is part of the Field. For full details,
see FIELD SETUP. Download the Field Setup
Guide at www.firstlegoleague.org/challenge.
 Definitions (continued)
D07 - BASE - “Base” is the space directly above the Field’s quarter-circle region, in the southwest.
It extends southwest from the curved line TO the corner walls (no farther). The diagrams below
define “COMPLETELY IN” for Base, but apply for ANY area.

YES YES NO NO NO NO NO
(COMPLETELY IN) (COMPLETELY IN) (PARTLY IN) (PARTLY IN) (PARTLY IN) (OUT) (OUT)

D08 - LAUNCH - Whenever you’re done D10 - TRANSPORTED - When a thing

handling the Robot and then you make it GO, (anything) is purposefully/strategically being…
that’s a “Launch.” • taken from its place, and/or
D09 - INTERRUPTION - The next time you • moved to a new place, and/or
interact with the Robot after Launching it, • being released in a new place,
that’s an “Interruption.” it is being “Transported.” The process of
being Transported ends when the thing
being transported is no longer in contact
with whatever was transporting it.
Equipment, Software and People
R01 - ALL EQUIPMENT - All Equipment must be made of LEGO-made building parts in original
factory condition.
Except: LEGO string and tubing may be cut shorter.
Except: Program reminders on paper are okay (off the Field).
Except: Marker may be used in hidden areas for identification.
R02 - CONTROLLERS - You are allowed only ONE individual controller in any particular Match.
• It must exactly match a type shown below (Except: Color).
• ALL other controllers must be left in the PIT AREA for that Match.
• All remote control or data exchange with Robots (including Bluetooth) in the competition area
is illegal.
• This rule limits you to only ONE individual ROBOT in any particular Match.

EV3 NXT RCX

R03 - MOTORS - You are allowed up to FOUR individual motors in any particular Match.
• Each one must exactly match a type shown below.
• You may include more than one of a type, but again, your grand total may not be greater than FOUR.
• ALL other motors must be left in the PIT AREA for that Match, NO EXCEPTIONS.

EV3 “LARGE” EV3 “MEDIUM” NXT RCX

 Equipment, Software and People (continued)
R04 - EXTERNAL SENSORS - Use as many external sensors as you like.
• Each one must exactly match a type shown below.
• You may include more than one of each type.

EV3 TOUCH EV3 COLOR EV3 ULTRASONIC EV3 GYRO/ANGLE

NXT TOUCH NXT LIGHT NXT COLOR NXT ULTRASONIC

RCX TOUCH RCX LIGHT RCX ROTATION

R05 - OTHER ELECTRIC/ELECTRONIC THINGS - No other electric/electronic things are allowed

in the competition area for Mission-related activity.
Except: LEGO wires and converter cables are allowed as needed.
Except: Allowable power sources are ONE controller’s power pack or SIX AA batteries.

R06 - NON-ELECTRIC ELEMENTS - Use as many non-electric LEGO-made elements as you like,
from any set.
Except: Factory-made wind-up/pull-back “motors” are not allowed.
Except: Additional/duplicate Mission Models are not allowed.

R07 - SOFTWARE - The Robot may only be programmed using LEGO MINDSTORMS RCX, NXT,
EV3, or RoboLab software (any release). No other software is allowed. Patches, add-ons, and new
versions of the allowable software from the manufacturers (LEGO and National Instruments) are
allowed, but tool kits, including the LabVIEW tool kit, are not allowed.
R08 - TECHNICIANS
• Only two team members, called “Technicians,” are allowed at the competition Field at once.
Except: Others may step in for true emergency repairs during the Match, then step away.
• The rest of the team must stand back as directed by tournament officials, with the expectation of
fresh Technicians being able to switch places with current Technicians at any time if desired.
 Play (continued)
R09 - BEFORE THE MATCH TIMER
STARTS - After getting to the Field on time,
you have at least one minute to prepare.
During this special time only, you may
also...
• ask the Ref to be sure a Mission Model
or setup is correct, and/or
• calibrate light/color sensors anywhere
you like.
R10 - HANDLING DURING THE MATCH
• You are not allowed to interact with any
part of the Field that’s not COMPLETELY
in Base.
Except: You may Interrupt the Robot any
time.
Except: You may pick up Equipment that
BROKE off the Robot UNINTENTIONALLY,
anywhere, any time.
• You are not allowed to cause anything to
move or extend over the Base line, even
partly.
Except: Of course, you may LAUNCH the
Robot.
Except: You may move/handle/STORE
things off the Field, any time.
Except: If something accidentally crosses
the Base line, just calmly take it back - no
problem.
• Anything the Robot affects (good or
bad!) or puts completely outside Base
stays as is unless the Robot changes it.
Nothing is ever repositioned so you can
“try again.”
R11 - MISSION MODEL HANDLING
• You are not allowed to take Mission
Models apart, even temporarily.
• If you combine a Mission Model with
something (including the Robot), the
combination must be loose enough
that if asked to do so, you could pick
the Mission Model up and nothing else
would come with it.
R12 - STORAGE
• Anything completely in Base may be
moved/stored off the Field, but must
stay in view of the Ref, on a stand.
• Everything in off-Field Storage “counts”
as being completely in Base.
R13 - LAUNCHING - A proper Launch (or re-
Launch) goes like this:
• READY SITUATION
o Your Robot and everything in Base it’s
about to move or use is arranged by hand
as you like, all fitting “COMPLETELY IN
BASE” and measuring no taller than 12
inches” (30.5 cm).
o The Ref can see that nothing on the Field
is moving or being handled.
• GO!
o Reach down and touch a button or signal
a sensor to activate a program.
FIRST LAUNCH OF THE MATCH – Here,
accurate fair timing is needed, so the exact
time to Launch is the beginning of the last
word/sound in the countdown, such as “Ready,
set, GO!” or BEEEEP!
R14 - INTERRUPTING - If you
INTERRUPT the Robot, you must stop it
immediately, *then calmly pick it up for a
re-Launch (*if you intend one). Here’s what
happens to the Robot and anything it was
Transporting, depending on where each was
at the time:
• ROBOT
o Completely Re-Launch
in Base:
o NOT completely Re-Launch +
in Base: Penalty
• TRANSPORTED THING
o Completely Keep it
in Base:
o NOT completely Give it to the Ref
in Base:
The “PENALTY” is described with the
MISSIONS.
R15 - STRANDING - If the UNINTERRUPTED
Robot loses something it was Transporting,
that thing must be allowed to come to rest.
Once it does, here’s what happens to that
thing, depending on its rest location:
• TRANSPORTED THING
o Completely Keep it
in Base:
o Partly in Base: Give it to the Ref
o Completely Leave as is
outside Base:
 Play
R16 - INTERFERENCE
• You are not allowed to negatively affect
the other team except as described in a
Mission.
• Missions the other team tries but fails
because of illegal action by you or your
Robot will count for them.
R17 - FIELD DAMAGE
• If the Robot separates Dual Lock or
breaks a Mission Model, Missions ob-
viously made possible or easier by this
damage or the action that caused it do
not score.
R18 - END OF THE MATCH - As the
Match ends, everything must be preserved
exactly as-is.
• If your Robot is moving, stop it ASAP
and leave it in place. (Changes after the
end don’t count.)
• After that, hands off everything until after
the Ref has given the okay to reset the
table.
R19 - SCORING
• SCORESHEET - The Ref discusses what
happened and inspects the Field with you,
Mission by Mission.
o If you agree with everything, you sign the
sheet, and the scoresheet is final.
o If you don’t agree with something, the
Head Ref makes the final decision.
• IMPACT - Only your BEST score from
regular Match play counts toward awards/
advancement. Playoffs, if held, are just for
extra fun.
• TIES - Ties are broken using 2nd, then 3rd
best scores. If still not settled, tournament
officials decide what to do.
CHANGES FOR 2017
• The word “objects” has been replaced with
the word “things” for parallelism with the
term “anything.”
• Definition of “Transporting” is opened up for
situations not directly involving the Robot.
• Maximum Equipment height UPON
LAUNCH is now limited.
 2017/2018 Robot Game Missions

FOR THE MISSIONS…

*Asterisks tell you a specific METHOD is required, and must be observed by the referee.
Underlined conditions must be visible at the END of the match.

M01 - PIPE REMOVAL M04 - RAIN

Move the Broken Pipe Make at least one
so it is completely Rain come out of
in Base. the Rain Cloud.
20 Points 20 Points
SCORE SCORE

M02 - FLOW M05 - FILTER

*Move a Big Water (one Move the Filter
time maximum) to the north until the lock
other team’s field *only latch drops.
by turning the Pump 30 Points
System’s valve(s).
SCORE SCORE
25 Points

M03 - PUMP M06 - WATER

ADDITION TREATMENT
Move the Pump Make the Water
Addition so it has Treatment model
contact with the mat eject its Big Water,
and that contact is *only by moving the
completely in the SCORE Toilet’s lever. SCORE
Pump Addition 20 Points
target. 20 Points
 2017/2018 Robot Game Missions (continued)

M07 - FOUNTAIN M09 - TRIPOD

Make the Fountain’s middle layer rise some
obvious height and stay there, due only to a
Big Water in the gray tub. 20 Points
Move the inspection camera Tripod so it is
FOR PARTIAL SCORE: partly in either Tripod
target, with all of its feet touching the mat.
15 Points
FOR FULL SCORE: completely in either
Tripod target, with all of its feet touching the
mat. 20 Points

NO SCORE

M08 - MANHOLE COVERS

Flip Manhole cover(s) over, obviously past
FULL PARTIAL
vertical *without it/them ever reaching Base.
15 Points EACH
Each cover is scored individually.

SCORE SCORE
FOR BONUS: Score 30 Manhole Cover
points as described above.
WITH both covers completely in separate
Tripod targets. 30 Points Added
PARTIAL NO
M10 - PIPE REPLACEMENT (Install the
Optional Loop first, in Base, if you wish.)
Move a New Pipe so it is where the broken
one started, in full/flat contact with the mat.
20 Points

BONUS ADDED “FULL /FLAT CONTACT” SCORE

NO BONUS SCORE NO
 2017/2018 Robot Game Missions (continued)
M11 - PIPE CONSTRUCTION (Install the M13 - FLOWER
Optional Loop first, in Base, if you wish.) Move Make the Flower rise some obvious height
a New Pipe so it is and stay there, due only to a Big Water in the
FOR PARTIAL SCORE: partly in its target, brown pot. 30 Points
in full/flat contact with the mat. 15 Points
FOR FULL SCORE: completely in its target,
in full/flat contact with the mat. 20 Points

SCORE SCORE

NO PARTIAL

SCORE BONUS ADDED

FOR BONUS: Score Flower Points as

FULL described above WITH at least one Rain in the
purple part, touching nothing but the Flower
model. 30 Points Added
M12 - SLUDGE
Move the Sludge so it is touching the visible M14 - WATER WELL
wood of any of the six drawn garden boxes. Move the Water Well so it has contact with the
30 Points mat and that contact is
FOR PARTIAL SCORE: partly in the Water
Well target. 15 Points
FOR FULL SCORE: completely in the Water
Well target. 25 Points

SCORE SCORE

FULL FULL

NO

PARTIAL
 2017/2018 Robot Game Missions (continued)

M15 - FIRE
Make the fire drop *only by making the Firetruck apply direct force to the House’s lever. 25 Points

SCORE

M16 - WATER COLLECTION

Move or catch Big Water and/or Rain water (one Rain maximum; no Dirty Water) so it is touching the
mat in the Water Target, *without the target ever reaching the white Off-­Limits Line shown below. Water
may be touching the target, and/or other water, but not be touching nor guided by anything else. Each
water model is scored as an individual.
At least one Rain: 10 Points Big Water: 10 Points EACH

OFF-­LIMITS LINE EXTENDS NO SCORE SCORE: NO SCORE SCORE:

ALL THE WAY NORTH/SOUTH TWO BIG WATER AT LEAST ONE RAIN
INCLUDING UNDER RAMPS AND AT LEAST ONE RAIN

SCORE: SCORE: SCORE: SCORE:

TWO BIG WATER ONE BIG WATER AT LEAST ONE RAIN TWO BIG WATER

FOR BONUS: Score at least one Big Water in its target as described above WITH one on top, which is
touching nothing but other water. 30 Points (Maximum only one Bonus can score)

BONUS ADDED BONUS ADDED NO BONUS NO BONUS

 2017/2018 Robot Game Missions (continued)

M17 -­SLINGSHOT M18 - FAUCET

Move the SlingShot so it is completely in its Make the water level obviously more blue than
target. 20 Points white as seen from above the cup, *only by
turning the Faucet handle. 25 Points

SCORE SCORE
SCORE SCORE

NO
NO NO
FOR BONUS: Score SlingShot points as
described above WITH the Dirty Water and a
Rain completely in the SlingShot target.
15 Points Added

BONUS ADDED BONUS ADDED

PENALTIES -­Before the match starts, the Ref

removes the six red Penalty discs from the Field,
and holds on to them. If you Interrupt the Robot,
the Ref places one of the removed Samples in the
white triangle, in the southeast, as a permanent/
untouchable Interruption Penalty. You can get up
to six such penalties, worth -­5 Points EACH
 Robot Design Executive Summary
An “executive summary” is often used by engineers to briefly outline the key elements of a product
or project. The purpose of the Robot Design Executive Summary (RDES) is to give the Robot Design
Judges a quick overview of your team’s robot and all that it can do.

Some regions require all teams to prepare a Robot Design Executive Summary, while others do not.
Either way, the RDES is a great tool to help your team organize their thoughts about the robot and the
design process they used. Check with your tournament organizer to see if your team is expected to
present your RDES in the Robot Design judging session.

Unlike the Core Values Poster, teams do not
need to create a poster or written material for
the RDES. However, if the team would like to
share pictures of the design process, records
of strategy sessions, or examples of
programming (either printed or on a laptop),
the RDES presentation is an appropriate time.
Have your team prepare a short presentation
(no longer than four (4) minutes) covering the
elements below:
Robot Facts: Share a little bit about your
1. 
robot, such as the number and type of
sensors, drivetrain details, number of
parts and the number of attachments. The
Judges also like to know what programming
language your team used, the number of
programs, and the Robot Game mission
where your team had the most success.
2. Design Details:
a. Fun: Describe the most fun or interesting
part of robot design as well as the most
challenging parts. If your team has a fun
story about your robot please feel free to
share.
Strategy: Explain your team’s strategy
b. mission(s) of your team’s choice. Please do
and reasoning for choosing and
accomplishing missions. Talk a little bit
about how successful the robot was
in completing the missions that were
chosen.
Design Process: Describe how
c. 
your team designed their robot and
what process they used to make
improvements to the design over
time. Briefly share how different team
members contributed to the design.
d. Mechanical Design: Explain the robot’s
basic structure. Explain to the Judges
how the robot moves (drivetrain), what
attachments and mechanisms it uses to
operate or complete missions, and how
your team makes sure it is easy to add/
remove attachments.
Programming: Describe how your
e.
team programmed the robot to ensure
consistent results. Explain how the team
organized and documented programs.
Mention if the programs use sensors
to know the location of the robot on
the field.
f. Innovation: Describe any features of
the robot’s design that the team feels
are special or clever.
3. Trial Run: Run the robot briefly to
demonstrate how it completes the
not do an entire robot round. The Judges
need time to ask questions after the RDES.
 Want to learn more?
• Find the essential details of the Robot Game in the Challenge:
www.firstlegoleague.org/challenge.
• Check the Robot Game Updates often: www.firstlegoleague.org/challenge. Here FIRST®
LEGO® League staff will clarify common questions. Updates supersede anything in this
Challenge document and will be in effect at tournaments.
• Your team will be assessed in the judging room using a standard rubric. Review the
Robot Design judging information and rubric: www.firstlegoleague.org/challenge.
• Your team will also compete in at least three Robot Performance matches. Learn more
about Robot Performance, how to approach the Robot Game with your team, and tips
from experienced Coaches in the Coaches’ Handbook:
www.firstlegoleague.org/challenge.
• If you are completely new, check out the FIRST LEGO League Resource page for videos,
tips, and additional helpful rookie links: www.firstlegoleague.org/challenge.
 Challenge Updates

Robot Game Updates

29 August 2017
UPDATE 1 – Leniency

If you Interrupt the Robot while it’s Transporting a Mission Model that came from Base during the
most recent Launch, you may keep that model.

Project Updates

29 August 2017
UPDATE 3 – SEA LEVEL RISE
Clarification of the Human Use of Water

The potential for sea level rise is an issue of great concern for many communities. In order for this
subject to be an acceptable Project topic, your team should be able to relate sea level rise to a
problem in the human water cycle. Please remember to focus on a human use of water.

UPDATE 2 – NARROWING YOUR FOCUS

Clarification of the Phases of the Human Water Cycle

While the definition of the human water cycle includes four phases (“find, transport, use, and
dispose”), your team does NOT have to investigate all of these as part of your Project. You may
focus on one or more parts of the human water cycle when identifying a problem and designing a
solution.

UPDATE 1 – FRESH WATER VS. SALT WATER

Clarification of Categories of Water

The HYDRO DYNAMICSSM Project is not limited to the study of fresh water. Teams may explore a
use of fresh water, brackish water or salt water. However, the problem your team selects should be a