Decide where the work belongs
Rank consequence by boundary
For each timezone issue, record whether it changes an event day, reporting total, sort order, retention window, or only presentation. Identify the workflows and cutoff frequency involved. A narrow midnight shift can outrank a broad display discrepancy if it changes an operational decision.
Separate policy from defect
Label each item as incorrect instant conversion, missing offset, local-date policy question, daylight-saving edge, or display formatting. Estimate the evidence needed to resolve it. Queue policy clarification before coding when two interpretations are both consistent with the stored data.
Set a reviewable queue
Choose investigate now, define business-time semantics first, implement a bounded correction, or monitor boundary samples. Name the owner, cohort, comparison output, and escalation trigger. Keep a separate priority for future events when historical conversion cannot be repaired safely.
What to carry forward
Return a queue that ranks timezone work by decision impact and resolution confidence, with policy questions visible beside defects. Every item should identify its boundary samples, affected workflow, owner, and next evidence. Treat a count of shifted rows as insufficient without knowing whether the shift changes meaning.
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