Corrections Policy

Last updated: May 2026

SalaryLabs deals with salary, tax, and compensation numbers that people use to make real decisions. If something is wrong, we want the fix to be clear and fast.

How to Report an Error

Email [email protected] with:

• The page URL where the error appears
• The specific inputs you used
• The result you received
• What you believe the correct result should be, and why (source link if you have one)

Our Process

1. Acknowledge: We respond to correction reports within 1 to 2 business days.
2. Investigate: We reproduce the result and compare it against the relevant primary source.
3. Fix: If the issue is confirmed, we correct the page and update dateModified.
4. Note: For material errors, we add a visible correction note on the affected page.

Types of Errors We Fix

• Calculator logic errors — wrong formula, wrong bracket, wrong FICA limit
• Stale data — tax figures from a prior year, outdated BLS wage benchmarks
• Factual errors in guides — incorrect FLSA rules, wrong standard deduction amounts, wrong rate citations
• Broken links to primary sources
• Typographical errors that change meaning

Severity Tiers

Not every report has the same impact, so we triage in tiers. This shapes both how fast we respond and whether we leave a visible note on the affected page.

• Tier 1 — Material formula or rate error. A calculator returning the wrong number for a common case, or a guide stating an incorrect tax rate, FICA limit, or FLSA threshold. We fix within 1 to 3 business days when reproducible. We add a visible correction note on the page and update dateModified.
• Tier 2 — Stale primary-source data. An IRS or SSA figure that has been updated upstream but not yet reflected in our tools and guides. Fixed in the next batch update, typically weekly or as soon as we confirm the upstream change.
• Tier 3 — Wording or interpretation issue. A sentence that could mislead a careful reader, even if the underlying number is correct. Edited within 1 to 2 weeks, no visible note unless the prior wording could plausibly have caused harm.
• Tier 4 — Typo, broken link, formatting. Fixed quietly during normal maintenance.

What We Do Not Correct

• Simplification by design — some tools use limited models on purpose. Those limits are documented in our Methodology.
• Employer-specific differences — pre-tax deductions, local taxes, and payroll choices can produce different results from our estimates.
• BLS benchmark disputes — we do not replace published government wage data with anecdotes or proprietary salary claims.
• Personal preference on framing — we will not change a neutral explanation of a rule because a reader prefers a more flattering or alarming framing.

How We Acknowledge Past Errors

When a Tier 1 correction is published, the affected page receives a visible note near the top of the relevant section, in this format: "Correction (date): the [bracket / rate / formula / claim] was previously stated as X; the correct value is Y, sourced from [primary source]." The note stays on the page for at least 30 days so users who acted on the prior result can recognize it.

For methodology revisions that materially change how a calculator interprets inputs (for example, a switch from one tax assumption to another), the change is logged in the Methodology changelog with a dated entry.

Track Record

Past fixes have included tax-estimator updates after SSA wage-base changes, salary-heatmap purchasing-power data updates, and state-tax corrections in the take-home pay calculator. Confirmed changes are reflected in dateModified on affected pages.

What Makes a Report More Useful

The fastest reports include the exact tool URL, the values you entered, the result you received, and a source showing why you think the output is wrong. That lets us reproduce the issue quickly instead of guessing what assumptions were active when the result was generated.