How we check our tools

CoryVu uses several types of checks to improve accuracy and usability:

• Worked examples: selected inputs are checked against expected results.
• Automated tests: software checks help identify broken functionality and problems introduced by changes.
• Mobile and desktop checks: pages are checked in a browser, including forms, populated results and supporting content.
• Sources and assumptions: tool pages explain relevant methods, limitations and published guidance.

What these checks cover

Testing helps identify problems, but cannot cover every possible input or individual situation. Automated checks do not amount to professional certification or independent expert review.

Rates, thresholds and guidance can change. Check the sources and any applicable dates on the individual tool before relying on a result.

Source reviews and maintenance

A page build, design change or software test is not presented as a source review. We only record a source-review date when the underlying sources or rules have actually been checked; that date belongs with the relevant tool's method, sources or limitations.

We keep a dated maintenance register for published tools with changing rules, rates, reference prices or product specifications. UK employment, legal, tax and financial-rule pages are queued for review at least every 90 days. Reference prices, tariffs and product specifications are queued at least every 180 days, and currency reference rates are refreshed daily. A due review means the source needs checking; it is not a claim that the page is wrong.

The maintenance check runs weekly and reports any due reviews before a page can be described as newly source-reviewed. If a source cannot be confirmed, we correct, qualify or remove the affected claim rather than silently rolling its date forward.

Report a problem

Please send us the tool URL, the figures you entered and a description of the issue. A reproducible example helps us investigate.