Decide where the work belongs
Identify the missing decision context
Compare the artifact with its applied filters, period, units, and data freshness. Record what readers could incorrectly infer from the missing information. Keep demonstrated context gaps separate from hypothetical delivery failures; an artifact can be delivered successfully and still fail to explain the population or time window behind its values.
Scope recurring report definitions
Find schedules that reuse the same snapshot template or omit the same parameter labels. Compare a correctly contextualized artifact as a control. Estimate reach from those recurring definitions rather than all report views, and note whether different scheduled variants produce similar-looking artifacts whose populations cannot be distinguished from their visible titles.
Assess reconstruction and clarification
Determine whether a reader can identify the schedule, generation time, and original parameters from the artifact or its supported destination. Compare this with the effort of manually reconstructing a historical result after data changes. A link to the current report only helps when it preserves or clearly explains the snapshot’s original context.
What to carry forward
Record priority with the omitted meaning, recurring definition reach, reconstruction limits, and available clarification. Assign a trigger for another indistinguishable filtered variant or missing freshness label. Keep the queue decision focused on an interpretable snapshot rather than adding more notification text that still fails to identify the underlying report context.
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