# Project Execution — Dependencies

![Project Execution — Dependencies](/docs-content/b15ad2923a-04-dependencies.png.webp)

**Navigation:** Intelligence → Project Execution → Dependencies  
**Primary audience:** project managers, delivery teams, engineering leads, and dependency owners

## Purpose

Dependencies maps the external, customer-owned, internal, third-party, and technical prerequisites that can affect project sequencing. It makes critical paths, slack, ownership, due dates, confirmation state, and downstream impact explicit.

## Scope controls and indicators

Project selects scope. Path filters critical-path, near-critical, or all dependencies. Owner filters responsibility. Type selects customer, internal, third party, technical, contractual, or another configured class. State filters open, watching, unconfirmed, blocked, or resolved.

Open Dependencies is total active volume. Critical Path counts those with no acceptable alternative or slack. Customer-Owned identifies customer responsibility. Fresh Evidence shows the percentage updated within the configured window.

## Dependency map

The map connects prerequisite, dependent activity, milestone, and resulting effects. It shows direction and criticality; selecting a node or edge opens the dependency record.

## Selected dependency

The detail panel shows statement, required item, impact, owner, source authority, required date, state, confirmation, evidence, affected milestones, slack, alternatives, and linked risks or actions.

## Supporting analysis

**Dependency ownership** distributes customer, internal, third-party, and unassigned items. **Critical-path slack** lists days remaining and state. **Dependency actions** surfaces date confirmation, owner assignment, notification, and escalation work.

## Actions

- Create or link a dependency.
- Confirm owner and required date.
- Notify or request confirmation from the responsible party.
- Add an alternative, mitigation, or downstream link.
- Escalate a critical-path item.
- Mark resolved with evidence and recalculate affected path.

## Recommended procedure

Start with unconfirmed critical-path dependencies. Verify the authoritative required date and responsibility, then create a dated follow-up. Recalculate impact when dates or alternatives change and confirm that affected owners are notified.

## Interpretation

Critical-path status depends on the current plan and can change after replanning. Customer-owned does not mean customer fault; it identifies the party expected to provide the prerequisite.

## Related screens

[Risks & Issues](/documentation/packages/bnd-project/screens/intelligence-project-risks-and-issues), [Actions](/documentation/packages/bnd-work/screens/work-actions), [Meeting Context](/documentation/packages/bnd-evidence/screens/home-meetings-context), and [Projects](/documentation/packages/bnd-project/screens/intelligence-project-projects).