📊 Role 03 — Spartan Design

You are the Strategist

Your job is to make winning decisions. Know the game, know the opponents, know the plan. You win matches before the robot is turned on.

🚀 New Strategist? Start Here
Read the game manual → Scout your first match → Fill a pre-match plan before queueing. That’s the whole job.
Game Manual → Game Analysis → Scouting Sheet → EV Calc → Match Plan →
📝 Kickoff Week — Notebook First
The notebook is a team effort — every role contributes entries. On kickoff day, the strategist coordinates the analysis and ensures it gets started: game overview, problem statement, criteria and constraints. These entries belong to the whole team and are written before any mechanism is chosen.
🕮 Game Manual → ⚡ Game Analysis → 🗺 Notebook Pathway → 📝 Getting Started → 📄 Open Template →
📊 What are you working on today?
🚀 New Strategist? Your first week.
  1. Read the Game Manual
  2. Game Analysis — understand scoring before anything else
  3. Match Scouting Sheet — use it at your first practice
  4. Notebook Pathway — strategist leads the analysis entries
  5. 🤝
    Alliance Selection & Pick Strategy
    Captain prep, negotiation, pick order
    📊
    Match Score Predictor
    OPR-based alliance scoring model
    Autonomous Strategy — once you have a working auton
📚 Strategy guides all guides →
▶ You are here Start at Beginner. Learn the game before building your toolkit.
🚀 Strategist Progression
● Beginner — Learn the Game
Read the manual. Track AWP every match. Scout every team you face.
Game Analysis → Match Scouting → Season Timeline →
● Intermediate — Build Your Toolkit
Calculate EV, plan routes, brief your driver with data — not guesses.
Auton Strategy → Route Planning → AWP & Skills → 🧰 Strategist Toolkit → 📈 VRC Data Analysis →
● Advanced — Win Matches Before They Start
Build an alliance list. Read opponent autons in one match. Adjust mid-event.
Alliance Selection → Alliance Coordination → Match Reading → 🎤 Interview Prep → 📝 Notebook →

📊 Your role on the team

How Strategists train and compete.

The progression above builds your strategic toolkit. This section explains where that toolkit gets used — which squad you support, what you're responsible for at each event, and what competition readiness actually means for a strategist.

"Your role is what you train to master. Your squad is where you compete right now."

Strategist role pair

Qualifier Squad

📊 Qualifier Strategist

League Squad

📊 League Strategist

What training partners develop together

  • Game analysis — both strategists work through the same scoring breakdowns, efficiency calculations, and decision frameworks
  • Scouting habits — both strategists practice observation, data collection, and team ranking using the same scouting sheet and criteria
  • Alliance planning — pre-match briefs, partner coordination, and elimination logic are rehearsed together in class before any event
  • Notebook reasoning — both strategists contribute analysis entries, decision rationale, and testing evidence — not just the notebook lead
  • Post-match reflection — after every practice match and event, both strategists debrief what the data showed and what changes are warranted

In-class responsibilities — every strategist, every session

  • Game manual reading — know the scoring rules, edge cases, and AWP conditions cold. If you're looking it up during a match, you're not ready.
  • Game analysis — work through efficiency calculations, points-per-second, and scenario modeling before your team locks in any strategy.
  • Route planning — translate scoring priorities into actual robot paths. Know which routes are fast, which conflict with partners, and which break under pressure.
  • Scouting habits — practice filling the scouting sheet in real time. Record auton, cycle time, mechanism reliability, defense, and end-game every match you watch.
  • Alliance-fit thinking — evaluate teams not by raw score but by whether they complement your robot's strengths and can execute a coordinated plan.
  • Notebook evidence and reasoning — write the analysis entries. Document the decisions. Record what changed and why. The judges want to see your thinking, not just your conclusions.
  • Decision frameworks — build repeatable systems for auton selection, alliance ranking, and in-match pivots. Improvised decisions in the queue are too late.

Event assignments

League Squad at league events
  • League Strategist owns pre-match priorities and match planning
  • Fill the match plan form before every queue
  • Brief the drive team on opponent auton and zone assignments
  • Update scouting notes within 2 minutes of each match ending
  • Lead the post-match reflection with the drive team
Qualifier Squad at qualifiers
  • Qualifier Strategist owns pre-match priorities and match planning
  • Fill the match plan form before every queue — no exceptions
  • Brief drive team before queueing; update immediately after
  • Coordinate with the League Strategist who is scouting from the stands
  • Use the combined scouting data for elimination decisions

