Build a useful investigation brief
Freeze boundary dates
Create rows immediately before, on, and after fiscal month, quarter, and year edges. Record calendar date, fiscal label, expected inclusion, dictionary revision, and report period selected. Add one 53-week or stub case only when the source policy permits it.
Follow the period path
Capture date parsing, calendar lookup, filter predicate, grouping key, aggregate input, comparison label, chart axis, and export field. Compare the report with an independent date table. Mark the first point where a boundary row changes period or a fiscal label loses its definition.
Test one dictionary change
Replay the fixture with only the period mapping revision or selected basis changed. Compare membership, totals, labels, and exports. Treat the preferred period basis as a policy hypothesis until the reporting owner confirms whether the decision follows fiscal or ordinary calendar time.
What to carry forward
The investigation is ready when the brief identifies the date fixture, dictionary revision, first assignment divergence, affected outputs, and competing period rule. Recommend a scoped correction or label. Keep the case open when fiscal policy is not versioned or owned.
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