Decision Asset · Template

KPI / Metric Dictionary Template

One source of truth for metric definitions — so dashboards stop disagreeing.

What this template is

A practical worksheet for defining KPIs consistently so reporting logic becomes easier to govern and explain.

Who it is for

Data, finance, product, and operations teams that need shared metric definitions across stakeholders.

Main outcome

Clearer KPI ownership, fewer reporting disputes, and stronger trust in dashboards and executive reviews.

Revenue in Sales ≠ Revenue in Finance

Sales counts all deals. Finance only counts revenue recognized. The dashboard shows something else. Nobody knows who's right. A metric dictionary makes them all agree.

Template columns

Metric Name

What it's called everywhere (e.g., "Active Users")

Definition

Plain-language explanation

Calculation Logic

SQL query or formula

Source of Truth

Database table or system

Owner

Team or person accountable

Last Updated

Date of last change

Notes / Caveats

Known limitations or edge cases

Example entry

Metric Name: Monthly Active Users (MAU)

Definition: Users who logged in at least once in the last 30 days

Calculation: COUNT(DISTINCT user_id) WHERE last_login_date >= CURRENT_DATE - 30

Source: analytics.user_activity table

Owner: Product Analytics Team

Last Updated: 2025-01-15

Notes: Excludes internal test accounts (domain @straitworks.com)

How to build it

1

Start with top pain points

Which 10-20 metrics cause disagreement?

2

Facilitate a workshop

Bring Sales, Finance, Product, and Data together

3

Document each one

Definition, calculation, owner, source of truth

4

Enforce it in your BI tool

Lock calculations in Looker, Power BI, or semantic layer

5

Review quarterly

Add new metrics, update definitions, keep it current

Opens in Google Sheets — make a copy to customize

Common questions

What is a KPI or metric dictionary?

A KPI or metric dictionary is a governed reference that defines business metrics consistently across dashboards, teams, and reporting workflows.

Why do teams need a metric dictionary?

Teams need a metric dictionary to reduce reporting disagreements, clarify ownership, standardize calculations, and improve trust in dashboards.

What fields should a metric dictionary template include?

A useful metric dictionary template should include the metric name, plain-language definition, calculation logic, source of truth, owner, update date, and important notes or caveats.

Make all your dashboards agree

We can facilitate workshops to define your metrics consistently, then integrate them into your BI platform. Once done, every dashboard will show the same truth.

Straitworks Concierge

👋 Here to help you navigate

Good afternoon! 👋 What can I help you find?

What brings you here today?

Choose what you'd like to explore