- Templates
- Dependency register review
Dependency register review
Review every open cross-workstream dependency against a client owner, a due date and the milestone it holds up, and escalate the one that has no owner.
- Industry
- Management and Strategy Consulting
- Team
- Operations
- Use case
- Project management
- Tags
- Client delivery
- Includes
- 1 database · 1 app
Template preview
Included items
-
Program dependency and decision register
Database · Embedded view: Open dependencies · Requires sign-in
-
Dashboards
App · 2 embedded blocks: Chart: Open dependencies by age (c-dep-age); Chart: Open dependencies over the fortnight (c-deps-waterfall) · Requires sign-in
Overview
What this template supports
A dependency register review for a program director and client workstream owners. It counts the open dependencies, ties each to a client owner, a due date and the milestone it holds up, shows their age and the fortnight movement with live Dashboards blocks, and sets out the escalation rules and recovery steps. It embeds a live Kanban board of open dependencies with sample records.
- Stats row of open, without an owner and oldest
- Embedded open dependencies board
- Live ageing and fortnight waterfall blocks
- Escalation rule definition list
- No-owner danger callout
- Recovery steps and tabs
How to use this template
-
List the open dependencies
Pull every open dependency from the register with its status, client owner, due date, days open and the milestone it holds up.
-
Apply the escalation rules
Mark any dependency with no client owner by day 10, open 30 days or more, or past its due date, and write the ask for the sponsor.
-
Agree the recovery path
Record the next step, owner and date for each escalated dependency, then check them before the next steering meeting.
Frequently asked questions
What counts as a dependency without an owner?
One where nobody on the client side has accepted the request. It shows Waiting for owner and has no due date until an owner is named.
Why is age counted from the day it was raised?
Because a dependency can be old and still on time. Age shows how long a workstream has been exposed, and the due date shows the commitment.
What does Dependency register review help me do?
Review every open cross-workstream dependency against a client owner, a due date and the milestone it holds up, and escalate the one that has no owner.
Who reads and maintains this page?
Program director and client workstream owners. The client workstream owners reviews it.
When is the page ready to share with the client?
Sent only after every open dependency shows a client owner or is marked for escalation, and the embed is filtered to the client.
What do visitors see in the public link?
The public link opens the full page without sign-in. The embedded Program dependency and decision register view and the live Dashboards blocks are separate items that need FuseBase sign-in and workspace access, so a visitor without access does not see their live records.