> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/governance/dependencies.md).
# Dependencies
What waits on what, across programmes and portfolios, and which links are slipping.
A dependency says that one piece of work waits on another: the **successor** depends on the **predecessor**. Either end can be a programme, a project, a phase, a milestone, a sprint or a cadence, and the two can sit in different programmes or portfolios.
Dependencies are the D of the [RAID log](/portavi-docs/governance/raid-log.md), beside risks, assumptions and issues.
## Where dependencies show
* **The RAID tab** on a programme or a portfolio, on **Dependencies**. It lists every dependency with either end inside it, plus every dependency created on it. A link between two programmes therefore shows on both.
* **A project's RAID tab**, on **Dependencies**: every link with an end inside the project, read-only, each opening on the programme or portfolio where it is managed.
* **The Timeline tab** of the same programme or portfolio draws each dependency as an arrow, read-only. See [On the timeline](#on-the-timeline).
* **Governance › Dependencies** lists every dependency in the workspace. See [The register](#the-register).
* **My Focus** lists the dependencies that are slipping. See [When a dependency slips](#when-a-dependency-slips).
They don't show on project pages, and they don't change anyone's health status.
## Adding a dependency
On a programme's or portfolio's **RAID** tab, on **Dependencies**, select **Add dependency**.
1. **Predecessor**: the work that must happen first. Search across all six kinds; results are grouped by kind, and each one shows where it sits and its dates.
2. **Successor**: the work that depends on it.
3. **Type**: what has to happen before what. **Finish → start** is selected to begin with, and a sentence under the four cards says what your choice means for the two you picked.
| Type | The successor can… |
| ------------------- | ------------------------------------ |
| **Finish → start** | start once the predecessor finishes |
| **Start → start** | start once the predecessor starts |
| **Finish → finish** | finish once the predecessor finishes |
| **Start → finish** | finish once the predecessor starts |
4. **Note** (optional): why it depends on it.
You can pick something that has no dates yet. The dialog shows a warning, because the dependency can't show whether it's slipping until the date it compares is set.
Adding a dependency records an entry in the Activity feed of the programme or portfolio you added it on. It also sends an in-app notification to the owner of each end, apart from you.
## Who can add and change them
* **PMO managers** can add a dependency on any programme or portfolio.
* **Programme and portfolio owners** can add one on what they own, as long as the successor sits inside it: the work that waits must be theirs. The predecessor can be anything in the workspace.
A dependency belongs to the programme or portfolio it was **created on**. Only that one's owner and PMO managers can edit or remove it, from its preview's **⋯** menu. Everywhere else it is read-only, and the row says **Created on** with the programme or portfolio to go to. Neither editing nor removing a dependency sends a notification.
Removing a programme, project, phase, milestone, sprint or cadence removes every dependency that names it.
## Reading a row
Each row shows the type (FS, SS, FF or SF), the predecessor, then the successor. Under each end you see what it is, where it sits and the date the type compares. On the right is the status:
* **On track**: the predecessor's date comes on or before the date the successor needs it.
* **Slipping**, with the number of days: the predecessor's date has moved past the date the successor needs. A finish → start link slips when the predecessor finishes after the successor starts.
* **No date**: one of the two dates is missing, so there is nothing to compare yet.
* **Satisfied**: the predecessor is finished, so the dependency holds whatever the dates say. Finished means a programme or project marked completed, a phase whose work is all done, a milestone that is done, a sprint that is closed, or a cadence that has closed and been finalised. A satisfied dependency never counts as slipping.
On a phone, each row becomes a card: the type in words, the predecessor above the successor, and the status.
Open a row for its preview: both ends, both dates, how many days late, the note, and who added it. When a date has moved since the dependency was added, the preview also shows what it **was**.
## On the timeline
On a programme's or portfolio's Timeline tab, each dependency is an arrow. It runs from the predecessor's finish (or start, for start → start and start → finish) to the successor's start (or finish).
* A **grey** arrow holds.
* A **red** arrow is slipping. A dotted red line under the successor covers the slip, labelled with the number of days.
When one end sits outside the programme or portfolio, it gets its own row at the bottom of the chart, in light grey with an **External** pill in the Status column. Hover over an arrow to see which link it is, and select it to open the preview. Selecting an arrow opens a card with the type, both dates and the status; its **Preview** button opens the dependency. To hide the arrows, along with the External rows, turn off the **Dependencies** chip above the chart. The timeline is read-only; make changes on the Dependencies tab.
## When a dependency slips
The first time a dependency starts to slip, Portavi sends one in-app notification. It goes to the owners of both ends and the owner of the programme or portfolio it was created on.
While it is slipping:
* it appears under **Slipping dependencies** in [My Focus](/portavi-docs/tracking-delivery/my-focus.md) for those same people; selecting the row opens its preview;
* the **RAID** tab and its **Dependencies** toggle show a dot on every programme and portfolio where the dependency appears;
* it is counted on Governance's [RAID dashboard](/portavi-docs/governance/raid-log.md#the-raid-dashboard).
It drops off once the dates line up again or the dependency is removed. If it slips again later, it sends a new notification. Dates are checked every hour, and again whenever a Dependencies tab loads.
## The register
Governance › Dependencies lists every dependency in the workspace.
The **Dependencies** card above the tabs counts the open dependencies, split into on track, slipping and no date. Satisfied dependencies are left out of it, since their predecessor is finished; they are still listed in the register.
* **Search** matches both ends' names, where they sit, the programme or portfolio the dependency was created on, the note and the type.
* **Group by**: **Created on** (the default), Status, Type, or no grouping.
* **Sort by**: status (slipping first), date added, or type.
PMO managers and executives can open the register. It is read-only, like every register on Governance: a dependency's preview names the programme or portfolio it was created on, and it is edited or removed there.
