Letter · PTD-ARC-2024-009
Reporting definition letter
Internal letter recording common reporting-date definitions.
PTD CAPITAL LLC PTD-ARC-2024-009 REPORTING DEFINITION LETTER Original record date: 1 July 2024 Recorded author: Systems & Data Reconstructed edition: 16 October 2026 / Version 2.0 / Open To the portfolio reporting roles, The archive retains a letter concerning common reporting-date definitions. This reconstructed edition presents the distinctions used by the current central register. It preserves the original record date without representing the expanded text as a signed letter available in July 2024. 01 / Dates describe different events An event date records when an operating action occurred. A period end defines the boundary of a report. A publication date records release of the document. A revision date records a later change. These fields must remain separate even when two dates happen to coincide. A target date is the intended boundary for a workstream. It is not a completion date. When work moves, the original target remains in the history and the revised boundary receives a dated record. A completion record requires a completed state and evidence identifying the accepted result. An indicator's as-at date describes the observation. It is not the day on which a web page was rendered or a PDF regenerated. A historical report must continue to use its accepted observation after the live project record changes. 02 / Definitions and units An indicator has a stable identifier, label, unit, collection method and source. A queue count, a completion count, a percentage and an interval answer different questions. They are not added into a single performance total. A prior observation is shown only where the population and method remain comparable. Unavailable is distinct from zero. Zero records an observed absence within a defined population. Unavailable records the lack of sufficient evidence. The reporting system must not impute a plausible value to preserve the appearance of a continuous chart. Planning parameters remain separate from operating observations. A proposed capacity or participation cohort is useful for reviewing a programme, but it does not establish installed capacity, signed participation or work delivered. 03 / Revision and reconciliation When a definition changes, the file retains the earlier method and the reason for revision. The responsible role decides whether earlier observations can be compared, restated with an explicit note or left outside the new series. The same rule applies to narrative: a correction in the project record must be reconciled with the report before a new version is released. Sources: metric and metric-history schemas; workstream target and completion fields; report-snapshot and document-revision registers; Reporting Dates, Definitions and Revisions. Expanded edition recorded on 16 October 2026.