A useful calculator helps someone answer a specific question with information they can reasonably provide. Start by naming that question and the decision it supports. A small tool with understandable inputs and a clear next step is easier to assess than a page of numbers whose meaning is uncertain.
Describe the result before the inputs
Write a plain sentence explaining what the result represents. It might compare quantities or help somebody prepare information for a conversation. Decide whether the answer should be a whole number, a measurement or a choice between options. That decision shapes the questions the tool needs to ask.
Keep assumptions beside the result. If an allowance or a default changes the answer, show it and explain whether the user can adjust it. The customer should be able to recognise which information came from them and which came from the business.
Make units and input limits visible
Put the unit in the label. A length in metres and the same length in millimetres need consistent treatment before calculation. Give an example where the expected format could be unclear. Check what happens with an empty field, a decimal, zero and a value outside the supported range.
Luke Wroblewski's form research supports helpful feedback at an appropriate point in the interaction. MDN documents number controls with minimums, maximums and step sizes. Those controls help express allowed inputs; the calculation still needs its own checks.
Reading behind this section: Luke Wroblewski, A List Apart; MDN contributors
Explain rounding and the source of the rule
Agree how the tool handles precision. If a quantity needs whole packs, explain when it rounds up. If extra decimal places add no useful meaning, choose a sensible display precision. Keep that presentation decision distinct from the precision used in the underlying calculation.
Record who owns the calculation rule, where it came from and which version the tool uses. When the rule changes, somebody should be responsible for checking the existing examples and updating the explanation. This keeps maintenance connected to the business knowledge behind the tool.
Test the answer and the next step
Prepare a few worked examples independently of the website. Include ordinary values, limits and equivalent inputs in different units. Compare the website's answer with those examples, then check the form on a phone and with a keyboard.
Finish by checking what a customer can do with the answer. They might adjust an input, copy a result or send the relevant details with an enquiry. Carry the units and assumptions into that next step so the business receives enough context to understand the result.
Put it to use
A useful check for your business.
- Name the question and the meaning of the result.
- Label units and explain allowed inputs.
- Record the rounding rule, source and version.
- Check worked examples and the next action.
The thinking behind this guide
Sources & further reading.
Our practical interpretation, with the references below for the specific principles and further detail.
- Inline Validation in Web Forms
Specific feedback and its timing affect form usability. The research concerns registration forms, not calculator accuracy or commercial results.
- The number input element
Number inputs support minimum, maximum and step constraints. These controls do not validate a business formula or its assumptions.
