---
title: "AI Dashboards Everywhere: Who Owns the Official Number?"
canonical: "https://www.owox.com/blog/articles/ai-dashboards-analytics-team-source-of-truth"
updated: "2026-11-02"
---

# When Everyone Builds Their Own AI Dashboard: How the Analytics Team Stays the Source of Truth

When anyone can build a dashboard in Claude or ChatGPT, the analytics team cannot own every dashboard. It can own the official numbers, the one source an official number must come from, and the sentence it says when asked to make someone else's figure match. This guide reports what 40 practitioners in two October 2026 threads said they do, shows what turned up on one governed Data Mart in our demo project, and gives the split of who owns what, the five places an agent-built number parts from the official one, and the paragraph to send upward.

[AI in Analytics](/blog/topics/ai) · Updated November 2, 2026 · 14 min read

![When Everyone Builds Their Own AI Dashboard: How the Analytics Team Stays the Source of Truth](https://cdn.owox.com/www/content-marketing-article/ai-dashboards-analytics-team-source-of-truth/thumbnail/1-27zbmf.png/public)

> If you build your own report, the numbers are yours. If it needs to be official, it comes from the governed version. But then someone asks us to help make theirs match the official one and suddenly we're QA for something we never built.
>
> \-- an analytics lead on r/analytics, October 2026

The same post ends with the question this article answers: “how do you say ‘that’s not our job’ without sounding like you’re being difficult?”

## The short answer

**You cannot own every dashboard any more. Own three things instead: a short list of official numbers, each with an owner and a date it counts from; the one source an official number has to come from; and the sentence you say when someone asks you to make their figure match.** Everything built outside that is the builder’s, and you say so without apology.

The order matters. In the two threads behind this article, 13 practitioners said the builder owns their own dashboard, and only 7 of them had an official set of numbers to point to. “It’s yours” with nothing official behind it is a shrug, and it is the position the question above comes from.

That split is not new. What is new is the volume. One commenter gets “at least one Claude vibe coded dashboards a week that are 100% wrong”, usually when a senior leader shows it off. You will not win by checking them. You win by making the official number easy to tell apart, and cheap to reach.

## What 40 practitioners said they actually do

We read every comment the scraper returned from two r/analytics threads that ask this question: one posted on 14 October 2026, quoted above, and a follow-up from 19 October asking how teams find out about agent-built numbers and check them. Of the 72 comments returned, 42 from 40 people described a practice or a position. One reader coded each against a fixed list on 2 November 2026; a comment can carry more than one code. Five of the 40 disclosed or showed a tie to a vendor in this space, and the third column leaves them out.

| What they described | People | Not vendors |
| --- | --- | --- |
| Definitions or context the AI must use: a semantic layer, documented tables, a plugin | 18 | 15 |
| “You built it, you own it”: the builder validates their own numbers | 13 | 13 |
| The AI reads only curated or approved tables | 12 | 10 |
| An explicit official set: a certified list, a “blessed” dashboard list, an official template | 10 | 9 |
| A wrong agent-built number that reached leadership or a decision | 5 | 5 |
| Every number shows its source, filters, date range and owner | 5 | 3 |
| Compare a headline number with the official one before it goes up | 5 | 3 |
| A log or check that finds agent-built numbers routinely | 4 | 3 |
| Needed, or got, a sponsor above the analytics team | 4 | 4 |
| No warehouse access for business users at all | 3 | 3 |

Three things stand out.

**“It’s yours” only works when there is something official to point to.** Thirteen people put validation on the builder. Seven of them could point to a defined official set: a list, a template header, certified definitions, governed models. The other six had a position and nothing behind it, which is the position the original poster is in.

**Almost nobody finds out first.** Only three people outside vendors described a routine way of finding agent-built numbers: a single connector that checks generated SQL against the official definitions, an audit of the jobs a shared plugin creates, and logging “the query, the tables, and the person who shared it”. The rest find out the way one commenter does: “when someone forwards a screenshot in slack asking why their number don’t match the official dashboard.”

**The cost is real and late.** Five people described a wrong number reaching a decision. The clearest: an ops team had Claude build a churn figure that “counted paused accounts as churned”, it went into a board deck, and finance caught it a month later when theirs didn’t match.

## The Turning Point

OWOX Data Marts

See your first report built in real time. _15 minutes._

1.  Connect your data warehouse
2.  Pick your metrics
3.  Get a live Google Sheets report

In the time it takes to write a ticket. Then imagine never writing that ticket again.

[Book a Demo](/book-a-call)

We'll use your actual use case

## Who owns what

The thread’s own answer, tidied into a table. The point is that each row has exactly one owner, so nobody has to ask.

| What | Who owns it | What the analytics team does |
| --- | --- | --- |
| The definition of an official number | the business owner who signs it off: finance for revenue, the head of sales for pipeline | writes it down, with the filters, the date logic and the date it counts from |
| The source an official number comes from | the analytics team | maintains it, and makes it the easiest thing for an AI assistant to read |
| A dashboard someone built for themselves | the person who built it | nothing, unless it is promoted to official |
| Why a number differs from the official one | the analytics team, once per definition | explains it once and publishes the answer, not once per dashboard |
| An exception that is legitimately different | the manager who needs it | records who approved it and why |

The last row comes from one commenter whose company tried it after managers first wanted a ban: “We set up a Slack flow where the manager validates and justifies the exception, so it’s documented instead of floating around.” The same person on the shift it produced: “We stopped QA-ing people’s reports. We own the definitions and the guardrails, and the tooling does the checking.”

Start with three or four numbers, not forty. “Publish the official definitions for the three or four numbers people fight over most, with the exact filters and date logic, and keep everything else out of scope for now,” as another reply put it. If the fight is about revenue, our guide to [reconciling three revenue figures line by line](/blog/articles/source-of-truth-your-numbers-answer-to) shows how to get to one definition. This article starts after that, when the definition exists and the dashboards keep coming.

## How to say “that’s not our job” without being difficult

Offer the explanation, not the QA. The difference is that an explanation is about the definition and happens once; QA is about their dashboard and never ends.

What people in the threads actually say:

*   **“Is it on the list?”** One analyst kept a list of verified dashboards and answered every question about another one with it: “is the dashboard in the list? If not, we don’t support it, you’ll need to contact whoever made it.”
*   **A visible mark.** Another team built an official dashboard template “so we can say that we only maintain the ones with that exact header.”
*   **A route in, at a price.** “If you want us to write or validate that dashboard there needs to be a request that is agreed upon and prioritized at our monthly analytics steering meeting.”

In your own words it can be as short as this: _“That number counts booked orders; the official one counts settled orders, as of 1 September, signed off by finance. Here is the definition. If you want yours to be the official one, here is how it gets on the list.”_

One warning from the thread, and it is fair. Doing the fix for them teaches the company it does not need you: “Cleaning up their single prompt reports only convinces people they don’t need actual analysts which is the opposite of what you want.” Explain the gap; let them rebuild.

## How you find out before the board deck does

There are three ways, and the threads describe all of them.

1.  **One door, with a log.** If the AI reaches your data through one connector, every question it asks is recorded somewhere you can read. One commenter’s team sent every business request through an MCP connector with a hook that “checks the generated SQL against the official definitions and flags deviations. The key is that the connector is the only way in.”
2.  **A receipt on every number.** “Source, fields, date range, timezone, filters. Attached to the answer itself, not kept in a separate registry,” in one commenter’s words. Then a forwarded screenshot takes a minute to check.
3.  **Ask the source who reads it.** If official numbers come from one governed source, that source can list what was built on it, by whom, and with which fields.

We tried the third on our own demo project, because it is the one people mention least.

### What we found on one governed Data Mart

Our demo project models an online store, and its documentation names settled revenue as the key revenue metric: order lines from completed orders only, with cancelled and returned orders counted as zero. It lives in the Purchases Data Mart as the field _Item Net Revenue_. The same Data Mart also holds _Item Revenue_, which counts every order line in every status. Both are described in plain words on the Data Mart.

On 2 November 2026 we listed every report built on Purchases. There were 25, created between 23 April and 21 September 2026 by six accounts, sending data to Google Sheets (22), Slack, Data Studio and Microsoft Excel (one each).

| What the reports read | Reports |
| --- | --- |
| Settled revenue only | 3 |
| Both booked and settled revenue | 10 |
| Booked revenue only | 3 |
| Every field | 1 |
| No revenue field (line items, costs, ids) | 8 |

The three booked-only reports are all called some version of “Top Selling Products: Last Month”. None is wrong. Booked value is a real number. But none is the official one, and the name does not say which it is.

So we ran the same question both ways, for October 2026:

```
{
  "data_mart": "Purchases",
  "fields": ["products_e_commerce__product_name", "line_revenue", "line_net_revenue"],
  "aggregations": [
    {"field": "line_revenue", "function": "SUM"},
    {"field": "line_net_revenue", "function": "SUM"}
  ],
  "filters": [
    {"field": "orders_e_commerce__order_date", "operator": "between",
     "value": {"from": "2026-10-01", "to": "2026-10-31"}}
  ],
  "sort": [{"field": "line_revenue", "direction": "desc"}]
}
```

This is the query as we sent it, run on 2 November 2026 on demo data; the second run sorted by `line_net_revenue` instead.

*   Booked revenue for October was **$267,817**; settled revenue was **$224,413**. The gap, $43,404, is 16% of booked.
*   **Four of the ten “top selling” products by booked revenue are not in the top ten by settled revenue.**
*   The number one product by booked revenue, at $3,657, kept $1,418 of it, 39%. Settled, the number one is a different product, at $2,398.
*   The sixth product on the booked list, at $1,711, settled at **$0**: every order for it in October was cancelled or returned.

![The ten top-selling products by booked revenue in October 2026 in the demo store, each with its settled revenue: four of the ten, including the number one at $3,657 booked and $1,418 settled and one at $1,711 booked and $0 settled, are not in the top ten by settled revenue](https://cdn.owox.com/www/content-marketing-article/ai-dashboards-analytics-team-source-of-truth/body/1-nyri6a.png/public)

Two things follow, and only one of them is good news.

The good news: on a governed source, this took one listing and two queries. Each report names its owner, its fields and its destination, so the conversation is “your report reads Item Revenue; the official number is Item Net Revenue”, not an afternoon of rebuilding someone’s logic.

The less good news: **a governed source does not stop anyone choosing the other number.** Both fields are documented, and someone still built three reports on the one that is not official. Governance makes the choice visible and the owner findable. The list of official numbers, and the habit of asking “is it on the list?”, is what makes it matter.

The listing showed one more thing worth knowing about AI-era reporting. On 5 August 2026, the same account created four reports asking for weekly revenue by category this year, within nine minutes. That is what iterating with an assistant looks like from the source’s side: drafts pile up as reports, and nobody deletes them.

## Five places an agent-built number parts from the official one

When an agent-built number lands in your inbox, check the five places two right numbers usually part:

1.  **Which field.** Booked or settled, gross or net, sessions or users. In our demo, this alone moved four products out of a top ten.
2.  **Which date.** Order date, invoice date and settlement date all give a “revenue for October”, and only one of them is the official one.
3.  **Which statuses and filters.** Test orders, cancelled orders, internal traffic, the business unit.
4.  **Which time zone and window.** “Meta reports in the ad account’s timezone, GA4 in the property’s, Shopify in the store’s. So ‘yesterday’ can be three different days.”
5.  **How old the logic is.** A query an assistant wrote weeks ago and someone copied still runs, and no longer means what the official number means.

If it matches, it can be used, and it is still not official until it comes from the official source. If it does not, label it exploratory and send back the definition. Tracing one AI answer link by link down to the rows is a longer job; [this guide traces an AI answer to its SQL](/blog/articles/ai-analytics-hallucinations-sql-traceability).

## Without a top-down rule, and where you still need one

You can start without anyone’s permission. Write the three or four definitions down. Make the official source the easiest one for an assistant to read: documented, curated, and connected. Use the list and the header. Answer every “make mine match” with the definition, once.

What you cannot do alone is make the list binding. The original poster said it plainly in a follow-up: “Without that anything we write down as a suggestion people can ignore.” The people in the threads who got further had someone above them. One VP used “some of those wild personal dashboards non technical people made as examples” to get other executives behind governance. In one company, “we found one breach in one of those dashboards and data team got full control again.” Another commenter’s advice was blunter: if you have no allies on the business side, “just wait a bit for there to be some kerfluffle with them being off and you’ll get a few.”

So prepare for that moment. When the first wrong number reaches a decision, have the list, the definition and the source ready, and ask for one thing: that anything shown to leadership comes from the list. The commenter who described getting furthest put it this way: “It did need buy-in from my manager, but not a top-down ban.”

## Where OWOX Data Marts fits

[OWOX Data Marts](https://www.owox.com/app-signup) is built for the second row of the ownership table: the one source an official number comes from. It is not a BI tool. An analyst writes each definition as SQL in your warehouse and publishes it as a Data Mart, with described fields and declared joins, in a [Data Model](/product/data-modeling).

*   **The AI asks your definitions, not the raw tables.** [AI assistants](/product/ai-assistants) such as Claude and ChatGPT reach the Data Marts through OWOX MCP for Claude and ChatGPT. It works “only with published data marts that your project role lets you see” and “cannot run arbitrary SQL”, only structured queries built from the fields a Data Mart exposes ([OWOX documentation](https://docs.owox.com/docs/getting-started/setup-guide/mcp/)). Every answer rests on SQL the analyst wrote and can read.
*   **The door has a log.** Through OWOX MCP, “every call is recorded in Run History”, in the documentation’s words: the query definition and the SQL that ran, never the row values.
*   **The source knows its readers.** Each Data Mart lists the reports built on it, with owner, fields, destination and last run: the listing this article used.
*   **Who sees what is set by the data owner.** In our demo project, finance data is “closed to business users”.

The [dashboards](/product/dashboards) people build in Claude or ChatGPT on top of it then read the same definitions as everything else.

What it does not do: decide which of two documented numbers is official, or stop someone building on the other one. That is the list, and it stays yours. Building dashboards on top of governed definitions is covered in [vibe-coding dashboards the safe way](/blog/articles/vibe-coding-dashboards).

## For the person above you: the one-paragraph version

_People across the company now build their own dashboards with AI, which is good and will not stop. The cost is numbers that disagree reaching decisions: in two public discussions in October 2026, five practitioners described wrong agent-built numbers reaching leadership or a decision, including a churn figure that went into a board deck and was caught by finance a month later. We propose three things: a list of three or four official numbers, each signed off by its business owner with a date it counts from; one source those numbers must come from, which the AI tools read; and a rule that anything shown to leadership comes from that list. Everything else stays free to build, and its builder owns it. The analytics team will explain any difference from an official number, once per definition. We need you to back the leadership rule._

## How we gathered this

*   **Threads:** “Everyone at my company can hook Claude up to source systems and build their own dashboards” ([r/analytics, 14 October 2026](https://www.reddit.com/r/analytics/comments/1x5rj3u/everyone_at_my_company_can_hook_claude_up_to/)) and “Analytics leads: how are you handling dashboards that people build with Claude or Cursor straight off the warehouse?” ([r/analytics, 19 October 2026](https://www.reddit.com/r/analytics/comments/1x9mvrw/analytics_leads_how_are_you_handling_dashboards/)).
*   **Collection:** on 2 November 2026, with a Reddit scraper. Reddit lists 69 and 42 comments; the scraper returned 72 in all, including six replies by the first thread’s author, which were not coded. Comments not returned were not read.
*   **Coding:** one reader, a fixed list of codes, more than one code per comment allowed. 66 comments from 59 people were read; 42 comments from 40 people described a practice or a position and were counted. Five commenters disclosed or showed a vendor tie, and are left out of the last column of the table. Quotes are verbatim, spelling included.
*   **Demo data:** the OWOX demo project, a synthetic online store. The report listing and both queries ran on 2 November 2026 through OWOX MCP; totals are computed by OWOX over all matching rows.

## Topics

[AI in Analytics](/blog/topics/ai)

## Related articles

[AI in Analytics · AI Analytics Agents Replace Your Backlog, Not Your Analyst · July 2, 2026](/blog/articles/ai-analytics-agent-replace-backlog)

[AI in Analytics · AI Hallucinating SQL: What It Looks Like and How to Catch It · October 14, 2026](/blog/articles/ai-analytics-hallucination-deterministic-sql)

[AI in Analytics · Trace an AI Answer to Its SQL: From Number to Source Table · October 14, 2026](/blog/articles/ai-analytics-hallucinations-sql-traceability)

[See all articles →](/blog/articles)

## Links

Pages this page links to, on this site and on docs.owox.com. Where the page has a Markdown twin, its address follows the link.

- [AI in Analytics](https://www.owox.com/blog/topics/ai) — /blog/topics/ai.md
- [Book a Demo](https://www.owox.com/book-a-call) — /book-a-call.md
- [reconciling three revenue figures line by line](https://www.owox.com/blog/articles/source-of-truth-your-numbers-answer-to) — /blog/articles/source-of-truth-your-numbers-answer-to.md
- [this guide traces an AI answer to its SQL](https://www.owox.com/blog/articles/ai-analytics-hallucinations-sql-traceability) — /blog/articles/ai-analytics-hallucinations-sql-traceability.md
- [OWOX Data Marts](https://www.owox.com/app-signup)
- [Data Model](https://www.owox.com/product/data-modeling) — /product/data-modeling.md
- [AI assistants](https://www.owox.com/product/ai-assistants) — /product/ai-assistants.md
- [OWOX documentation](https://docs.owox.com/docs/getting-started/setup-guide/mcp)
- [dashboards](https://www.owox.com/product/dashboards) — /product/dashboards.md
- [vibe-coding dashboards the safe way](https://www.owox.com/blog/articles/vibe-coding-dashboards) — /blog/articles/vibe-coding-dashboards.md
- [AI in Analytics · AI Analytics Agents Replace Your Backlog, Not Your Analyst · July 2, 2026](https://www.owox.com/blog/articles/ai-analytics-agent-replace-backlog) — /blog/articles/ai-analytics-agent-replace-backlog.md
- [AI in Analytics · AI Hallucinating SQL: What It Looks Like and How to Catch It · October 14, 2026](https://www.owox.com/blog/articles/ai-analytics-hallucination-deterministic-sql) — /blog/articles/ai-analytics-hallucination-deterministic-sql.md
- [See all articles →](https://www.owox.com/blog/articles) — /blog/articles.md