⚡ Push Back 2025–26 · Game Analysis

Understand the Game.
Win the Match.

Most teams memorize the rules. Top teams analyze them — finding the highest-value actions, reading the meta, and making strategic decisions faster than anyone else on the field.

1
Scoring
2
Efficiency
3
Match Score
4
Meta
5
Tournament
6
Decisions
// Section 01
The Complete Scoring Breakdown
Before you can build a strategy, you need to know every way to score, every point value, and the maximum achievable score. Most teams only know half of this.

Every Way to Score Points

ActionPointsMax AvailableNotes
Score a Block in any Goal Core 3 88 blocks × 3 = 264 Block must contact Goal interior, not touch Floor, not touch same-color Robot
Control a Long Goal zone Critical ? Verify in SC3 Majority of blocks in control zone are your color. Long Goal = 48.8”, center section 13.33” enclosed
Control a Center Goal zone Critical ? Verify in SC3 Center Goal = 22.6” long, holds up to 7 Scored Blocks
Autonomous Bonus Critical 10 10 pts per match Awarded to alliance with more points at end of auton. Tie — both get 5 pts. Violation — awarded to opponent.
Park one Robot End-game ? Verify in SC4 Robot at least partially within Alliance Park Zone, not touching Floor outside zone
Autonomous Win Point (AWP) Win Point +1 WP 1 WP per match Standard: 7+ scored blocks of your color, 3+ goals each with 1+ your block, 3+ blocks removed from your loaders, neither robot touching park zone barrier
📚
Always verify control zone and parking point values in the current Game Manual. The Game Manual is updated throughout the season. The exact point values for Control and Parking are defined in rules SC3 and SC4. Download the latest version from vexrobotics.com/push-back-manual before every competition.

Field Layout — Know Your Zones

PUSH BACK 2025–26 — FIELD OVERVIEW (not to scale)

📦
Loader
LONG GOAL
15 blocks max
📦
Loader
PARK ZONE
Red alliance
CENTER GOAL
7 blocks max
CENTER GOAL
7 blocks max
PARK ZONE
Blue alliance
📦
Loader
LONG GOAL
15 blocks max
📦
Loader
■ Long Goals (×2, 48.8”) ■ Center Goals (×2, 22.6”) ■ Loaders (×4, 6 blocks each) ■ Park Zones (×2)

Block Inventory — Know What’s on the Field

88
Total Blocks
44 red + 44 blue on the field at start
24
Match Loads
12 per alliance, added during driver control via loaders
4
Loaders
6 blocks each at match start. Robots remove, drivers add.
4
Goals
2 Long Goals (15 blocks max each), 2 Center Goals (7 max each)
💡
Key rule — Goalkeeping: A robot cannot block a goal without actively scoring. Rule <SG10>. This means passive blocking strategies are penalized — your robot must always be either moving blocks in, out, or actively positioned elsewhere.

AWP Conditions — Standard vs Worlds-Qualifying

✅ Standard Events
  • › 7+ blocks of your color scored
  • › 3+ goals each with ≥1 of your blocks
  • › 3+ blocks removed from your loaders
  • › Neither robot touching park zone barrier
⭐ Worlds-Qualifying Events
  • › 10+ blocks of your color scored
  • › 2+ blocks per goal (all 4 goals)
  • › Same loader and park zone conditions
  • › Higher bar — prioritize block volume
⚙ STEM HighlightMathematics: Game Theory & Constraint Analysis
Reading a game manual is a constraint analysis problem — the same skill engineers use when given design specifications. The scoring rules are constraints that define the solution space. A strategist’s job is to find the maximum achievable score within those constraints, then determine which path to that maximum is most reliably achievable. This is exactly what operations research professionals do when optimizing logistics networks.
🎤 Interview line: “We start every season by doing a full constraint analysis of the game manual — extracting every scoring method, calculating the maximum possible score, and ranking actions by point value and achievability. It’s the same approach engineers use when analyzing a new design specification.”
Your alliance scores 12 blocks total in the autonomous period, but your opponent scores 8. Both alliances earn their AWP. What does your alliance receive at the end of autonomous?
10 points for winning autonomous + 1 Win Point for AWP
10 point Autonomous Bonus (you outscored them) + 1 Win Point from AWP. Your opponent also gets their AWP Win Point independently.
10 points only — the AWP cancels out when both alliances earn it
5 points — you have to split the bonus because both earned AWP
1 / 6
// Section 02
Points-Per-Second Analysis
Knowing point values isn’t enough. The real question is: which action produces the most points per second of time spent? That ranking is your strategic priority list. Build your robot and practice your driver around #1 first.
⚡
The formula: Efficiency = (Points × Reliability) ÷ Cycle Time in seconds. A 3-point block scored in 4s at 90% reliability = (3 × 0.9) ÷ 4 = 0.68 pts/sec. The autonomous bonus scored in 15s at 80% reliability = (10 × 0.8) ÷ 15 = 0.53 pts/sec. Use this calculator to rank your team’s actual actions.

