Inspection-Ready Bundle
For adminsInspection-Ready Bundle
Section titled “Inspection-Ready Bundle”When an inspector, safeguarding review or audit committee arrives, they tend to ask for the same handful of documents first. The Inspection-Ready Bundle assembles those into a single signed ZIP at the press of one button, so you don’t have to export each artefact separately and collate them by hand.
Find it under Admin → Trust → Inspection-Ready Bundle (served at /admin/inspection-bundle).
Permission
Section titled “Permission”The bundle is gated on platform::assurance::manage. A trust admin passes the gate automatically. Generating a bundle is read-only apart from a single audit row — it assembles artefacts that are each already exportable on their own.
What’s in the ZIP
Section titled “What’s in the ZIP”- cover — your trust, the provenance of the bundle (who generated it and when) and a headline KPI strip drawn from the assurance report and the estates compliance summary.
- scr-annex-f — the KCSIE Annex F snapshot of the Single Central Record. The same artefact as the standalone SCR inspection export, inside the bundle.
- trust-assurance-report — the live Trust Assurance posture: every open finding with its owner, due date and status.
- compliance-summary — every active estates compliance schedule, with overdue and due-soon items flagged and the relevant regulation references.
- manifest.json — a machine-readable list of everything in the bundle, including a pointer to the audit row.
- README.txt — a short explainer for whoever receives the ZIP.
File formats
Section titled “File formats”Each document is rendered to PDF by a headless browser at the moment you generate the bundle. Where the host has no browser available, that document is included as HTML instead — it opens in any browser and prints to PDF identically. The bundle never fails for the want of a renderer.
The audit trail
Section titled “The audit trail”Each generation writes a tamper-signed audit row (event=platform.inspection_bundle.generated) recording the filename, the constituent sections, the workspace and who generated it. The bundle itself isn’t stored — the audit log is the record of what was produced and when. To reproduce a bundle, generate a fresh one; to prove one was produced, filter the audit log.