● Not sure what to do?
1. Complete Today’s Focus  •  2. Log a notebook entry  •  3. Ask your squad: “What did we learn and what changed?”
★ Spartan Design Program

Spartan Design
Team Hub

Train · Build · Compete · Improve
📝 Kickoff Week — Before You Build
Game reveal happened. Before anyone cuts metal: analyze the game, open the notebook, define the problem, brainstorm mechanisms, run a decision matrix.
⚡ Game Analysis 🗺 Notebook Pathway 📝 Start Notebook
Who are you on this team?
🏎 Role 01 — Driver Driver You perform under pressure. Score points every match. Know your robot, know the field, and execute when it counts.
Drills Match Timer Session Log Self Score
Go to Driver →
⚙️ Role 02 — Engineer Engineer You build reliable systems. Keep the robot competition-ready — before, during, and after every match.
Build Log Auton Tracker CAD / Onshape Troubleshoot
Go to Engineer →
📊 Role 03 — Strategist Strategist You make winning decisions. Know the game, know the opponents, and plan the match before the robot turns on.
Match Plan Scouting EV Calculator Notebook
Go to Strategist →
Next Competition
Set your event date below
—
Days
—
Hrs
—
Min
Today’s Focus
● Today’s Practice Tasks 0 / 4 done
Practice Week
✅ Everything done! What’s next?
  • Improve something
  • Run another test cycle
  • Help another squad
✎  Coach: edit the tasks list in spartan.html — search for WEEKLY_TASKS to update each week.
☰ Today’s Work
Daily Workflow
01
⚡
Analyze
Game analysis. Scoring efficiency. Strategic constraints.
02
📝
Document
Open the notebook. Define the problem before choosing a solution.
03
🔄
Design
Brainstorm 3+ concepts. Run a decision matrix. CAD before cutting.
04
🔧
Build
Assemble, test, iterate. Log every change in the notebook.
💬 Squad Communication When to talk to each other
Most squad problems are communication failures, not skill failures.
⚙ Engineer → Driver
  • › “Code uploaded — test the auton.”
  • › “Robot ready — give me drive time.”
  • › “Intake changed — does it feel different?”
🏎 Driver → Engineer
  • › “Robot is pulling left — check the drive.”
  • › “Intake feels slow — can we tune it?”
  • › “Something sounds wrong when I turn.”
📊 Strategist → Squad
  • › “We need the auton reliable for next match.”
  • › “Match is in 3 — do a quick pre-check.”
  • › “We need a notebook entry before leaving.”
🔧 Build & Design Support
⚙️ Mechanisms
🎰 Intake Design Rollers • Compression • Anti-Jam ⬆️ Lift Systems Arm • Four-Bar • DR4B 🎯 Flywheel Shooter Velocity • Compression • Accuracy 🚀 Launchers Catapult • Slingshot • Puncher 🔁 PTOs Motor Sharing • Shifting • Hang
🔄 Onshape in Spartan Design How we use CAD
How We Design

Spartan Design uses Onshape as our main design tool. Every robot starts as a digital model before we cut metal. Designing first means the robot goes together right and the whole team can see the plan.

🚗
Design
Full robot layouts in 3D
🗣
Communicate
Shared live with squad
🎓
Train Rookies
See systems before touching hardware
🔧
Build Accurately
Right shaft lengths, verified clearances
For parents: Onshape is free, browser-based CAD used by engineers in industry. Students access via dusd.onshape.com.
Start CAD →
Quick Access
🔧
Build Resources
Drivetrain • Mechanisms • Hardware
→ 💻
Programming
PROS • EZ Template • Auton
→ 🏆
Competition Tools
Strategy • Scouting • Match Prep
→ ⚡
Game Analysis
Scoring • Efficiency • Decisions
→ 🔬
Testing System
Protocols • Data • Iteration
→ 📝
Engineering Notebook
Design process • Judging
→ 🔄
CAD / Onshape
Setup • Drivetrain • Mechanism
→ 🔧
Tools Guide
Hand • Power • Safety
→ 🎯
Pit Crew System
Roles • Workflow • Repairs
→
🏆 Competition Day
🏆 Tournament Day Logistics Schedule, protocols, common mistakes
Competition Day
Most competition failures are logistics failures, not robot failures.
⏰ Schedule
  • › Check Robot Events the night before
  • › Queue = 2 matches before yours. Be in pit at −3
  • › Strategist watches the schedule
⚙ Between Matches
  • › Return robot to pit immediately
  • › Drive check + screw check + battery swap
  • › Strategist logs result + scouts next opponent
🚫 Competition Don’ts
  • › No major code changes day-of — test first
  • › No mechanism rebuilds between qual matches
  • › Never miss your queue window
📊 Practice vs Maintain
  • › Robot reliable → Driver practices
  • › Robot has issues → Engineer fixes
  • › Skills: only if robot is competition-ready
🔨 Pit Crew System Roles, between-match flow, emergency rules
Pit Operations
You have 3–5 minutes between matches. How you use that window is a skill — not luck.
👥 Pit Roles
  • Engineer — fixes the robot
  • Driver — prepares for next match
  • Strategist — reviews last match, plans next
Only the Engineer touches the robot.
🔄 Between-Match Flow
  1. Robot returns to pit
  2. Quick damage check — 30 seconds
  3. Battery swap
  4. Quick fix only if something is broken
  5. Strategist updates plan
🚨 Emergency Fix Rule
Fix only what affects performance right now.
Working → practice
Inconsistent → test first
Broken → fix it
❌ Common Mistakes
  • × Everyone on the robot at once
  • × Panic changes between matches
  • × No clear roles — mixed signals
  • × Major changes during eliminations
Browse All 56 Guides Setup • Programming • Hardware • Competition • Notebook
Full Library →
📝 End of Session
End of Session
📝 Squad Reflection Takes 3 minutes. Do it before you leave.
← ALL GUIDES SPARTAN DESIGN // VRC RESOURCES