Decide where the work belongs
Show the decision exposure
Use a date near a fiscal boundary to demonstrate which quarter, month, or year changes and which report decision follows it. Record actual included rows and labels. Do not infer impact from a familiar period name or assign an unsupported forecast to the next period.
Compare correction paths
Evaluate correcting the fiscal lookup, exposing calendar and fiscal labels together, and splitting reports with different period bases. For each option, list historical continuity, filter behavior, exports, fixtures, and owner approval. Keep a clarification path for unsettled stub or 53-week rules.
Set the queue action
Choose one bounded action with an evidence threshold and revisit trigger: update the dictionary, correct assignment, or clarify the report label. Attach the boundary fixture. Leave date freshness, timezone display, and chart scale as separate items unless the comparison proves they are the first fault.
What to carry forward
Prioritization is complete when one fiscal-calendar action has an owner, decision consequence, fixture, evidence threshold, and review trigger. Escalate shared period changes only after the dictionary is agreed; otherwise keep the correction at the specific report boundary.
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