How to use this guide
Read for the decision you need to make.
A calculator is a model. Its output is only meaningful when the units, inputs and assumptions match the real situation. Use the sections below to understand the logic, then use the working sequence to turn that understanding into a concrete next step.
Use the visual and written context together; the operational decision still depends on the approved source, local conditions and accountable review.
01 · Core idea
Inputs are not facts automatically
A calculator cannot know whether an entered value is current, approved or representative. Input quality remains the user's responsibility.
02 · Core idea
Units change the answer
A correct number in the wrong unit can produce a wrong result. Keep units explicit and consistent.
03 · Core idea
Scenario values are not predictions
Use scenario inputs to explore consequences, not to imply that a future outcome is guaranteed.
Decision boundary
Know what the guide can clarify — and what it cannot authorise.
Use this guidance to structure the task, inputs and review. Product labels, SDS, technical documentation, contracts, approved SOPs and accountable human decisions remain authoritative where they apply.
Working sequence
Turn the guide into an operating sequence.
Use these steps as a compact handoff from reading back to the real task.
- 01
Check units before entering values.
- 02
Understand what the model includes and excludes.
- 03
Treat scenario inputs as assumptions, not predictions.