KPI Glossary: One Definition, One Owner
Two reports, two revenue figures: the definition is the problem. A KPI glossary with one definition, one owner and version notes, and Floemdata's measure catalog.

In the sales manager's report revenue is one number, in finance's report another. Both may be right: one measures gross invoices including VAT, the other net sales after returns. The meeting is spent arguing about which figure is correct. The fix is a single written definition of the measure.
What a KPI glossary is
A list that brings the company's measures together and that everyone can read. Defining a measure's formula in a dashboard is a separate job; the glossary says what the measure means and who is responsible for it.
What each row needs
- Name: the name that appears in reports, exactly. One measure never gets two names.
- Definition: in a sentence or two, what it measures, what it includes and what it leaves out (cancellations, returns, VAT, foreign-currency sales).
- Formula: which fields it is calculated from and with which aggregation.
- Owner: the person or role who decides when the definition changes; one person, not a committee.
- Source: which system and which table it comes from.
- Version and date: when the definition last changed, and why.
What happens when a definition changes
If the definition changes, past figures change too. Decide in advance: will earlier periods be recalculated with the new definition, or stay with the old one? Whichever you pick, the change date must be written in the glossary; otherwise last year's figure is compared with this year's definition and misleads.
Start small
- Begin with the ten measures most argued about in management meetings.
- For each measure, open a real report and reproduce the number from the glossary definition.
- Make the glossary reachable next to the report; a link or help panel is enough.
Where Floemdata stands
In Floemdata's Gold layer the measures are defined in one catalog in code (olculer.py): net sales, gross profit, document count and customer count, for example; the margin percentage is derived as gross profit over net sales. According to the code's own description, the compiler allows only measures in the catalog, so the dashboard and the AI layer stay bound to the same definitions.
The catalog lives inside the code. We did not find an owner, description text or version-note field for a measure, and there is no user-facing glossary screen. The history of a definition can be followed only through the code's revision history. The glossary approach in this post is not part of the product today.
To start, write the ten most argued measures in a spreadsheet and put an owner's name next to each. Questions are welcome at info@floemdata.com or via Floemdata.