A manager asks an AI assistant: What was revenue last quarter by product group? Within a minute there is a live chart. An hour later a colleague asks the same question, worded a little differently, in another tool. The number is not the same. Nobody made a calculation error. There were simply questions nobody ever settled: what a customer is, when a discount counts, what a financial period is and how products are grouped.

This is an illustrative scene, not a promise about speed. The problem is not the chart. It is the meaning behind the question.

AI dashboards make the visible part easier

Anthropic describes interactive dashboard creation with Claude as a beta feature.1 That can shorten the path from a question to an initial visualisation. A first picture helps people explore patterns and formulate follow-up questions.

But the dashboard is the last, visible piece of a long chain. Making it easier to build says nothing about whether it is right. Datahub builds AI dashboards too. The central question remains what sits underneath: which data, agreements and calculations make the answer defensible?

A chart is an answer with a face. The foundation decides whether the answer is right.

Business questionPeriod and scope made explicitAgreed definitionKnown version and ownerApproved calculationSources, filters and permissions appliedVerifiable answerFigure, explanation and lineage togetherFrom business question to verifiable answer: meaning, calculation and lineage belong together.

Establish meaning and ownership

Meaning. What is a customer? When does a discount count? Which transactions belong to a financial period? A semantic layer records business definitions and calculation rules so connected applications can use the same agreements.

That layer does not automatically guarantee equal numbers. Definition versions, scope, sources and permissions must also be applied consistently. Revenue including returns differs from revenue excluding them. A difference can be legitimate, provided its reason is visible.

Ownership. Every definition, source and calculation needs a named accountable owner. Who decides when there is ambiguity? Who approves a change? Who explains what that change means for existing reports?

Ownership also concerns control and portability. Definitions and rules should not remain hidden inside one dashboard or prompt. Establish how they can be maintained, exported and reused. Self-hosting alone does not establish data sovereignty or safety; access, operational responsibilities and contractual arrangements still need scrutiny.

Make trust and governance testable

Trust. A convincing number is not necessarily a verifiable number. An answer should be traceable to its source, filters, calculation and definition. Anthropic describes showing the underlying query for charts in Claude.1 That supports inspection, but does not prove that the query follows the organisation’s agreed meaning.

For known, repeatable questions, answers should come from controlled retrieval and approved deterministic calculations. The language model can verbalise the result. That explanation still needs evaluation: does it preserve the unit, period, scope and relevant limitations?

Governance. Who may see which data? Who may change definitions? What gets recorded? These rules belong in the underlying data platform and must be enforced and tested across every connected application.

An AI interface is not automatically safe because access rules exist somewhere underneath it. Check what happens in summaries, exports and follow-up questions too. Changes to permissions or definitions should trigger the relevant checks again. Governance is an operating responsibility, not a label attached to a platform.

04Every connected applicationDashboard, colleague or AI03Meaning and calculationsShared agreements, version and scope02Access and auditEnforce permissions, record each step01Sources and ownershipAccountability for data and rulesShared definitions work only when sources, access and ownership are also governed.

Frequently asked questions

Five questions to ask today

  1. Who owns the definitions of customer, discount, financial period and product group, and where are they documented?
  2. If two people ask the same question in different tools, do they get the same number when scope and permissions match?
  3. Can every dashboard number be traced to its source, intermediate steps and the definition the organisation agreed on?
  4. Is access managed centrally in the data platform, and do all connected tools enforce those rules?
  5. If the organisation switched AI or BI tools next year, could its definitions, lineage and rules move with it?

List the uncertainties. Then review one repeatable question with the definition’s owner and check its answer from source to chart. That creates a concrete starting point without requiring every unresolved issue to be solved at once.

The dashboard shows it. The foundation makes it true.