Scout lens — what the League Strategist watches at qualifiers

The League Strategist at qualifiers is running the full scout operation. Every match is active observation work — the data you collect directly shapes the team's alliance decisions and elimination strategy.

Compile notes

Fill the scouting sheet for every match — auton, cycle time, mechanism reliability, end-game, defense

Identify alliance fit

Track which teams complement your robot — not just who scores highest, but who coordinates well

Track trends

Which teams improve across the day, which fade, and what the overall field meta looks like by match 8

Build recommendations

Rank alliance candidates before eliminations open. Have the list ready — not in-progress — when selections start

Pre-match briefs

Between matches, give the Qualifier Strategist a short brief on what you saw — opponent auton, threats, openings

Post-match reflection

Help the drive team debrief after each match — what the data shows, what to adjust, what held up

Your scouting sheet and alliance tracker — the tools already on this page — are your primary instruments. Use the full scouting section below for the complete workflow.

Notebook connection

📝

Strategist thinking belongs in the notebook

The notebook is not just an engineering document. Judges want to see how the team made decisions — and strategists own a significant part of that evidence.

  • Design decisions — why the team chose this autonomous routine, this mechanism, this game strategy
  • Strategy decisions — what the game analysis showed, what EV math supported, what was ruled out and why
  • Testing evidence — auton consistency results, cycle time benchmarks, and the data that justified each change
  • Changes over time — when the strategy changed and what drove that change. Judges reward teams that show iteration, not just outcomes.

The Notebook section below this page and the Notebook Pathway → guide cover the full entry process. Your job as a strategist is to make sure the reasoning is documented.

How class work prepares you for either assignment

Game analysis

Working through scoring math and scenario modeling in class builds the decisions you'll make in the queue

Scouting practice

Filling the scouting sheet in practice matches trains the eye and speed you need at a real tournament

Notebook entries

Documenting decisions and analysis all season means you're ready for the judge interview regardless of squad assignment

Tournament roll call

Before every tournament, the team holds a tournament role roll call. Every strategist is expected to be ready to cover scouting, match planning, notebook, or interview support. Tracking every match you watch and keeping your scouting sheet current is how you stay ready.

⚡ Game Analysis → 📊 Match Scouting Sheet → 🏆 Auton Strategy → 🌎 Route Planning → 📝 Notebook Pathway → 🎤 Interview Playbook → ★ Full Team Structure → ★ Spartan Hub →
AI Match Brief Generator
Powered by Claude

Describe your robot and the match situation — get a 3-sentence match brief ready for your drive team.

⚠ RECF EN4 — AI use notice
Match briefs from this tool are for live match-day use only — a thinking prompt for the drive team. RECF rule EN4 prohibits pasting AI-generated content into engineering notebooks. Do not copy any match brief, strategy note, or debrief text into your notebook.
Your robot's strengths
Opponent team # (optional)
Scouting notes on opponent
Before Every Match
📋 Before Queuing
  • › Know current rankings and standings
  • › Confirm your auton selection and why
  • › Check alliance partner’s robot status
  • › Know opponents’ autonomous routines
▶ During Match
  • › Watch opponent auton — adapt next round
  • › Count scored pieces, track goal ownership
  • › Signal driver if a strategic pivot is needed
✅ After Match
  • › Update scouting sheet within 2 minutes
  • › Tell engineer what broke or underperformed
  • › Update your AWP status and skills ranking
🎲 Game Strategy
First question every match: What is the highest-value action my team can take in the first 10 seconds of driver control? Know the answer before queueing.
🎯 Autonomous Priority High Impact
A reliable 10-pt auton beats an unreliable 18-pt one across 12 matches. Use EV math (probability × points) to choose your routine. Track your auton win rate every practice.
👥 Alliance Coordination
Talk to your alliance partner for 60 seconds before every match. Agree on zones, scoring assignments, and end-game plan. Most alliances skip this — don’t.
📈 Points-Per-Second
Points scored ÷ time used for each action. Prioritize the highest efficiency actions first. In 1:45, efficiency beats raw score ceiling.
🚫 Defensive Decisions
Defense is correct when opponent’s expected score exceeds yours and you can meaningfully reduce their output. Decide before the match, not during it.
End-Game Planning
At 0:30, your driver executes a plan decided before the match — not deciding in real time. Know your end-game sequence cold before queueing.
AWP Strategy
Know the exact AWP conditions. Coordinate with alliance to both meet them — one missed step forfeits the point for both teams.
🏆
🌎
🔎 Scouting
💡
Scout in every match you’re not playing. Watch and record: auton routine, cycle time, scoring positions, mechanism failures, defense capability. Two observations beat zero.
✍️ What to Record
  • › Autonomous: works / fails / partial + points
  • › Driver cycle time (estimate in seconds)
  • › Scoring positions they prefer
  • › Mechanism failures observed
  • › Defense capability: can they? do they?
  • › End-game: do they have one?
