"Certified" is used loosely in data governance, usually to mean a metric someone approved once. That is not enough to be useful, and the gap shows up eight months later when two people disagree.
A metric is certified when five things are documented and one person has signed off on all of them.
The five attributes
Definition, in business language. Not the SQL. A sentence a CFO would recognize: project delivery margin is project revenue less fully loaded delivery cost, expressed as a percentage of revenue. If the definition can only be expressed as code, it has not been agreed — it has been implemented.
Grain. The level at which it is measured. Per project per month is a different metric from per client per quarter, even with identical logic. Most definitional disputes are actually grain disputes that neither party has recognized.
Source. Which system, which field. Where two systems hold a version, which one is authoritative and who decided.
Calculation. The exact logic including — and this is where the arguments live — the exclusions. Does fully loaded cost include benefits? Bench time? Unbilled overtime? Allocated overhead? Each exclusion is a decision, and undocumented decisions get remade differently by the next person.
Owner. A named individual who approved the other four.
Why the owner is the load-bearing attribute
The first four can be written by an analyst. The fifth cannot, and it is the one that makes the others hold.
Consider what happens without it. In month eight, Delivery says margin is 18% and Finance says 16%. Both are calculating correctly from their own definition. There is no document, so the meeting becomes a debate about which definition is more sensible. That debate is unresolvable, because both are defensible — and it recurs.
Now consider it with an owner. The answer is: that is the definition the Finance Director approved on 14 March, here is the record, and if it should change, that is her decision to make.
The dispute takes four minutes instead of two meetings, and it produces a decision instead of a stalemate.
The second-order effect nobody plans for
There is a benefit to certification that has nothing to do with governance.
An executive who has personally signed off a definition defends the number in meetings rather than questioning it. The act of approval creates ownership. The person becomes invested in the metric being used correctly rather than in reserving the right to dispute it later.
This is why certification sessions should not be delegated to analysts, and should not happen by email. Thirty to forty-five minutes with the named owner buys organizational commitment that no amount of documentation quality can substitute for.
The rule that gets tested
A metric without a named owner is not built as certified.
That rule will be tested — usually as "the owner is on leave, just use the old definition for now." One uncertified metric sitting in a certified catalogue undermines the credibility of every metric beside it, and it is invariably the one that gets challenged first.
Metric certification with named owners is a core deliverable of a Management Intelligence Build.