How we build and check our calculators
Every result on CalculatorLib is computed by code that we can test. This page explains how a calculator is built, how we check it, where its rules come from, how a change reaches the site and what happens when something is wrong.
Last reviewed November 15, 2026
Built as code
Each calculator is a small program with four parts: the input form, the input handling, the calculation and the result. The calculation runs on our servers, and the same code answers the web page, the embeddable widget and our MCP server for AI assistants, so each of them gives the same number. Where a calculator follows a published formula, its page explains it.
AI does not do the maths
Numbers come from the calculator's code, never from a language model. The AI chat assistant on our pages gets its figures by running the same calculators through our MCP server and only puts the result into words; it does not calculate anything itself.
Checked against known answers
We keep a regression suite of "golden" cases: real inputs together with the outputs the calculator must produce. Today it holds more than 13,000 cases for more than 1,600 calculators, and it grows as calculators are added or fixed. Where an official worked example exists, such as a tax authority's sample calculation, it is used as one of the cases. The cases are run on our development server before a change is released and again on the live site afterwards; a mismatch blocks the release or rolls it back.
Official sources, named on the page
When a result depends on a rule someone else sets, such as a tax band, a contribution limit or a clinical cut-off, we take the value from the body that publishes the rule. A calculator that has been sourced lists that publisher in a sources section at the end of its page, with the date the rule takes effect and the date we last verified it. We are adding sources calculator by calculator, starting with tax and other rules that change. A source is added only after a person has opened it or an automated check has confirmed that the official page exists and matches. AI tools may suggest a source; they never add one on their own.
Health and medicine
Our standard for calculators that give a medicine dose or a clinical score is stricter: they list the clinical sources they follow, say when their numbers were last checked against those sources and state plainly that they have not been reviewed by a clinician. A tool whose core numbers we cannot trace to an authoritative source is narrowed or taken down. We are applying this standard to dosing calculators first.
How a change reaches the site
Changes are made on a separate development copy of the site first. They are checked there against the golden cases and our page checks, reviewed in a separate step and only then released to the live site in a planned release. The previous version is backed up before every change, so any change can be traced and rolled back.
How mistakes are fixed
Errors reach us from reader reports, our error monitoring and the automated checks. We reproduce the problem, fix it, add the failing case to the golden suite where it applies, and release the fix the same way as any other change.
What the date on a page means
The update date at the end of a calculator page is the date its calculation or its text last changed. We do not move it forward without a real change.
Limits
Results are estimates for information and education. They are not financial, legal, tax or medical advice, and they cannot take your whole situation into account. For a decision that matters, check the result with a qualified professional.
Found a wrong result?
Tell us which calculator, the inputs you used and the answer you expected. Every report reaches our team as a support ticket and is checked, and a confirmed error is fixed as described above.
Report a wrong result