Why a global tournament is the hardest event in sport to watch at a sensible hour

Three constraints that cannot all be satisfied

A tournament has to place each fixture at a time that is safe for the players, workable for the host city, and valuable to the audiences that fund it. Player welfare pushes fixtures away from the hottest part of the day in warm host countries, which removes a substantial block of the available hours. Host city logistics push against very late finishes, because a stadium emptying after public transport has wound down creates a problem the city has to solve.

Audience value pulls in whichever direction suits the largest paying markets, which in a distributed tournament may be several directions at once. Because these constraints point different ways, every published schedule represents a compromise in which somebody's viewing hours were sacrificed deliberately.

Why the host's own convenience is not decisive

It is tempting to assume fixtures are placed for the benefit of people in the host country, since they are the ones physically attending. In practice the host market is rarely the largest source of revenue, because attendance is a small number of people compared with the global viewing audience. A tournament is therefore willing to schedule fixtures at hours that are awkward locally if doing so opens a much larger audience elsewhere.

There are limits, since a fixture placed too far outside local norms produces empty seats and a flat atmosphere that damages the broadcast product itself. The resulting slots tend to sit at the edges of local convenience rather than at its centre, which is why attendance can feel oddly timed to residents.

The final round of group fixtures is different

When the last group fixtures are played, each team knows exactly what result it needs, and knowledge of another match in progress could distort behaviour. Tournaments therefore schedule the final round of each group simultaneously, removing the possibility of one pair of teams playing with complete information. This is a fairness requirement rather than a broadcasting one, and it directly reduces the number of distinct slots available on those days.

Fewer slots means more fixtures compressed into the same hours, which pushes some of them further from convenient viewing time in every market. It is one of the clearest cases where the integrity of the competition takes precedence over the convenience of both audiences and attendees.

Distributed hosting multiplies the problem

A tournament held across several time zones cannot even define a single local evening, because evening in one host city is afternoon in another. Scheduling then has to reconcile the internal spread of the host territory with the external spread of the audiences watching from other continents. The usual outcome is a long daily broadcast window running from early afternoon in the westernmost host region to late evening in the easternmost.

For a distant viewer that window may sit entirely inside their night, turning the tournament into a sequence of decisions about which fixtures are worth losing sleep for. Nothing about this is fixable, since it follows from geography rather than from any decision that could have been taken differently.

Reading a schedule for what it tells you

The placement of a fixture carries information about how the organiser rates it, because the slots reaching the most audiences are allocated to the fixtures expected to draw them. Fixtures involving the host nation are usually placed to suit the host, since a full stadium and a mobilised city are worth more than marginal distant viewers. Fixtures between teams with large followings elsewhere migrate towards the hours that serve those followings, regardless of what that means locally.

Reading the schedule this way tells a supporter which of their team's fixtures are being treated as the significant ones long before anyone plays. It is a more durable skill than memorising any particular timetable, because the logic persists across tournaments while the timetable does not.