Corrections Policy

1. How errors are identified

TT Calculator finds errors through four channels: reader reports, scheduled source reviews, quarterly content audits, and automated formula tests. Reader reports catch most factual issues. Scheduled reviews catch stale rates and benchmarks before readers notice them.

The team monitors official TikTok and ByteDance announcements for policy or payout changes that invalidate existing assumptions. When an announcement lands, the affected pages enter the correction queue automatically.

Quarterly audits target three high-risk areas: payout formula pages after TikTok program changes, tax calculator pages at the start of each calendar year, and benchmark tables that depend on third-party reports.

2. How to report an error

Three inboxes accept error reports, and all three feed one triage queue. corrections@ttcalculator.net handles content and data errors, bugs@ttcalculator.net handles calculator behavior, and contact@ttcalculator.net handles everything else. The Contact page works for all three purposes.

A complete report takes four steps:

1. Copy the URL of the page containing the error.
2. Describe the incorrect value, statement, or formula behavior.
3. Attach a source that supports the correct information, such as an official doc or benchmark report.
4. Send the report to corrections@ttcalculator.net or through the contact page.

Calculator bug reports that include the page URL, the input values used, and the expected result usually resolve in one reply. Reports missing a supporting source still get reviewed; verification just takes longer.

3. Correction workflow

Every confirmed report follows the same five-step path: report, triage, verify, fix, log.

1. Report: the message is logged, given an owner, and sorted by type within 1 business day.
2. Triage: the owner classifies the report into a severity tier and sets a resolution target.
3. Verify: the claim is checked against the primary source, and financial or technical claims route to the assigned expert reviewer.
4. Fix: the content or formula updates, and affected calculators re-run boundary-value tests.
5. Log: the last-verified date refreshes, and material changes enter the page change log.

No step is skipped for speed. A Tier 1 formula fix compresses the five steps into 24 hours; a Tier 3 typo runs the same path inside a maintenance batch.

4. Severity tiers and how each is handled

Reports sort into three severity tiers, and each tier carries its own resolution target and handling steps. Severity depends on one question: does the error change a number, formula result, or factual claim a reader acts on?

5. Correction notes vs silent updates

Corrections fall into two classes based on whether the change affects a published value or formula result. A public correction note is logged when the substance changes; a silent update covers routine maintenance.

Public correction note (logged):

• Formula changes that alter calculator output
• Material corrections to published rates, ranges, or benchmarks
• Factual corrections to platform policy or feature descriptions

Silent update (routine):

• Typographical, grammar, and formatting fixes
• Clarifying rewording that preserves the original meaning
• Routine refreshes of dates, links, and non-substantive copy

6. Response timeline

The target acknowledgment window is 48 hours. Confirmed corrections publish within 5 business days. Formula errors that affect calculator output take priority with a 24-hour resolution target.

Triage happens within 1 business day of receipt, and most email replies arrive within 1 to 2 business days. Corrections that require fresh research, such as sourcing a replacement benchmark, take 3 to 5 business days.

7. Update cadence

Correction requests run alongside a scheduled review cycle, so pages refresh even without an inbound report. The full assumption-refresh process appears in the Methodology.

• Calculator assumptions: reviewed weekly
• Rates and benchmarks: reviewed quarterly or on platform announcement
• Tax rates and brackets: reviewed annually alongside IRS updates
• Trust and policy pages: reviewed at least quarterly

8. Change log and transparency

Every public correction note records three fields: what changed, when it changed, and which source drove the correction. The notes appear in the change history inside each calculator’s E-E-A-T section. Silent updates do not generate a log entry.

Three examples of changes that generate a log entry:

• A payout range widened after a quarterly benchmark refresh
• A formula fix that changed calculator output for a specific input band
• A rewritten description of a TikTok program rule after a policy announcement

Historical entries stay visible so readers trace how a calculator’s assumptions evolved over time. The supporting data behind each correction follows the standards in the Sources Policy.

9. What we do not change

TT Calculator does not alter content for:

• Brand or advertiser pressure
• Disagreements about subjective strategy advice
• Requests to remove accurate but unflattering information about platforms or practices

A rejected correction request still gets a reply that explains the decision. Independence standards are documented in the Editorial Policy.

Frequently asked questions

Related Resources