Project Analytics

Project Analytics

Dashboard date: 28 September 2026. The statistics below are management indicators derived from the site’s current control record. Where a number is not supported by a complete task ledger, the dashboard deliberately uses a proxy and labels it as such.

Current baseline

Performance measures

Visual dashboard

Control maturity

M0 Governance: active · M1 Evidence Recovery: active · M2 Title: active · M3 Planning/Heritage: active · M4 Accountability: active · M5 Narrative Justice: active · M6 Replica Museum: structured · M7 Remedy: assessment stage · M8 Stewardship: later stage.

External-dependency load — The project currently carries multiple live review, complaint and disclosure dependencies, including Wales Office 26FOI 103, Vale review 00210772 and related requests, HMLR N610CGV / ICR route, MoD FOI/SAR matters, Cadw ATISN 27021 and the National Archives CAS-347296-M0V4Y1.

Monthly trend model

The dashboard should be updated once each monthly Highlight Report is closed. For each period store: planned tasks, completed tasks, carry-over tasks, new issues, closed issues, new risks, closed risks, FOI/EIR actions, documents received, documents verified, correction actions and remedy/museum outputs. These values form the dataset for a later charting layer without changing the underlying evidence record.

Data-quality rule

No statistic is allowed to imply completeness where the underlying task or correspondence ledger is incomplete. The dashboard distinguishes project activity from external institutional performance and distinguishes documentary evidence from named testimony, SOURCE PENDING statements or inference.

Backfilled records-access activity — Nov 2025 to Sep 2026

The monthly series below counts the event entries explicitly carried into the reconstructed Highlight Reports. It is a project-control activity measure, not a score of institutional performance and not a claim that the underlying correspondence is complete.

Timestamped entries: the individual dated and timed entries behind these counts are listed once, in each month’s Highlight Report (the latest are in the September 2026 report, including the 28 September 02:16 project-control cut-off) and in the Records Access Chronology.

Interpretation rule

The activity series is deliberately neutral: a high month can mean more evidence movement, more disputes, more responses or more chasing. It is not itself a measure of success. Delivery performance is determined by the task acceptance tests in the Delivery Breakdown.

PRINCE2 7 control dashboard

The dashboard now measures the PRINCE2 control cycle as well as evidence activity: business-case health, stage performance, work-package delivery, accepted products, open risks, open issues/changes, quality failures/rework, lessons applied, decisions pending, exception count and external-dependency ageing. A monthly figure is valid only when its underlying ledger is complete enough to support the calculation.

PRINCE2 7 Compliance & Control Manual · PRINCE2 Control Registers · S0 Stage Plan & Control Register

October 2026 execution baseline

30 controlled project tasks were created in the CRM on 1 October 2026 for the October S0 baseline. They cover governance, P1, P2-T, P2-C, P2-F, P3, P4 and the G0 pack. Two pre-existing HubSpot sample tasks are excluded from the project denominator. This gives October a fixed task-planning baseline for measuring completion, carry-over, ageing and exception performance.

Each controlled task carries a WBS code, target date, cost basis, acceptance test and execution notes. Completion is counted only after the acceptance test is satisfied.