DRAFT 101 · UPDATED OCTOBER 21, 2026
Draft analysis becomes less useful when familiar phrases replace reasoning. DraftBlaster has never been exempt from that temptation. These are the habits we try to catch in our own work, along with better questions for readers to ask of any mock draft.
“They should just trade down.”
Trading down requires a willing partner and an acceptable offer. The chart can help frame the price; it cannot create demand. Explain who would move up, which player would motivate the move and why the proposed compensation makes sense to both teams.
A better formulation is: “They should consider moving down if an offer preserves access to a useful group of prospects and pays enough for the opportunity they surrender.”
“This is a lock.”
Confidence is not certainty. A forecast can be strongly supported and still be wrong. Injuries, private evaluations, unexpected availability and another team’s choice can change the outcome.
Explain why a selection is plausible, what the strongest alternative is and which assumption would have to change for the prediction to move. Superlatives need evidence, not merely emphasis.
“They do not need that position.”
A depth chart is a snapshot. Contracts, age, injuries, development and the likely roster a year later also matter. An apparent luxury can be succession planning. A glaring immediate need can still be addressed through another route.
That does not mean needs are irrelevant. It means the explanation should distinguish an immediate opening from a longer-term investment. Team needs in our mock are editorial assessments, not claims about private draft boards.
“They will take the best player available.”
Available according to whose board, and best for which role? Teams can value the same player differently because their assignments, roster plans and tolerance for development differ. A public ranking is not a universal price list.
Discuss talent, positional value and fit together. Avoid using “best player available” as a sentence that ends the analysis before it begins.
“He is a system player.”
Every player operates within a system. Identify which responsibilities the college offense or defense demanded, which skills transferred across situations and which tasks remain unproven. The label alone tells the reader very little.
The same caution applies to “project” and “versatile.” A development plan needs a specific skill to improve and a reasonable opportunity to learn it. Versatility needs several useful assignments, not merely several position names.
Disagreement is not evidence of incompetence
A team choosing differently from our mock does not prove that its decision-makers are foolish. They may have different information, priorities or grades. Evaluate the reasoning and eventual results without relying on personal insults.
Similarly, do not infer a coach’s philosophy from one quarter of a game, or a prospect’s character from an anonymous rumor. Distinguish confirmed events from allegations and interpretation. Explain what is known and leave private assessments private.
Make the argument testable
Write down the reason for a prediction before the result arrives. If the prediction changes, identify the new evidence. If it fails, do not quietly replace the original rationale with a convenient explanation.
The most useful reader response is not merely “I like this player.” It explains the fit, the concern or the overlooked alternative. That kind of disagreement improves the work. Continue with our guide to building a better mock draft and draft trade values.