FT, postponements, abandonments and the safeguards around automated updates. This historical guide is tied to season 2024/25; it is not a current-season scoreboard.
A status is part of the fact
A fixture marked NS is not a goalless draw; it has not started. FT signals that the match has ended according to the provider. PST means postponed, CANC cancelled and ABD abandoned. These abbreviations are data labels, not final rulings by the competition organiser. On the result board we require a final status and numeric scores.
The sync validates all fixtures before replacing the stored snapshot. A final match with missing goals, a duplicate ID or an unexpectedly short historical archive causes the update to stop. The previous published release remains available. This is especially important for unattended timer runs.
Corrections travel downstream
The API can amend a date, status, venue or score after an initial publication. Our timer fetches a fresh complete season and rebuilds the static site. The page notes the time of the last successful fetch. When an official correction conflicts with the feed, contact us with both references; we can add an editorial note while the underlying source is reviewed.
What the common abbreviations mean in practice
NS usually means not started. It is not evidence that the fixture will definitely kick off at the listed time. FT is a final score in the provider's record. AET and PEN signal a completed match that involved extra time or penalties; the main goal fields may not fully describe a shootout. PST is postponed, CANC cancelled and ABD abandoned. An awarded or walkover status needs extra organiser context before it is turned into a simple sporting result.
Our results filter includes final statuses only when both goal values are integers. The upcoming list excludes postponements, cancellations, abandonments, awards and walkovers. This separation is why an empty archive schedule can coexist with a populated historical results board. It is also why a postponed fixture with a stale date should not be advertised as an upcoming match.
One fixture ID can be updated in place by the source. The next complete sync refreshes that record, and the static site is rebuilt as a whole. If a corrected match is important to a season story, an editorial note may also need an update; automation does not rewrite prose on its own.
How the release gate protects readers
The importer checks every fixture for an ID, valid date, two distinct team names and a status. It rejects duplicate IDs and final matches missing a numeric score. For the known 2024 season it also checks minimum feed sizes for both leagues. A partial response from one competition cannot be treated as a valid complete site update just because the other competition succeeded.
After validation, the new JSON is written to a temporary file and renamed into place. Astro then builds static pages and a quality script checks links, images, metadata and core-page depth. Only a successful build is copied into a new release directory and pointed to by the `current` symlink. If an earlier step fails, the previous release continues to serve visitors.
This is not a guarantee that a source never makes an error. It is a practical guard against foreseeable technical failures. A factual dispute still requires a source comparison and, where appropriate, editorial correction.
Related reading
How to read a league table
Points, games in hand, goal difference and the limits of reconstructed rankings.
Open article →Football times in Kenya
How East Africa Time and API timestamps affect fixture listings.
Open article →Kenyan football glossary
A plain-language reference for league, fixture and data terminology.
Open article →