Points-Per-Second Calculator

Add up to 5 scoring actions. Enter the point value, your team’s estimated cycle time in seconds, and your reliability (how often it works, 0–100%). Hit Rank to see your priority list.

Push Back — Pre-Calculated Benchmarks

These are starting estimates based on game rules and typical competitive performance. Your actual numbers will differ — use the calculator above with your real data.

ActionPtsEst. CycleEst. ReliabilityPts/SecPriority
Score block in goal (driver) 3 5–8s 85–95% 0.38–0.57 Primary
Win autonomous bonus 10 15s (fixed) 70–90% 0.47–0.60 Primary
Control zone (Long Goal) varies Included in scoring Depends on block count — Multiplier
Park robot varies 3–8s at end 80–95% — End-game
Remove blocks from loader 0 direct 2–4s 90%+ — AWP only
💡
The counter-intuitive insight: Scoring blocks is your primary action in Push Back, but control zones multiply the value of what you’ve already scored. A team that scores 9 blocks all in one zone might outscore a team that scored 12 blocks spread across zones — depending on the control zone bonus. Always score with zone control in mind, not just raw block count.
⚙ STEM HighlightMathematics: Expected Value & Optimization
Points-per-second analysis is an application of expected value optimization — the same framework used in economics, operations research, and game theory. Expected value = probability × payoff. By dividing by time, we convert it to a rate (points per second), which allows us to compare actions that have different time costs. This is how professional sports analytics teams evaluate player actions and how manufacturing engineers optimize production lines.
🎤 Interview line: “We rank our robot’s actions by expected points per second — that’s points times reliability divided by cycle time. This tells us which action produces the most value for the time invested, so we can prioritize what to practice and what to build for.”
Action A: scores 3 points, takes 4 seconds, works 90% of the time. Action B: scores 6 points, takes 10 seconds, works 80% of the time. Which action should be your driver’s primary focus?
Action A — it scores 0.675 pts/sec vs Action B’s 0.48 pts/sec. Lower point value but faster cycle makes it more efficient over a full match.
Action B — it scores more points per attempt so it will always produce more total points
They’re equal — you should alternate between them depending on the situation
Action B — higher point value means it’s worth the extra time
2 / 6
// Section 03
Match Score Estimator
Before every match, a top strategist knows the expected score range for both alliances. This tool lets you build a realistic projection based on what you know about your team and your opponent.

Build Your Match Score Projection

■ Your Alliance
■ Opponent Alliance
—
YOUR ALLIANCE
vs
—
OPPONENT
Fill in the estimates above

What Real Match Scores Look Like

This gives you a baseline for what’s realistic at different skill levels. Use these to calibrate your estimates.

Team LevelTypical ScoreKey DriverWhat Wins Matches
Beginner 15–35 pts Auton bonus often decides it Having any reliable autonomous wins half your matches at this level
Intermediate 40–80 pts Block volume + auton Cycle time and consistency — 15+ blocks per match
Advanced 80–130 pts Zone control + auton Control zone strategy becomes decisive — not just raw blocks
Top Teams 130+ pts All systems maximized AWP every match, zone control, match loads fully utilized, parking every match
⚠️
The 10-point swing rule: The autonomous bonus is worth 10 points — roughly 3 scored blocks plus change. In a close match, that bonus is often the entire margin of victory. A team that consistently wins autonomous has a structural advantage that cannot be overcome by driver skill alone in tight matches.
You’re projected to win 74–62 with 30 seconds left. Your robot starts having mechanical trouble. Which is the better decision?
Stop pushing for more blocks and immediately try to park — the 12-point lead needs to be protected, not grown. A mechanical failure mid-cycle could cost you more points than you gain.
Keep scoring blocks — a bigger lead is always safer and the robot might be fine
Ask your engineer to fix it during the match from the alliance station
Pivot to defense against their robot to prevent them from scoring more
3 / 6
// Section 04
Meta-Game Analysis
The “meta” is the dominant strategy at any given point in the season — what the best teams are doing and why. Understanding the meta tells you whether to follow it, adapt it, or beat it by being ahead of it.
📊
What is the meta? The meta is the set of strategies that produce the best results given the current skill level of the competitive field. It evolves as the season progresses. A strategy that wins early-season regionals may be countered by the time State comes around.

