Reporting Trust Glossary
What Is a Semantic Gap in Reporting?
Why it matters
Semantic gaps make reports look clearer than they are.
A dashboard may show “revenue”, “active customers”, “conversion rate”, or “pipeline” as if the term is obvious. But each label can hide different definitions, timing rules, exclusions, and source logic.
When the label and the underlying meaning drift apart, teams argue about the number instead of the decision.
What it looks like in a growing business
Semantic gaps often appear when different teams use the same word for different work.
Examples:
- Finance and sales both say “revenue” but use different timing rules.
- Product and customer success both say “active customer” but count different behavior.
- Marketing and sales both say “qualified lead” but use different thresholds.
- A dashboard says “churn” without showing whether it includes voluntary, involuntary, logo, or revenue churn.
Each team may be using a reasonable definition in context. The problem is that the context is not visible.
How to spot it
Ask people from different teams to explain the same metric without looking at the dashboard.
If the explanations differ, there is likely a semantic gap.
Also check:
- Does the metric label hide important caveats?
- Are inclusions and exclusions documented?
- Does the report show which source and timing rule it uses?
- Are related metrics easy to confuse?
- Does the business know which version is authoritative?
What to do next
Do not start by changing the chart. Start by naming the meaning.
Write a plain-English definition, list inclusions and exclusions, identify the owner, and link the metric to the decision it supports. If the number is important, turn that into a reporting contract.
For related reading, start with what to do when every team has a different version of revenue or the KPI definition template.