A worked example · four ways into a programme
A viaduct renewal team wants to see which handoffs connect its phases. A portfolio team wants to compare when work happens. Trace the links, then compare the dates.
Historical toy scenarios · 25 March 2026. Names, dates and status flags were supplied as illustrative story material. They are not records of real programme progress, regulatory decisions or present-day plans.
View files preserve the selected examples, filters and selected item. Example data exports preserve all four original datasets and supplied narratives; they are reference files, not view files.
Computed from the supplied graph
Hover to preview; focus, click or tap a node to keep its connections in the detail panel. Curves are grouped by phase or gate. Direction is listed as source → target below. On a small screen, enlarge and scroll the diagram or use the selector and table.
| Source | Target | Group relation |
|---|
These supplied labels are retained for provenance. “Critical” and “risk” are source wording, not calculated scheduling or assurance results.
One shared date scale · separate facets
Scroll the charts horizontally on a small screen, or use the item selector and data table. Dashed line = source date, 25 March 2026. Status colours reproduce supplied flags.
| Facet | Item | Start | End | Elapsed days | Supplied status |
|---|
Each row is one pair of activities in different facets with a positive date intersection. This is a calendar comparison, not evidence of competition for resources. The complete example is compared regardless of the status filter; milestones and shared endpoints do not count.
| Activity A | Activity B | Overlap starts | Overlap ends | Days |
|---|
Supplied labels preserve the original story. No critical path, slippage against a baseline, or programme health is inferred.
Hierarchical edge bundling routes connections through the containing groups. It is a way of drawing adjacency in a hierarchy. A shared stretch of curve is not an extra dependency.
This native SVG version blends the source → group → root → group → target route toward a straight line, then draws a cubic basis spline at strength 0.82. Links within one group pass through that group only. See the D3 bundle-curve documentation, which describes the curve used by the original.
Incoming and outgoing counts use directed, explicitly listed edges. Incident links count an edge once for each node it touches. The busiest node has the highest incident count; ties are retained. This degree is not a critical path, probability of delay, safety judgement, or proof that removing a handoff helps.
Changing a filter changes only what is drawn. Summary counts and supplied narratives always describe the complete selected example.
Durations are elapsed calendar days from start to end, using UTC midnight and no inclusive end-day addition. Weekends and holidays count. Milestones take zero days. Pair overlap is max(0, earlier end − later start), excluding pairs within one facet.
All facets keep the full example’s date scale, even when filtered. The source-date line is historical provenance, not today. The graph and timeline examples are independent illustrations: no automatic mapping joins their nodes.
Local save stores only your selections in this browser under this app’s own key. It does not upload, share or edit any project data. Exported view files can restore the same choices; imports validate their version, example names and item references before applying.
Reset restores the default view without deleting a saved view. The separate example-data export contains the retained original datasets and narrative labels.