Decide where the work belongs
Describe the comparison risk
Show a current window with fewer elapsed days or different weekdays than its reference and identify the decision that could change. Use observed dates and included rows, not a forecast of eventual performance. Record whether the reader sees a to-date or completed-period label.
Compare correction paths
Evaluate a completeness badge, equal-length window, same-weekday alignment, and a blocked comparison until close. For each path, list user wording, historical continuity, filter behavior, export context, and owner approval. Preserve a monitoring option when partial data is the intended question.
Choose the next queue action
Select one action: define the comparison basis, correct period selection, label partial status, or split live and historical views. Attach edge fixtures and a revisit trigger for calendar or reporting-policy changes. Leave chart scale and baseline concerns separate from period completeness.
What to carry forward
Prioritization is complete when one partial-period action has an owner, decision consequence, evidence threshold, and revisit trigger. Escalate a shared comparison change only after the alignment rule is agreed; otherwise prioritize a visible status that lets readers judge the limitation.
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