How Football Matter Processes and Verifies Football Data

Verification starts by making a claim precise. A score, a player's club, a table position and a tactical explanation are different claims. They require different evidence. A successful import can establish that Football Matter received a provider record. It cannot establish that an interpretation drawn from that record is correct.

Our approach is therefore to separate ingestion, consistency checking, correction and editorial review. This guide explains the distinctions through the implemented service. It is deliberately specific about limitations: where our code offers a check, we describe the check; where a human decision is still needed, we do not replace it with a confident label.

What an imported record establishes

Football Matter requests structured football information through API-Football. Fixtures, teams, events and player data are represented in database tables. A provider identifier helps associate later information with the same entity. That is a foundation for consistency, because a name alone can be ambiguous or change over time.

Importing a record establishes provenance at the system level. It does not mean our staff witnessed the match or independently confirmed every field. For a contentious factual claim, the evidence should reach beyond the presence of a database row. An official match record or competition decision may be needed, and the specific supporting reference should be retained.

Identity comes before comparison

A useful check begins by matching the fixture, competition and season. Comparing two totals is meaningless if one belongs to another season or to a different scope. Player-team relationships also need a time frame: a current club association is not sufficient evidence about a past fixture.

Readers can apply the same discipline. Open the relevant fixture or season entry rather than combining a search snippet, a current profile and an older report. Ask whether each source describes the same object. This often turns a vague disagreement into a clear question that can be tested and corrected.

Consistency is useful, but not independent confirmation

If a score and an event list agree, that is reassuring as a consistency check. It does not make them independent sources when both originated from the same provider. Repetition across several Football Matter pages likewise does not multiply the evidence. Those pages may be different views of one stored record.

This matters when evaluating an AI explanation. A generated answer, a cached response and a match page can repeat the same underlying mistake. Before calling a claim corroborated, identify the origin of each piece of evidence. Two interfaces are not necessarily two witnesses.

Reconciliation revisits a specific failure mode

The implemented fixture reconciler searches selected stale records whose scheduled kickoff is sufficiently far in the past and whose state remains unfinished. It requests a provider update using the fixture identifier. Retries and daily calls are limited, so the process can revisit missing finishes without assuming unlimited provider access.

That procedure addresses a particular problem: a stored fixture may have missed the update that would finalize it. It does not automatically investigate every historical discrepancy. A permanently unavailable provider response remains unavailable. The presence of a retry mechanism should not be translated into a claim that all results are continuously certified against official publications.

Derived tables require an explicit caveat

Some configured single-table competitions can have standings rebuilt from completed fixtures in our own database. This is useful when current provider standings are unavailable. It also creates an extra layer of interpretation: the calculated table depends on which completed fixtures are stored and on the ordering rules the code implements.

Our derived ordering uses points, goal difference and goals scored. It must not be presented as a complete implementation of every league's official regulations. Competition-specific tiebreaks, deductions or administrative decisions can require additional information. A derived result is most useful when its scope and limitation are visible alongside it.

Missing values should stay distinguishable from zero

Zero is an observation. Missing is a statement about availability. Replacing one with the other can produce a false conclusion: an absent player rating is not a poor rating, and an unavailable expected-goals field is not evidence that no chances were created.

When reading player and team pages, check the sample and the competition before comparing totals. If a statistic is unavailable, describe that limitation. A useful analysis can still explain what the available data supports without pretending that an incomplete panel is a complete account of performance.

Editorial verification operates at claim level

Our content-quality process identifies candidates for review, preserves records and records decisions. A quality score is a triage signal, not proof of truth. A quotation still needs attribution and a supporting source. A historical date still needs an appropriate record. A numerical claim needs evidence for the number and the scope in which it is used.

The review workflow records the checked version of an article. A changed body invalidates the current review for indexing purposes. That helps prevent a prior review being silently attached to a substantially different article. It does not replace the reviewer: someone still has to inspect the evidence and make an honest decision.

Why source links need an explanation

A source list is useful only when readers can connect it to the argument. Linking a competition's home page does not establish a particular result. Linking a provider's documentation can explain a field, but it does not independently verify an event that happened in a named match.

For substantial claims, identify what the source supports. Distinguish a rule, a data definition, a match observation and our interpretation. This makes correction easier because another reader can challenge the precise step rather than guessing which part of the article the reference was intended to justify.

How to report a data problem

Include the Football Matter URL, the relevant season or fixture date, the disputed field and a primary reference showing the expected information. If the issue concerns timing, explain when you observed it. If a competition has issued a ruling, link that decision instead of assuming that ordinary score arithmetic captures it.

Our methodology describes how the displayed features work, and our editorial policy sets out the sourcing and correction standards. You can start a specific fixture check at Matches. The useful outcome is not a universal assurance that errors cannot happen. It is a record that can be traced, questioned and amended using evidence.

A finished score may need a separate correction

Verification needs a separate check for an already-finished score. The stale-fixture pass targets unfinished states; a successful run therefore does not certify that every final result was compared with a later official amendment. Record the discrepancy and its supporting decision as a separate correction question.

Sources & References

• API-Football documentation
• IFAB Law 5: the referee's authority and decisions
• Football Matter methodology
• Football Matter editorial policy