Methodology

Why Beat Writers Beat Big Boards

A consensus board tells you how good players are. It does not tell you what teams will do. Those are different questions, and only one of them is answered by reporting.

The standard way to build a mock draft is to take a big board, take a list of team needs, and walk down the order matching one to the other. It is intuitive, it is fast, and it is reliably mediocre, because it answers a question nobody actually asked.

A big board answers: how good is this player? A mock draft has to answer: what is this specific front office going to do at this specific pick? Those questions have different inputs. Player quality is a scouting problem. Team behaviour is an information problem, and information about team behaviour does not live on big boards. It lives with the people in the building.

The information asymmetry

By the week of the draft, every team has spent a year assembling private information: full medical files, formal interviews, private workouts, top-30 visits, psychological testing, and coaching-staff opinions about scheme fit that never become public in any form. A national board has essentially none of that. It has tape, testing numbers, and production.

The gap between those two information sets is enormous, and it is exactly why consensus top-40 players routinely fall to Day 3. The board is not wrong about the tape. It is missing the file.

There is, however, one channel through which fragments of that file reliably leak: the reporters who cover a single team every day. A beat writer does not need a source to confirm a draft plan. They need to notice which prospect the head coach mentions unprompted, which position group the GM keeps circling back to in a press conference, who came in for a visit, and who the team sent to a pro day. Over a full pre-draft cycle, that accumulates into a genuine signal.

What we actually weight

Our simulator tracks reporting from more than 300 beat writers and national analysts across all 32 teams, and converts it into a numeric bonus applied to specific team-player pairings. Not all of it counts equally:

Why this beats need-matching

Simple need-matching produces mocks that are internally coherent and externally wrong, because it assumes teams draft to fill holes. They frequently do not. Teams draft to their board, to their scheme, to their coaching staff's specific preferences, and sometimes to a conviction about one player that no outside model can derive.

Reporting captures some of that conviction before it shows up in a pick. Need-matching, by construction, cannot; it only knows the roster.

This is also why our engine never lets reporting override the board completely. A signal linking a team to a prospect the board has fifty slots lower raises that player's score; it does not teleport him up the board. The engine enforces a mock-range constraint precisely so a single loud report cannot produce an outcome no evaluator anywhere considered plausible. The goal is to weight information, not to be captured by it.

The honest limitation

Reporting is not evenly distributed. Some markets have five excellent beat writers; some have one. Some front offices leak constantly and some are genuinely airtight. That means signal quality varies by team in a way no model can fully correct for, and it is a real limitation of this approach rather than a footnote.

The mitigation is to be explicit about it: when a team has thin coverage, the engine falls back harder on board rank, regime tendency and need. That produces a more generic result for those teams, which is the correct behaviour when you genuinely know less. A model that pretends to equal confidence everywhere is lying about something.

The complete scoring method, including every weight and multiplier, is documented on how the simulator works. The 2026 results it was tested against are in the full draft results.

More analysis

See the method in action

Take control of any franchise, trade up and down the board, and simulate all seven rounds of the 2027 draft.

Start a mock draft