The Metric Contract and Semantic Model Standard: One Definition, Known Limits and Accountable Ownership

For a metric to support a decision, people must be able to reproduce it. Agree the included records, exclusions, source transformations, reconciliation rules and action thresholds. Name the owner and control definition changes so they do not silently rewrite history.

1. The Market Connection Context

Leaders often discover the semantic problem only after two credible teams present different numbers for the same commercial question. Finance counts recognised value, sales counts booked opportunities, service counts completed cases, and product counts events. Each number can be technically correct within its own population, period, grain and exclusion rules while being unsafe for the decision in front of leadership.

The bottom-line harm is not merely reporting inconvenience. An unstable definition can redirect investment, conceal margin leakage, misstate capacity, reward the wrong behaviour, trigger avoidable customer contact or create a false signal of retention. A single enterprise glossary does not remove those risks if the calculation, lineage, exclusions, reconciliation and decision boundary remain implicit.

Business question
→ bounded metric contract
→ traceable source and transformation logic
→ reconciled interpretation and threshold
→ named human decision
→ controlled operation and change

By [decision date], the CFO will classify each in-scope metric ACCEPT WITHIN LIMIT, VALIDATE, CHANGE, RESTRICT, RETIRE or STOP USE. Acceptance applies to a named decision, population, period and version; it is not universal certification of a dataset, dashboard or team.

This guide starts after the material decision and candidate metric are known. The Measurement and Decision Intelligence Audit: An Executive Standard for Trustworthy Action inventories the enterprise data estate, The Executive Decision Inventory: Mapping Signals, Thresholds, Owners and Actions inventories decisions, The Data Maturity, Quality and Lineage Assessment: Establishing What Can Be Trusted for Which Decision tests whether data is fit for a specific use, and The Executive Reporting and Review-Cadence Standard: Turning Dashboards into Decision Systems governs executive reporting and review cadence. The Metric Contract and Semantic Model Standard: One Definition, Known Limits and Accountable Ownership defines the stable semantic contract that those activities consume. It does not design a dashboard, choose a platform, validate a predictive model or establish a reporting meeting.

Working files

• Metric Charter and Authority Register
• Metric Definition and Lineage Contract
• Metric Reconciliation and Threshold Ledger
• Metric Decision and Change Register

The W3C Data on the Web Best Practices supports machine-readable metadata, provenance, versioning and documented quality, while the W3C Data Cube Vocabulary provides a formal model for observations, dimensions and measures. The SDMX Information Model distinguishes concepts, structures, constraints and metadata for statistical exchange. The UK Government Data Quality Framework frames quality as fitness for purpose and assigns accountable roles. These are VERIFIED primary standards or official guidance. They inform controls, not a claim that one vocabulary or statistical model automatically fits every commercial metric. The Abrasim execution method below is PROPOSED.

2. The Leadership vs. Delegation Boundary

The reader recognises that durable agreement requires business facilitation, source lineage, calculation rules, exclusions, reconciliation, thresholds and governed change control.

An internal team can run this standard when it has authorised source access, a business definition owner, technical lineage owners, finance or commercial reconciliation authority, independent challenge and the ability to stop an unsafe use. Independent facilitation is justified when incentives favour one definition, historical reports conflict, supplier logic is opaque, or ownership crosses functions. Legal, privacy, security, accounting, regulatory and statistical authorities retain their mandates.

Stop when the requested metric requires fabricated history, prohibited data, concealed exclusions, unverifiable transformations, retroactive changes without versioning, or a predetermined conclusion. A technically reproducible calculation is not automatically a valid business meaning. A signed definition is not proof that the source data is fit. Resource approval remains separate from evidence classification.

3. The Step-by-Step Execution Standard

Step 01: Charter the metric decision

Purpose and decision served Name the business decision before defining the number, preventing a familiar label from becoming the scope.

Accountable owner CFO or the executive accountable for the decision.

Delegated lead and contributors Metric Steward leads with Finance, Business Owner, Analytics Lead and Independent Challenger.

Preconditions, inputs and access Accepted decision question, affected population, decision date, consequence of error and access to current reports.

Actions

1. Write one decision question.
2. State who acts, by when and on which population.
3. List candidate metrics and competing definitions.
4. Set exclusions and stop conditions.
5. Record conflicts and protected challenge.