How the Meta Evolves in Push Back

E
Early Season — Figure Out the Field
Teams are still learning the game. Matches are won by whoever has a functional robot and any auton at all. Block volume is low (8–14 per match). Zone control is ignored by most. Winning move: have a working auton and reliable drive.
M
Mid Season — Volume Matters
Block volume rises (15–25 per match). AWP becomes contested. Cycle time and auton reliability separate teams. Winning move: maximize block throughput and hit AWP consistently.
L
Late Season / Regionals — Zone Control Decides
Top teams plateau on block volume. Zone control and match loads become decisive. Match scores are closer. Defense is now viable. Winning move: precision zone strategy, full match load utilization, and adaptive play.

Pioneer vs Follow the Meta

🚀 Pioneer Early
If your team finds a strategy others haven’t tried yet, you may win early events before opponents adapt. Risk: it might be pioneer for a reason — it might just be worse. Reward: early wins and ranking points before the meta catches up.
📊 Follow and Refine
Watch what top-ranked teams are doing and do it better. Lower risk, faster path to competitiveness. Risk: everyone is doing the same thing and execution becomes everything. Reward: proven strategy, known ceiling.

Four Strategic Priorities Every Match

①
Win Autonomous
The 10-point swing is structural — it can’t be recovered without outscoring the opponent by 11+ blocks. Win auton first. Run AWP second. Never skip auton practice to add one more block to driver control.
②
Maximize Block Volume
More blocks in goals = more points and more opportunities for zone control. Score continuously during driver control. Utilize match loads — 12 extra blocks per alliance that most beginner teams completely ignore.
③
Control Zones Strategically
Score blocks to control zones, not just to fill goals. A block that gives you majority control of a zone is worth more than a block that adds to a zone you already control. Think about zone control with every cycle.
④
Secure End-Game
Parking at the end of the match costs very little time (3–8 seconds) but adds guaranteed points if the game rules reward it. Decide before the match whether you’re parking. At 0:30 is too late to make that call for the first time.
You’re at your first tournament of the season. You watch 4 matches and notice all the high-scoring teams are focused on one specific zone every match. What’s the most important thing to do with this observation?
Immediately copy their exact strategy for your next match without further analysis
Record what you observe, identify why that zone appears more valuable than others, then decide if your robot can exploit the same zone or whether you should contest a different one to avoid direct competition
Ignore it — every match is different and zone strategy doesn’t generalize
Pivot to defense against teams using that zone to neutralize their advantage
4 / 6
// Section 05
In-Tournament Game Reading
Scouting teams is one thing. Reading the game as it’s being played around you is another skill entirely. This is what separates strategists who can adapt from ones who can only execute a pre-planned script.
👀
The rule: Every match you’re not playing is a data collection opportunity. If you’re watching for entertainment, you’re wasting it. Your phone is your notebook. Tap the checklist below every match you watch.

In-Match Observation Checklist

Tap each item as you confirm it for any match you watch. Tracks per match. Reset between matches.

Patterns That Should Change Your Pre-Match Plan

