Federation Dashboard
Federation-wide operations across every competition
Finished games versus the total scheduled in the current scope, with the percentage of the schedule completed.
The share of measured games that started within a few minutes of their scheduled time. Only games that have both a scheduled time and an actual start time are counted.
The percentage of games decided by forfeit instead of being played out. High values can distort the standings.
How many different umpires worked at least one game in the current scope.
How many different teams have games in the current scope.
Operations & Scheduling
Late starts by field
The share of games that started LATE at each ballpark — the longer and redder the bar, the more often games run late there. (A game counts as on time only if it started within a few minutes of the scheduled time.) Click a bar to open those games.
Late starts by time slot
How often games scheduled at each time of day start late. Longer red bars flag slots — the first game of the day, for example — that habitually run late. Click a bar to open those games.
Late starts by day of week
The share of games that started late, grouped by the day of the week. Longer red bars flag days — busy weekends, for example — that run later than others. Click a day to open those games.
Average duration by field
The average length of a game at each ballpark, in minutes. Longer averages can point to slower play or scheduling pressure at that field. Click a bar to open those games.
Schedule completion
How the schedule breaks down: games already played, still scheduled, and forfeits. The bigger the played slice, the more of the schedule is done. Click a slice to open those games.
Officials Program Health
The share of finished games that had an umpire assigned. Low coverage means many games went unofficiated in the records.
The share of all umpire assignments handled by the three busiest umpires. A high value means the program leans heavily on a few people.
Umpire certification mix
The umpires who worked games, grouped by certification level. A large 'None' slice means many games are worked by uncertified umpires. Click a slice to open those umpires.
Umpires by games worked
How many umpires fall into each workload band, from those who worked a single game to the busiest. A tall '1' bar with a small '11+' bar means the program depends on a few people. Click a band to open those umpires.
Competitive Health
The average total runs scored per game, counting both teams.
The share of games decided by 10 or more runs. A high value means many one-sided games.
The share of games decided by a single run or tied. A high value points to a competitive, balanced league.
Run-margin distribution
How games were decided, by the final run difference — from ties and one-run nail-biters up to double-digit blowouts. A healthy league has plenty of close games. Click a band to open those games.
Most forfeits by team
The teams with the most forfeited games. Frequent forfeits can signal a team in trouble and affect the fairness of the standings. Click a team to open its forfeited games.
Data Integrity & Reporting
The typical number of days between a game being played and its result reaching DiamondCore. Measured from import by default.
The share of finished games that carry every key piece of data: start time, duration, attendance, officials, box score and lineups.
How many standings-integrity problems the scan found across the editions in scope, split into red (serious) and yellow (warnings).
Reporting lag (days from game to report)
How long after a game its result reached DiamondCore, grouped into day bands. Measured from import by default. Tall bars on the right mean results are arriving late. Click a band to open those games.
Missing data by component
For finished games, the share that are MISSING each piece of data — start time, duration, attendance, officials, box score and lineups. Longer bars show what is most often missing. Click a bar to open the games missing that piece.