Evidence to retain Signed charter, current reports, decision record, conflict log and evidence-access approvals.

Decision or scoring rule Proceed only when one decision and its consequence are explicit; do not rank candidate definitions by popularity.

Output and template Metric charter row in the charter and authority register.

Acceptance gate DECISION BOUNDARY ACCEPTED or RE-CHARTER.

Leadership checkpoint Executive owner confirms that the metric will serve the decision rather than justify a preferred answer.

Human control point Affected owners may challenge the population, consequence or exclusion boundary.

Failure modes and safeguards Dashboard-first framing hides the decision; require a plain-language question before a metric name.

Change, stop or escalation condition Stop if no authorised decision owner accepts the consequence of error.

Handoff to the next step The accepted charter determines the authority map.

Step 02: Establish semantic and technical authority

Purpose and decision served Separate authority to define meaning from authority over sources, transformations, controls and use.

Accountable owner CFO.

Delegated lead and contributors Data Governance Lead with Business Steward, Source Owners, Privacy, Security and Accounting authorities.

Preconditions, inputs and access Accepted charter, system ownership records, policy obligations and current approval routes.

Actions

1. Name definition, source, transformation, quality, control and decision owners.
2. Record delegated limits.
3. Identify conflicting incentives.
4. Approve access and retention.
5. Establish dissent and escalation routes.

Evidence to retain Authority register, access approvals, responsibility records, conflicts and qualified-control referrals.

Decision or scoring rule No role may self-approve a material definition and the evidence used to validate it when independence matters.

Output and template Completed authority rows.

Acceptance gate AUTHORITY COMPLETE or ESCALATE.

Leadership checkpoint CFO accepts decision rights and unresolved conflicts.

Human control point Qualified authorities can restrict access or require specialist review.

Failure modes and safeguards Assigning ownership to “data” creates no accountability; name people or accountable roles with acceptance evidence.

Change, stop or escalation condition Stop if source access, business authority or independent challenge is absent.

Handoff to the next step Authorised owners define the concept and boundary.

Step 03: Define the business concept and decision boundary

Purpose and decision served Create a meaning that a decision-maker and source owner interpret consistently.

Accountable owner Business Definition Owner.

Delegated lead and contributors Metric Steward with Finance, Operations, Customer, Product and Analytics representatives.

Preconditions, inputs and access Charter, policies, process definitions, customer terms, accounting definitions and known synonyms.

Actions

1. Write a plain-language definition.
2. Define unit, grain, population and period.
3. State inclusion and exclusion rules.
4. Define event-time and correction treatment.
5. Record related but non-equivalent terms.
6. Test examples and counterexamples.

Evidence to retain Definition workshop record, examples, counterexamples, policy references and unresolved semantic disputes.

Decision or scoring rule Accept only when the same case receives the same classification under the written rule; ambiguity is REQUIRES VALIDATION.

Output and template Business fields in the metric definition and lineage contract.

Acceptance gate CONCEPT UNAMBIGUOUS WITHIN BOUNDARY or VALIDATE.

Leadership checkpoint Business owner confirms the definition serves the chartered decision.

Human control point Finance or qualified domain authority decides material policy interpretation.

Failure modes and safeguards Circular definitions repeat the metric name; require observable events and counterexamples.

Change, stop or escalation condition Escalate when two legitimate concepts are being forced into one metric.

Handoff to the next step The bounded concept becomes a calculation contract.

Step 04: Specify calculation, exclusions and edge cases

Purpose and decision served Translate meaning into reproducible rules without losing commercial context.

Accountable owner Analytics Lead.

Delegated lead and contributors Analytics Engineer with Business Steward, Finance Analyst and Source Owners.

Preconditions, inputs and access Accepted concept, sample records, source schemas, calendars, currencies and correction policies.

Actions

1. Define numerator and denominator.
2. State aggregation and weighting.
3. Declare null, duplicate, refund, reversal and late-arrival treatment.
4. Define time zone, calendar and currency.
5. Specify segment rules.
6. Create test cases for boundaries.

Evidence to retain Formula, executable or pseudocode logic, exclusion table, edge-case tests and versioned sample outputs.

