Capacity review case
Owner: Valegate Support operations lead.
Question: Which teams build a higher peak than their final net workload change?
Data: Fictional ordered team/day workload movements.
Done: One row per Team with PeakChange and NetChange, calculated from the full movement history.
Valegate Support logs daily changes to its outstanding workload. A positive change adds work and a negative change clears it. The operations lead needs to understand each team's peak outstanding change during the period, not just the net difference between the first and last dates. Comparing neighboring records can also expose a sharp reversal.
Keep records ordered within the team before you calculate state across rows. A previous value from another team has no meaning for this question. The workflow continues through preparation, a neighboring-row calculation, a comparison field and a running total. The final evidence table reports each team's peak cumulative change and its net change. Those are different measures, and the hidden period changes the daily sequence so one can't be substituted for the other.
input: {"source":"main"}
sort: {"fields":[{"field":"Team","direction":"asc"},{"field":"Day","direction":"asc"}]}
Worked example: Multi-row calculations depend on incoming order. Keep each team together and its days ascending.