FRC Scouting Sheet Template: Printable Paper Sheet + Google Form to Sheets Setup

A good FRC scouting sheet records one robot's performance in one match using a handful of objective, countable fields — autonomous actions, teleop scoring by location, endgame/climb, defense, fouls, and reliability — backed by a separate pit sheet for robot specs. Below is a ready-to-print paper template plus a Google Form to Sheets setup that turns one row per scout into per-team averages you can rank on.

What to scout (and what to leave off)#

The golden rule: scout what you can count, not what you feel. Design every field so two different students watching the same robot write down the same number. Vague fields like "how good is their driver?" produce noise; countable fields produce a pick list.

Quantitative match scouting#

Break the robot's match into phases, because points and failures cluster differently in each.

• Autonomous. Did the robot move out of its starting zone? How many game pieces did it score, and into which goal? Did it attempt an endgame action early (some games allow it)? Auto has the biggest point swings and the biggest failures, so record both a count and a plain "auto worked? Y/N."
• Teleop scoring. Count game pieces scored, broken out by target/location, because most games score different goals at different values. Use tally boxes rather than one number at the buzzer — real-time tallies are far more accurate than end-of-match guesses.
• Endgame / climb. Record the exact end state as a single-select (none / park / level reached), never free text. This is usually a large, discrete point block.
• Defense. Two fields only: "Played defense? Y/N" and a 1–5 effectiveness rating. Optionally "Was defended against? Y/N" to explain a low scoring game.
• Fouls / penalties. A tally of fouls you saw the robot commit. Don't classify every rule — a raw count plus a note is enough for picking.
• Reliability. The most under-scouted and most decisive column. Checkboxes for: no-show, disabled/died mid-match, tipped over, dropped comms, mechanism jam. A robot averaging 40 points that dies one match in four is a very different alliance partner than one that reliably delivers 30.

Qualitative / pit scouting#

Done once per team at their pit, not every match:

• Drivetrain type (swerve, tank, mecanum) and rough speed
• What it can score, and into which goals/levels
• Can it climb, and to what level?
• Robot weight and dimensions, plus which auto routines they plan to run
• Vision/programming maturity and driver experience

Match data is your ground truth; pit notes explain the "why" behind it. Keep them short and factual.

Printable one-match-per-team paper sheet#

Fill in one card per robot per match (print six per page — one for each robot on the field). Use tally marks in the count cells and circle the endgame result. This copies straight into a Google Doc or Sheet:

Rename Target A/B/C to your game's actual goals before printing. Everything above the Notes line is a number or a checkbox on purpose — that is what makes a stack of sheets addable.

Google Form to Sheets with auto-aggregation#

Paper is fastest to fill in the stands; a linked Sheet is fastest to analyze. Build one form, one submission per robot per match (six submissions per match), and let the spreadsheet do the math.

1. Build the Form — one question per field#

Match the paper sheet field-for-field, using the question type that constrains the answer:

• Match # — Short answer with Response validation → Number (forces an integer)
• Team # — Dropdown populated with the event's team list (prevents the typos that silently break grouping)
• Alliance — Multiple choice (Red / Blue)
• Scout initials — Short answer
• Auto: left zone? — Multiple choice (Yes / No)
• Auto pieces, Teleop pieces per target, Fouls — Short answer, number-validated
• Endgame — Multiple choice (single-select: None / Park / L1 / L2 / L3)
• Defense played — Multiple choice; Defense rating — Linear scale 1–5
• Reliability — Checkboxes (multi-select)
• Notes — Paragraph

2. Link to a Sheet — one row per scout#

In the Form's Responses tab, click the green Sheets icon, which opens the "Select destination for responses" dialog, and choose Create a new spreadsheet. Every submission becomes one row, and Forms adds a Timestamp column automatically. Treat this Responses tab as raw, append-only data — never edit or sort it by hand.

3. Aggregate to per-team averages#

On a second tab, roll the raw rows up per team. Two ways:

• Pivot table (no formulas). Insert → Pivot table on the Responses range. Set Rows = Team #; add Values for Auto pieces, Teleop pieces, Endgame points, and Fouls, each summarized by AVERAGE, plus one COUNT for "matches scouted." Sort by any value column to get a ranking.
• QUERY (live and sortable). Reference columns by letter, matching your own layout: =QUERY(Responses!A:Z, "select C, avg(H), avg(I), count(C) where C is not null group by C order by avg(H) desc", 1)
• Single stat with AVERAGEIF: =AVERAGEIF(Responses!$C:$C, A2, Responses!$H:$H), where A2 holds a team number.
• Reliability rate: =COUNTIFS(Responses!$C:$C, A2, Responses!$Q:$Q, "Died") / COUNTIF(Responses!$C:$C, A2).

Why one row per scout matters: averaging several scouts across a robot's matches cancels individual bias and reveals consistency. Convert tallies to points once, on the summary tab, using the current game's point values — so when scoring changes, you edit one place, not every row.

2026 REBUILT variant note#

The template above is game-agnostic; only the scoring fields change each season. For REBUILT presented by Haas (2026), there is one game piece — Fuel, high-density foam balls scored into your alliance's Hub — and the endgame is a climb up the Tower. Scout these fields (confirm exact point values in the current 2026 Game Manual — scoring can change via Team Updates):

• Fuel is scored into your alliance's Hub in both autonomous and teleop, but only while the Hub is active (activation alternates through the match). Scout Fuel as a running tally — a fast, consistent Fuel scorer is the backbone of a strong alliance.
• Tower climb: the endgame is a climb to Level 1, 2, or 3. Record it as a single-select — None / L1 / L2 / L3 — plus whether it happened in autonomous.
• Ranking points: add a checkbox for whether the alliance reached each RP threshold (Energized and Supercharged come from Fuel; Traversal comes from the climb). Confirm the exact thresholds in the current manual.

So a REBUILT match card becomes: Auto Fuel (tally), Auto climb (Y/N + L1), Teleop Fuel (tally), Endgame climb (None/L1/L2/L3), Defense (Y/N + 1–5), Fouls (tally), Reliability (checkboxes). Every other part of the sheet — the structure, the Form, the pivot — stays identical next season. Swap the scoring fields, keep the frame.