Dashboard commentary that writes itself:
what moved, and why it might matter
A dashboard shows the numbers but rarely says what they mean. People stare at a chart trying to decide if a dip is a problem or ordinary noise. An agent adds a short written note next to each metric that moved: what changed, how it compares to normal, and what might be worth checking.
A line dips. Now someone has to guess why
A dashboard is good at showing a number and bad at saying whether that number is a problem. A line dips, and whoever is looking at it has to decide on the spot. Is this dip inside the range the metric normally wanders in, or does it actually need attention? Different people reading the same chart make different calls. The same person reads it more carefully on a Monday morning than between meetings on a Thursday.
This gets worse as dashboards accumulate metrics. A team that started with five key numbers on one screen ends up with thirty across several tabs. That happens after a year of “just one more chart.” Nobody has the bandwidth to look closely at all of them every day. A metric with a genuine anomaly gets the same thirty seconds of attention as one sitting exactly where it always does. Nothing distinguishes “normal” from “worth a second look,” until a person manually checks the history.
The deeper cost is that a dashboard full of numbers without context trains people to stop really looking at it. Checking the dashboard becomes a habit rather than an analysis, after a few months of glancing at charts without time to interpret them. A real problem can sit visible on the screen for days before anyone connects the dots. Not because the data was hidden, but because nobody had the moment of attention that turning a number into a sentence would have forced.
What the note next to the chart actually says
The agent reads the same dashboard your team already looks at. For each metric, it calculates a baseline from that metric’s own history: the range it normally moves in, accounting for patterns like weekday cycles or seasonality. Every time the dashboard refreshes, the agent writes a short note next to each metric. The note says whether the current value sits inside or outside that range, and by how much, in a sentence instead of a chart to eyeball.
Sometimes a metric move correlates with another metric that also moved. A spend change lining up with a conversion shift, say, or a traffic spike lining up with a campaign launch. The commentary names the correlation as a possible explanation, with the supporting numbers shown. It states this as a hypothesis a person can accept or dismiss in seconds, never as settled fact.
The commentary lives wherever your dashboard already lives. That can be an annotation directly on the chart, if the tool supports it, or a companion summary that updates on the same refresh schedule. Nothing about the dashboard’s actual data changes. The commentary is a layer on top. It turns “here is a number” into “here is a number, and here is whether it is normal,” the part a person was previously doing manually and inconsistently.
For teams juggling several dashboards across different parts of the business, the same approach runs on each one. The handful of numbers that actually moved outside their normal range this week surface consistently, instead of depending on which tab someone happened to open first.
Where judgment still belongs to your team
Deciding whether a flagged anomaly warrants action stays with the people who own that part of the business. So does judging a correlation against context the data itself does not contain: a known one-off event, a planned change. Any decision that follows from the dashboard is theirs too. The agent explains what the numbers show. It does not decide what to do about it.
Why the commentary stays trustworthy
Every explanation shown is tied to specific, visible numbers, not a bare assertion, so a person can check the reasoning in seconds. The normal range used for each metric comes from that metric’s own real history and gets reviewed and retuned after the first couple of weeks of use. That way the commentary neither cries wolf on ordinary noise nor stays quiet on something that genuinely moved. Access to the underlying data stays read-only and scoped to the dashboard being commented on.
Price and timeline
| Option | Price | What it covers | Timeline |
|---|---|---|---|
| Single automation | from $500 | One dashboard, written commentary on each key metric, refreshed with the dashboard | 3 to 8 days |
| Department package | from $2,500 | Commentary across several dashboards plus weekly plain-language reports for the team | 2 to 4 weeks |
Running cost is usually $10 to $40 a month in model usage depending on dashboard refresh frequency and metric count, with a budget cap set before launch.
Related
This is the always-on companion to weekly reports in plain language, which rolls the same kind of analysis into a scheduled narrative. It depends on the same clean, joined data that data cleaning and deduplication is meant to guarantee underneath it. See the automation-everything overview and the AI agents service page for the full catalogue. The two-brand analytics warehouse with an AI analyst in Telegram answers exactly this “is this normal” question on demand. It shows how much a correctly joined baseline changes what a metric move actually means.
If your dashboard has thirty metrics and nobody has time to read all of them every day, get in touch. We will show you what commentary on top of it would actually look like.
Tired of doing this by hand? We can take the whole routine off your team, not only this step: Routine takeover, from $400 →
FAQ
How much does dashboard commentary automation cost?
From $500 to add written commentary to an existing dashboard with a defined set of metrics. Covering several dashboards or adding cross-metric explanations across a wider data model is $1,200 and up.
How long does setup take?
3 to 8 days, most of it spent establishing what a normal range looks like for each metric from its own history. The commentary should not flag ordinary variation as something noteworthy.
Which dashboard tools does it connect to?
Looker, Metabase, Power BI, Tableau or a custom dashboard built on your own warehouse. We connect through a direct database read, an API, or an export the dashboard already generates.
What if the AI's explanation for a metric move is wrong?
Every explanation is phrased as a hypothesis tied to the specific correlated data that supports it, not a confident claim. The underlying numbers are always visible next to the commentary, so a person can judge whether the explanation actually holds up.
Does this expose our dashboard data anywhere else?
The commentary reads from your dashboard or warehouse through a scoped, read-only connection and writes back only into the dashboard or the companion summary you choose. No separate copy of the underlying data is kept outside that pipeline.