Corrections
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.
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.
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.
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.
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.
A strong report should be short, reproducible, and tied to a public page. The most useful format is: URL, visible value, expected value, source or evidence, and whether the issue appears on one page or several related pages.
Corrections that affect trust, searchability, or repeated pages should be fixed at the shared source whenever possible. A single typo can be page-local, but a wrong team ID, stale venue, broken route label, or bad stat mapping usually needs a shared data or service fix.