How Knackdesk Checks Its Calculators
This page sets out the rules every Knackdesk calculator and workbook has to meet before it is published, and the checks that run each time the site is released. It is meant to let you judge how far to rely on a result. For a shorter overview of the site, see the about page.
The rule for every page
Each calculator does one calculation. It answers a single question, such as what a late fee comes to or how many clients a schedule can hold, rather than trying to model a whole business.
The inputs are figures the reader actually has: a price, a number of hours, an invoice date, a cost from a supplier bill. If a calculation would need a number most people cannot look up, the page either asks for something simpler or explains where to find the figure.
The formula is printed on the page. You should always be able to repeat the sum on paper or in a spreadsheet and arrive at the same answer. If you cannot, that is an error and we want to hear about it.
Testing
The arithmetic behind each calculator lives in a small module, separate from the page, so that it can be tested on its own. Every one of the 130 calculators has its own automated test file. The tests are written before the page and cover at least these cases:
- a worked example with fixed inputs, whose answer was calculated by hand before the code was written;
- the default values the page loads with, so the first result you see is a correct one;
- rejection of impossible inputs, such as negative amounts, zero hours or minutes where a duration is required, and percentages above 100 where a share cannot exceed the whole.
When an input is rejected, the calculator shows a message that names the field and the allowed range instead of returning a number.
The whole test suite runs before every release. The release process is set up so that the site is not published if any test fails. A change to one calculator cannot quietly break another, because all of them are tested together each time.
Workbook checks
The paid workbooks are generated by a script, not assembled by hand. This keeps the layout consistent and means a fix to a formula is applied the same way everywhere it appears.
- Every formula is recalculated in LibreOffice after the file is built, and the recalculated file is scanned for formula errors. The release requires zero errors.
- Key cells, such as totals, margins and break-even figures, are checked against hand arithmetic using the sample figures in the workbook.
- Input cells use blue text and formula cells use black text, so it is clear which cells you are meant to type into.
- Workbooks contain formulas only. There are no macros or scripts.
What we refuse to publish
Some content is left out on purpose, even where it would be easy to add.
- Industry benchmarks presented as targets. Knackdesk does not publish them, because published figures vary by country, year and source, and a figure that suits one market can mislead in another. Pages show the arithmetic and explain where to find your own number instead.
- Invented statistics. If a page states a fact, it is a fact about the formula or about how the calculation works, not a survey figure without a source.
- Clinical, legal, tax or licensing advice. Some calculators are used by clinics, care providers, law firms or trades, but they deal with the money side only.
Where a rule depends on where you work, such as a tax rate, a statutory late-payment rule or a minimum notice period, the page says that this is a matter for your jurisdiction and leaves the figure as an input you supply.
Rounding and edge cases
Calculations are carried out at full precision and rounded to two decimal places at the end, when the result is shown. Rounding in the middle of a calculation can shift the final figure by a cent or more, so it is avoided.
Some results are ratios, such as a percentage of revenue. When the figure underneath would be zero, the ratio cannot be calculated. In that case the calculator returns no value and the page shows "n/a" rather than a misleading number such as zero or infinity.
Computers store most decimal numbers with tiny inaccuracies, so a sum that should be exactly 12 can come out a fraction below it. Where a result has to be a whole number, such as a count of appointments or clients, the calculation includes a small guard so that rounding up or down does not land on the wrong side because of that inaccuracy. These cases are covered by the tests.
Site checks on every build
Alongside the calculator tests, an audit test builds the real site and inspects the output. It fails the release if:
- any internal link points to a page that does not exist;
- a calculator page is missing a required block: the definition, the formula, the privacy answer in its questions or the related tools;
- a headline is longer than 60 characters, or two pages share a title;
- the sitemap lists a page that was not built, or lists the post-purchase thanks page;
- a block of workbook suggestions shows more than three kits, or a tool's pinned workbook is not shown first.
Review dates and corrections
Each calculator and guide shows a "last reviewed" date. It is the date on which the explanation, the formula and the links on that page were last checked against the tested code. It does not mean the page was rewritten on that day.
When someone reports a possible error through the contact page, we run the reported inputs through the calculator's module. If the result is wrong, the formula is fixed, a test for the reported case is added so it cannot come back, and the reviewed date is updated. If the result is right but the page made it hard to understand, the explanation is rewritten instead. Either way we reply with what we found.
Privacy by construction
Every calculation runs in your browser. The numbers you type are not sent to a server, are not stored and are not seen by us. There are no accounts to create. This follows from how the calculators are built rather than from a setting that could be switched off. The privacy policy explains what the site does record, such as anonymous page views and advertising.