Aglet

Verify Report Ratio Denominator Semantics

Ratio verification tests the population behind the arithmetic. Use a fixture where the numerator stays fixed while eligible rows change, then inspect a card, chart, table, and export. Confirm that labels and explanations keep pace with the formula so a mathematically correct rate is not semantically vague.

Check whether the outcome improved

  1. Write formula assertions

    Define expected numerator, eligible denominator, exclusions, zero-denominator outcome, precision, and label for every fixture. State whether repeated memberships count once or per event. A pass requires the report to reveal enough context for a reviewer to identify the population.

  2. Exercise eligibility boundaries

    Run full, filtered, excluded, and zero-eligible cases. Compare row membership, numerator, denominator, ratio, rounding, and visible wording. Inspect a period comparison and an export when they use the same measure, recording any intentional population difference.

  3. Ask a reviewer to explain it

    Have a reviewer describe who is included, what the numerator counts, and what a zero or missing rate means using the report and export alone. Preserve filter state, source revision, calculation trace, and evidence. Record a bounded result when one surface omits denominator context.

What to carry forward

Verification passes when the displayed ratio matches its documented populations and a reviewer can explain numerator, denominator, exclusions, and zero behavior. Report a bounded pass for uncovered scopes. Keep verification inconclusive if filter changes alter eligibility without an explicit label or explanation.

Technical background: Metabase documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow