V5 Push Back Scorekeeper Training for Head-to-Head Matches

This article includes tips from experienced Head Referees on how to train and use Scorekeepers for Push Back head-to-head Matches. See this related article for tips on training and using Scorekeepers for Push Back Skills Matches.

Last updated on October 3, 2025

Thank you for being here! You are in a unique position to help put the teams at ease, help them find answers to questions, and help them avoid breaking the rules.

• All Scorekeepers should have tablets or devices with TM Mobile installed and connected to the server
• One Scorekeeper at each field might be asked to queue matches and start/stop the match timer, and will submit the score
• Each Scorekeeper will typically be responsible for watching half of the field
  • Watch for robots that cross the autonomous line during the autonomous period <SG7>
  • Track which robots remove blocks from the field, and how many <SG4>
  • Watch for interference with parking robots <SG11>
  • Record points for an assigned part of the field, and show one or both alliances the scores after they’re tallied
• Each Scorekeeper is a valuable set of eyes on a match, with a different viewing angle from the head referee’s; head referees may ask for input on the interactions you see during the match, especially at the corner of the field you’re closest to
• If a team asks you a question about the rules, point them to the Head Referee

The lists below are key rules and tasks to keep in mind while watching a match.

Before Each Match

• Field requirements
  • Check field setup
  • Check alliance station for preloads (2 red, 2 blue)
• Team requirements
  • Safety glasses <S4>
  • Up to 3 drive team members per robot <GG1>
  • No powered headphones or earbuds <GG1>
  • Devices in airplane mode <GG1>
  • Fill pneumatics off the field before the head referee arrives <GG3>
• Robot requirements
  • Correct color license plates <R6>
  • Robot starting positions <SG1>
    • Within a max size of 18”x18”x18”
    • Contacting the barrier of their alliance's park zone
    • Not contacting any Robots or non-preload objects
    • Nothing in motion
• Preload positions <SG5>
  • Touching exactly one alliance robot
  • Not contacting or within the volume of a Goal or Loader

Autonomous Period

• Watch for:
  • Robots that don’t move at all; once they move of their own accord, the team can’t reach in to troubleshoot electronics/connectivity <GG4>
  • Robots that contact tiles, blocks, or robots that start on the other side of the Autonomous line <SG7>
• Count your assigned goals for the autonomous period
• Check for earned Autonomous Win Points (not needed in elimination matches)
  • 7 scored blocks of their color (10 for worlds-qualifying events)
  • 3+ goals with at least 1 scored block of their color (2 blocks per goal for worlds-qualifying events)
  • 3+ blocks of their color removed from "their" loaders
  • Neither robot contacting the park zone barrier

Driver Control Period

• Holding <GG17>
  • Start counting immediately, at about 1 count per second (1, 2, 3, 4, etc.)
    • Better to call it unnecessarily than to miss it
    • The Head Referee may signal you to stop the count if they disagree, or to continue if they do agree (thumbs-up, etc.); they might also take over the count so you can stop
    • Ends when either robot moves away; becomes a penalty if it lasts longer than a 3-count
  • Pinning
    • Must be trying to escape
    • Can be against anything, including another robot
  • Trapping
    • Must be trying to escape and *not* have an escape route
    • Confining a robot to a small section of the field
  • Lifting
    • Does not have to be trying to escape
    • Raising or lifting another robot so it can’t move
• Don't anchor to goals <GG9>
  • Watch for robots "camping" with a mechanism inside of a goal
• Keep Objects in the Field <SG4>
  • Track which robots remove blocks from the field, and how many
  • Return blocks to the matching alliance drive teams
• Park Zones (last 20 seconds) <SG11>
  • Note any contact or change to park zones or robots in their own park zones

After Each Match

• Notify the Head Referee of any violations you observed during the match
• Score your assigned portion of the match
• Confirm your count with your partner
• Confirm the autonomous winner and AWPs with your partner
• Show scoring to the teams
• Preserve the match & field layout if there are rules questions or scoring issues; notify the Head Referee
• One person submits scores after teams agree
• Tell the teams they can take their bots
• Activate the field reset crew
• Notify queuers to send teams for the next match if needed

Quick Reference for Push Back Head-to-Head Scoring: Points & Criteria

Criteria for a Scored Block <SC2>

• The Block is in contact with the inside surface(s) of the clear plastic part of a Goal.
• The Block is not in contact with a Robot of the same color as that Block.
• The Block is not in contact with the Floor.

Criteria for a Controlled Zone <SC3>

• For Long Goals, a Scored Block is considered Scored in the Control Zone if it is entirely contained
  within that Control Zone.
• A Block must be considered Scored in a Goal (see <SC2>) to also be considered Scored in a Control Zone.

Criteria for a Parked Robot <SC4>

• The Robot is not contacting the Floor outside of its Alliance-colored Park Zone.
• The Robot is not contacting any Field Elements other than the inside face of the Field Perimeter, the
  Floor inside of its Alliance-colored Park Zone, and/or the plastic extrusions and connectors that are
  part of the Park Zone. Contact with these allowed elements is not required.
• The Robot is at least partially within the vertical projection of its Alliance-colored Park Zone.