Built in Lahore, PakistanHow we check the math

Methodology

How a Tallyworks calculator goes from an idea to a published page.

At a glance

  • Every tool starts from the official source document, not a secondary summary.
  • The worked example on each page is run by hand and must match the engine to the cent.
  • Calculators run entirely in your browser; nothing you type is sent anywhere.
  • Common mistakes and limitations on each fully-reviewed tool are hand-written, not boilerplate.

1. The question

A calculator here answers one well-defined question. "What is my take-home pay in Washington DC?" is a question. "How do taxes work?" is not. The question has to be specific enough that the answer is a number, and important enough that someone will type it into a search engine. If a tool cannot pass both tests, it does not get written.

2. The source document

Before any code is written, the formula is traced back to its official source — an IRS revenue procedure, a state revenue department bulletin, an FHA announcement, HUD table or SSA cost-of-living release. For settled textbook formulas (loan amortisation, body-mass index, present value) the formula is stated and derived in the "How it works" section instead.

Secondary summaries, blog posts and forum answers are not used as sources. The URL and date of the primary document are kept and go into the tool's "Sources" section.

3. The worked example

The formula is run by hand on a realistic input. The hand calculation has to match the tool's output to the cent (or the half-yard, depending on the tool). If they do not match, the error is in the tool, not the paper arithmetic, and the tool is fixed. The worked example that appears on the page is the same calculation — it is not a stylised version. This is why every tool page shows a worked example: readers can replicate it and know they can trust the engine.

4. The calculator

The calculator runs entirely in the reader's browser. No inputs are sent to a server, logged or stored. This is both a privacy choice (the content of a paycheck or a loan balance stays with the person) and a reliability choice (the page keeps working if the server goes offline).

The code is written as a pure function wherever possible — input in, number out, no side effects — so that the hand-checked example is literally the same code path that any other input will travel.

5. Common mistakes and limitations

For a fully-reviewed tool, the author lists the mistakes real users make with that calculation (based on client questions, tax-return reviews and feedback received through the contact page) and the honest limits of the tool — what it does not model, what simplifications it makes, when to see a professional. These sections are hand-written per tool. They are not boilerplate.

6. QA before publication

  • The TypeScript build must pass without warnings.
  • The worked example in the article prose must match the engine output.
  • Every source link in the "Sources" section must resolve to an official document (checked at publication time).
  • The page is read end-to-end from mobile.
  • The reviewed date is set to the day of publication.

7. After publication

Reader-reported errors are triaged within two business days. If the report is correct, the fix is made, the reviewed date is updated and the change is logged on the corrections page. If the report is incorrect, the reader gets a reply explaining the current treatment with its source.

A worked check from source to page: the 2026 HSA limits

Here is the exact process a single update followed, in October 2026, so you can see what "source to page" means in practice.

Source document. The IRS published Rev. Proc. 2025-19 in Internal Revenue Bulletin 2025-21, naming the 2026 HSA contribution limits: $4,400 self-only and $8,750 family, with the age-55 catch-up unchanged at $1,000. The IRB entry is the primary document; HR benefits sites, benefits-vendor blogs and tax-prep sites were ignored.

Hand check. I opened the bulletin, confirmed the two figures and the catch-up, and worked a full-year family example on paper: $8,750 room, 24% marginal federal rate, payroll contributions. By hand: $8,750 × 24% = $2,100 federal; $8,750 × 7.65% = $669.38 FICA; total ≈ $2,769.

Calculator code. The HSA page reads a single constant object (hsa2026) for its limit math. I changed selfOnly: 4300 → 4400 and family: 8550 → 8750, saved, and reloaded the page. The on-page calculator now showed $2,769 for the family 24%-bracket scenario, matching the paper number to the cent.

Page copy. Every mention of "$4,300" and "$8,550" was swapped in the page body, the FAQ, the meta description, the schema source list and the card description shown on the hub. The meta description was retrimmed to 138 characters (under the 160 cap). The source list now cites the IRB page directly, not a secondary summary.

Review date. The page's "last updated" was set to the day the change shipped, which is what the badge on the tool header reads from.

Repeat for every page that cited the figure. A full-site grep for "4,300" and "8,550" found the same numbers restated on the paystub decoder's HSA explanation and on the HSA-related card description. Both were updated in the same pass. If any one of them had been missed, the site would say two different things at once, which is the opposite of the promise.

The whole update, from reading the bulletin to pushing the change, took about forty minutes. The dollar numbers on the site now trace, step by step, back to a document anyone can open at irs.gov/irb/2025-21_IRB.

Who does this

Every step above is done by Muhammad Ahmad. There is no editorial team and no undisclosed outsourced writers. See the editorial policy for the full statement on sources, review cadence and advertising independence.