Completions count the item you finished, not the package it came in

Completions used to count the whole order. If an order holds ten items and your crew finished seven of them, that read as nothing finished, because the order only counts once the last item lands. A week of real work could show a two.

Completions now count each thing for the work it holds. Where an order is broken into individual pieces, each piece counts on its own. Where an order carries work directly as well, that work counts too, so an order holding three of its own steps plus one broken-out piece shows up as both. Phases work the same way. Nothing about your setup has to change for this.

The same page now counts stages completed rather than tasks. A task count moved with how many line items somebody put in a stage, so a stage built from twenty small steps buried one built from a single sign-off, and the number said more about how the route was written than about what got done. A stage is the thing your team signs off, so that's what gets counted.

Completed Stages opens up. Start at a phase, open a stage, and you get the individual items that stage was finished on, each with its date, its crew and its hours. The completions list does the same from the other direction: project, then order, then the items inside it, with each item's own estimate against its actual hours.

Exports follow what you see. Exporting a grouped table used to give you a flat list with no sign of which phase, stage or item each row belonged to. Now every row carries its full path, and the whole list comes out, not just the parts you had expanded.

The date filter gained Last Week, meaning the previous Monday through Sunday. That's a fixed week you can compare against, rather than the last seven days counting back from today.

Variance to estimate moved from Completions over to Hours. Completions is about how much you finished, and hours belong with the rest of the hours.