Start game analysis by identifying criteria and constraints. This is Spartanβs suggested learning sequence, not a mandated GRSF notebook format. Students record their actual analysis and decisions.
The criteria and constraints entry is one of the most important in your notebook. Judges look for it right after the game analysis. It shows that your team understood the design problem before picking a solution.
| Type | Example | Why It Matters to Judges |
|---|---|---|
| Criterion | Robot scores β₯ 4 pins per match | Measurable β judges can verify it against test data |
| Criterion | Autonomous routine succeeds β₯ 80% of attempts | Connects to testing entries later in the notebook |
| Constraint | Robot stays within the 88 W total motor-power limit (VRC rule <R10>) | Rule reference shows you read the manual |
| Constraint | Robot must fit within 18" Γ 18" Γ 18" at start | Hard rule β non-negotiable design boundary |
| Constraint | Build budget limited to $150 in new parts | Team-specific β shows honest planning |
The criteria and constraints entry goes in your first EDP cycle, right after the game analysis. It belongs in the Identify the Problem section (green slides). Write it the week of game reveal β before any mechanism is chosen.