Name the blocked task and owner
Synthetic launch L-3 needs an approved domain setting, a reviewed data sample and sign-off on reminder text. Dates are project discussion fields; the sheet contains no promised delivery date.
| Dependency | Supplier of input | Blocked task | Next decision if absent |
|---|---|---|---|
| Domain-setting authority | Company domain owner | Connecting the agreed live hostname | Keep test environment; escalate access decision |
| Reviewed data sample | Data owner | Checking full import mapping | Do not replace with invented production facts |
| Reminder wording approved | Content owner | Enabling customer reminder | Decide whether reminder can be deferred |
A dependency is not always a whole-project blocker
Reminder wording is pending. Does the worksheet prove the entire project must stop?
Show the worked answer
No. It identifies the reminder task as blocked. The authorised owner decides whether that task can be deferred while other accepted work continues; do not silently enable unapproved wording.
This is dependency tracking, not a critical-path algorithm or a guarantee that delay can be absorbed. Any revised launch scope or date needs actual impact review.