Project Intelligence Timeline Dashboard

Timeline Dashboard Generator

Purpose

Generate a complete, self-contained HTML file that visualises the full Project Intelligence Engine output as an interactive root cause analysis dashboard. The file must be saved to SharePoint and opened directly in a browser — no external dependencies of any kind.

The dashboard answers two questions every stakeholder needs answered after a project goes off the rails:

1. "What went wrong, and when did we know?"
2. "How far off was the original plan — and why?"

Every visual choice should serve those questions. The audience is a delivery director, client sponsor, or steering committee member who needs to understand the failure pattern in under 5 minutes — not a technical reader who will study it carefully.

---

Inputs

This skill reads from two sources:

1. Change Events list — must be fully populated by both prior skills:

• Change Event Extraction: 16 fields per event
• Root Cause Analysis: Is Root Cause, Intervention Window, Early Warning Signal, Root Cause Statement, Intervention Action, Detectability, Causal Chain Step

2. SHAREPOINT.md — Project Analysis Summary section — for the root cause statement, causal chain narrative, failure type, and recommendation used in the dashboard callout boxes.

If the Change Events list is empty, the root cause flags are not set, or the Project Analysis Summary in SHAREPOINT.md is blank, run Change Event Extraction and Root Cause Analysis first.

All KPI metrics and the Scope Churn Index are computed from the Change Events list at generation time.

---

Required Sections (in order, top to bottom)

---

Section 1 — Project Header Bar

A dark navy (#1B365D) full-width header containing:

• Project name (large, white, bold)
• Client name (smaller, light gray)
• Engagement type and contract reference in small gray text
• Four stat pills in a row:
  • "Original completion: [date]" — neutral gray
  • "Revised completion: [date]" — amber (#BF6A00) if delayed, green if on track
  • "Original contract: $[value]" — neutral gray
  • "Projected overrun: $[amount]" — red (#C00000) if overrun, gray "Within budget" if not
• A small badge in the top-right corner showing the Documentation Quality Rating (1–5) with a colour: red for 1–2, amber for 3, green for 4–5, labelled "Doc Quality"

---

Section 2 — KPI Metrics Bar

A horizontal band of metric cards immediately below the header, rendered as a single row of 6 equal cards on a light gray background (#F4F6F8). Each card:

• A large bold number (the metric value)
• A small label below it
• A coloured left border: red for negative, green for positive, gray for neutral

The six cards, left to right:

1. Total change events — gray border
2. HIGH signal events — red border
3. HIGH signals actioned — format "N of N" — green if all actioned, amber if partial, red if none
4. Events with no change order — red border, include % in small text below
5. Governance gap score — red if ≥ 7, amber if 4–6, green if ≤ 3 — label "/ 10"
6. Scope Churn Index — format "N%" — red if ≥ 50%, amber if 25–49%, green if < 25%

---

Section 3 — The Contrast Panel

This is the most important visual in the dashboard. It must appear before the timeline.

Render a side-by-side comparison of what the project was built on vs what was actually found. Use the Scope Churn Index table from the Change Event Extraction output. Show one card pair per changed parameter.

Primary parameter pair (data volume + table count):

Left card — "What the Plan Was Built On" (light blue background #DAE8FC):

• Large bold number: the assumed data volume
• Below it: the assumed table count
• Below that, in small italic text: the source document and week — e.g. "Single verbal estimate — Discovery Workshop, Week 2"
• Label at top: "PLANNED BASIS" in blue uppercase small caps

Right card — "What Profiling Found" (light red background #FFEBEB):

• Large bold number: the actual data volume in red
• Below it: the actual table count in red
• Below that: any additional context from the profiling report (e.g. undocumented schemas, data quality issues)
• Label at top: "ACTUAL" in red uppercase small caps

Between the two cards, render a large arrow (→) and a variance callout showing the percentage difference for each parameter — e.g. "+212% volume · +89% tables" — in bold red.

Secondary parameters (budget, timeline, team size, etc.): Below the primary pair, render a compact row of smaller parameter cards for any other parameters in the Scope Churn Index table, showing baseline → actual → variance % for each.

---

Section 4 — Root Cause Statement

A prominent full-width callout box in dark navy (#1B365D) with white text, containing:

ROOT CAUSE label in small caps teal (#2C7DA0), followed by the root cause event number and title in small gray text.

Then the root cause statement sentence in large bold white text — e.g.: "A verbal data volume estimate made in Week 2 was accepted as the project baseline without validation, anchoring the sprint schedule, resource plan, and budget to a figure that understated actual scope by 212%."

Below that, in smaller white text in two columns:

• Left: Failure type — e.g. "Assumption failure + Governance failure (compound)"
• Right: Preventability — e.g. "Preventability: HIGH — standard discovery validation would have caught this"

---

Section 5 — Causal Chain

A numbered step-by-step sequence (max 8 steps) showing how the root cause cascaded into the impact event. Render as a clean vertical flow with connecting arrows between steps.

Each step:

• Step number in a colored circle (navy background, white text)
• Bold event title (with event # from change log in gray)
• One sentence explanation
• Small "Week N — [date]" label
• If this step had an intervention window: show a small amber badge "⚠ Intervention window" and a one-sentence tooltip/subtext describing what the available action was

---