Skip to main content
    Updated Reviewed for 2025 & 2026 tax years

    Accuracy Transparency

    The high-risk, date-sensitive datasets we track — their verification cadence and when each was last verified. This page is generated from the same machine-readable contract our automated guard suite enforces: if a tracked source goes stale past its cadence or deadline, the test suite fails — on every push to the main branch and again on a weekly schedule — until a human re-verifies it against the primary source. Coverage grows as datasets are enrolled; it is not yet every page on the site.

    How our accuracy system works

    Primary-source verification

    Figures trace back to an IRS publication, Revenue Ruling, Treasury regulation, or an official state Department of Revenue page — a primary source wherever one exists; a small number of aggregate datasets cite reputable secondary compilations, and each entry names exactly what it relies on.

    Automated tests lock the figures

    1,000+ automated Vitest assertions anchor statutory numbers (brackets, mileage rates, phase-outs, SEPP factors). If a constant drifts by accident, the guard suite fails in continuous integration.

    Stale content fails the guard suite

    Every tracked source has a cadence and, where the calendar demands one, a hard deadline. Exceed either and the test suite fails — run on every push to the main branch and again on a weekly schedule — until a human re-verifies against the primary source.

    weekly automated monitoring

    A scheduled sentinel job runs weekly, watching a curated set of high-impact IRS and state pages for changes and rotating through the full cited-source list for dead links. It emails the maintainer when something moves, or a weekly heartbeat when there are no findings.

    Search-engine notifications

    When a new guide or calculator ships, our build pings the IndexNow protocol so Bing, Yandex, DuckDuckGo, Seznam, and Naver learn about the new URL within minutes instead of waiting on a crawl. Google does not consume IndexNow and continues to discover pages through our sitemap.

    Methodology

    The list of sources, with each one's last-verified date, cadence and any hard deadline, is generated by scripts/generate-freshness.ts from a single source of truth (src/lib/freshnessManifest.ts) at build time — the same file the CI regression tests read and the same file the sentinel job re-checks weekly. Each source's status is then worked out in your browser against today's date, so a source that goes past its cadence or deadline shows as Overdue even if the site has not been rebuilt. Dataset-specific "Last verified" dates shown on calculators (the §6621 rate schedule's, for example) are read from the same registry constants these rows are generated from. Pages outside the manifest show a general "Updated" date instead — that is a content-update stamp, not a per-figure verification claim.

    A source shows as Fresh when more than 30 days remain before its cadence runs out and before any hard deadline. It becomes Due soon when 30 or fewer days remain on either, and Overdue once either has passed — the day after the last day of its cadence, or the day after its hard deadline — which also fails the next scheduled test run.

    Nothing on this page is a substitute for professional tax advice. It is a transparency report about how we keep the educational content current.