Why The Order Of Play Is A Data Problem

The order of play looks like a list. It is the output of an assignment problem with more constraints than most people realize, solved fresh every evening.

The constraints are hard and numerous

Players need minimum rest between matches, doubles entrants cannot be scheduled in two places, and broadcast partners have contracted windows for certain matches.

Court capacity differs, so match selection is partly a demand forecast. Putting a high-demand match on a small court creates a crowd management problem.

Grass adds a constraint other surfaces do not, since court wear accumulates and the schedule has to distribute usage across the fortnight.

Every constraint is a recorded fact

The scheduler works from data: match completion times, which players are still in which events, court usage totals, and previous days' assignments.

None of that is guesswork, which is why the exercise is tractable. The difficulty is the number of interacting constraints rather than uncertainty about the inputs.

Weather is the one genuinely uncertain input, and it is the reason schedules are built with contingency rather than optimized tightly.

Why the schedule is published late

The order of play for the following day is released in the evening because it depends on results that are still being decided.

A late finish can invalidate a draft schedule entirely if it leaves a player without adequate rest, forcing reassignment across several courts.

Publishing early would mean publishing something likely to change, which is worse for spectators than publishing accurately and late.

Timing is deliberately vague

Matches after the first on a court are listed as following rather than at a stated time, because tennis has no fixed duration.

This is a record-keeping decision as much as a practical one. Publishing a specific time would create an expectation the tournament cannot meet.

Actual start and finish times are logged precisely, and that log is what feeds the next day's scheduling. The precision exists internally and not publicly.

What the logs make possible afterward

Accumulated timing data lets a tournament measure how long matches actually take by round, surface condition and time of day.

Those measurements feed session planning and roof usage decisions in subsequent years, so the archive is an operational input rather than a historical curiosity.

Scheduling improves through this feedback rather than through intuition, which is why long-running events schedule more accurately than new ones.

The phrase you hear in selection meetings is that a player is one-dimensional. It is said as a criticism. I have never fully understood why, given that the format is short enough that a team only needs a handful of dimensions in total and can distribute them across eleven bodies.

Consider the batter who can only hit down the ground and only against pace. He is useless in the middle overs against two spinners on a turning surface. He is also, in the right six deliveries, the most valuable player on the field, because the thing he does badly never comes up and the thing he does well comes up repeatedly.

The counter is obvious and it is about flexibility. If a wicket falls at the wrong moment, a specialist walks into a situation he cannot handle, and you have burned a slot. That is real. But it is a scheduling problem, not a talent problem, and scheduling problems have solutions that talent problems do not.

What actually happens is worse than either. Sides pick a squad full of players who are competent in every phase and outstanding in none, then wonder why they keep posting adequate totals and losing to somebody who had one man go berserk for four overs. Competence across the board is a way of guaranteeing you are never the reason a match turns.

I would rather carry two narrow players and accept that in a third of matches one of them is dead weight. The distribution of outcomes matters more than the average, because you do not get half a trophy for finishing consistently mid-table in a knockout competition.

There is a coaching dimension to this that gets ignored. Telling a specialist to broaden his game usually makes him worse at the thing he was picked for, because the technique that lets a player hit a length ball over long-on is not the technique that lets him work it into the leg side. They fight each other. He ends up in the middle, hitting neither shot with conviction, and within a season he is a squad player.

Leave him alone. Let him be strange.

The best selections I have watched were not the most complete cricketers on the list. They were the ones whose weakness the captain had a plan to hide.