Aglet

Triage Partial Period Report Comparisons

Partial-period triage asks whether current and reference windows cover comparable time. Inspect start and end boundaries, elapsed units, available rows, and the report's completeness signal. Preserve one case where the current period is still open, because a changing numerator can look like a trend when the denominator is calendar time.

Establish what is happening

  1. Map both windows

    Write the current and reference start, end, timezone or calendar basis, expected duration, and completion state. Record rows by day or unit around each edge. Include a fully closed comparison and one open window so the report's behavior can be contrasted.

  2. Trace period selection

    Follow controls through date predicates, aggregation, comparison arithmetic, narrative text, and chart labels. Compare included records at each boundary and note where partial status disappears. Preserve refresh time and source revision because a current window may legitimately change between views.

  3. Bound affected decisions

    List cards, charts, tables, exports, alerts, and planning decisions using the comparison. Separate views that intentionally show to-date values from views that require complete periods. Ask the report owner to confirm whether equal elapsed time, equal weekdays, or closed calendars define fairness.

What to carry forward

Triage is complete when both periods, completion states, first missing boundary signal, affected decisions, and an owner are explicit. Keep the result provisional when the report never states whether a current window is complete or comparable.

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