Day 0: Baseline and Benchmarks

Day 0: Baseline

Before picking a focus, you need an honest read on where you actually are. This section is a manual data-collection step, done once, before Block 1 begins.

• Open your in-client match history and find your last 10 completed games (ranked if you have them, normal if not -- consistency of game mode matters less than having 10 real games).
• For each game, open the post-game stats screen and read off: the game number/date, your CS at the 10-minute mark (use the in-game timeline/graphs tab if your client has one; otherwise estimate from your final CS and average CS/min), your final CS/min, your total deaths, your vision score, and the result (win/loss).
• Enter all 10 rows into the Baseline sheet in the Tracker Workbook. Do not skip a bad game -- a badly-performing game is data, not something to leave out.
• Let the sheet compute your 10-game averages. Do not average them by hand; the workbook does this so you cannot accidentally round in your own favor.

This step takes about twenty minutes the first time, using nothing but your own client and the included spreadsheet. There is no automated shortcut in this package on purpose -- reading your own games manually is the first rep of the self-review habit Section A8 builds on later, and it means this program depends on no external tool, account, or API staying available.

If you are brand new and do not have 10 completed games yet, play 10 normal games as close to how you'd play ranked as possible, then use those as your baseline. The number matters less than having an honest starting point to measure change against.

Resist the urge to "clean up" the numbers by excluding a game where you got outplayed badly, or one where a teammate went AFK. Ten real games, including the ugly ones, is what makes the baseline honest. A baseline built only from your best games will make every future block look like regression, which is discouraging and wrong.

Read Your Baseline

With your 10-game averages computed, compare your CS/min against the Benchmarks table below for your current rank. This is the only comparison in this program that uses a number you did not personally measure over time -- everything after this point compares you against your own baseline, not against a community table.

Community coaching-figures, not Riot-published data: boostingmarket.com, leagueoflegendstools.com, wecoach.gg CS/min-by-rank tables, cross-checked against the 90-CS-by-10:00 and stricter 107-CS-by-10:00 practice-tool targets. Treat every number here as a calibration target, not a guarantee.

Junglers run roughly one CS/min lower than the lane figures below because jungle-clear pathing and ganking time trade directly against farm. Subtract 1 from both ends of your rank's band before comparing your own jungle CS/min.

If your CS/min sits below your rank's band, farming consistency (the Farming Consistency focus card) is a strong first pick -- it is the single most common gap and it compounds into gold for every other decision you make. If your CS/min is inside or above your band, look instead at your deaths-per-game and vision score against your own sense of what a clean game looks like for you, and consider Death Cause Control or Vision Cadence instead.

The rule for picking your first focus: choose the ONE measurable thing that is furthest from where it should be, not the one that feels most embarrassing or the one your teammates complain about most. A quiet weakness that is dragging every game down is worth more to fix first than a loud one that only shows up occasionally.

Pick exactly one focus for Block 1. If two things look equally broken, pick the one that is easiest to measure cleanly -- an ambiguous focus produces an ambiguous review, and an ambiguous review is where this whole method quietly falls apart.