How to Run a Structured Scrim in League of Legends
Most teams scrim. Very few actually improve from scrims.
Because running a scrim is not just "playing games." It's a structured process designed to test specific scenarios, isolate mistakes, and build consistent decision-making.
Without structure, scrims turn into low-quality SoloQ with random drafts and unfocused reviews. This guide breaks down how to run scrims like a competitive team.
What a scrim is (and what it isn't)
A scrim is not a ranked game. It's not a place to "try hard for wins" or a test of mechanics only.
A scrim is a controlled environment to improve team play.
The goal is not to win the game. The goal is to learn something specific every block.
Step 1: Define a clear objective
Before loading into champ select, define what you're testing. This could be early game jungle pathing, bot lane wave control, mid-game lane assignments, or a specific comp execution.
Bad objective:
"Let's play clean"
Good objective:
"Play for bot prio and stack first 2 drakes"
No objective means no useful review.
Step 2: Structure your scrim block
A scrim should be organized in blocks of 3 to 5 games, ideally against the same opponent under consistent conditions.
Within a block, keep variables controlled. Use a similar draft style, follow the same early game plan, and maintain the same focus objective. You are not testing everything at once. You are isolating variables.
Step 3: Draft with intent
Draft is part of the training. A common mistake is picking random comps every game with no link to the objective.
Instead, define the draft purpose. Are you testing scaling vs early? Engage vs poke? A specific matchup?
For example: "We draft early bot prio + jungle invade setup."
Then evaluate whether the draft enabled the plan and whether players executed it correctly. Draft is a hypothesis. The scrim is the test.
Step 4: Set in-game rules
To keep scrims productive, define constraints. No coinflip fights before objective setup. Respect wave states before rotating. Commit to the planned win condition.
These rules reduce noise, force discipline, and make reviews clearer. Without them, scrims become chaotic.
Step 5: Focus on key timings
Don't try to analyze the whole game live. Focus on specific windows.
0 to 5 min for early setup. 5 to 10 min for lane priority and jungle interaction. 10 to 15 min for first rotations and objective control. Mid-game for lane assignments and tempo.
Most scrim value comes from early and mid-game decisions.
Step 6: Run fast, structured reviews
The biggest mistake in scrims is reviews that are too long and unfocused.
After each game, spend 5 to 10 minutes. Focus only on whether you followed the plan and where execution broke. Avoid blaming mechanics or discussing every fight.
After the block, go deeper. Look at recurring patterns, macro mistakes, and communication issues. Review patterns, not isolated plays.
Step 7: Track the right data
Scrims without tracking means lost information.
Follow key metrics like CS/min per role, gold diff at 15, objective control on drakes and herald, and death timing before objectives. But numbers alone are not enough. You need the context behind them: wave states, decisions before fights, and rotations that led to those numbers.
Step 8: Assign clear responsibilities
Each role should have defined focus points during scrims. Top lane focuses on wave control and TP usage. Jungle focuses on pathing and objective setup. Mid focuses on tempo and side wave control. ADC focuses on lane execution and positioning. Support focuses on vision and engage timing.
When everyone reviews everything, no one improves.
Step 9: Avoid common scrim mistakes
Playing for the win only. Winning bad scrims teaches nothing.
Changing too many variables. New comp plus new strategy plus new roles equals no signal.
Over-reviewing. Too much feedback means no retention.
Ignoring early game. Most games are decided before 15 minutes.
No follow-up. If the same mistake repeats, your process is broken, not your players.
Step 10: Turn scrims into progress
A good scrim block should answer three questions. Did we execute the plan? What failed consistently? What do we fix next block?
Each block should produce one to two clear adjustments. Not 10 random takeaways.
Why most teams don't improve from scrims
Because they don't define objectives, don't control variables, don't review efficiently, and don't track patterns. The result is high volume with low learning.
Structured scrims vs SoloQ practice
SoloQ is chaotic, individual-focused, and inconsistent. Scrims are controlled, team-focused, and repeatable. Improvement at the team level only happens through structured scrims.
From scrim to real insight
Running structured scrims gives you better games. But improvement comes from identifying patterns, linking decisions to outcomes, and tracking progress over time. Manual review makes this slow.
Tools like VictoryView allow you to track key timings automatically, link stats to decisions, and identify recurring macro issues.
Instead of "we played better this block," you get clarity on where execution failed, why it failed, and how to fix it next session.
That's how scrims turn into actual progress.