Aglet

Prioritize a Cumulative Reset Correction

A cumulative boundary error can make every later point look plausible while shifting the baseline. Prioritize it by the decision using the series, the number of groups or periods sharing the calculation, and the clarity of the reset policy. Keep period ordering, missing-value, and chart-axis concerns separate until evidence connects them.

Decide where the work belongs

  1. Describe the downstream risk

    Use two groups, a reset date, and a missing period to show how carryover changes a total or trend. Name the report question and audience. Record actual sequence and values rather than estimating the share of decisions affected.

  2. Compare correction paths

    Evaluate correcting the partition, defining a reset event, carrying values forward, breaking the series, or exposing separate measures. For each option, list historical impact, filters, exports, fixtures, and owner approval. Retain a clarification path when the accumulation period is a product choice.

  3. Choose a bounded action

    Queue one next step with evidence threshold and revisit trigger: document the reset, revise the calculation, or label separate series. Attach the boundary fixture. Leave chart scale and period comparison work separate if they do not explain the first reset divergence.

What to carry forward

Prioritization is complete when one cumulative action has an owner, consequence, evidence threshold, and review trigger. Escalate a shared calculation change only after accumulation and reset semantics are approved; otherwise prioritize a visible boundary statement.

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