Close the week on actual completed units
Synthetic batch T-H has ten units. Seven complete this week and three remain. Next week has capacity for two of those units. The local tracker uses one parent task with dated allocations; moving the remainder does not create a new ten-unit batch.
| Period | Completed / allocated | Residual state |
|---|---|---|
| This week | 7 completed | 3 remain on T-H |
| Next week | 2 allocated from same 3 | 1 unscheduled |
| Parent scope | 10 total | No second batch |
Carry only the unfinished three
- Confirm seven completed units
- Retain three on same T-H
- Assign two next-week slots
- Keep one visibly unscheduled
Copying the whole ten-unit batch into next week would duplicate the completed seven; use a linked allocation rather than a new parent task.
The next-week plan has two planned units and one unplaced unit, all belonging to T-H. This week’s seven remain credited once in the historical completion record.
Next week completes its two assigned units. How many of T-H are complete and still open?
Show the worked answer
Nine complete and one open: seven plus two, out of ten.