Decision or scoring rule Every exclusion must have a business reason and material exclusions must be visible beside the metric.

Output and template Calculation and exclusion fields in the contract.

Acceptance gate CALCULATION REPRODUCIBLE or RETURN.

Leadership checkpoint CFO accepts treatments capable of changing the decision.

Human control point Definition owner approves semantic choices; engineering cannot settle them by implementation convenience.

Failure modes and safeguards Hidden filters create false agreement; enumerate exclusions and retain counts where lawful.

Change, stop or escalation condition Stop when required source elements do not exist and no bounded proxy is authorised.

Handoff to the next step Calculation fields define the lineage evidence required.

Step 05: Trace source-to-metric lineage

Purpose and decision served Make every material input and transformation inspectable from originating event to metric output.

Accountable owner CIO.

Delegated lead and contributors Data Engineer with Source Stewards, Process Owners, Analytics Engineer and Metric Steward.

Preconditions, inputs and access Calculation contract, schemas, transformation code, orchestration records, manual files and override procedures.

Actions

1. Map source events and authoritative systems.
2. Record grain and keys.
3. Trace joins, filters and derived fields.
4. Include manual adjustments and spreadsheet stages.
5. Identify loss, duplication and meaning changes.
6. Link code and evidence versions.

Evidence to retain Lineage map, source extracts, transformation references, manual-control evidence and identified gaps.

Decision or scoring rule Unknown material lineage is not inferred as correct; classify it REQUIRES VALIDATION.

Output and template Source and lineage fields in the contract.

Acceptance gate MATERIAL LINEAGE TRACEABLE or RESTRICT USE.

Leadership checkpoint CIO confirms technical ownership and gaps.

Human control point Source owners attest origins; a generated diagram cannot approve accuracy.

Failure modes and safeguards Tool lineage omits manual work; interview operators and inspect actual handoffs.

Change, stop or escalation condition Stop use when an untraceable stage can materially alter the reported value.

Handoff to the next step Traceable lineage enables controlled reconciliation.

Step 06: Reconcile competing totals and meanings

Purpose and decision served Explain differences among legitimate sources without forcing false numerical agreement.

Accountable owner CFO.

Delegated lead and contributors Finance and Analytics Leads with source owners and Independent Challenger.

Preconditions, inputs and access Metric contract, lineage, comparable extracts, historical reports and adjustment records.

Actions

1. Align population, period, grain and unit.
2. Reproduce each total.
3. Build a difference bridge.
4. Classify timing, scope, event and error differences.
5. Retain unexplained variance.
6. Decide whether metrics are reconcilable, related or non-equivalent.

Evidence to retain Reconciliation ledger, source totals, difference bridge, explanations, contradictions and approvals.

Decision or scoring rule A difference is accepted only with evidenced cause and owner; tolerance does not erase a semantic difference.

Output and template Reconciliation rows in the reconciliation and threshold ledger.

Acceptance gate DIFFERENCES EXPLAINED WITHIN LIMIT or VALIDATE.

Leadership checkpoint CFO decides which definition serves which decision.

Human control point Independent challenger may retain a minority interpretation.

Failure modes and safeguards Forcing one total can destroy legitimate meanings; preserve non-equivalent contracts where decisions differ.

Change, stop or escalation condition Escalate unexplained material variance or suspected manipulation.

Handoff to the next step Reconciled meaning supports segment and comparability tests.

Step 07: Test comparability, segmentation and aggregation

Purpose and decision served Prevent a stable total from hiding incompatible groups or invalid comparisons.

Accountable owner CDO.

Delegated lead and contributors Analytics Lead with Domain Stewards, Finance and Risk.

Preconditions, inputs and access Reconciled contract, relevant segments, historical versions and decision populations.

Actions

1. Test material subgroups separately.
2. Check denominator stability.
3. Identify composition changes.
4. Test whether aggregation preserves meaning.
5. Record comparability breaks.
6. Define restatement or annotation rules.

Evidence to retain Segment tests, denominator analysis, comparability notes, restatement decisions and limitations.

Decision or scoring rule Do not average away a material subgroup failure or compare periods across an undocumented definition break.

Output and template Comparison and contradiction rows in the reconciliation ledger.

Acceptance gate COMPARABLE WITHIN STATED LIMIT or ANNOTATE / RESTRICT.