What You ObserveWhat It MeansAdapt By
Opponent consistently wins autonomous Your auto bonus is at risk every match Run AWP tasks during auton even if you lose the bonus — get the Win Point
Opponents are heavily contesting one goal That goal is high-value — they know something Score in that goal early to contest control, or pivot to a goal they’re ignoring
Opponent robot is slow on one side of the field Mechanical or code limitation Start on that side — score fast before they arrive
Opponent is not utilizing match loads They have 12 blocks sitting unused each match Utilize your match loads fully — that’s a 12-block (36 pt potential) advantage
Opponent has fast auton that consistently fails at 0:15 Reliability problem — high ceiling, low floor Target the same zones their auton is trying to reach — when it fails, you get them for free
Matches are being decided by 5–10 points This is a high-margin-sensitivity tournament Every decision needs justification — parking, AWP, zone control all matter more
⚙ STEM HighlightScience: Observation, Inference & Hypothesis Testing
In-tournament game reading is applied scientific observation. You observe (opponent always contests the left goal), infer (that goal may have a control zone bonus advantage), form a hypothesis (scoring there first will yield more total points than the right goal), then test it in your next match. This is the scientific method running in real-time. Every match is an experiment and every data point updates your model of the competition.
🎤 Interview line: “During tournaments, our strategist watches every match as a structured observation session — recording auton results, zone control patterns, and cycle times. We use that data to update our strategy between matches, the same way scientists update their model when new data comes in.”
You watch three matches and notice the team you’re about to face never uses their match loads. What’s the strategic implication?
No implication — match loads are optional and their strategy might be working fine without them
They’re leaving up to 12 blocks (36 points) unused per match. If you maximize your match loads, you have a structural scoring advantage they cannot overcome through driver skill alone.
You should also avoid match loads to keep things even
It means their robot is probably faster at scoring pre-loaded blocks so they don’t need them
5 / 6
// Section 06
Strategic Decision Framework
Use this before every match. Work through each question in order. At the end you have a clear strategic priority for this specific match against this specific opponent.
⏱
When to use this: Fill this out during queue — the 2–3 minutes before you walk to the field. The answers to each question should already be in your head from scouting. This just structures the thinking.

Pre-Match Decision Tree

Q1 Did we earn AWP last match?
Check your consistency. If yes, it’s part of your standard run. If no, why not? Can you fix it in the next match?
↳ YES — keep the same auton routine
↳ NO — identify the missing condition before you queue
Q2 Is our opponent’s autonomous reliable?
Did it work in the matches you watched? If they have a better auton than you, the 10-point bonus is likely theirs. You need to outperform in driver control by 11+ blocks.
YES Their auton is reliable
Accept losing the 10-pt bonus. Focus driver control on maximizing blocks and zone control to overcome it. Target: outscore by 12+ points in driver control.
NO Their auton is inconsistent
Run a reliable auton and win the bonus. Even a simple routine that works 9/10 beats a complex routine that works 5/10. Bank the 10 points.
Q3 Which goal is most valuable right now?
Based on your scouting — which goal does your opponent target? Do you contest it or take a different one? You can’t control all four goals with two robots.
Contest Go for the same goal
Use this when: you’re faster, you have a match load advantage, or the zone bonus there is clearly higher than other goals. Start early and establish position.
Avoid Take a different goal
Use this when: they’re clearly faster at that goal, or a different goal has a zone bonus that’s almost as good with less competition. Two robots scoring different goals beats two robots fighting over one.
Q4 What’s the end-game plan?
Decide now, not at 0:30. Are you parking? When do you stop scoring to go to the park zone? What’s the score threshold where parking vs scoring one more cycle is the right call?
Rule If winning by more than parking points: park
A secure lead means the guaranteed parking points matter more than a risky extra cycle. Protect the lead.
Rule If score is within 1–2 blocks: keep scoring
Parking won’t close the gap. Stay in your scoring cycle until 0:10, then make a call based on exact scores.
Q5 Are we using all 12 match loads?
This is often the most overlooked question. Match loads are 12 free blocks your alliance gets. If you’re not planning to use them, why not? If your driver hasn’t practiced picking up from loaders, that’s a practice priority this week.
YES Using match loads
Coordinate with your alliance partner on which loaders each robot takes. Divide them so neither robot wastes time at the wrong loader.
NO Not using match loads
You are leaving a scoring opportunity on the table. Minimum viable plan: your drive team member adds match loads to your nearest loader as fast as possible during driver control. Even if the robot picks up 4–5 of them, that’s 12–15 free points.

The Match Call (One Sentence)

After working through the decision tree, summarize the entire strategy in one sentence. This is what your driver hears right before they queue.

🔅 Craft your match call
This is the last thing your squad hears before they walk to the field. Say it out loud.

Related Guides

🏆
Autonomous Strategy
Scoring tiers, reliability, alliance coord
 ⭐
AWP & Skills Strategy
AWP conditions, skills run tracker
 📊
Match Scouting Sheet
Track teams, build your alliance list
 🌎
Route Planning
Path design, paper planning, PATH.JERRYIO
 🔬
Testing System
Data tracking, iteration, failure protocol
 🔅
Strategist Role Page
EV calculator, match planner, elim strategy
6 / 6
← ALL GUIDES