The Governed Semantic Layer Checklist
The contract a metric needs before two dashboards are allowed to show it. Twelve checks. If a metric fails any of the first four, it is not ready to be on a slide.
At a glance
- Time
- One working session per metric
- Who runs it
- The metric’s owner, and whoever builds the reports that show it
- You leave with
- The metric’s contract, written down in one place
- Whether it is ready to be on a slide
- The gaps to close before a second dashboard shows it
How it works
Read this first. Then fill it in.
Best run with the metric’s owner, and whoever builds the reports that show it.
A semantic layer is not a feature that comes with a BI tool. It is an organisational agreement: what the number means, who owns that meaning, which source may compute it, and what happens when someone wants to change it.
The four checks that bite
- A named owner with the authority to refuse a change.
- One allowed source of record, rather than whichever warehouse table is convenient.
- A written definition a new hire can apply without a hallway conversation.
- A change log. If the definition moved last quarter and nobody can say why, it is not a contract.
Eight more, where two ‘revenue’ numbers quietly become four
- Grain. The level the metric is counted at (deal, account, order line) is written down.
- Which date counts. Created, closed, booked or recognised, and in which time zone.
- Currency. Which rate applies, taken on which date, for anything not in the base currency.
- Late data. What happens when a record arrives after the period closed, and whether past numbers restate.
- Exclusions. Returns, credits, internal accounts, test data or renewals, whichever apply, listed by name.
- Known variants. Every other number people call by the same name, and how each one differs.
- Where it is used. The meetings, reports and compensation plans that depend on it.
- How it changes. Who proposes a change, who approves it, and how long the old and new versions run side by side.
Run the checklist once per metric. If it fails any of the first four, it is not ready to be on a slide: without an owner, one source, a written definition and a change log there is nothing to agree on. The other eight are where it drifts. Close those before a second dashboard shows it.
Before you run it
What does a metric need before it goes on a slide?
The first four checks: a named owner who can refuse a change, one allowed source of record, a written definition a new hire can apply, and a change log.
How long does the checklist take?
One working session per metric, with the metric’s owner and whoever builds the reports that show it.
Do we need a semantic layer tool to use it?
No. The checklist is the agreement. A tool can hold the contract once it exists, but it cannot write it for you.
The template
Check one metric. Twelve checks.
Everything you type stays in this browser tab. Nothing is sent or saved, so print it or save it as a PDF before you close the page.
0 of 12 answered
The four that bite
Fail one and it is not ready
Named owner
A named person with the authority to refuse a change.
One source of record
One allowed source, not whichever warehouse table is convenient.
Written definition
A definition a new hire can apply without a hallway conversation.
Change log
When the definition last moved, why, and who approved it.
Eight more
Where it quietly drifts
Grain
The level it is counted at (deal, account, order line) is written down.
Which date counts
Created, closed, booked or recognised, and in which time zone.
Currency
Which rate applies, taken on which date, for anything not in the base currency.
Late data
What happens when a record arrives after the period closed, and whether past numbers restate.
Exclusions
Returns, credits, internal accounts, test data or renewals, whichever apply, listed by name.
Known variants
Every other number people call by the same name, and how each one differs.
Where it is used
The meetings, reports and compensation plans that depend on it.
How it changes
Who proposes a change, who approves it, and how long old and new run side by side.
Readout
Answer the checks above and the readout appears here. A check you skip is not counted either way.
Keep going. More free templates.
- Interactive template · 90 minutes
The Decision Latency Audit
A 90-minute working session your team can run without me: pick five recurring questions, time the path from ask to trusted answer, and see where the latency actually lives.
Open the template - Interactive plan · 4 weeks
The 30-Day XP&A Reset
A four-week sequence for a finance and ops pair who are tired of reconciling last month before they can plan next month.
Open the template
Work with me
Found a number nobody owns? Bring it to a call.
A free 30-minute call with Yagnesh. You'll find out if the problem is the data, the definition or who owns it.