Project links
Project links let you record cross-project dependencies — when Project A relies on something delivered by Project B.
Why use them
- Visibility — see at a glance what your project depends on, and what depends on you
- Slip impact — when a milestone slips on Project A, every linked project sees the warning
- Programme management — programme leads can see dependency networks across projects in their portfolio
Add a link
From a project → Links → + New link:
- Linked project — pick from your org
- Link type:
- Depends on — this project needs something from the other
- Provides to — this project supplies something to the other
- Related to — informational only, no dependency
- What — the deliverable / artefact involved
- Required by — date this project needs the dependency
- Notes — context
Links are bidirectional — adding one shows up on both projects' Links tab.
Visualisation
The Programme page shows a dependency graph of all projects in the programme. Critical-path dependencies (depend-on links with tight dates) are highlighted.
When dependencies slip
If Project B has a slip on a milestone that Project A depends on, Sageon Business adds an issue to Project A's RAID automatically (subject to your settings).
Tips
- Be specific about what. "API" is too vague. "Customer API v2 endpoints /list and /detail" is useful.
- Add a date. Dependencies without dates can't drive scheduling.
- Close links when no longer needed. Old links clutter the view and obscure real risks.