Scouting Treatise
Introduction
Scouting in the FIRST Robotics Competition is a critical process that allows teams to gather, analyse, and apply data to improve performance in qualification matches and strategize for alliance selection. Effective scouting provides an advantage in match planning, alliance selection, and understanding the evolving meta-game of the competition. This treatise aims to outline comprehensive strategies for collecting, managing, and utilizing scouting data efficiently.
The Importance of Scouting
Scouting serves multiple purposes:
-
Match Strategy: Analysing opponents’ strengths and weaknesses allows teams to adjust tactics accordingly.
-
Alliance Selection: Ensuring informed decisions when selecting alliance partners for playoffs.
-
Understanding Trends: Identifying how the game is being played across different teams and competitions.
-
Self-Improvement: Tracking your own team’s performance to identify areas of improvement.
Field Areas
Stand Scouting
Stand scouting involves observing and recording data on robot performance from the audience stands during matches, focusing on objective metrics like scoring efficiency, defensive capabilities, and strategy execution.
Auto Stand Scouting Involves:
-
Choosing the starting position of the robot, keep in mind this is in respect to those standing in the corresponding alliance zone.
-
Select if the robot is preloaded - is equipped with a piece of coral before starting
-
Analyse if the robot passes the black line during the start of the game, located directly in front of it (towards the alliance’s driver section).
-
Check if the algae has been removed (from the reef), processed (put inside the side processor chute), and put in the barge. Put the number of times the event occurred by the robot.
-
Select whether the coral was placed on level 1, 2, 3, or 4. The levels are corresponding to height, where 4 is the tallest and one is at the base reef level. Include the number of times this has been accomplished by the robot in question.
Tele-op Stand Scouting Involves:
-
Check if the algae has been removed (from the reef), processed (put inside the side processor chute), and put in the barge. Put the number of times the event occurred by the robot.
-
Select whether the coral was placed on level 1, 2, 3, or 4. The levels are corresponding to height, where 4 is the tallest and one is at the base reef level. Include the number of times this has been accomplished by the robot in question.
Endgame Stand Scouting Involves:
1. Check if the robot climbs on the deep climb, shallow climb, parking or outside of the barge.
Deep if the robot is hanging from the lower barge.
Shallow if the robot is hanging from the higher barge.
Parked if the robot is touching the barge zone (the tape of the own team's color between the tape and the barge).
Out of the barge if the robot is not in the barge zone (not parked).
Misc. Stand Scouting Involves:
Noting down how well the robot’s defence is compared to other robots on the field. A rating of 0 is no defence and a rating of 5 is lockdown (being able to consistently pin robots with no penalties or block of significant opportunities to score)
Notes are an important way to describe details on the robot and elaborate on its strengths and weaknesses; What to write for Notes Section of Stand Scouting:
-
Robot Performance – How well the robot scores, defends, or supports its alliance.
-
Consistency – Does the robot perform the same way every match or struggle with reliability?
-
Strategy and play style – Does the team focus on offence, defence, or assisting others?
-
Driver Skill – Is their driving smooth, aggressive, or hesitant?
-
Coordination with Alliances – Do they work well with partners or play solo?
-
Penalties and Fouls – Do they frequently commit rule violations?
-
Mechanical Issues – Did their robot break down or show signs of failure?
What not to write about:
-
Don’t write bad abbreviations such as DNP (Do not pick).
-
Personal Opinions About the Team – Avoid comments like "This team is annoying" or "They are bad."
-
Overly Vague Notes – Avoid writing "good" or "bad" without explanation—be specific about what was good or bad.
-
Unverified Information – Don't write things like "They said they can climb but didn't try." Only record what you see.
What not to write about |
What to write about (reword based on specific scenario) |
Don’t write bad abbreviations such as DNP (Do not pick). |
"Their robot struggled to pick up game pieces, missing multiple attempts, and had difficulty manoeuvring around defence." |
Personal Opinions About the Team – Avoid comments like "This team is annoying" or "They are bad." |
“The team had difficulty coordinating with alliance partners and often acted independently rather than following a single set strategy." |
Overly Vague Notes – Avoid writing "good" or "bad" without explanation—be specific about what was good or bad. |
"They consistently scored 5+ game pieces per match and had a fast cycle time of ~10 seconds per piece." |
Unverified Information – Don't write things like "They said they can climb but didn't try." Only record what you see. |
“This team did not attempt to climb in the matches observed, so their endgame ability is unclear." |
Pit Scouting
Pit Scouting is where teams visit the workspace of other teams in the competition area and gather information regarding the overall robot and its functionality on the field.
Pit Scouting Involves:
-
Writing Number - the name will autofill for the set team.
-
Preferred Starting Position, can be left, right or centre. This can
-
The amount of coral the robot can score in one autonomous position. This is not the amount of points the team can score on autonomous, but the number of coral specifically.
-
Check off the capabilities for Tele-op performance, based on whether the team in question says they can complete the given task.
-
Add the cycle time of coral, the team states they can do.
-
Select a climbing option that the team can complete, keep in mind most robots should be able to park.
What to write for Notes Section of Pit Scouting:
-
One of the key things you could write down would be any unique features, like is there anything special or innovative about their design that stands out.
-
Another thing you could write down could be their weaknesses. For example, if their intake jams or if they are having drivetrain struggles. Additionally, you could highlight vulnerabilities in the robot, such as an exposed intake.
-
Something that you should keep in mind is to always be respectful when typing your notes out, just like with stand scouting as they are also public on the team's profile.
-
Something else you could write about would be the team's strategy and play style like whether they plan to play offence, defence, or support in matches. Additionally, you could see what part of the game they plan to do well in like Autonomous, Tele-op, or Endgame.
-
Another thing you could write about could be whether they have any sensors that could help them, like creating a pre-planned autonomous path. You can also check whether they are using vision tracking or sensor-based automation.