Methodology

Team Needs Framework

Roster count is a lie. The simulator scores needs by the quality of a team's top options at each slot.

A common piece of feedback: “You've got starting pitching listed as depth for the Nats — it's actually a need.” That's usually because a team has plenty of names but nobody who profiles as a mid-rotation-or-better starter. We now score need on Top-N Quality, not headcount.

The 11 slots we score

  • SP — top 5 starters (rotation)
  • RP — top 6 relievers (bullpen)
  • C — top 2 catchers
  • 1B / 2B / 3B / SS — top 1 at each infield slot
  • LF / CF / RF — top 1 at each outfield slot (bucketed by primary position)
  • DH — top bat available at DH

Top-N Quality score

  1. Take the top N players eligible for the slot (by trade value).
  2. Average their model value.
  3. Compare to league benchmarks for that slot.

Each slot lands in one of four color-coded buckets:

  • Strength — well above the league average at that slot.
  • Solid — near league average.
  • Depth — quantity present but no impact bat/arm.
  • Need — clearly below the bar; a trade at this slot moves the needle.

How this affects grades

The Trade Grading Rubric weights fit heavily:

  • Sending a player from a Strength slot to a team's Need is a big fit bonus.
  • Trading away a Need without replacing it triggers a red flag in the pros/cons.
  • Prospect acquisitions apply partial fit credit based on ETA — a 2028 SS doesn't solve a 2026 SS hole.

Limitations

  • Positional eligibility uses primary position; utility guys don't get credit at multiple slots.
  • Injuries reduce a player's value but don't remove them from the depth chart.
  • Platoons aren't modeled — a LHH-only bat counts the same as an everyday player.
Questions or corrections? themorning@thenatsreport.com