Product Breakdown Structure & Product Descriptions

page · 2026-10-18T18:19:57Z · from wiki page 5284

Part of Workstream: evidence recovery. Product Breakdown Structure & Product Descriptions (originally wiki page 5284) was copied unchanged on 19 October 2026; this site stands alone, so evidence references are given as plain IDs (e.g. EV-0249). All PRINCE2 pages →

About this page type → Read the Docs#prince2-pbs

Product Breakdown Structure — 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.

GroupProducts
ManagementMandate; Brief; PID; Business Case; Plans; Registers; Reports; CI records; PM File (PDF)
EvidenceEV pages (EV-0001–EV-0243); Evidence Register 4517; Pending Evidence; Closure Log; Source Conflicts; Kissed Frogs
RequestsGmail drafts; sent emails; HubSpot send tasks; send-readiness list
Public recordWiki; dartboard, bpvsbuckler, wayback, email and clerk sites
DecisionICR complaint (PD-04); legal triage paper; End Stage Report

Product descriptions added 19 Oct

PDProductQuality criteria
PD-07Outbound emailOne per body; correct To (last reply address); refs/dates/quotes checked; no accusation as fact, threat, admission, placeholder, cc/bcc or banned phrase; not a duplicate; HubSpot task closed after send
PD-08Debrief runEvery relevant new item on each surface; live check of each; Cloudflare deploy of the new commit confirmed; one Change Log row
PD-09PM File (PDF)PRINCE2 products only; contents with bookmarks; tables legible; version and date on title page

Product breakdown

No.Product
0Closure-tested evidence position (project product)
1Management products: Mandate; Brief; PID; Business Case; Plans; Registers; Reports
2Evidence products: 2.1 Evidence Register and EV pages (PD-01); 2.2 Pending Evidence (PD-02); 2.3 Closure Log (PD-05)
3Title products: 3.1 Title-chain reconstruction (PD-03); 3.2 Estate parcel table (PD-06)
4Route products: 4.1 Custodian and route matrix (WP-OQ-01/02); 4.2 Complaint pathways (WP-OQ-03); 4.3 ICR full complaint (PD-04); 4.4 Court-application options paper (WP-OQ-04)
5External products (supplied by others): HMLR official copies; archive images; FOI/EIR/SAR replies; legal advice

Activity breakdown (WP-00 to WP-39): Delivery Breakdown.

Product descriptions

PD-01 Evidence page (EV-NNNN)

FieldEntry
PurposeHolds one document and what it does and does not prove
CompositionHeader table (EV ID, title, date, type, repository and reference, status); quotation; Proves; Does not prove; claims relying on it
DerivationArchives, HMLR, press, family papers, media library
FormatWiki page, slug evidence/ev-NNNN-…
Quality criteriaEvery field filled or marked unknown; Proves states only what the document shows; scan linked when HELD
Quality methodLine-by-line check against the source
ResponsibilitiesProducer: Tab (research). Reviewer: Project Assurance TBC — Sion to confirm. Approver: Executive

PD-02 Pending Evidence entry

FieldEntry
PurposeRanks records not yet held and how to obtain them
CompositionEV ID; record; holder; route; cost; who acts
DerivationPending items on EV pages
FormatRow on Pending Evidence
Quality criteriaRoute and cost sourced or marked TBC
Quality methodCost check against fee schedules
ResponsibilitiesProducer: Tab. Approver: Executive

PD-03 Title-chain reconstruction (AC-006)

FieldEntry
PurposeShows each conveyance from 1877 to WA240304
CompositionPer item: date, parties, parcel, plan, state (produced / recited / schedule-listed / missing / not examined), EV ID
DerivationEV pages; HMLR copies
FormatTable on a wiki page
Quality criteriaEvery row cites an EV ID or PENDING
Quality methodTitle-chain review; parcel-map cross-check
ResponsibilitiesProducer: Tab. Reviewer: legal adviser TBC — Sion to confirm. Approver: Executive

PD-04 ICR full complaint (ICR/090/26)

FieldEntry
PurposePuts the HMLR complaint to the Independent Complaints Reviewer
CompositionComplaint points; chronology; evidence list with EV IDs; remedy sought
DerivationForm 1C; HMLR schedule; stage 1–2 replies
FormatDocument sent by Sion
Quality criteriaEach point traceable to an EV page; dates checked
Quality methodEV citation check; Sion review
ResponsibilitiesProducer: Tab drafts. Approver and sender: Sion

PD-05 Closure Log

FieldEntry
PurposeRecords the closure status of every identified item
CompositionItem; status (5); basis; date; EV ID
DerivationEvidence Register; replies
FormatTable on a wiki page
Quality criteriaNo item without a status and its basis
Quality methodExecutive review
ResponsibilitiesProducer: Tab. Approver: Executive

PD-06 Estate parcel table

FieldEntry
PurposeCharacterises each parcel of the Cedwyn Estate
CompositionParcel no.; names; tithe owner/occupier; later owners; title numbers; events; evidence label per cell
DerivationDB/E/1, tithe apportionment, HMLR INSPIRE, press
FormatTable page
Quality criteriaEvidence label on every cell; field level needs DB/E/1
Quality methodPrimary-source check per cell
ResponsibilitiesProducer: Tab. Approver: Executive

Project product description: Brief §3.

Page version & change log

Current version: 1.1.0

VersionDate (UTC)Editor (human or agent name)ChangeSource / evidence
1.1.02026-10-19T21:09ZTab (for Sion Buckler)Added current baseline section (19 Oct 2026): PBS groups; PD-07 to PD-09; earlier content keptSion Buckler, 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.