Decide where the work belongs
Identify the interpretation that changes
Compare the displayed total with the intended measure over a controlled dataset. Record whether readers infer a sum, average, ratio, or unique population that the report does not actually calculate. Keep observed decision consequences separate from a general preference for totals that happen to match visible-cell arithmetic.
Scope the affected measure patterns
Find pivots using the same total expression or non-additive measure. Compare additive controls and note hidden categories, filters, or row limits that change visibility. Estimate reach from those report definitions rather than all pivots, because ordinary sums and distinct counts can require different total semantics under the same layout.
Assess available explanation and alternatives
Check whether the report labels the total’s population and calculation clearly or provides a useful underlying-record view. Determine whether a definition change, computation fix, or clearer total label is needed. Include the effort readers spend reconciling a number that cannot be explained from the visible cells alone.
What to carry forward
Record priority with the affected measure, misleading interpretation, report reach, and available clarification. Assign a trigger for another non-additive or hidden-population case. Keep the queue decision tied to the intended total contract rather than forcing every report to use a visible-cell sum that may count the same underlying record repeatedly.
Technical background: Google Cloud 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