These are returning-production projections at the team level: the model estimates each program's 2026 talent, works out how much of that production graduates, applies a growth curve to the players who come back, and assumes departing production is partially replaced. It reads one season of aggregate output, which is a different and coarser thing from the player model in the Players tab.
The growth factors in step 3 below are still the reasoned values this page launched with. The four-season archive can now measure them directly, and the Players tab does. Reconciling the two is the next job on this page.
Every input is CCAA-calibrated. WAR comes from the same oWAR and pWAR figures used across the site, which recalibrate to league average on every page load. A projection is a central estimate, not a prediction of what will happen.
—
coming back, not share of WAR
and is marked as such
drawn from comparable players
Every returning player in the conference, projected forward one season. Each component of a hitter's line is projected separately and regressed by its own measured reliability, then aged on a curve derived from the archive rather than assumed. This is a different animal from the team model in the other tab, which works off a single season of aggregate production.
These numbers are frozen. They will not move when a stat update is pushed. That is the point: a forecast that quietly rewrites itself cannot be checked, and this one is meant to be checked in June against what actually happens.
—
2025 and 2026, then scored against them
n/(n+k), which never reaches full credibility. That is deliberate and it is the opposite of what the leaderboards do: the stats pages describe what a player did, so playing time earns full credit, while a projection estimates what he is, and no high school sample is ever fully convincing.