The tolerated pain
A spreadsheet or dashboard produces the number management expects, so the reporting process appears to work. The weakness appears only when somebody asks where the figure came from, which records were included, which adjustments were made or why it differs from another report.
Operational consequence
Staff then reconstruct lineage manually: opening source exports, comparing formulas, asking the report owner and recreating transformations. That makes explanation dependent on individual memory and turns routine assurance into recurring investigative work.
Financial consequence
Measure the avoidable burden as hours spent tracing, reconciling and re-explaining recurring metrics × loaded cost of the people involved. Record decision delay separately where a disputed figure prevents action. Do not automatically translate every delay into lost revenue; only value commercial consequences that can be evidenced.
Commercial urgency
The trigger is repeated challenge without fast provenance. If a critical metric cannot be traced from presentation back to authoritative source, definition and transformation logic, management is paying both a labour cost and a control cost for uncertainty.
Resolution
Define the metric, authoritative source, transformation rules, refresh timing and accountable owner. Preserve lineage through the reporting flow, automate repeatable transformations where appropriate and make exceptions explicit rather than hidden inside private spreadsheet steps. A reader should be able to answer not only "what is the number?" but "why is this the number?"
The economic meaning
Reporting value comes from decision confidence. A figure that must be reverse-engineered before it can be trusted consumes analytical capacity twice: once to produce it and again to prove it.
Sources and method
This article uses an input-based labour model and repository-contained reporting context. It asserts no universal audit cost or financial-loss benchmark.