🏆 Alliance Selection Priority
Rank teams by: (1) auton reliability — consistent beats high ceiling, (2) average cycle time, (3) whether they complement your robot. Make your list before elimination rounds, not during.
📈
📊
✎️ Autonomous EV Calculator
Expected Value = probability × points. A reliable 10-pt auton beats an unreliable 18-pt one. Add up to 3 routines and compare.
🏆 Alliance Selection Tracker
Track teams you’ve scouted. Rank by auton reliability and driver score. Build your alliance list before elimination rounds.
🏁 Match Planning
📝 Pre-Match Plan — Fill Before Queueing
✅ Saved!
Summarize your entire plan in one sentence. Say it out loud to your squad before you queue.
This is the last thing your squad hears before walking to the field.
Recent Plans
📝 Engineering Notebook
✎️
Notebook entries are team-wide. Engineers log builds, Drivers log test data, you log analysis and decisions. Your job: make sure it happens.
5-minute rule: Write the session entry before anyone leaves. Memory fades fast.
✅ Today’s Notebook Checklist
Date, team members present, EDP step label
Every entry needs a header
What did we do today? (1-2 sentences)
Context: why did we do this? What problem prompted it?
Labeled diagram or annotated photo
Every mechanism change needs a drawing or photo with labels
Test result with n= and benchmark comparison
Example: “Intake: 0.71s avg (n=10). Target 0.8s. PASS.”
Next step — one specific action
Creates the chain between entries that judges look for
📝
🏆
📅
🚫
🏁
🔬
📊
⚔️ Elimination Match Strategy
Elimination strategy is completely different from qualification strategy. You are no longer playing for ranking points — you are playing to win a single match. Change your approach accordingly.
① How Eliminations Differ
  • › Single-elimination — one loss ends your run
  • › You choose your alliance partner — choose wisely
  • › Reliable beats flashy every time here
  • › Defense becomes a valid primary strategy
  • › Your opponent has also been scouting you
② First Pick Logic
  • › Pick the team with the highest floor, not ceiling
  • › Consistent 10-pt auton > unreliable 18-pt auton
  • › Pick a robot that complements yours — not a clone
  • › Can they agree and execute alliance strategy?
  • › Avoid teams with mechanical reliability issues
③ In-Match Adjustments
  • › After Match 1: what did you learn about their strategy?
  • › If losing by <8 pts — switch to aggressive scoring
  • › If winning — switch to defense and hold the lead
  • › Communicate changes to driver between matches
  • › Adjust autonomous based on what you saw them do
← ALL GUIDES
Not your role?
🏎 Driver Control, drills, and match execution. 🧰 Engineer Build, program, and keep it running.
🤝 Alliance & Driver Coordination
🤝
Alliance Coordination
Calls field split, communication signals
👁
Match Reading
Score logic for the match call brief
🏆
High-Stakes Driving
How to brief driver before eliminations
Offensive Driving
Understand what your driver needs from game analysis
📍
Field Positioning
Understand zone priorities when calling strategy
Endgame Execution
Know the commit threshold when calling park timing
🔧
Recovery Driving
Recognize when your driver needs the recovery protocol
📋 General Competition Resources
🚀 Season Kickoff, Budget & AI Tools
Cross-role guides every strategist needs — game reveal planning, budget documentation, and AI assistants for review sessions.
🚀
3-Day Design Sprint
Lead the 72h kickoff — all roles
💰
Budget Hub
Live tracker, championship cost estimator
💰
Team Budget Planning
Season costs, budget calculator
💰
Sponsor Outreach
Tiered packages, email templates
📝
Budget Notebook Entries
Rubric-mapped templates for judges
🎤
Budget Interview Prep
Judge Q&As, Expert-level answers
📋
BOM → Notebook Cost Table
Parts list from CAD to notebook
Cost as a Design Constraint
Decision matrix with cost criterion
🤖
EZ Template Assistant
Review auton code with your programmer
🔄
Onshape Assistant
CAD review questions for design meetings