Archive: PRINCE2 Project Initiation Documentation — G0 Pack
The Project Office › Archive › PRINCE2 Project Initiation Documentation — G0 Pack
Archived 21 October 2026. Copied from the Legal Wiki (page 1004, last modified 2026-10-21), 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/prince2-project-initiation-documentation-g0-pack/.
Page ID: 1004 · Title: PRINCE2 Project Initiation Documentation — G0 Pack · Evidence status: Not yet labelled — see the Editing Protocol · Version: 1.2.0 · Editing Protocol
About this page type → Read the Docs#prince2-pid
PID — summary — current baseline, 19 Oct 2026
Current baseline, 19 Oct 2026 (PM File v0.1). Where earlier sections on this page differ, this one governs; they are kept as history.
| Element | Where / rule |
|---|---|
| Brief, scope, tolerances | Project Brief |
| Business Case | 5280 |
| Organisation | 5281 |
| Plan; Stage Plan | 876; 5283 |
| Quality management | Evidence-first (EV pages); live verification of every write; banned-phrase scan; pre-send check — Quality Register (1003) |
| Risk management | Cause → event → effect; owner; P/I; response; reviewed each Highlight and each debrief (1003) |
| Issue management | Issue Register; off-specification fixed and logged; decisions in the Decision Log |
| Change control | 5286; every page edit logged in the Master Change Log |
| Configuration management | CI Records; wiki is master; sites mirror it |
| Communication | 5282 |
| Controls | 6-hourly research updates; Highlight Reports; Exception Report same day on tolerance breach; G0 18 Dec |
Tailoring
- One-person Board: the Executive is Executive and Senior User.
- Tab is PM and Senior Supplier; workers are Team Managers per work package.
- Registers live on one page (1003); HubSpot is the private execution ledger; the wiki is the public record.
- Flywheels replace manual checkpoints: research, send, debrief.
| Field | Entry |
|---|---|
| Project | Great House Farm / Tŷ Mawr — Evidence Recovery |
| Version state | Working baseline; authorisation at G0, 18 Dec 2026 |
| Executive | the Executive — TBC — the Executive to confirm |
Contents
| PID element | Where |
|---|---|
| Project definition; project product description | Project Brief |
| Business Case | Business Case |
| Project management team and roles | Project Organisation & Roles |
| Quality management approach | below |
| Risk management approach | below |
| Issue management approach; change control | below; Change Control — Change Request Log & Form |
| Communication management approach | Communication Management Approach |
| Project Plan | Project Plan |
| Project controls | below |
| Tailoring | below; method reference 1001 |
Projects in the programme
| Project | PID | Purpose | State |
|---|---|---|---|
| P1 Evidence & Archive | P1 PID | Recover, preserve, catalogue and verify the evidence base | Working baseline |
| P2 Title, Justice & Accountability | P2 PID | Title/register, accountability and evidence-gated justice routes | Working baseline |
| P3 Artefacts | P3 PID | Object census, provenance, recovery/loan/replica routes | Working baseline |
| P4 Tŷ Mawr Replica Museum | P4 PID | Evidence-graded reconstruction, interpretation, museum vehicle | Working baseline |
Constraints
- Research support only, not legal advice.
- the Executive makes every external contact and request; Tab contacts nobody and orders nothing.
- the Executive is outside the UK (2922): searchroom work needs paid copying or a proxy.
- Privileged legal material is not published.
- Free WordPress plan: no plugins; editing connection under a 30-day grace period (R-010).
Tolerances
| Type | Tolerance |
|---|---|
| Time | Statutory, limitation and preservation deadlines: zero (Plan, 16 Oct). Other dates: +5 working days, then Exception — proposed, TBC — the Executive to confirm |
| Cost | S0: £0–£800 (1348) |
| Scope | Changes only through Change Control; trigger events go to a separate project |
| Quality | Zero unlabelled inference: every claim cites EV, PENDING or HYPOTHESIS |
| Risk | Any threat to a statutory deadline or of evidence loss: escalate the same day (Plan) |
| Benefit | TBC — the Executive to set |
Quality management approach
- Standard: Editing Protocol, Claim–Evidence Linking.
- Methods: line-by-line check against the opened source; claim audit; Executive review.
- Records: Quality Register.
Risk management approach
- Identify: each flywheel cycle, each reply received, each stage boundary.
- Assess: probability and impact H/M/L (PM assessment); proximity.
- Respond: avoid, reduce, fallback, transfer, share, accept.
- Record: Risk Register.
- Escalate: any risk outside tolerance → Exception Report.
Issue management approach
- Types: request for change; off-specification; problem/concern.
- Record: Issue Register; change requests in Change Control.
- Authority: PM within tolerance; Executive beyond tolerance or on any baseline change.
Project controls
| Control | Frequency |
|---|---|
| Checkpoint | Each research cycle (every 6 h), update to the Executive; page update each Friday (1543) |
| Highlight Report | Monthly, first Monday (1543); HR-01 at this rebuild |
| Exception Report | Same day as a forecast breach |
| End Stage Report | By 16 Dec 2026 |
| Gate | G0, 18 Dec 2026 |
Tailoring
- Executive and Senior User combined.
- All registers on one page (1003).
- Checkpoints are the 6-hourly research updates.
- Highlight Reports monthly, plus HR-01 at this rebuild.
- Checkpoint, Exception and End Stage Reports as templates until first used.
G0 approval test
- Each PID complete enough to authorise the next stage.
- Business Case still justified within tolerance.
- Roles accepted.
- Product descriptions and quality criteria adequate.
- Risk, issue, change and communication controls in place.
- Stage Plan, Work Packages and acceptance tests defined.
- No open exception above PM authority without a decision.
Operational assurance baseline — 19 October 2026
This is a dated control addendum to the working PID; it does not authorise external correspondence, paid orders, legal steps, or a new project baseline. The 18 December 2026 G0 gate remains unchanged. The HubSpot audit found 305 tasks (201 NOT_STARTED, 48 WAITING, 21 IN_PROGRESS, 35 COMPLETED); 111 open tasks are flagged overdue, 72 open tasks have priority NONE, and 55 HIGH-priority open tasks are overdue.
- Association gap: 70 tickets are currently in open pipeline stages; 27 tasks are directly associated with tickets. The documented TASK → WP ticket → PROJECT ticket → PROGRAMME hierarchy must be reconciled against live associations; the older P1 deal has task associations that do not substitute for work-package links.
- Held communications: 22 HubSpot tasks mirror Gmail drafts whose subjects explicitly say DON’T SEND. Ten were quarantined on 19 October as WAITING / LOW with a review date of 26 October; 12 remain to classify. Original bodies, recipients, message IDs and draft links must be preserved. Nothing is sent by this control update.
- Organisation hygiene: 125 company records include eight duplicate-domain pairs. Among 180 contacts, 172 have a blank textual company field; that alone does not prove the CRM association is absent. Inspect associations and preserve distinct people, cases and correspondence before any merge.
Deterministic artifact-recovery cycle
- Trigger: every new reply, archive discovery, notice, deadline change or scheduled review starts a recorded cycle. Do not claim a six-hour cycle ran unless a run log or dated record proves it.
- Capture: preserve the original artifact or message, source/reference, sender/custodian, received/sent date, exact attachments and metadata. Keep sensitive or privileged material out of public pages.
- Catalogue: assign or confirm a stable Evidence Library identifier; record provenance, hash where available, preservation location, access restrictions and what the artifact does and does not establish.
- Control: update the authoritative case ticket; associate the task to its work-package and project ticket where those records exist; set one accountable owner, a justified priority, the next action and a verified due date.
- Accept: distinguish acknowledgement, substantive response, artifact received, search completed, no-records response, withheld/partial response and unconfirmed lead. An acknowledgement alone never closes the work.
- Escalate and learn: act the same day on a statutory/preservation threat; issue an exception when tolerance is forecast to be exceeded; record decision/lesson, next control date and evidence of completion.
Control rules: no automatic merge, deletion, sending, or completion changes to improve dashboard counts. Duplicate resolution requires review of associations and source context. The no-send quarantine is a safety state, not closure.
Page version & change log
Current version: 1.2.0
| Version | Date (UTC) | Editor (human or agent name) | Change | Source / evidence |
|---|---|---|---|---|
| 1.0.0 | 2026-10-18T15:20Z | the Executive’s Tab agent | Footer standardised; no content change | Editing Protocol, 18 Oct 2026 |
| 1.1.0 | 2026-10-19 | GPT-6 | Added 19 Oct operational assurance baseline and deterministic artifact-recovery controls | HubSpot audit and associations, 19 Oct 2026 |
| 1.2.0 | 2026-10-19T21:09Z | the Executive’s Tab agent | Added current baseline section (19 Oct 2026): Current PID summary and tailoring; earlier content kept | Owner, 21:59 BST 19 Oct 2026 (PRINCE2 update and PM File); sources: send-readiness list, 19 Oct WG letters, research cycle 14, task ledger |
Agents and editors: follow the Editing Protocol.
PRINCE2 7 outlines: sources · product set · archive