Your dashboard shows 99.7% uptime rounded to 100% while the SLA still failed for six minutes that month. Rounding is a communication choice, not a cleanup step. Done without rules, it becomes a lie your audience cannot audit.
Match precision to the decision
If the decision tolerates ±2%, showing two decimals on a conversion rate is noise. If you are billing per kilowatt-hour, shaving decimals costs real money. Write the decision tolerance first, then pick display decimals—not the other way around.
Example: warehouse pick accuracy at 98.4% versus target 98.0%—one decimal is enough for the standup. In the same company, freight cost per unit at $12.347 should stay at three decimals until rolled into a thousand-unit purchase order.
Round late, not early
Keep full precision in calculation columns; round only in presentation columns tied to charts or PDFs. Early rounding in intermediate steps biases totals—financial reports fought this battle decades ago with "penny drift."
When you must round mid-chain, store both the rounded and unrounded totals for any line that crosses a threshold (bonus gates, SLA credits, compliance limits).
Significant figures for mixed-scale data
Multiplying a 3.2 m board by 12 boards is fine at two significant figures in the length if both numbers are measurements. Do not show six decimals because the spreadsheet allows it. Significant figures discipline stops faux precision after unit conversion.
Use a Number Rounding Calculator to test alternative rules (half-up, floor, ceiling) on the same dataset before you publish which rule the report uses.
Footnotes that earn trust
When rounding hides a cliff, footnote it: "Percentages rounded to whole numbers; sub-0.5% changes not shown." Executives prefer honest granularity limits to silent drift.
Survey and test score displays
Likert averages shown to two decimals imply precision respondents did not provide. Round to one decimal for slides, keep raw sums for analysis. When comparing class sections, use the same rounding rule or parents compare unequal displays.
Conversion rates on low traffic pages swing wildly when rounded: 1/3 visitors vs 2/6 visitors looks like a doubling when rounded to whole percents. Show denominators in the tooltip.
Dashboards versus invoices
Dashboards invite friendly rounding; invoices invite legal precision. Use two columns in the warehouse export: qty_exact and qty_display. Operations schedules pick from exact; the customer PDF picks from display. Never let the PDF column feed back into inventory without a deliberate rule.
Scientific and engineering readers expect significant figures; business readers expect currency decimals. A single global "two decimals" format in a BI tool will lie to one of those audiences—split visuals by audience instead of arguing about "correct" decimals in the abstract.
Teaching stakeholders to read footnotes
When you round 99.7% to 100%, add a one-line methods note the first time each quarter. The second time, people remember the cliff. Without the note, someone will bonus off the rounded 100 while the SLA log shows a miss.
For classroom grade exports, show both fraction points earned and percent to one decimal. Parents understand 42/50; they argue when 84% becomes 8.4% because of a shifted decimal in a mail-merge field.
Machine-readable exports
JSON feeds should carry unrounded numbers; UI rounds. APIs that round early force every downstream consumer to inherit the lie. Version the API field as "amount_exact" when you must add display rounding without breaking integrators.
Regression tests on rounding rules catch policy changes: assert that 2.5 rounds to 3 under half-up before deploy, not after finance calls angry.
Publish a one-page rounding policy PDF linked from the BI tool footer. New hires and vendors then share the same definition of "nearest cent."
Edge cases near zero
Small denominators make percent changes shout. A ticket count moving from 1 to 4 is 300% but still three tickets. Cap display or switch to absolute delta when the old value is below a threshold you publish in the methods note.
Heatmaps that color by rounded percent change exaggerate noise in low-volume regions—use minimum volume filters before coloring.
Frequently Asked Questions
Is banker's rounding always best?
It reduces bias in large datasets but confuses people expecting half-up. Pick one rule per report family and document it.
How many decimals for currency?
Display usually two for USD/EUR in summaries; keep more in internal cost models until FX conversion is final.
Can I round totals after rounding lines?
Prefer rounding lines then summing, or sum unrounded then round once for the headline—never mix without labeling which total is authoritative.
What about rounding percentages to 100%?
Pie charts that force 100% after rounding should show a note that segments were adjusted for display, or use one decimal so the need is rare.
When should I not round?
Regulatory filings, calibration certificates, and anything near a pass/fail cliff—show the measured value and the limit on the same line.
Pair display rules with change math carefully: rounding before Percent Change Calculator inputs can invent fake improvements.