Leadership checkpoint Decision owner accepts which comparisons remain valid.

Human control point Affected domain owners can challenge aggregation that conceals harm or service failure.

Failure modes and safeguards Simpson-like composition effects mislead totals; publish material segment context beside the result.

Change, stop or escalation condition Stop comparative use when population or definition change cannot be bounded.

Handoff to the next step Accepted comparability limits inform thresholds.

Step 08: Define thresholds, actions and guardrails

Purpose and decision served Connect observed metric states to human action without turning a number into an automatic decision.

Accountable owner Business Decision Owner.

Delegated lead and contributors Metric Steward with Finance, Operations, Risk and Analytics.

Preconditions, inputs and access Validated baseline, variance evidence, risk appetite, operating capacity and decision rights.

Actions

1. Define baseline and uncertainty.
2. State trigger, caution and stop conditions.
3. Name the action and authority for each.
4. Add customer, risk and capacity guardrails.
5. Define confirmation evidence.
6. Set expiry and exception routes.

Evidence to retain Threshold rationale, baseline evidence, action matrix, guardrails, approvals and exception records.

Decision or scoring rule Thresholds prompt an authorised review; they do not automatically prove cause or prescribe action.

Output and template Threshold rows in the reconciliation and threshold ledger.

Acceptance gate THRESHOLD AND RESPONSE AUTHORISED or BASELINE REQUIRED.

Leadership checkpoint Executive owner accepts action burden and false-positive risk.

Human control point Named authority confirms context before material action.

Failure modes and safeguards Arbitrary targets invite gaming; require evidence, guardrails and review.

Change, stop or escalation condition Suspend threshold use after structural definition or population change.

Handoff to the next step The complete contract can be challenged and accepted.

Step 09: Challenge the complete metric contract

Purpose and decision served Test whether another competent person can reproduce the metric and understand its limits.

Accountable owner Independent Challenger.

Delegated lead and contributors Reviewer with Metric Steward, Finance, Engineering and affected business owners.

Preconditions, inputs and access Draft contract, source evidence, lineage, reconciliations, tests and thresholds.

Actions

1. Reproduce sample outputs.
2. Test counterexamples.
3. Trace exclusions.
4. Challenge competing definitions.
5. Inspect threshold logic.
6. Record dissent and unresolved evidence.
7. Test consumer comprehension.

Evidence to retain Reproduction results, challenge log, defect list, dissent, corrections and residual limitations.

Decision or scoring rule Material failed tests block acceptance; minor limitations require visible disclosure and owner.

Output and template Challenge and disposition rows across the contract and ledger.

Acceptance gate DECISION-FIT, CONDITIONAL or RETURN.

Leadership checkpoint CFO reviews unresolved contradictions rather than a summary score.

Human control point Independent reviewer can block a misleading contract.

Failure modes and safeguards Review by the original builder confirms assumptions; require separation where material.

Change, stop or escalation condition Escalate evidence suppression, non-reproducibility or unresolved material semantic conflict.

Handoff to the next step Challenge evidence informs executive disposition.

Step 10: Make the metric disposition

Purpose and decision served Give the metric a bounded human-authorised status for the chartered decision.

Accountable owner CFO.

Delegated lead and contributors Metric Steward prepares; executive owner decides with CDO, CIO and domain authorities.

Preconditions, inputs and access Complete contract, challenge evidence, limitations, dissent and resource implications.

Actions

1. Review definition and evidence boundary.
2. Confirm unresolved limitations.
3. Select ACCEPT WITHIN LIMIT, VALIDATE, CHANGE, RESTRICT, RETIRE or STOP USE.
4. Record conditions and resources separately.
5. Name owner and expiry.

Evidence to retain Signed decision, evidence references, conditions, dissent, funding record and review date.

Decision or scoring rule The executive selects a disposition; no composite confidence score substitutes for judgement.

Output and template Decision row in the metric decision and change register.

Acceptance gate DISPOSITION RECORDED or RETURN.

Leadership checkpoint CFO owns the final bounded use decision.

Human control point Qualified control authorities retain veto within their mandates.

Failure modes and safeguards “Approved” can imply universal fitness; record decision, population, period, version and limits.

Change, stop or escalation condition Stop if leadership will not accept an owner, limitation or expiry.

