Check whether the outcome improved
Exercise boundary cases
Use a report with an unchanged source, a newly changed source, a delayed source, and no rows in the selected period. Record the visible freshness statement and the expected inclusion boundary for every case, including any rounding of displayed times.
Compare rendered and exported context
Inspect the page, table, downloaded result, and saved or shared representation used by reviewers. Confirm each retains the report period, filters, and as-of boundary needed to distinguish prepared material from current source state.
Check comparison semantics
Verify that period comparisons and change indicators use compatible data boundaries. A current period compared with a still-updating prior result can mislead even when both labels are individually accurate; capture that case in the acceptance record.
What to carry forward
Accept the freshness context when the displayed boundary matches the included data, remains understandable across delayed and empty cases, and survives the review surfaces people use. Fail it when a reasonable reader could mistake an older result for current data or compare incompatible boundaries.
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