T84 Dependency register review
Dependency register review
Every cross-workstream dependency of the Fairhaven store operations improvement program that was still open on Monday, September 28, 2026, tied to a Fairhaven owner, a due date and the milestone it holds up, with the one that has no owner marked for escalation. Prepared by Philippa Sinclair, program director at Ferncastle Operations Group, for Gareth Pryce, chief operating officer at Fairhaven Home Stores, and the Fairhaven workstream owners. Since the program started in June, 23 dependencies have been logged: 17 are closed and 6 are open. Two of the open six had no owner on the Fairhaven side until Sep 24, when Gareth Pryce assigned the store system data extract to the IT director. One still has none.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
The open dependencies
The board groups every open dependency by status, and each card shows the owner, the due date and the milestone it holds up. Six cards belong to Fairhaven Home Stores: one is Escalated (Store system data extract), one is Waiting for owner (Loss prevention data access) and four are Owned. The same view also holds two cards for Prescott Medical Supply and one for Halvard Brewing Company, nine in all. Read the Waiting for owner and Escalated columns first, because nothing moves in them until a person acts.
Before you share this page with a client
This sample view holds dependencies for several clients: Fairhaven Home Stores, Prescott Medical Supply and Halvard Brewing Company. Switch the embed to a view filtered to Fairhaven Home Stores before you send this page to Gareth Pryce or anyone at Fairhaven.
Six dependencies, each with an owner and a milestone
Days open are counted to Sep 28. Owner is the Ferncastle person who chases it; Fairhaven owner is the person who has to deliver it.
| Dependency | Status | Fairhaven owner | Owner | Holds up | Due | Days open |
|---|---|---|---|---|---|---|
| Store system data extract | IT director | Emeka Achebe | Replenishment pilot | Oct 9 | 34 | |
| Shift template sign-off by HR | HR lead | Hamish Aldous | Labor scheduling pilot | Oct 5 | 21 | |
| Planogram file for the pilot stores | Merchandising manager | Saoirse Quigley | Replenishment pilot | Oct 6 | 16 | |
| Loss prevention data access | None | Philippa Sinclair | Shrink baseline | No date | 12 | |
| Distribution center slotting window | DC operations manager | Hamish Aldous | DC flow wave 2 | Oct 12 | 9 | |
| Store manager briefing slot | Regional operations manager | Emeka Achebe | Labor scheduling pilot | Oct 7 | 4 |
What each one needs next. The data extract needs confirmation that Fairhaven IT has scheduled it. HR needs to give a sign-off date for the new shift template. The planogram file covered 9 of the 12 pilot stores when it was sent in August, so the file for the three missing stores is outstanding. The slotting window is a two-day window at the second distribution center outside the peak receiving days, and its dates are still to agree. The briefing slot is 30 minutes in the Oct 7 regional store manager call.
How old they are
Three of the six open dependencies are older than 15 days: Store system data extract (34 days), Shift template sign-off by HR (21) and Planogram file for the pilot stores (16). Two are 7 to 14 days old and one is under 7 days. Age is counted from the day the dependency was raised, not from its due date, so a dependency can be old and still on time.
Live example from the Dashboards app, shown with Fairhaven Home Stores' demo data. Block dates move forward each week, so they can differ from the sample dates on this page.
What changed in the fortnight
Seven dependencies were open at the Sep 14 window. Three were raised since: Loss prevention data access on Sep 16, Distribution center slotting window on Sep 19 and Store manager briefing slot on Sep 24. Four were closed. Six are open now. A raised dependency and a closed dependency are counted separately, never netted off.
Live example from the Dashboards app, shown with Fairhaven Home Stores' demo data.
Escalation rules
Loss prevention data access has no Fairhaven owner
Philippa Sinclair raised this dependency on Sep 16. It is 12 days old on Sep 28 and it passed the 10 day mark on Sep 26. The shrink baseline cannot be agreed without read access to the loss prevention system, and nobody on the Fairhaven side has accepted the request, so it has no due date.
What it holds up. The access request is drafted but cannot be sent without a Fairhaven owner. The shrink baseline method draft, due Oct 23, starts only once access is granted. Consequence. Without a baseline, shrink results cannot be shown as a change at the November value review. Ask. Gareth Pryce names an owner at the Oct 8 steering meeting.
Recovery steps
The recovery path for the dependency without an owner, from the day it was raised to the first usable baseline:
The two aged dependencies and the planogram file each have their own recovery path:
Path. Gareth Pryce names a Fairhaven owner on Oct 8. The owner accepts, sets a due date and approves the access request that Philippa has drafted. Saoirse Quigley then starts the shrink baseline method.
If no owner is named on Oct 8. The baseline method cannot start, the baseline cannot be agreed with the loss prevention lead before the November value review, and shrink stays not measurable.
Path. The IT director confirms the extract is scheduled and gives the date of the first daily extract of store stock positions. Saoirse Quigley then re-runs the store stock test on a one-week sample (due Oct 12). Owner on the Ferncastle side: Emeka Achebe.
If it is not scheduled by Oct 9. The Oct 16 replenishment pilot date resets for a second time, and Gareth Pryce decides whether to hold it.
Path. The merchandising manager sends the current planogram for the three pilot stores missing from the August file, due Oct 6. Saoirse Quigley checks it against the replenishment rules for all 12 pilot stores.
If it is late. The replenishment rules cannot be confirmed for three stores, and the Oct 16 pilot start is at risk for them.
How to use this template
Review the open dependencies after every status window. Tie each one to a client owner, a due date and the milestone it holds up, and escalate any dependency that has no owner or has reached the age limit.
| Variable | Meaning | Required |
|---|---|---|
{{program.name}} | Program the review covers | Required |
{{window.close_date}} | Date the status window closed | Required |
{{dependency.open_rows}} | Open dependencies with status, owner, due date and days open | Required |
{{dependency.client_owner}} | Client person who has to deliver each dependency | Required |
{{milestone.held_up}} | Milestone each dependency holds up | Required |
{{dependency.no_owner_list}} | Dependencies with no client owner, with the escalation ask | Required |
{{dependency.fortnight_change}} | Dependencies open at the last window, raised, closed and open now | Optional |
If a required value is missing, show Needs review in its place and hold the review; never fill it with a guess. If the register cannot be read, show Unavailable instead of the counts.
The live Dashboards blocks on this page show the Fairhaven Home Stores demo profile. Point each block at your own client's profile, or remove it, before you share the page. Filter the embedded view to the same client as well.