Why Mock at All
A mock draft is a full practice draft under realistic conditions — either against other humans in a lobby or against AI opponents in a simulator like FantasyPros' Draft Wizard, Fantasy Football Calculator, or Draft Sharks' simulator. The point isn't to discover who you'd pick — you already know your rankings. The point is everything rankings can't teach: how the room behaves between your picks. When positional runs start, how far your targets actually fall, what the board looks like at pick 3.08 when you took a tight end at 2.05. Draft night is a timed test with eleven adversaries; mocks are the only place to take it open-book first.
Rule One: Match Your Real League Exactly
A mock under the wrong settings is worse than no mock — it trains instincts calibrated to a league you don't play in. RotoWire's simulator guide is emphatic on this: configure team count, roster slots, and scoring to your actual league before anything else, because player values swing hard between PPR and standard, and a superflex slot roughly doubles quarterback value. Twelve-team boards behave nothing like ten-team boards. This is the same wrong-settings mistake that ruins real drafts, just imported into practice. Every serious simulator supports full customization — use it, and your mock reps compound instead of contradicting each other.
Mocking for fun vs. mocking as preparation
Run Experiments, Not Reps
The managers who get the most from mocks treat each one as a controlled experiment. Pick one variable per mock and test it deliberately. Test builds: force a Zero RB start, then a Hero RB start, then early-TE, and compare the rosters that come out the other side — simulators exist precisely so those experiments are free. Test slots: since most leagues randomize draft order days before the draft, practice from an early, middle, and late position, because the game plays completely differently from each slot. And test patience: let a target slide a round past where you'd normally take him and see if the simulator's ADP-driven opponents call your bluff. That last one quietly teaches ADP-as-price better than any article can — you learn exactly how long the market holds players, and where your league's runs typically ignite.
Simulators vs. Human Lobbies
The two flavors of mock teach different lessons, and it's worth getting reps in both. Simulators are fast — a full twelve-round draft in ten minutes, restartable the moment an experiment answers itself — which makes them the right tool for volume: testing builds, learning tier timing, and rehearsing your slot. Human mock lobbies are slow and occasionally flaky (drafters bail mid-mock, autopick takes over), but they're the only place to practice against actual human irrationality — the manager who takes a kicker in round nine, the homer reach, the panic run that starts two rounds before any simulator would fire it. A sensible split: simulators for your experiments, then one or two human mocks in the final week as a dress rehearsal for the chaos.
A Two-Week Plan That Actually Fits
Advice to "do more mocks" is useless without a number and an order, and the honest number is smaller than most people assume. Six to eight purposeful mocks in the final fortnight will teach you more than thirty aimless ones, because each of yours is answering a question. Spend the first two on builds — one forcing an early-receiver start, one forcing an anchor back — and compare the rosters, not the picks. Spend the next two on your slot, once your real draft order is known, running the same build from that seat twice to see what the board reliably offers you at the wrap.
Then spend two on the middle rounds specifically, which is where drafts are actually won and where almost nobody practices: start the simulator from round five with a roster you have already decided on, and draft only the back half. Finish with one human lobby in the last few days as a dress rehearsal. If you only have time for three mocks total, do one build test, one from your real slot, and one human lobby — in that order.
Keep a Mock Journal
The reps only compound if you write things down, and the useful record is four lines long, not a spreadsheet. After each mock, note the round each positional run ignited, the two or three players who consistently fell past their ADP, the two or three who never made it back to you, and one sentence on whether the roster you finished with could actually win your league. That last line is the one people skip and the only one that grades the mock rather than describing it.
What emerges after five or six entries is a picture the individual drafts cannot give you: the same names keep sliding, and the same names keep vanishing. Those two lists are your real draft plan. The sliders are the players you can wait on, which buys you a round of flexibility everywhere else on the board; the vanishers are the ones you either take a round early or forget about entirely. A ranking tells you who you like. The journal tells you which of them you are actually going to get.
What Mocks Can't Tell You
Two honest caveats. First, simulator opponents draft off ADP with mild randomness; your real leaguemates have homer picks, stale takes, and vendettas, so treat mock results as the baseline and your knowledge of the room as the adjustment layer. Second, mocks go stale. A March mock is a fine strategy lab, but the player pool it trained you on will be repriced twice over by camp battles and preseason injuries — which is why the reps that matter most come in the final two weeks before your draft, on current ADP. Early-offseason mocks teach you the format; August mocks teach you this year's board. You want both, weighted toward the second.
- •Configure every mock to your league's exact size, slots, and scoring — no exceptions
- •One experiment per mock: a build, a slot, or a patience test
- •Mock from early, middle, and turn slots before your real order is revealed
- •Note the round each positional run started; the pattern repeats on draft night
- •Front-load reps in the last two weeks before your draft, when ADP is current