Dependency Register (sample)
The table below is a simplified representation. In practice, each dependency links to a milestone chain and escalation rule.
How I use this register
- Tracked weekly with owners; escalated if no movement within agreed SLA
- Linked to IMS milestones to avoid “invisible blockers”
- Status must include next action + due date (not just “in progress”)
| ID | Dependency | Upstream Owner | Downstream Impact | Risk | Status / Next step |
|---|---|---|---|---|---|
| DEP-01 | Utility approval for power energisation | Power Segment Lead | Blocks commissioning start | High | Escalate approval pathway; confirm target date + evidence |
| DEP-02 | Long-lead equipment delivery window | Supply Chain Owner | Shifts install/test sequence across two sites | Medium | Lock shipping plan; define alternate supplier/sequence |
| DEP-03 | Network integration window alignment | Network Program Lead | Impacts commissioning completion date | Medium | Confirm integration slot; publish dependencies to IMS |
← Back to Pack index