Solutions/Business Glossary
Stop settling arguments in meetings. Settle them in the glossary.
"Active customer," "revenue," "churn." Ask three teams and you'll get three different numbers, pulled from the same warehouse. dScribe gives every metric one agreed definition, and puts it exactly where the question comes up, not in a wiki nobody opens.
- Every meeting starts with “whose number is right” instead of what to do about it. The same argument, different room, every week.
- Nobody owns keeping a definition current. So it drifts quietly until someone finally notices the dashboard is wrong.
- One disputed number is all it takes for people to stop trusting the dashboard and start asking around.
How it works
Define it, approve it and keep its history.
Create the business term, assign an owner and route it for review. Once approved, connect it to the datasets and reports that use it, with changes kept in a traceable history.
Multilingual
One definition, in every language your teams work in.
European organisations rarely run on one language. When "active customer" is defined only in English, local teams translate it themselves and the meaning drifts again. In dScribe, each term carries its approved definition in every language you operate in, linked to the same owner, the same history and the same connected assets.
- One governed meaning per term, shown in the reader's own language.
- Translations follow the same review and approval workflow as the original.
- Search, BI extensions and MCP-connected assistants return the same term in any supported language.
How dScribe helps
Manage the definition once, then make it easy to retrieve.
One number, not a dozen local versions of it.
Every business term, metric and KPI gets one clear, agreed definition instead of a dozen local variants.
Use the approved definition without hunting for it.
Find it through dScribe search, surface it in a supported BI extension, or make it available to chatbots and agents through the MCP server.
An answer in seconds, not a Slack thread to the one analyst who knows.
Type a plain-language question and get pointed straight to the right metric, owner and any calculation attached to the term.
A glossary that can't go stale without someone noticing.
Definitions link back to their underlying datasets and reports, so it reflects what's actually in production, not what was true at the last documentation sprint.
The foundation
Everything else dScribe does, starts here.
The glossary is what makes governance enforceable and what gives your semantic layer for AI a consistent, business-approved vocabulary to draw from.
Day to day
The person who asks gets the answer.
Type "what's our definition of active customer?" into search and get back the exact governed definition, Active user: users with 1+ activity, read or update, together with its owner and any calculation attached to the term. The same approved definition can also appear through a supported BI extension or an MCP-connected assistant.
What it's worth
What changes when everyone means the same number.
Give every metric one true meaning.
Twenty minutes, your own metrics, harmonized.
What people usually ask at this point.
Who approves a definition when teams disagree?
Each term has a named owner and review workflow. Teams can propose changes, but the accountable owner approves the shared definition and the decision remains in its history.
Can we bring in definitions we already maintain?
Yes. Existing definitions can be brought together and connected to the datasets, columns and reports that use them, rather than being recreated from scratch.
Where can people find an approved definition?
They can retrieve it through dScribe search, supported BI extensions, APIs or an MCP-connected assistant. Every surface uses the same governed definition.