INSIDE AN ABS CHALLENGE DASHBOARD
This is part one of a blog series around the MLB ABS system, the data build, dashboard build and select number of Tableau specific functionalities that allowed me to make this an interactive experience for you.
R. GUEVARA
How MLB’s challenge system reshapes close calls–and what a season of data can show us.
Baseball has always balanced tradition with change. Few moments make that tension clearer than a close pitch: the home-plate umpire makes the call in an instant, and that judgment can shape an at-bat, a game, or a season.
Pitch-tracking technology now offers a precise way to review those calls. MLB’s Automated Ball-Strike (ABS) Challenge System keeps the umpire’s call in place but lets players challenge it, pairing human judgment with technology rather than replacing one with the other.
I built a Tableau dashboard to explore how teams used that new option during the 2026 season: who challenged, which calls changed, and where the pitches crossed the strike zone. The dashboard moves from league-wide patterns to individual pitches and video.
What is the ABS Challenge System?
MLB’s Automated Ball-Strike (ABS) Challenge System uses pitch-tracking technology to review a home-plate umpire’s ball-or-strike call when a player challenges it.
Hawk-Eye determines whether the pitch crossed the batter-specific strike zone. The umpire still makes the initial call; ABS does not automatically call every pitch.
How a challenge works
A challenge follows four steps:
- The umpire makes the initial call (strike or ball)
- A player requests a challenge
- Hawk-Eye tracks the pitch
- The official result appears on the screen

Below are the challenge rules:
| RULE | MLB Requirement |
|---|---|
| Initial challenges | 2 per team |
| Successful challenge | Retained |
| Unsuccessful challenge | Lost |
| Who can challenge? | Batter, pitcher, catcher |
| Managers | Cannot initiate challenges |
| Challenge signal | Tap helmet or cap |
| Time to challenge | Immediately, approximately 2 seconds |
| Extra innings | Additional challenge if entering an inning with none remaining |
| Position player pitching | No challenges permitted |
A successful challenge is retained; a team loses one only when the original call stands.
How a strike zone is set

Below is a schematic of player and pitch tracking cameras around a field:

With the dashboard build I wanted to answer the following questions:
- How did teams use their limited challenges? Did they save them for later or higher-stake situations?
- Who initiated challenges? Did patterns differ among batters, catchers, and pitchers?
- Which teams had more success overturning calls? How did their results compare with the entire league?
- How did these same results vary by home-plate umpire? Which umpires resulted in a higher rate of confirmed calls?
- How can I see all challenges visualized but also view video evidence for added context?
Building the Dataset

I built the dataset in four steps. I used the MLB Stats API schedule to identify completed games and game IDs, then gathered pitch records from Baseball Savant, removed duplicates, and flagged ABS challenges. I joined each challenge to its game, teams, players, and home-plate umpire.
Finally, I prepared Tableau fields for readable outcomes, video links, normalized pitch locations, and the strike-zone outline.
Inside the Dashboard

The dashboard opens with the season-wide picture: challenge volume, success rate, and challenges per game. A short in-dashboard explainer then walks through the challenge process and the strategic choice behind it.
From there, the views narrow in stages. Monthly charts show how volume and success changed over the season, and role-based comparisons break challenges out by batter, catcher, and pitcher. Team and game-context views add clubs, innings, and day versus night games.
Filters let readers narrow any comparison, though small groups should be read with caution.


The strike-zone views come next, plotting each challenged pitch against the displayed zone. Selecting a mark links its location to video, so readers can examine a call in context and not rely on the dot alone. Further views offer routes into individual stories: notable games, the closest and farthest calls, lost challenges, catchers, and umpires.


The strike-zone plot and the video are designed to work as a pair. The mark shows where the pitch crossed relative to the displayed zone, and the video restores the players and the moment around the call. Because the chart normalizes vertical location across batters, it offers a visual comparison, not a substitute for the official ABS ruling.
In Overview
Together, the dashboard moves from league-wide patterns to individual moments. Readers can start with a broad question, narrow the context, find a pitch, and watch the play.
The design aims to feel like an exploration of baseball, not a wall of charts. Summary numbers establish the scale, comparisons reveal patterns, and pitch-level views bring the analysis back to the field.
Typography and color reinforce that path. Bold figures carry the headlines, while smaller labels and subdued text provide context. In the monthly view, bars show challenge volume and an orange line marks success rate, and outcome styling distinguishes confirmed from overturned calls.
Design Tradeoffs
More labels and pitch details would add information but make the dashboard harder to scan, so spacing, sections, tooltips, and selection reveal detail on demand. Placing the video beside the strike-zone view uses space, but it makes the connection between data and play immediate.
What’s On-Deck in this blog series:
- Mining ABS data with Claude and VS Code; Making a video wrapper for challenging pitches
- Collection of Tableau functionalities (Dashboard/URL actions, Parameters and Dynamic Zone Visibility) to provide you a full experience (with a walk-through video)
- Wrap-Up Review Video
