Corrections

How to report a CFBTrack data issue so it can be fixed quickly and cleanly.

The fastest correction reports are specific. CFBTrack pages often share data paths, so one clear report can fix more than one surface when it includes the exact page, the mismatch, and the expected value.

Contact CFBTrackReview data status

What this page covers

  • Send the exact URL

    A route-level report is easier to reproduce than a broad description of the problem.

  • Name the mismatch

    Say whether the issue is wrong data, stale data, a misleading label, or a broken interaction.

  • Include evidence when possible

    A screenshot, official source, or season/team reference helps narrow the fix path.

What to include in a correction report

The more precisely the issue is framed, the more likely it can be reproduced on the first pass. This is especially important on routes that support filters, tabs, and query-param state.

  • The full public URL, including relevant query parameters.
  • What the page currently shows and what you believe it should show instead.
  • Any supporting source, screenshot, or historical reference that clarifies the expected result.

What happens after you report it

Some corrections are route-local, while others require a shared data-path fix. When the same issue can affect multiple pages, the preferred fix is the shared source or formatter rather than a one-off hardcode on one team or one route.

  • Trust issues such as conflicting records, misleading times, or broken defaults are treated as high priority.
  • Shared data or formatting fixes are preferred over page-specific hardcodes.
  • If a source feed is missing data entirely, the safest fallback is used until the upstream data is available.

Best contact path

Use the contact page for the actual report so it reaches the site team. This corrections page exists to set expectations and help you package the report in the most useful format.

  • Use the contact page for data corrections, page bugs, and route behavior issues.
  • If the issue affects multiple URLs, include the clearest example first.
  • If a correction touches a future or in-progress season, note that explicitly.