PRINCE2 Project Initiation Documentation — G0 Pack

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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.