Data Status

What is current, what may lag, and how to think about in-season CFBTrack coverage.

Different parts of the site refresh on different cadences. This page explains the broad expectations so users know when to trust a number as settled, when to expect change, and when a route may still be catching up.

Report a correctionBrowse schedule data

What this page covers

  • Historical pages stabilize fastest

    Closed seasons and long-run aggregates are usually the least volatile surfaces.

  • In-season pages can move

    Schedules, current-season summaries, and live route overlays are more likely to shift as source data settles.

  • Coverage varies by route family

    A complete team page does not guarantee the same freshness on every recruiting, media, or video surface.

Refresh expectations

Team, schedule, and stat routes aim to stay current, but the exact timing depends on the source pipeline behind that page. Historical routes are usually stable once the season closes. In-season routes should be treated as live references rather than final archival records.

  • Schedules and kickoff metadata may update as games are announced or corrected.
  • Season summaries can shift while future or newly started seasons are still incomplete.
  • Specialty routes such as recruiting, media, and videos can trail the core team/schedule surfaces.

Known lag patterns

The most common lag is not total failure. It is usually partial coverage, missing metadata, or a page waiting on a supporting feed before it can expose its strongest view. Public pages should prefer an honest partial state over a misleading confident one.

  • Unknown kickoff times should stay marked as TBD until the source provides a real time.
  • If a route cannot populate the latest season, it should fall back to the most recent season with usable data.
  • A page may hide a secondary module when the underlying source is absent instead of showing an empty shell.

What to do when something looks off

Use this page as a status guide, not as a substitute for the route itself. If a page still looks wrong after you account for in-season drift or route-specific coverage, send a correction with the exact URL and the discrepancy you noticed.

  • Include the public URL and the exact value or section that looks wrong.
  • Mention whether the issue is a missing record, stale value, wrong label, or broken interaction.
  • Use the corrections page when you want the fastest path to a fix.