Corrections Policy

We publish analysis people use to make decisions about their fantasy teams. When we get a fact wrong, the useful thing is not to quietly edit it — it is to fix it, say so, and make the fix easy to find.

How to report an error

Email jordan@fantasywaiverwizard.com with the word “Correction” in the subject line, or use our contact form. The more of the following you can include, the faster we can act:

  • •A link to the article, and the sentence or statistic you believe is wrong
  • •What you believe the correct information is
  • •A source for it, if you have one

What we do with it

We aim to acknowledge every correction report within two business days, and to resolve it within five. If a claim is materially wrong and we cannot verify the correct version quickly, we will remove or amend the claim while we work it out rather than leave it standing.

How we handle the fix depends on what kind of error it is:

  • •Factual errors — a wrong team, statistic, date, or name — are corrected in place, the article's updated date is changed, and the correction is logged on this page.
  • •Typos and broken links are fixed without a log entry. They do not change the meaning of anything.
  • •Superseded analysis — an article that was accurate when published but has been overtaken by events — is not a correction. Where it matters, we note the change rather than rewriting history. An article about a player's outlook in July is a record of what was known in July.
  • •Disagreements about opinion are not corrections, and we will say so plainly. We are happy to be argued with and we read every message, but a take you think is wrong is not the same as a fact that is wrong.

Errors in automated content

Our daily deep dives are AI-assisted and pass an automated accuracy check before publishing, as described in our editorial policy. That check is not perfect. When an error gets through it, we treat it exactly like any other factual error — corrected in place and logged here — and we also treat it as a bug in the check itself, because an error that reached publication means something upstream failed to catch it.

Published corrections

No corrections have been issued to date. This log starts on August 10, 2026 — the day this policy was published — and every correction we make from here forward will appear on it.