CPD Report
Feature Overview
The CPD Activities Report and its CSV / PDF exports — structure, branding, audit footer, column layout, and compliance metrics. The canonical multi-feature export ACs live in exportable-reports.md; this spec covers the CPD-specific report surface. Split out of cpd.md on 2026-05-27.
Open Questions
All questions have been answered.
Acceptance Criteria
- ✅
cpd.export.report-structure— the exported report is structured (1) high-level summary → (2) detailed activity log (CSV-equivalent) → (3) evidence appendix, with no hyperlinks to evidence (URLs/PII stripped — security). Canonical export ACs live inexportable-reports.md. † - ✅ Date-range filter is timezone-safe for AEST/AEDT
- ✅ Export CSV button on CPD Activities Report
- ✅ CSV uses friendly headers and escapes formula-injection chars
- ✅ Export button disabled with tooltip when no activities visible
- ✅
cpd.report.activity-names-match-published— every activity name in an exported CPD record is the string the published CPD Activities by Category and Hours (July 2026) table uses, character-for-character. The export is the artefact a regulator reconciles against the published list, so a name that differs only by casing or hyphenation (eLearningfor the publishede-Learning,Patient Experience SurveyforPatient-experience survey) yields no exact match and makes the record harder to audit, not merely untidy. The names come from the same master list the report is built from (seecpd-activities.md § cpd.activity.master-list-is-the-published-table), so the report cannot drift from the published spelling independently. (#11057) † † ‡ - ✅
cpd.report.pdf-export— PDF export for CPD Activities Report; a PDF export button is available alongside the existing CSV export; columns are auto-sized and do not require user adjustment †. Layout, branding, and audit footer per § PDF — branding & layout below.
PDF — branding & layout
Applies to every CPD-generated PDF: the existing certificate (✅ #3694) AND the upcoming Activities Report PDF AND any future reports (e.g. End-of-Year Reflection). Generated via the project's pdf-producer agent which enforces this contract.
✅
cpd.pdf.typography— body type Nunito with Arial fallback per/brand/typography; H1/H2/H3 sized per the brand scale✅
cpd.pdf.colour— primary brand blue + category accents drawn from/brand/colour— same palette as CPD Home, no ad-hoc colours✅
cpd.pdf.logo— full PPP logo from/brand/logo-assetsin the header band; icon mark in the footer✅
cpd.pdf.layout— header band, content sections, footer with audit metadata. Layout follows/brand/componentsand/brand/guidelines✅
cpd.pdf.audit-footer— every page footer carries: generated date (ISO 8601), user name + PPP ID, date range or plan year, content hash (SHA-256 of body),n / Npage numbers✅
cpd.pdf.accreditation-line— closing line: "Generated by PPP — AMC-accredited CPD Home" on the final page✅
cpd.pdf.accessibility— WCAG 2.1 AA contrast across all text, document tagged with structure (headings → roles, table headers → row scope), alt text on logo image, embedded TOC for multi-page reports✅
cpd.pdf.same-contract-cert-and-report— the existing certificate PDF and the Activities Report PDF share the same brand contract; certificate AC retroactively covers items above (cert was built before this contract was speced — track in follow-up issue)✅
cpd.certificate.verified-only— the formal CPD certificate aggregates PPP-verified hours only; provider-replied (unverified) hours are excluded until a PPP super-admin completes stage-2 verification, because the certificate is regulatory evidence. This is the certificate-side half of the #8770 split — the in-app progress surfaces (to-do CPD gap + roadmap milestone cadence) deliberately diverge and credit verified + provider-replied (unverified) hours (seecpd.unverified-hours.progress-surfaces-includeincpd.md). ‡ † (#8770)✅
cpd.pdf.use-pdf-producer-agent— backend code generating these PDFs MUST go through thepdf-produceragent's enforcement (brand consistency + accessibility + audit trail) — never a one-offpuppeteerscript✅
cpd.report.column-widths— Activities Report renders without horizontal scroll up to 1280px; column widths are pre-set and auto-sized, no user resizing required † (5 May)✅
cpd.report.provider-data-loaded— Provider list populates fromcpdProviders.listfor the current user; regression for the missing-provider bug Rob raised on 5 May✅
cpd.report.compliance-metric-mo-rp— Report shows a combined compliance metric for Measuring Outcomes + Review of Performance alongside the per-category breakdown; aggregates verified hours from both categories vs the 25h cap✅
cpd.report.program-requirements.real-counts— Program Requirements chips count verified activities bycpdCategory.name, mirroring the CPD Home PLR ticks, so they agree with the dashboard instead of reading 0✅
cpd.report.multifeature-export-plr-column— the multi-feature export (on-screen curated columns, CSV, and PDF; distinct from the Activities Report's Program Requirements chips above) surfaces a human-readable "Program Requirements" column derived from each CPD row's confirmed, non-rejected PLR claims, instead of silently excludingplrClaims/plrConfirmationsas internal plumbing. Governed jointly withexportable-reports.md(exportable-reports.cpd.plr-coverage-column) — this AC records that the multi-feature export lives undercpd-report's code-paths (instances/ppp/src/modules/reports/MultiFeature/**), that skill records the derivation logic and policy rationale. (2026-08-23) (#11046) † ‡
Open GitHub Issues
Open issues on label:feature:cpd-report — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-10-04 | The evidence appendix of the exported report no longer aborts the whole PDF when an activity name contains characters the standard PDF font cannot encode, and its "back to contents" line no longer uses an arrow glyph that failed to encode. Unencodable characters render as "?". | #0, #12601 | Reported on UAT (#12601) against the Multi-Feature Report PDF export; the evidence appendix is shared with this report's structure AC (cpd.export.report-structure). No acceptance criteria change. |
| 2026-07-27 | Adds cpd.report.activity-names-match-published: every activity name in an exported CPD record is the published July-2026 string character-for-character. Nine names are corrected at source (e.g. "eLearning" to "e-Learning", "Patient Experience Survey" to "Patient-experience survey"), and the report draws them from the same master list, so it cannot drift from the published spelling independently. | #11082, #11057 | The export is the artefact a regulator reconciles against the published list. A name differing only by casing or hyphenation yields no exact match, which makes the record harder to audit rather than merely untidy — so this is a correctness concern for the report, not a cosmetic one (#11057). |
| 2026-06-01 | Program Requirements chips on the User Activities report now count verified PLR activities by cpdCategory.name, matching the CPD Home dashboard PLR ticks, instead of grouping by the legacy cpd_classes dimension. | #7992, #7945 | Screen-by-screen review found the report chips read "0 hrs (0)" for Cultural Safety / Health Inequities / Professionalism / Ethical Practice while the dashboard correctly ticked the same PLRs 1/1 for the same user. PLRs are tracked by category name, not cpd_classes, so the two surfaces disagreed. |