In this guide 6 sections
A metric definition document gives every business number one page of facts: its name, formula, source system, filters, owner and refresh time. Add a line for each edge case, such as returns, credit notes and cancelled orders. Those lines end most arguments. They do it before a dashboard is built.
What goes on a metric’s page
One metric gets one page. Start with the name people say in meetings. Follow it with a one-sentence meaning that a new joiner could understand without asking anyone, and keep the wording free of jargon.
Next comes the formula. Write it with real field names, so net revenue reads as invoice total less credit notes, never “revenue after adjustments”. Then name the system and table the figures come from, so a successor can trace every number back to a row in the ledger.
- Name and one-sentence meaning
- Formula using real field names
- Source system and table
- Filters and date field used
- Owner and refresh time
Choose the date field and the grain
Most disputes hide here. Revenue by invoice date and revenue by delivery date land in different months, and the board notices at once when a sales report and a finance report disagree. Outstanding by due date and by invoice date fill different ageing buckets, so the same debtor looks current in one report and overdue in the other. Pick one date and write it down.
State the grain too. Is it counted per line, order or customer? A distinct customer count taken from invoice lines will overcount anyone who bought twice, which inflates every ratio built on it, from sales per customer to repeat rate.
Add the refresh time. A figure that updates at six each morning should say so on the page, otherwise the evening shift quotes a stale number and loses faith in the dashboard.
Write down the edge cases before they bite
Every metric has awkward records. Returns arrive weeks after the sale. A credit note may reference an invoice from the previous quarter, and an order can be cancelled after it was already invoiced and dispatched from the warehouse.
For each case, write what the metric does. Does a return reduce the month it happened or the month of the original sale, and is a cancelled order removed or shown as zero? A short rule beats a long debate.
Keep examples with real document numbers. When someone doubts the rule, point to invoice 4471 and its credit note, and show the effect on the month in two lines.
- Returns and credit notes
- Cancelled and part-shipped orders
- Test, internal and sample records
- Currency conversion date
- Records edited after month-end
Name an owner and a way to change it
Each metric needs an owner. Usually that is the head of the function that lives by the number, so finance owns outstanding while operations owns on-time delivery.
Definitions change. A new product line or a revised credit policy will force an edit, so record the date, the old wording and the reason in a version line.
Without that trail, nobody can explain why last year’s figure differs from this year’s, and the finance head ends up rebuilding old reports by hand to find out. With it, the answer takes seconds. Keep them beside the data dictionary.
Run the document past the people who argue
Gather finance, sales and the report builder. Read each page aloud, and wherever two people hear different things, rewrite the sentence until they agree.
Then test the document against one live report. Recalculate a single month by hand using only the written formula, and compare the result with the dashboard tile for the same month.
A mismatch is your first fix, and usually it is a missing filter such as test customers or an unposted batch that nobody wrote down. Book the next review now, perhaps the week after quarter close, while every owner still remembers why the page exists.
Metric definition page template
A single-page form, one per metric. Top block: name, owner and refresh time. Middle block: meaning, formula, source system, source table, date field, grain and filters, with one blank line each. The bottom block is a three-column grid of edge case, rule applied and example document number, plus a version history line.
Open a blank worksheet to printQuestions owners ask
How many metrics should we define first?
Start with the handful your management meeting actually argues about, and add more once the first set has settled and the dashboards agree with it. Eight to twelve is a workable first batch.
Where should the document live?
Somewhere everyone can read and only a few can edit, such as a shared document or a wiki page with locked permissions. Link each dashboard tile back to its page, so that readers can check the meaning in one click instead of asking the analyst.
Is this the same as a KPI target sheet?
No. The definition says how a number is calculated. Thresholds say what counts as good. Define first and set targets second, otherwise you are measuring against a moving ruler held by a different person each month.
What if two teams need different versions of a number?
Give them different names. Gross sales and net sales are two metrics. Each gets its own page, formula and owner. Dashboards then label each tile with the exact name, so nobody quotes gross sales while believing it is net, and the argument never starts. Short names beat clever ones.