Methodology

This page explains how SnapCalc calculators are designed and what the site optimises for: practical decision support with clear assumptions.

1) Scope is intent-first

Each calculator is built to answer one specific question. This keeps inputs, outputs, and assumptions aligned to a single use case instead of trying to cover every scenario.

2) Minimal inputs, optional refinement

Most calculators start with the smallest set of inputs needed for a meaningful result. Where extra inputs improve realism or precision, they are offered as optional fields, not requirements.

3) Assumptions are explicit

When a calculator uses defaults, rounding, conversion factors, or simplified rules, the page should state that in plain language. The goal is that you can see what the output represents and when it might not apply.

4) Guardrails for invalid inputs

Calculators should handle common input problems such as missing values, invalid ranges, negative numbers where they do not make sense, and mixed units, and guide the user back to valid entries.

5) Outputs focus on decision support

Outputs are designed to be usable. This usually means the result, key intermediate values where helpful, and short context. The aim is quick clarity, not academic completeness.

6) Static and browser-based by design

SnapCalc is a static site. Calculations run locally in your browser. This keeps pages fast and reduces the need for user data collection.

Reporting issues

If you think a calculator is incorrect, the only useful report includes:

• The page URL
• The exact inputs used
• The expected result and why
• The actual result shown