The Strategist Toolkit

📦 The Strategist Toolkit

Strong strategists use a small set of tools — each for a different job — and combine them before, during, and after every event. The goal is not to use all of them at once. The goal is to know which one to open first.

🚦 Start Here: Which Tool Should I Open First?

The answer depends on what you're trying to do. Use this block to find your starting point fast.

🔧 Best Tool for Each Job

📋 Official Tools — The Source of Truth

📊 Analysis Tools — The Intelligence Layer

📱 Mobile Companion Tools — At the Event

🔬 VRC Data Analysis vs Robot Stats — Which to Use?

📋 RobotEvents vs VEX via — What's the Difference?

🗺 Shadow / Rookie / Veteran Tracks

Not every student needs every tool. Start simple, add complexity as experience grows.

📅 Pre-Event Workflow

The Week Before

The Night Before — 20-Minute Strategist Routine

🏁 Qualification Match Workflow

Quals are your scouting window. Use data to know what to expect. Use your eyes to verify what the data said.

Before Each Match

After Each Match

🤝 Alliance Selection Workflow

By the time alliance selection opens, you should have three data sources in hand: your pre-event brief (from VRC DA + Robot Stats), your match notes (from VRC RoboScout), and what your team observed in the pits. The board opens quickly — be ready before it does.

📖 Rules + Scoring Support Workflow

⚠️ Common Mistakes

• ✗Opening VRC Data Analysis before getting the event ID. Looking up random teams wastes time on people who aren't at your event. Event ID first, always.
• ✗Using RobotEvents for team strength analysis. It shows registration and results, not TrueSkill. It won't tell you who's strong — that's VRC Data Analysis's job.
• ✗Treating V5RC Hub as the official rules source. It's a community reference tool. Always verify critical rule interpretations against the official Game Manual.
• ✗Ignoring σ on VRC Data Analysis. A team with μ = 30 and σ = 5 from one event is less trustworthy than a team with μ = 26 and σ = 0.8 from eight events. Always check σ alongside the rating.
• ✗Not writing match notes at the event. Pre-event data without live verification is just a guess. VRC RoboScout exists so your observations update your picture in real time.
• ✗Using every tool at once. Switching between 7 tools simultaneously during quals creates noise, not clarity. Know which tool to open for which task before the event starts.
• ✗Letting one number make the pick. "Their TrueSkill is highest" is not a pick justification. Rating + σ + live observation + complementary strengths = a real pick justification.
• ✗Not using VEX via to study the meta. The game evolves every few weeks. Watching two or three recent matches on VEX via each week costs 20 minutes and teaches you more about the current meta than most practice sessions.

👨‍🏫 Coach & Mentor Teaching Notes

How to Introduce Each Level to the Toolkit

📋 Assign From the Event Page — Structured Scouting

Open the event page the night before. Divide the team list explicitly. Everyone scouts from the same starting point — no random lookups.

📋 Night-Before Assignment Template

Fill this out the night before. Print it or share it with your team before you leave for the event.

Turning Data into a Match Plan

📝 Engineering Notebook & Interview Connection

Using a structured research toolkit is a documentable, judge-facing process. It shows organized decision-making, external evidence, and an iterative improvement loop — exactly what the RECF rubric rewards.

What to Document

• ✓Pre-event research process: Write which tools you used, in what order, and what you found. Include the RobotEvents event ID, the date, and the top 5–6 teams from the event page with their TrueSkill ratings. This is traceable, repeatable research.
• ✓Watchlist creation: Document how you narrowed the full event list to your scouting focus. How were teams assigned? What criteria did you use? This demonstrates systematic prioritization.
• ✓Data vs. observation comparison: After each event, write a brief entry comparing what TrueSkill predicted vs what you actually saw. Where did the tools help? Where did they miss? This is evidence of analytical thinking.
• ✓Alliance selection reasoning: Document who you picked, which tools informed it, and why. Three-part justification: TrueSkill evidence + live observation + complementary strength. Two data sources beats one.
• ✓Toolkit improvement: Did you add a new tool this season? Did you change how you use one? Document the change and why. Iterating your process is part of the design process.