Define the time window
Record date, time zone and inclusive boundaries. A 15:00 UK kickoff is not the same local or UTC time throughout every daylight-saving period. Use official competition fixtures and recheck broadcast or postponement changes; the Premier League fixture source explicitly notes that fixtures can move.
The 2026/27 opening slate checked on 20 August illustrates the filter: Saturday 22 August includes explicitly timed 12:30 and 17:30 matches alongside three entries with no different time stated. Under the fixture page's published convention, only those untimed weekend entries inherit the 15:00 UK default. Recheck each event at the decision cutoff rather than selecting every Saturday match.
Fixture verification table
| Field | Required value |
|---|---|
| Competition | Official competition identity |
| Event | Stable fixture ID and teams |
| Kickoff | Local time, time zone and UTC |
| Venue | Final confirmed venue |
| Market | Event, line and period |
| Lineup state | Expected or confirmed with timestamp |
| Price | Quote and acceptance time |
Remove a moved fixture from the slate or create a new, separately timed decision record. Do not preserve a leg merely to maintain the original count.
Model and dependence
Kickoff time can be a feature only if it has a defined mechanism and held-out evidence. Validate chronologically using scikit-learn's TimeSeriesSplit guidance.
Same-window fixtures can share weather, travel disruption, competition incentives and a data release schedule. OpenStax's independence condition must be checked before multiplying probabilities.
Operational advantage without probability claims
A shared kickoff can make a slate easier to monitor, but it also means late lineups and price changes arrive together. Set an information cutoff and reject any leg that cannot be reviewed before it. Operational convenience does not improve expected value under OpenStax's framework.
Verify period and settlement rules; Betfair's football rules are one current example.
Next step
Use Weekend Acca Research for the next part of this topic.
Capacity and cutoff test
Same-time fixtures compress the lineup and price-review window. Set a maximum number of events that can be checked properly before the cutoff; reject the remainder instead of accepting stale probabilities.
| Operational check | Pass condition |
|---|---|
| Time-zone conversion | Local time and UTC agree for every fixture |
| Fixture status | No postponed or moved event remains |
| Lineup ingestion | Player entities map without unresolved names |
| Price timestamp | Quote follows the final model update |
| Dependence review | Shared weather and competition flags complete |
| Acceptance | Complete receipt saved before kickoff |
Create a daylight-saving regression fixture for dates before and after clock changes. The IANA Time Zone Database records versioned local-time history, UTC offsets and daylight-saving rules; the underlying UTC kickoff should map to the correct local window under the date-specific zone rule, not a fixed UTC offset.
When the slate exceeds the declared review capacity, save which candidates were rejected and why. A later winner remains an excluded event, not evidence that the cutoff should have been bypassed. Review recurring rejection causes to improve data preparation before expanding capacity.
After settlement, compare excluded and retained events only for process diagnostics; do not claim that an excluded winner should have been added retrospectively.
Continue learning
- Next guide: Title Race Accumulators
- Related guide: World Cup 2026 Accumulators
Assumptions and limitations
No Saturday fixture or market is recommended. Time zones, schedules, lineups and prices change, and the page must be refreshed after expiry.
GambleAware
GamCare
Gambling Therapy
GAMSTOP