Skip to content

Reconcile rounded table values without hiding raw observations

Separate display rounding from calculations and explain totals that differ after formatting.

Guides

Reconcile rounded table values without hiding raw observations — what should the operator record?

A table may display rounded values whose visible sum differs from the calculation made on full precision. That can be legitimate, but unexplained differences look like errors. Keep validated calculation inputs separate from display formatting and document the chosen rule without claiming more precision than the actual returned evidence supplies.

Practical operations check
Separate display rounding from calculations and explain totals that differ after formatting.
Record raw_value and known precision or representation before applying numeric conversion. A source-rounded value does not become more accurate when software stores many decimal places, and unknown precision should not be disguised by an elaborate display format in the derived table.
Attach calculation_revision and display_rule to the summary. Preserve actual unknown and source-limited precision states, and avoid presenting locally formatted decimal places as a guarantee of measurement accuracy, complete evidence coverage or comparability across unrelated source metrics.
01 / Guides

Inspect source precision

Record raw_value and known precision or representation before applying numeric conversion. A source-rounded value does not become more accurate when software stores many decimal places, and unknown precision should not be disguised by an elaborate display format in the derived table.

02 / Guides

Declare the rounding rule

Specify display_decimals and rounding_mode for the local artifact. State whether totals are computed from validated underlying values or displayed rounded cells, since those procedures can differ and should not alternate silently depending on which application opens the file.

03 / Guides

Test numerical edges

Use labeled fixtures around a rounding boundary and include an unavailable value. Verify the chosen parser and display path preserve unknowns and follow the declared rule, rather than allowing locale defaults or spreadsheet autoformatting to change the apparent total unpredictably.

04 / Guides

Reconcile visible totals

If rounded component displays do not add exactly to the displayed aggregate, explain that supported representation effect. Do not modify individual observations to force agreement or silently round the inputs early when the declared calculation contract requires the available validated precision.

05 / Guides

Publish the precision boundary

Attach calculation_revision and display_rule to the summary. Preserve actual unknown and source-limited precision states, and avoid presenting locally formatted decimal places as a guarantee of measurement accuracy, complete evidence coverage or comparability across unrelated source metrics.

Keep the boundaries clear.

  • Separate display rounding from calculations and explain totals that differ after formatting.
  • Operational record: Inspect source precision. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage