A racing table needs a source, a data cutoff and a real revision date

A published racing table should answer three questions without making the reader hunt through the page:

1. Where did these records come from?
2. How far does the table’s coverage extend?
3. When did its data last change?

One label saying “Last updated” cannot reliably answer all three. It may refer to a corrected result, a new year added to the table or merely an edit to the surrounding article.

Put a metadata block next to the table

Use a short block immediately above or below the table:

Coverage: Runnings through 2026 Data updated: 22 September 2026 Sources: Official results archive; racecourse records Status: Complete for the stated period; corrected records are noted below

The labels have separate jobs:

Label	What it tells the reader	What it should not mean
Coverage or Data through	The latest race, season or date included	The day the webpage was edited
Data updated	When a record was added, removed or corrected	A punctuation or layout change
Source	Who supplied or published the underlying records	A general list of websites consulted
Source accessed	When the cited online record or dataset was checked	When the event itself happened
Page updated	When the article or presentation changed	Proof that every table row was rechecked

This separation matters for an annual record such as Epsom Derby winners. A table can have coverage through the 2026 running even if it was checked again months later. Conversely, changing an explanatory paragraph should not make the data look newly verified.

Name the source precisely

“Internet research” is not a useful source. Name the authority, archive or publication and link to the exact record, results section or dataset where possible.

If different columns come from different places, map them clearly:

Sources: Winner, jockey and trainer from Source A; winning time and margin from Source B. Historical spellings follow Source A.

That note is more informative than attaching several undifferentiated links. It also exposes disagreements rather than hiding them. If one archive gives a different time, owner or field size, either explain which record governs the table or mark that cell as disputed.

This is data provenance: information about the origin and processing of a dataset. The W3C’s Data on the Web Best Practices lists provenance, data quality, version indicators and version history as separate publication practices. A visible source line is the reader-facing minimum; a fuller methodology note may also be needed for a compiled historical table.

Date the data, not just the page

Use an absolute date—“22 September 2026”—rather than “today” or “recently.” For annual tables, also state the latest included edition in plain language:

Coverage: 165 runnings, 1861–2025 Last data change: 13 September 2026

The first line describes the table’s extent. The second records the publication’s work on it. A reader can then tell that a Melbourne Cup winners table ending in 2025 is intentionally complete to that point, not necessarily abandoned.

Do not reset the data-update date after cosmetic changes. If the table is regenerated automatically but its records do not change, “Generated on” may be accurate; “Data updated” is not.

Distinguish additions, revisions and corrections

These changes are not equivalent:

• Addition: a new race or season is appended.
• Revision: a provisional value is replaced after better information becomes available.
• Correction: the publication fixes its own transcription, calculation or attribution error.
• Presentation change: sorting, headings or explanatory text changes while the records remain the same.

For a consequential change, add a dated note:

22 September 2026: Corrected the 19XX winning margin from X to Y after checking the official result. No other rows changed.

The Department for Culture, Media and Sport’s revisions and corrections policy provides a useful model even though a racing publication is not an official-statistics producer. It distinguishes scheduled revisions from error corrections, calls for provisional and revised figures to be marked in tables, and says reports and tables should state when data was first published and revised.

Keep the current value in the main table. A revision note should explain the former value and the reason for the change; it should not force the reader to compare archived pages.

Keep the note attached to the table

A source list at the bottom of a long article may satisfy citation mechanics while still leaving the table ambiguous. Put the compact metadata block beside the data, then use footnotes or a methodology section for detail.

The table itself also needs a descriptive title or caption. W3C accessibility guidance explains that a caption functions like a table heading, helping readers—including screen-reader users—identify the table, understand its subject and decide whether to read it. “Grand National winners, 1839–2026” is therefore better than “Table 1.”

For a long record such as Grand National winners by year, the practical publication pattern is:

1. a caption defining the event and period;
2. coverage and data-update dates;
3. source links with column-level attribution where necessary;
4. markers for provisional, disputed or corrected cells; and
5. a short dated revision log below the table.

That gives the reader enough context to judge the records without turning every row into a thicket of citations.