Handoff to the next step Accepted status proceeds to consumer impact and version control.

Step 11: Version, communicate and control change

Purpose and decision served Prevent semantic drift and silent rewriting of historical decisions.

Accountable owner CDO.

Delegated lead and contributors Metric Steward with Analytics Engineering, Report Owners, Finance and Communications.

Preconditions, inputs and access Disposition, consumer inventory, deployment controls, history and rollback capability.

Actions

1. Assign effective version and date.
2. Classify breaking and non-breaking changes.
3. Identify consumers.
4. Assess historical comparability.
5. Approve migration, annotation or restatement.
6. Communicate before effect.
7. Retain rollback and prior versions.

Evidence to retain Change request, impact analysis, approvals, consumer notices, migration evidence and version archive.

Decision or scoring rule A change affecting meaning, population, calculation, exclusion or threshold requires renewed human acceptance.

Output and template Change rows in the metric decision and change register.

Acceptance gate CHANGE CONTROL ACTIVE or DO NOT RELEASE.

Leadership checkpoint CDO confirms affected decisions and reports have named owners.

Human control point Decision owners approve impact; engineering release alone cannot authorise semantic change.

Failure modes and safeguards Overwriting a query destroys comparability; retain immutable definitions and effective dates.

Change, stop or escalation condition Rollback when deployment diverges from the accepted contract or consumers cannot interpret the break.

Handoff to the next step Controlled release transfers to operating ownership.

Step 12: Transfer ownership and review operation

Purpose and decision served Keep definition, lineage, reconciliation, threshold and consumer controls alive after release.

Accountable owner Business Definition Owner.

Delegated lead and contributors Metric Steward with Source Owners, Analytics Operations, Report Owners and Decision Owner.

Preconditions, inputs and access Released version, monitoring evidence, incident routes, consumer inventory and review schedule.

Actions

1. Obtain owner acceptance.
2. Monitor source and transformation changes.
3. Run reconciliations.
4. Review exclusions and threshold performance.
5. Log consumer challenges.
6. Renew, change, restrict, retire or stop the contract.
7. Hand accepted metric semantics to The Executive Reporting and Review-Cadence Standard: Turning Dashboards into Decision Systems where executive reporting is required.

Evidence to retain Handover, operational tests, incidents, reconciliation history, review decisions and retirement evidence.

Decision or scoring rule Continue only while the version remains reproducible, decision-relevant and within accepted limits.

Output and template Completed decision and change register with operating review.

Acceptance gate OPERATING OWNERSHIP ACCEPTED or RETURN.

Leadership checkpoint CFO confirms the next review and escalation route.

Human control point Operating and decision owners may stop use when the contract no longer represents reality.

Failure modes and safeguards Static catalogues decay; connect review triggers to actual source, policy, market and decision changes.

Change, stop or escalation condition Re-charter after a material change to decision, population, source, meaning, calculation, threshold or authority.

Handoff to the next step The Executive Reporting and Review-Cadence Standard: Turning Dashboards into Decision Systems may consume only the accepted version and its visible limitations.

4. The Evidence & Measurement Checklist

Preflight and authority

• One material decision and consequence of error are named. Evidence: metric charter. Owner: CFO.
• Population period grain and unit are bounded. Evidence: decision boundary. Owner: Business Definition Owner.
• Definition source transformation and use authorities are separate. Evidence: authority register. Owner: CDO.
• Sensitive access and retention are authorised. Evidence: access approval. Owner: Privacy Authority.
• Conflicts and protected challenge routes are recorded. Evidence: conflict log. Owner: CFO.

Evidence access and quality

• Every material source element has an authoritative origin or visible gap. Evidence: lineage contract. Owner: Source Owner.
• Manual adjustments and overrides are traceable. Evidence: transformation evidence. Owner: Process Owner.
• Extracts retain population period grain and version. Evidence: evidence manifest. Owner: Analytics Lead.
• Contradictions and failed records remain retained safely. Evidence: reconciliation pack. Owner: Data Steward.
• Missing evidence has an owner and validation action. Evidence: gap register. Owner: Metric Steward.

Method execution

