Turn the decision into executable tasks
Synthetic decision CH-A approves a four-hour export addition. It needs a one-hour field definition followed by three hours of implementation. The field owner has one hour today; the implementer has only two hours tomorrow. Approval grants scope but does not create the missing implementation hour.
| Task | Effort / prerequisite | Assigned slot | State |
|---|---|---|---|
| DEF-A | 1 hour; CH-A | Today / owner Mei | Ready |
| IMP-A | 3 hours; DEF-A complete | 2 tomorrow; 1 unscheduled | Queued |
| CH-A scope | 4 total hours | 3 placed; 1 unplaced | Approved; not completed |
Track the addition through readiness and allocation
- Link new tasks to CH-A
- Sequence DEF-A before IMP-A
- Reserve confirmed capacity
- Leave missing hour unscheduled
- Start implementation only with ready fields
If implementation cannot be split, the two-hour slot cannot begin the three-hour task under that rule; obtain a continuous slot.
The approved addition becomes two tracked tasks rather than an automatic completed milestone. Preserve the original work plan and add these allocations explicitly, so existing tasks are not silently displaced.
Can CH-A be marked completed after DEF-A finishes?
Show the worked answer
No. One hour is complete and three implementation hours remain, including one still unscheduled.