Provenance: an answer should say where its data came from

The most dangerous chart is a convincing one built partly on data that is not real. A note on why analytics should label what is measured and what is modelled.

For Head of BI and Data teams

Part of: iGaming business intelligence

A chart carries more authority than it usually deserves. Rendered cleanly, with axes and a confident line, it looks like a fact whether or not the data behind it is complete, current or even real. That authority is useful when the underlying data is sound and dangerous when it is not, because a polished visual invites a decision without inviting the question that should come first: where did these numbers come from, and can I rely on them for this. Provenance is the discipline of answering that question before the chart is trusted, not after it has already shaped a decision.

Not all data in a view is equal

In a real operation, a single view often draws on inputs of different quality. Some are measured directly and current; some are estimated; some, in a preview or a new area, may be illustrative while the real feed is connected. Presented identically, these look equally solid, and a reader who cannot tell them apart may build a conclusion on the weakest input in the set. The problem is not that estimated or modelled data exists; it is legitimate and often necessary. The problem is showing it without saying so.

Label what is modelled

The honest response is not to hide the softer inputs but to mark them. A figure that is a proxy should say it is a proxy. A view that mixes measured and modelled data should keep that distinction visible, so an analyst comparing them knows they are not comparing like with like. This is unglamorous and it is exactly what separates an analytics culture that can be trusted from one that quietly launders assumptions into apparent facts. A labelled estimate is a useful input. An unlabelled one is a trap.

Unknown is a valid answer

The same discipline applies to absence. Data that is missing, incomplete or not yet connected should read as unknown, not as zero and not as fine. Distinguishing "we measured this and it is low" from "we do not have this" is one of the most valuable things an analytical system can do, because the two look identical on a chart and call for opposite responses. A tool that says it does not know, when it does not know, is more trustworthy than one that always produces a confident number, and trust is the whole point.

The credibility is the product

For an operator making real decisions on this data, provenance is not a nicety; it is the foundation everything else stands on. An answer that shows its sources, marks its estimates and admits its gaps can be acted on with appropriate confidence. An answer that presents everything with the same polish, regardless of what is underneath, will eventually be believed when it should have been questioned. The goal is not a prettier chart. It is a chart you can tell how much to trust.

A confident chart is not the same as a correct one. Provenance is how you tell them apart.

Ask Bounty about your own data.

Book a 15-minute call. We scope a pilot with your team and your data.

Book a Pilot

More from Resources

All resources