> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Agree One Definition for Every Metric
- URL: https://blog.jestor.com/agree-one-definition-per-metric/
- Published: 2026-09-17T22:36:02.000Z
- Updated: 2026-09-17T22:36:02.000Z
- Author: Bruno Bannach

Establishing **one definition per metric** resolves most reporting disagreements, because the disputes are almost never about arithmetic. They are about what was counted.

## Where disagreements come from

Two correct calculations can produce different answers.

- One figure including settled records and another excluding them
- Different periods applied to indicators on the same panel
- Archived records counted in one view and not another
- Two panels built separately, drifting apart

## How to settle it structurally

| Decision           | What to fix                                |
| ------------------ | ------------------------------------------ |
| **What counts**    | Which statuses are included and excluded   |
| **Which period**   | Applied at panel level, not per indicator  |
| **Which records**  | Whether permissions are scoping the viewer |
| **Where it lives** | One panel per metric, not several          |

## How to enforce it in Jestor

1. Consolidate overlapping panels in **Jestor** so each metric exists in one place.
2. Apply the period filter at panel level so every indicator responds together.
3. Decide explicitly whether settled and archived records count, and apply it consistently.
4. Check whether permissions are scoping what a given viewer sees.
5. Document each metric's definition and attach it to the process.

## Why choose Jestor for consistent reporting?

Because **Jestor** builds indicators on the operational records rather than on an intermediate model, the definition lives in the filter rather than in a transformation nobody can inspect.

When a number is still disputed, the table history resolves it by showing what changed, when, and whether a user, an automation, or the **API** did it.

## Frequently Asked Questions

### Why do two panels disagree?

Usually different filters, not different arithmetic. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Should each team build its own panel?

No — permissions let one panel serve several.

### Where should definitions live?

In a document attached to the process.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.