How to Track SoloQ Performance Across Your Competitive LoL Roster

If you coach a competitive League of Legends team, you already know the drill: open five browser tabs, check each player's op.gg, try to remember what their CS/min was last week, and hope you catch a slump before it costs you a series.

It doesn't have to be this way.

Why SoloQ data matters for competitive teams

SoloQ isn't scrims. The matchmaking is different, the communication is nonexistent, and the draft is chaos. But SoloQ is where your players spend most of their hours — and the data it produces tells you things scrims can't.

• Mechanical consistency — CS/min and damage/min in SoloQ reflect raw laning ability without the safety net of coordinated play.
• Volume and commitment — A player grinding 4+ games per day is staying sharp. A player who hasn't queued in five days might not be.
• Champion pool trends — SoloQ is where players experiment. Track what they're playing and you'll know what they're comfortable bringing to scrims.

The point isn't to judge players by their SoloQ rank. It's to spot patterns you'd otherwise miss.

The metrics that actually matter

Not every stat on a post-game screen is worth tracking at the team level. Here's what experienced coaches focus on:

CS/min

The single most reliable indicator of laning fundamentals. A mid laner averaging 8.2 CS/min who drops to 7.1 over a two-week window is telling you something — even if their win rate hasn't changed yet.

KDA ratio

Useful in context. A support player with a 2.1 KDA isn't necessarily worse than one with a 4.8 — it depends on champion pool, playstyle, and team composition. Track the trend, not the absolute number.

Damage per minute

This one separates players who are actively impacting fights from players who are playing safe and padding KDA. Pair it with gold/min to get a damage efficiency ratio — how much damage is each gold producing?

Win rate over time

Not the all-time number. The 7-day or 14-day rolling window is what matters. A player on a 38% win rate over the last two weeks needs a conversation, not a benching.

Vision score

Especially for supports and junglers. Vision score doesn't lie — it tells you whether a player is actively contributing to map control or just laning and fighting.

How to structure your review cadence

Checking stats once before a scrim block isn't enough. Here's a simple cadence that works for most coaching staffs:

1. Daily glance — 2 minutes. Open the dashboard, check games played. Flag anyone with zero games or a sudden win rate drop.
2. Pre-scrim review — 10 minutes. Filter by the last 3 days. Look at CS/min and damage/min trends. Note anything you want to address in the session.
3. Weekly deep dive — 30 minutes. Compare week-over-week across the full roster. Identify who's improving, who's plateauing, and who needs targeted practice.

The key is consistency. Data is only useful if you're looking at it regularly.

Centralizing the data

The biggest time sink isn't analysis — it's data collection. If you're manually checking individual profiles across multiple sites, you're spending coaching time on clerical work.

A centralized dashboard that pulls from the Riot API and aggregates stats by team gives you everything in one view:

• Every player's recent games, filtered by queue type
• Team-wide averages with trend charts
• Per-player stat tables sortable by any metric

This is exactly what VictoryView is built for. Import your roster's matches in one click, enable auto-import if you want it hands-free, and filter by SoloQ, Flex, or Scrim.

What to do with the data

Numbers without action are just numbers. Here's how to turn SoloQ data into coaching decisions:

• CS/min dropping? Schedule a 1v0 or 1v1 laning drill. Review the player's last 5 games to see if they're losing CS to roam timings or to mechanical mistakes.
• Damage/min low relative to gold? The player might be building too passively or not committing to fights. Check their item builds and teamfight positioning.
• Win rate tanking? Before assuming tilt, check the context. Are they spamming a new champion? Playing at odd hours? Duo-queuing into harder lobbies?
• Vision score declining? Review their ward placement patterns. A support who stops warding deeply is usually a support who's lost confidence in their team's map response.

The conversation with the player matters more than the stat itself. Use the data to ask better questions, not to hand down verdicts.

Start tracking today

If you're coaching without centralized data, you're coaching blind. The good news: setting up takes about two minutes.

Create a free team on VictoryView, add your players by Riot ID, and import their recent matches. You'll have a full dashboard before your next scrim block.

No credit card. No setup complexity. Just the data your coaching staff needs to do their job.