• The business definition uses observable events and counterexamples. Evidence: definition contract. Owner: Business Definition Owner.
• Numerator denominator and every exclusion are explicit. Evidence: calculation contract. Owner: Analytics Lead.
• Time currency null duplicate and correction rules are stated. Evidence: edge-case specification. Owner: Finance Analyst.
• Competing totals have an evidenced difference bridge. Evidence: reconciliation ledger. Owner: CFO.
• Comparability and segmentation limits remain visible. Evidence: comparison tests. Owner: CDO.

Governance, privacy, security and risk

• Purpose and access authority are evidenced separately. Evidence: control matrix. Owner: Security Authority.
• Personal or sensitive elements are minimised. Evidence: handling plan. Owner: Privacy Authority.
• Accounting or regulatory meanings route to qualified authority. Evidence: specialist approval. Owner: CFO.
• Historical versions cannot be silently overwritten. Evidence: version repository. Owner: CIO.
• Stop-use and rollback controls reach downstream consumers. Evidence: control procedure. Owner: CDO.

Deliverables and acceptance

• Charter contract ledger and decision register reconcile by stable IDs. Evidence: artefact cross-reference. Owner: Metric Steward.
• Another competent person can reproduce sample outputs. Evidence: reproduction test. Owner: Independent Challenger.
• Material limitations appear beside the accepted meaning. Evidence: acceptance pack. Owner: CFO.
• Minority conclusions and rejected definitions remain visible. Evidence: dissent log. Owner: Independent Challenger.
• Each accepted metric names one accountable business owner. Evidence: decision register. Owner: CDO.

Measurement

• Each operating measure has numerator denominator and exclusions. Evidence: measure contract. Owner: Analytics Lead.
• Baselines are evidenced or marked baseline required. Evidence: baseline record. Owner: Measure Owner.
• Thresholds name actions authority and guardrails. Evidence: threshold ledger. Owner: Decision Owner.
• Segment failures cannot be averaged away. Evidence: subgroup test. Owner: Risk Executive.
• Attribution and detection limits are stated. Evidence: interpretation note. Owner: Metric Steward.

Decision and handover

• The disposition names decision population period and version. Evidence: signed decision. Owner: CFO.
• Resource commitment is separate from semantic acceptance. Evidence: funding record. Owner: CFO.
• Consumers acknowledge breaking changes before effect. Evidence: consumer notice. Owner: Report Owner.
• Operating owners accept reconciliation and incident duties. Evidence: handover. Owner: CDO.
• The Executive Reporting and Review-Cadence Standard: Turning Dashboards into Decision Systems receives only an accepted metric version. Evidence: reporting handoff. Owner: Executive Reporting Owner.

Review, change and stop controls

• Review and expiry dates are recorded. Evidence: review register. Owner: Metric Steward.
• Source transformation or policy change reopens acceptance. Evidence: change trigger. Owner: CIO.
• Definition changes carry effective versions and impact analysis. Evidence: change request. Owner: CDO.
• Material reconciliation failure can restrict or stop use. Evidence: stop record. Owner: CFO.
• Retired metrics have consumer migration and retention actions. Evidence: retirement record. Owner: Business Definition Owner.

Topic-specific measurement contracts

Measure A: Contract completion for decision-critical metrics

Measure B: Reconciliation exception rate

Measure C: Unexplained metric variance age

Measure D: Decisions using the accepted metric version

Measure E: Harmful semantic drift events

Evidence classifications used in this guide

• VERIFIED: retained evidence supports the fact within the named contract and version.
• INFERRED: an interpretation remains distinguishable from source observations.
• PROPOSED: a definition, threshold or Abrasim method awaits human acceptance.
• REQUIRES VALIDATION: a material semantic, lineage or reconciliation claim is unresolved.

Source notes

1. W3C Data on the Web Best Practices: recommendation used for metadata, provenance, versioning and quality documentation; it does not establish local metric fitness; recheck at publication.
2. W3C Data Cube Vocabulary: recommendation used for observations, dimensions and measures; it does not settle business meaning; recheck version at publication.
3. SDMX Information Model: standard used for concepts, structures, constraints and metadata; applicability to commercial metrics requires validation; recheck edition at publication.
4. UK Government Data Quality Framework: official guidance used for fitness-for-purpose and accountable roles; it is not assurance of local data; recheck at publication.