A meeting ends with agreement about a KPI. Someone updates a glossary. Three months later a new report uses another interpretation, and nobody knows whether that difference is deliberate. The definition was recorded, but the decision was not kept connected to the work.
Keep the scope attached to the definition
The same label can legitimately mean different things in different contexts. Record grain, time treatment, filters, exclusions, units and effective dates. If a finance definition differs from an operational one, name the distinction rather than flattening it into a false universal answer.
Preserve the decision, not just the final sentence
- The source calculations and evidence reviewed.
- The accountable owner and the approval record.
- The reason one interpretation was adopted.
- Known exceptions and unresolved questions.
- The reports and implementations expected to use it.
Review changes against the agreement
A new query or dashboard should not silently change the meaning of a published metric. Compare the intended definition with the implementation evidence available. If evidence is missing, leave the result unknown. If the business intentionally changes the definition, preserve the old version and record the new agreement.
Check the logic and the actual results
Review the measure, filters and grain, then compare actual results over an agreed period. Define the data access, validation cases, tolerances and explanation of intentional differences. Keep the evidence behind both the calculations and their outputs.
Make the next review easier
Keep evidence and decisions connected so a later review can begin from the previous reasoning. Use monitoring and review triggers around important changes to bring the right issue back to the accountable owner. The operating habit matters as much as the document.