Errors are inevitable in a reference site that tracks thousands of dollar figures, statutory citations, and regulatory dates. What matters is what happens next. This page documents how RothIRAHub handles errors, the standards we correct against, and every substantive correction we have ever made.

Our correction standard

We correct any statement that is factually wrong (a dollar figure, a date, a rule), legally misleading (a cited section that does not say what we claim it says), or materially incomplete in a way that could change a reader's decision. We do not "correct" matters of editorial judgment, framing, or emphasis — those we may revise, but not under this policy.

Our baseline for "correct" is the primary source: the Internal Revenue Code, Treasury Regulations, IRS publications (590-A, 590-B, current-year revenue procedures and notices), Treasury Decisions, and enacted legislation. Secondary sources can flag a question but cannot settle one.

How to report an error

Email us at corrections@rothirahub.com or use the contact form. The useful form of a report includes: the URL of the page, the sentence or figure you believe is wrong, the source you relied on, and (if possible) the primary-source citation that supports your reading.

We acknowledge every report within three business days. If a report is about a tax-year dollar figure that has changed, we treat it as urgent and verify within 24 hours.

Our correction process

Verify against the primary source. For any reported error we re-read the underlying statute, regulation, or publication. If the reported claim is right, we correct. If we believe our original claim was correct, we reply with the citation chain that supports it.

Fix the page. We update the text, update the dateModified in the page's JSON-LD, and append a dated entry to the corrections log below. For material errors (ones that could change a reader's action), we add an editor's note on the affected page itself indicating what was changed and when.

Log publicly. Every substantive correction appears below in a permanent, dated list. We do not quietly remove items or silently revise history. Typos and formatting fixes are not logged.

Thank the reporter. If a reader wants credit (first name or handle), we name them in the log entry. Most prefer to remain anonymous, which is fine.

What qualifies as a correction

Four categories:

Factual corrections. A contribution limit, phase-out threshold, effective date, form number, or statutory citation was wrong.

Interpretive corrections. A rule was stated in a way that does not match what the regulation or guidance actually says.

Scope corrections. A rule was described as universally applicable when the regulation limits it to a subset of taxpayers, account types, or tax years.

Currency corrections. A figure was accurate for a prior year and was not updated on a page that should reflect the current tax year.

Ambiguities where Treasury or the courts have not settled the question are not corrections. When we describe an unsettled area we say so plainly and present the competing readings.

Significant vs. minor corrections

A correction is significant if a reasonable reader could have acted on the wrong information in a way that cost money, missed a deadline, or triggered a penalty. Significant corrections get an on-page editor's note (at the top of the article) that remains visible for at least 12 months after the correction date.

A correction is minor if it would not change a reader's action — for example, a statute was cited with a typographical error that still resolved to the correct provision, or a date was off by a day in a context where the day does not matter. Minor corrections are logged but not flagged on the page.

Corrections log

Entries are listed newest first. Each entry notes the date, the affected URL(s), what was wrong, what we changed it to, and the primary source we verified against. The log begins with the public launch of this policy (2026-04-19); pre-launch content changes are tracked in our internal editorial history and summarized in the changelog.

No substantive corrections recorded since 2026-04-19.

This log is empty by design at launch. When we issue our first correction it will appear here, with the date, URL, description of the error, the corrected statement, and the primary source relied on. We prefer a well-populated log over a suspiciously empty one: an error-free reference site does not exist.

What we will not do

We will not quietly revise history, remove old posts, or edit archived versions of articles to pretend a statement was never made. Every version of every article is preserved in our private editorial history and we will produce it on request if a correction is contested.

We will not attack or diminish readers who report errors. A report is a gift. The right response is to verify it, correct if warranted, and thank the reporter.

We will not use "correction" to re-litigate editorial decisions that are not wrong but that some readers might disagree with (for example, how much caveat we choose to put around a legal gray area). Editorial disagreements are welcome but they are not corrections.

Related pages

Editorial Guidelines · Changelog · Technical Review · Contact