Standards

Editorial policy

The standard this site holds itself to: where every figure comes from, what is checked before a page ships, what review is not performed here, and what happens when a reader reports an error. It is written to be checkable rather than reassuring.

What this site publishes

Two kinds of page. Calculators compute a number from a dated parameter file; explainers describe how a rule works and cite the document that states it. Everything else on the site — about, contact, privacy, terms, this page — exists to make those two auditable.

Four things are refused outright: sponsored articles, paid placements, guest posts written by someone else, and affiliate links. No page carries a recommendation to buy a product or a service. Advertising is the only revenue and it is placed by a script, never by an editor: an advertiser cannot buy a page, a position in a ranking, or a rate on a page.

Where a number comes from before it can be published

Every tax parameter on this site lives in one file, data/tax-params.json, and every entry carries four things: the value, a label a reader can understand, the URL of the document that states it, and the date that document was read. A figure without a source URL is not accepted by the build.

Sources are ranked, and the ranking is not negotiable:

  • First: the statute, the revenue procedure or the state revenue code that sets the number.
  • Second: the agency publication derived from it — IRS Publication 15, a state department of revenue notice.
  • Never a source: another calculator, a news article, or a summary site. Those are used at most as a cross-check, and a disagreement sends the figure back to the first tier.

Where a page and its source disagree, the source is right and the page is wrong. That single rule is the whole editorial policy; everything below is machinery for enforcing it.

What is checked before a page ships

  1. Traceability. Every figure on the page resolves to a parameter that carries a URL. The release gate fails on a number that belongs to a different tax year than the one the page claims.
  2. Two implementations that must agree. The browser bundle and the build engine are written separately. They are compared across 5,120 combinations (16 states × 4 filing statuses × 10 incomes × 4 deferral rates × 2 household sizes) on every build.
  3. A third, independent reconciliation. A reference implementation written for auditing purposes recomputes 4,016 cases. It shares the parameter file, so it can prove the engines implement the described model — it cannot prove the model describes the law. That limit is stated wherever its results are quoted.
  4. Structural gates. 44 checks run before a deploy: metadata uniqueness and length, canonical self-reference, one h1 per page, a primary-source link on every content page, sitemap dates traceable to a commit or a log entry, ad policy, contrast and focus.
  5. Deliberate breakage. A gate that has never failed is not evidence. Corrections are shipped with a negative test: the old wrong value is restored, the failure it produces is recorded, and the fix is confirmed to clear it.
  6. Similarity ceiling. No two state pages may share more than 15% of their prose. This exists so that a state page cannot be produced by swapping a rate into a template.

What review is not performed here

This is the part most sites leave out, so it is stated plainly:

  • No page on this site is reviewed by a licensed tax professional. The publisher is not a CPA, an enrolled agent or an attorney. No credential is claimed, and no reviewer is named for work that was not done.
  • No legal review. State summaries describe a published schedule; they are not opinions about how a statute applies to a person.
  • Drafts may be produced with machine assistance. Every figure is still traced to the cited source, and every gate still has to pass, before a page is published. Responsibility for what ships sits with the publisher, not with a tool.
  • If an external reviewer is ever engaged, that person's name, credential and the exact scope of the review will be published on this page and on every page they reviewed. A reviewer is never named in advance of the work.

Corrections

An error reported and confirmed is fixed, and the fix is published in the change log with the date. Quietly editing a wrong number is not an option here: the log is public and a correction is a line in it.

To report one, send the page URL, the inputs used, the figure shown and the figure expected with its source, to the contact address. Reports are answered within two business days. If a reported figure holds up, the page is rebuilt and the check date moves forward; if it does not, the reply says which source was used and why the number stands.

Update cadence

A tax year is re-verified in full before it can become the active year; a year whose parameters are not marked as verified cannot be made live at all. Beyond that, three states are re-checked against their revenue departments each quarter on a rotation, and every page shows the date its figures were checked. That date is read from the parameter file, never typed into the page, so it cannot drift away from the figures it describes.

Independence and funding

The site is funded by display advertising and nothing else. There is no subscription, no affiliate arrangement and no paid placement. The advertising switch is currently off, and the privacy policy says so in the present tense rather than describing revenue the site is not earning.

Who is accountable

One person publishes this site, described on the authorship page. It is not a firm and employs nobody. The method behind each figure is on the method page, the limits of the estimates are on the disclaimer, and the address for anything that looks wrong is on the contact page.