A pitch-level scouting model for this series: how each lineup handles the other staff's pitch mix, who wins each hitter vs starter matchup, how each manager runs his bullpen, and a plate-appearance-by-plate-appearance simulation of the full series. Every number on this page is rebuilt from raw Statcast data by the pipeline in this repository.

Bottom line

Series win probability
How it ends
01 · Pitch mix

Run value against the pitches each staff actually throws

Each row is a pitch type. The grey bar is how often the opposing staff throws it. Next is the lineup's run value per 100 pitches against that pitch type, then the staff's run value with it, shown from the hitter's side so both bars read the same way. The edge column multiplies usage by the difference, so the total is an arsenal-weighted matchup score in runs per 100 pitches. These are raw season values, as Savant reports them.

Matchup score, runs per 100 pitches (hitter view)

■ red favors the hitter, ■ blue favors the pitcher. Staff = pitchers active in the last four weeks of the season.
02 · Player level

Hitter vs starter: expected wOBA from the outcome model

Each cell is the model's expected wOBA for that plate appearance: the hitter's outcome rates against the pitcher's hand and the pitcher's rates against the batter's side, combined with the odds-ratio method, then tilted by the pitch-mix edge if the backtest says the tilt helps. Click a cell for the outcome probabilities, the pitch-by-pitch breakdown and the zone overlay.

pitcher wins hitter wins (.255 · .315 · .375)
03 · Location

Where each lineup does damage vs where each staff throws

Statcast zones from the catcher's view: 1 to 9 is the strike zone, the four outer blocks are the chase areas. Left is the lineup's run value per 100 by zone, middle is where the opposing staff puts that pitch group, right is the staff's results by zone from the hitter's side.

04 · Handedness

Platoon splits and staff handedness

05 · Starters

Projected starters and how long they last

Cards follow the rotation in the config. The simulator draws each starter's length from his own 2026 batters-faced distribution, capped for planned openers, and pulls him early if he gets hit hard.

06 · Bullpens

Bullpen tendencies, roles and situations

Roles come from how each reliever was actually used, not from saves. Leverage index (LI) measures how much a plate appearance could swing the win probability, so a 1.0 is average and 2.0 is twice as important. gmLI is a reliever's average leverage when he entered.

Usage and results

Who the manager calls, by situation

Share of relief appearances in each inning and score state (fielding team's view), smoothed. This table drives reliever choice in the simulator.

Situational results

07 · Run prevention beyond the pitcher

Defense, baserunning and the parks

Team Outs Above Average

All 30 teams. The two series clubs are highlighted.

Park factors

Statcast park factors, 3-year window (100 = average). The simulator applies these by batter side.

Fielders and runners to know

08 · Context

Schedule, game times, weather, home field and form

Series schedule

Team xwOBA by month, batting

Team xwOBA allowed by month, pitching

09 · Simulation

Plate-appearance-level series simulation

Every simulated game runs plate appearance by plate appearance: outcome probabilities from the model, league-average baserunning, starters pulled on their own usage patterns, relievers chosen by each manager's tendencies, and bullpen fatigue carried across the series calendar. Postseason rules apply, so there is no automatic runner in extra innings. The range comes from rerunning everything on bootstrap resamples of the season's games.

10 · How much to trust this

Model check: does the matchup model predict anything?

Out-of-sample log loss

Lower is better. Trained before the split date, scored on plate appearances after it.

Does the pitch-mix edge explain what talent misses?

Test plate appearances grouped into fifths by arsenal edge. Bars show actual wOBA minus the talent-only model's expected wOBA.

Is the simulator scoring at the right level?

Simulated runs per game on this series' schedule and parks, next to each team's actual 2026 scoring scaled to the same parks. Large gaps would mean the simulator over- or under-rates a side.

Calibration of the talent model

Test plate appearances binned by expected wOBA. Points on the diagonal mean the model's probabilities are honest.

11 · Track record

Backtest on real games: the 2026 playoffs and the late regular season

Each game below was predicted using only what was known before first pitch: that day's batting orders and starting pitchers, each bullpen as it stood over the previous 30 days, real bullpen fatigue from the previous two days, and a model fit on earlier games only. Playoff games use a model fit on the full regular season. The late-season test fits on games before the split date and predicts every game after it.

Brier score is the average squared error of the win probability (lower is better, a coin flip scores .250). The baselines use the same pregame information: home field alone, and log5 matchups of each team's win percentage or Pythagorean record, each with home field.

Every playoff game so far

Model, market and Pythagorean columns are the home team's pregame win probability. The market is DraftKings' closing moneyline with the bookmaker's margin removed. A call is right when the side the model gave more than 50% won.

Scores by predictor

Bold marks the best score in each column.

Is the model really better?

Model Brier minus baseline Brier with a 95% bootstrap interval over games. Left of zero means the model was better. An interval crossing zero means the sample cannot tell them apart.

October run environment

Past postseasons, each game's actual runs against what the two teams' regular-season runs scored and allowed predicted. A factor below 1 means teams score less in October than their season numbers say. The simulator scales playoff scoring by this factor.

Calibration on late-season games

Games grouped by the model's home win probability. Points on the diagonal mean the probabilities were honest.

12 · Method

Method, definitions and caveats

Data. Every pitch of the season from Baseball Savant's Statcast search, plus Savant's Outs Above Average, sprint speed, catcher framing, baserunning and park factor leaderboards, and the MLB Stats API schedule (day/night, venue, temperature). The pipeline pulls, caches and refreshes them incrementally.

Run value. Change in run expectancy per pitch, summed per 100 pitches. Hitter view: positive means runs for the offense. Pitcher view: positive means runs saved. The model uses expected run value, which swaps each ball in play's actual result for its xwOBA, removing most defense and luck.

Shrinkage. Pitch-type values are regressed in two levels: pitch group toward league average, pitch type toward the player's own group value. Outcome rates use outcome-specific stabilization constants and a two-level platoon structure. Recent games count more (half-life set in the config).

Outcome model. Multinomial odds ratio over K, BB/HBP, 1B, 2B, 3B, HR and outs, with an optional pitch-mix tilt whose size is chosen on a validation window. Park factors apply by batter side, and home batters get a small tilt calibrated to an MLB-typical home win rate.

Caveats. Postseason managing is more aggressive than regular-season usage, which the leverage boost only approximates. Baserunning is league average. Lineups, rotations and bullpens come from the config file and should be updated when rosters are announced.

Sources: Baseball Savant Statcast Search, Savant Park Factors, Savant OAA, MLB Stats API.