Archive: October 2026 Highlight Report
The Project Office › Archive › October 2026 Highlight Report
Archived 21 October 2026. Copied from the Legal Wiki (page 1348, last modified 2026-10-19), where PRINCE2 records were kept until 21 October 2026. Kept word for word, except that personal names and contact details are replaced. Current product: see the product set.
This material now lives at https://projects.bucklerfamily.estate/october-2026-highlight-report/.
October 2026 Highlight Report
Reporting date: 5 October 2026. Stage: S0 Start-up & Initiation. Next gate: G0, 18 December 2026. Overall status: AMBER.
1. Executive summary
The programme remains within its current S0 governance structure and has a functioning PRINCE2 control architecture. The principal management change this period is the reconciliation of the public dashboard with the live HubSpot execution ledger. The raw HubSpot ledger contains 94 task records. Twelve are explicitly cancelled administrative/draft records and two are sample records marked for deletion, leaving 80 live delivery/control tasks. Of those live tasks, 4 are complete, 17 are in progress, 30 are waiting and 29 are not started.
2. Progress since the September baseline
- Evidence, archive and press material continue to be catalogued as discrete evidence records.
- The Wiki now contains a mature PRINCE2 management hierarchy: Mandate, Brief, Plan, Delivery Breakdown, PIDs, S0 Control Register, Control Registers, Analytics and Highlight Reports.
- HubSpot has become the private execution ledger, while WordPress remains the public programme/evidence record.
- New P1 work packages have been added for Glamorgan Archives, BP successor/corporate records, House of Lords papers, ITV/broadcast records, Cotswold Archaeology and photographic records.
- Preservation and deadline controls remain the immediate priority.
3. Exceptions / management attention
figure class=”wp-block-table is-style-stripes”>| Area | Status | Management response |
|---|---|---|
| Task population reconciliation | AMBER | Supersede the obsolete 47-task dashboard. Use 80 live tasks for performance reporting. |
| Evidence preservation | RED/AMBER | Maintain preservation notices and prioritise vulnerable institutional/archive sources. |
| HMLR / ICR timing | AMBER | Maintain a specific deadline trail and avoid reliance on generic correspondence dates. |
| Woodland decision | AMBER | Keep P2-T decision controlled and evidence-led before any irreversible route is taken. |
| Fraud/conduct stream | GREEN/CONTROLLED | Remain parked unless qualifying evidence establishes a proper basis for activation. |
4. Finance and resource
The current Phase-1 control envelope remains £0–£800. Actual expenditure is not inferred from the HubSpot deal amount. Unknown professional or external costs remain TBC until quoted or incurred. No budget variance is asserted without a recorded actual.
5. Quality
The acceptance rule remains: a task/product is complete only when its defined acceptance test is satisfied. External acknowledgement, administrative closure and receipt of a response do not by themselves establish evidential completeness. Evidence records must retain provenance and distinguish documented fact, family evidence and inference.
6. Next reporting period
- Resolve the 6 October and 9 October deadline controls.
- Progress P1 evidence-recovery work and the master evidence-capture protocol.
- Maintain the HMLR/ICR, woodland and external-response controls.
- Complete the four working PIDs and prepare the G0 decision pack.
- Reconcile the risk, issue/change, quality, lessons and decision registers against live execution.
7. Gate forecast
G0 remains forecast for 18 December 2026. The gate decision should be based on completed PIDs, justified Business Cases, accepted roles, defined products and quality criteria, established control registers, a credible Stage Plan and resolution or explicit acceptance of outstanding exceptions.
This report is the October management baseline. The next Highlight Report should supersede it with the next reporting period rather than silently rewriting this historical record.
Change history is maintained on the Master Change Log; no separate page-local version footer is maintained.
PRINCE2 7 outlines: sources · product set · archive