Key takeaways
- Most metric disputes are definition disputes, not data disputes.
- A usable definition covers formula, grain, source, exclusions, time basis, and owner.
- Publish the dictionary where the numbers are used and link each metric to its entry.
- Version changes with effective dates so history remains interpretable.
On this page
Definitions drift because nobody wrote them down
Two teams can report the same metric with different numbers and both be right. Sales may count bookings including tax and cancelled orders; finance may count revenue net of credits and tax. The label is identical, the calculation is not, and the meeting spends its first twenty minutes on reconciliation.
A metric dictionary is the contract between the people who produce a number and the people who use it. It does not need to be elaborate. It needs to be specific enough that two analysts, working independently, produce the same result.
Record the fields that change the answer
A short template is enough. The fields below cover the decisions that most often change a result, and each one should be filled in before a metric appears on a shared report.
| Field | What it records | Example |
|---|---|---|
| Name | The label used in reports | Active customer |
| Plain meaning | One sentence a new joiner understands | A customer who bought in the last 12 months |
| Formula | Numerator, denominator, and aggregation | Distinct customer IDs with a valid invoice |
| Grain | What one row represents | One customer per month |
| Source | Table, file, or system | Sales ledger invoice table |
| Exclusions | What is deliberately removed | Internal accounts and cancelled invoices |
| Time basis | Period and date field | Invoice date, calendar month |
| Owner | Who approves changes | Commercial finance lead |
| Version | Effective date and change note | Version 3, current quarter |
Write the formula like a specification
State the numerator, the denominator, the join keys, and the deduplication rule. Name the date field that decides the period. Say how returns, credits, tax, and internal accounts are treated. If the metric is a ratio, define both sides and the rounding.
For example, active customers could be defined as distinct customer IDs with at least one valid invoice in the last twelve months, excluding internal accounts and cancelled invoices. If the customer list has 1,240 records, 180 with no invoice in the period, and 40 internal accounts, the count is 1,020. That arithmetic is a test of the definition, not a performance claim.
Decide the time and currency rules once
Most silent disagreements come from timing and currency, not from the formula. Decide whether a month is calendar or fiscal, whether the end date is inclusive, and which time zone the data uses. For a retail calendar, state the 4-4-5 rule and how the extra week is handled.
- Revenue is net of tax, discounts, and credits, unless a gross measure is explicitly named.
- Headcount is period-end active employees on a full-time equivalent basis.
- Pipeline is as at the last day of the period, not the date the report is run.
- FX translation uses the rate policy agreed with finance, stated on the page.
- Dates use the source system time zone, converted where reports cross regions.
Publish, link, and review
Put the dictionary where the numbers are used: the BI workspace, the reporting folder, or the same documentation site as the dashboard. Link every metric tile to its entry. An entry nobody can find is an entry nobody will follow.
Keep entries short enough to read in a minute. Give each metric one owner who can approve changes. Review definitions when a source system changes, when a report is rebuilt, and at a fixed interval otherwise. Record changes with an effective date so historical reports remain interpretable.
Start with the metrics that cause arguments
Do not document every number in the business. Start with the ten to fifteen metrics that are shared across teams, used in decisions, or disputed. Revenue, gross margin, active customer, churn, pipeline, conversion, debtor days, headcount, utilisation, and on-time delivery are common candidates.
- Write the definition in the words people actually use, then add the precise label.
- Show the formula in plain language and in the query language used by the team.
- State what is excluded, not only what is included.
- Test it by having two people build the metric independently and compare.
- Record the effective date and keep prior versions available.
Frequently asked questions
How long should a metric definition be?+
Short enough to read in a minute: meaning, formula, source, exclusions, time basis, and owner. A long definition is usually compensating for a messy source.
Who owns the metric dictionary?+
A finance or analytics lead maintains the structure, but each metric has a business owner who approves changes.
Should every metric be documented?+
No. Start with shared, contested, or decision-critical metrics, then expand as reports are built.
What happens when a definition changes?+
Version it with an effective date, update the reports, and keep the old version visible so historical comparisons can be explained.
Need help applying this?
Get help with Automation & Workflows.
Review the service scope or tell us what you are trying to improve. We will reply with a clear next step.
Free KPI definition templateRelated reading
Variance analysis: price, volume, and mix
Price, volume, and mix explain most revenue and margin gaps. A worked example shows how to split the variance and reconcile it to the total.
Reporting calendar: keeping packs on schedule
A reporting calendar is a dependency map. Build it backwards from the review date, set cut-offs, and measure every miss to keep packs on schedule.