Rounding and Displayed Values

Why results are formatted

Long decimals are difficult to scan, especially in a project list. PackLedge formats values for reading while keeping the calculation’s underlying quantity available for subsequent arithmetic and structured exports.

A displayed 0.66 m³ can therefore be a shortened view of a value near that number. The purchase calculation must use the actual requirement, not recover a number from the text shown on screen.

Whole-package rounding is a separate operation

Packages use a ceiling: the smallest whole number whose entered capacity covers the required quantity. That operation is different from rounding a display to a convenient number of decimal places.

With an entered yield of 0.012 m³ per bag, exactly 0.66 m³ requires 55 bags. A genuinely larger amount may require 56, even if a short display looks very similar. A computational artefact must not create the extra bag, and a real excess must not be hidden.

Unit changes should not accumulate rounding

Switching between defined measurement units describes the same underlying physical quantity. If a shortened converted display were repeatedly stored as a new measurement, successive switches could change the result.

Use the original measurement and the defined conversion for calculations. A deliberate user edit is different: it creates a new input, which should be reviewed and recalculated.

Keep precision when combining areas

A shared purchase combines compatible unrounded adjusted requirements before the final pack calculation. Summing individually rounded packages describes separate purchases instead.

For example, two requirements of 0.11 m³ with a 0.012 m³ bag yield each round to 10 bags separately. Their shared requirement of 0.22 m³ rounds to 19 bags. That difference is a purchasing decision, not an inconsistency in the volume formula.

Use the export fields to audit a result

The structured export keeps quantity, unit, specification and source-input information together. Compare the adjusted requirement with the package capacity and count, rather than comparing only the number of decimals printed in a PDF.

If a boundary result seems wrong, first check whether the inputs actually equal the boundary, whether the allowance was applied once and whether the package capacity matches. Keep the original project when investigating so the measurements and parameters are still available.

Frequently asked questions

Related guides and calculators