How to review a scrim block with teammates
Scrim review should explain patterns across the block. If you review every game in isolation, you miss the structural mistakes that keep repeating.
Group the session before you judge the players
Look for the same issue across multiple games: weak backboard coverage, late second-man support, or bad boost routes under pressure.
A block review is more useful when it asks 'what do we repeat?' instead of 'who threw this game?'
Separate individual mistakes from system mistakes
Some problems belong to one player. Others belong to the team's spacing rules, rotation expectations, or challenge structure.
If the same awkward situation shows up with different players, it is usually a system issue.
Leave the review with team rules
The output of a scrim review should be a few concrete team rules for the next block.
- Who holds midfield when the first challenge goes in.
- When the last player should stay patient instead of pushing up too early.
- Which boost paths are acceptable when under pressure.
Common questions
What should a Rocket League scrim review focus on?
It should focus on repeated team problems across the block, such as support distance, challenge structure, or weak defensive lanes, rather than one isolated mechanical error.
How many team rules should come out of a scrim review?
A small set. If the review produces too many changes, the team usually remembers none of them in the next block.
A practical replay review structure for ranked sessions: start with goals, identify the real swing plays, then leave with one clear training focus.
The most expensive 2v2 errors are usually spacing, support distance, and poor challenge timing rather than flashy mechanical failures.
Back-post coverage, wide exits, and disciplined support lanes are the foundation of defense that does not collapse after one bad touch.
Want to apply this to your own replays?
Sign in, upload a replay, and use the same review structure on your own matches.