A game time that changes on you is almost never random. Behind every moved kickoff sits one of five specific mechanisms: television claiming a better window, a league’s flex rules, a TBD that finally resolved, a weather make-up, or, most common of all, a time zone quirk on your end that never involved the league at all.
Knowing which one you are looking at tells you instantly whether your calendar is stale, your settings are wrong, or nothing is wrong anywhere. Here is the field guide.
First, the trap that isn’t a change: time zones
Start here because it produces the most false alarms. American leagues publish schedules in Eastern time. Broadcasts, sites, and data feeds treat ET as the reference clock, then everything downstream converts.
When every game on your calendar is off by the same amount, one, two, or three hours, uniformly, no one rescheduled anything. A conversion setting is wrong. The usual suspect is the calendar itself: Google, Apple, and Outlook each let an individual calendar carry its own time zone, separate from your device. Import a season into a calendar pinned to Eastern while you live in Phoenix and every event renders three hours ahead (two in summer, and yes, Arizona’s refusal to observe daylight saving is its own trap). The fix takes thirty seconds and lives in the calendar’s settings, not the events. Our import guide covers the right setup from the start.
Daylight saving adds a seasonal wrinkle. In 2026 the clocks jumped forward on March 8 and fall back November 1. Properly built calendar files handle the transition automatically because the time zone rules ride inside the file. Hand-typed events do not: a game you manually entered in February as “7:00” can silently drift relative to broadcast reality after the March change. One more reason to import instead of type.
International fans live the conversion constantly. A 1:00 PM ET Sunday kickoff is 6:00 PM in London and 5:00 AM Monday in Sydney. The team pages here include a time zone selector, so you can preview any schedule in your zone before it ever touches your calendar.
TBD: the honest placeholder
TBD is not a glitch. Leagues genuinely do not know some start times when they publish, and they say so rather than guess.
Baseball is the heaviest TBD user. MLB publishes its season nearly a year ahead, then lets national broadcasters claim games in waves: Sunday nights, holiday windows, Friday streaming slots. September times firm up latest of all, once playoff-race stakes are visible. A TBD next to a late-September Braves game means the league is waiting to see whether it matters nationally.
Football’s TBDs concentrate in the playoffs, where entire rounds are scheduled only after the bracket exists, and in the late season, where flex windows keep times provisional on purpose.
Basketball and hockey publish nearly complete times up front; their TBDs cluster around playoff rounds and the occasional arena conflict.
A TBD resolves exactly once, and from then on it behaves like any published time. The today page always carries the current answer for anything playing soon.
Flex scheduling: football’s late-season shuffle
The NFL reserves the right to swap late-season games between broadcast windows so December primetime is not stuck showcasing two 4-9 teams. Sunday night swaps come with roughly 12 days’ notice; other windows have joined the system with longer notice. A game sold to you in May as a 1:00 regional can become the 8:20 national stage, and a fading matchup can drop out of primetime into the afternoon.
Flex is the single biggest reason an NFL season downloaded at the May release needs a December refresh. The league announces each move publicly, the data updates the same day, and a two-minute re-import restores truth. How the schedule gets built in the first place, and why flex exists at all, is the subject of its own deep dive.
Weather, make-ups, and the doubleheader shuffle
Rain does what television cannot: it moves games with zero notice. Baseball absorbs dozens of postponements a season, and each one spawns a make-up, sometimes a single-admission doubleheader months later, sometimes a random mutual off-day. The original calendar entry becomes fiction in an afternoon.
Hockey and basketball see a handful of weather and building postponements a winter. Soccer adds cup competitions and continental fixtures that shove league dates around, which is why an MLS calendar needs its mid-summer check. Reading a baseball schedule’s reshuffled aftermath, split doubleheaders included, gets a full field guide here.
The special cases: international windows and tournaments
Games played abroad bend the clock hardest. NFL games in London kick off at 9:30 AM Eastern to hit a local evening window, a start time that reliably ambushes West Coast fans at 6:30 AM. Tournament soccer scrambles things further: the World Cup that just wrapped spread 104 matches across 16 host cities in three countries and four time zones, with kickoff times chosen for global audiences rather than any single market.
The pattern to internalize: the stranger the venue, the earlier you should double-check the local conversion.
Daylight saving, the semiannual ambush
The two clock changes deserve their own section because they generate a predictable wave of confusion every March and November, and because the failure is subtle: nothing looks wrong until you compare against the broadcast.
The mechanics. United States clocks spring forward the second Sunday of March and fall back the first Sunday of November (March 8 and November 1 in 2026). Games are anchored to Eastern wall-clock time, so a 7:00 PM start is 7:00 PM on both sides of the change. What shifts is every relationship around it: the gap to UTC, the gap to viewers abroad, and the gap to Arizona and Hawaii, which sit out the ritual entirely.
Who gets bitten, concretely:
- Manual typists. An event entered as a fixed offset (7 PM “GMT-4”) in October is an hour off after November 1, because the offset became GMT-5. Files with real time zone rules sail through; hand-entered events do not.
- Arizona fans. Phoenix is three hours behind a 7 PM Eastern start in summer and two in winter, without touching a clock. A season spanning the change has both conversions in it. Trust the calendar, not the memorized offset.
- International viewers. Other countries change clocks on different weekends (Europe moves in late March and late October) or not at all. For a few weeks a year the usual conversion is off by an hour in one direction, the mismatch windows land mid-March and early November, and every viewer abroad learns this the hard way exactly once.
The immunization is the same as everywhere else in this guide: imported files carry the rules, the team pages render your zone correctly year-round, and the only entries that betray you are the ones typed by hand.
Venue changes: when the place moves, not the time
Rarely, the whole game relocates: hurricanes push games to neutral sites, building failures force emergency moves, and the occasional international series takes a “home” game abroad. Time listings usually survive these moves, but the local time zone context can silently change, a “home game” suddenly kicking off in a different zone than the one your mental math assumed. The event’s venue field, which rides along in every downloaded file, is the tell worth glancing at when news mentions a relocation.
The diagnostic, condensed
| What you see | What actually happened | What to do |
|---|---|---|
| Every event off by the same hours | Calendar time zone setting | Fix the calendar’s zone |
| Events drifted after March or November | Manual entries vs daylight saving | Re-import a proper file |
| One game moved hours or days | Flex, broadcast pick, or make-up | Re-download the season |
| Time shows TBD | League hasn’t announced | Nothing; check nearer the date |
| Game vanished entirely | Postponement, make-up pending | Watch for the new date |
| Extra game appeared same day | Doubleheader make-up | Enjoy two for one |
Broadcast picks: the invisible hand behind most moves
Flex gets the headlines, but the routine version of television-driven change is the broadcast pick, and it operates in every league. National partners hold selection rights over windows: a Sunday night baseball slot, a Friday streaming exclusive, a Saturday hockey showcase. Weeks out, the partner surveys the schedule, claims the matchup with the best stakes, and the chosen game slides from its regional afternoon slot into the national window.
From the fan’s side this looks like a random time change; from the industry’s side it is the whole economic model working as designed. The tell that distinguishes a broadcast pick from other changes: the date holds while the time and network change together. Rainouts move dates. Time zone errors offset everything uniformly. A pick moves one game’s clock and its channel in the same announcement, and the team page’s TV column updates the same day, which is how you confirm what happened without reading a press release.
Keeping a truthful calendar with minimal effort
The realistic goal is not a calendar that never disagrees with reality. It is a calendar whose disagreements you catch before they cost you. Four habits get you there:
- Import, never hand-type. Files carry time zone rules; typed events carry your assumptions. Start here.
- Refresh at the volatility points. After TV announcements, entering flex season, and once playoffs are set. The subscription-versus-download tradeoff explains why downloads need this rhythm.
- Trust uniform offsets to be settings problems and single-game changes to be real. The table above is the whole triage.
- Verify big commitments against the live page. Tickets, travel, watch parties: thirty seconds on the team’s page before you book anything.
Game times move because billion-dollar broadcast schedules, weather, and 16 host cities all pull on the same clock. Your calendar can keep up anyway. The data on every league hub refreshes daily precisely so that when a time changes, the truth is always one download away.