Keep the lesson for the next incident
Retain period exemplars
Keep fiscal month, quarter, year, stub, and extra-week fixtures with calendar dates, labels, expected members, and dictionary version. Preserve the original report output beside the agreed result. Include both fiscal and ordinary calendar views when readers compare them.
Classify recurrence causes
Review earlier incidents for unversioned calendars, copied labels, filter defaults, date lookup changes, and exports that omitted period context. Group named cases by missing definition or review cue. Avoid treating every period shift as a data error when policy intentionally changed.
Assign calendar stewardship
Make the reporting owner maintain the period dictionary and metric owners approve comparison changes. Add a review trigger for fiscal-year, week-count, or stub-period updates. State which boundary fixtures detect recurrence and which timezone or freshness questions still need separate review.
What to carry forward
The learning record is complete when it links period errors to a missing dictionary or review cue, preserves boundary fixtures, and names an owner and trigger. Keep intentional calendar revisions versioned so future readers can distinguish a policy change from accidental drift.
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