SCR inspection export

For the helpdesk team

Inspection export

When Ofsted, the local authority, or an internal auditor wants to see the SCR, the export landing page is the surface. One page, four output formats — pick whichever the inspector asks for.

What gets exported

The full SCR for the current workspace at the moment of export:

Every person on the register.
For each person, every check type and its status: completed / pending / not required / not applicable.
The date of each completed check.
Annex F layout (the standard inspection format).

Sensitive details — DBS numbers themselves, certificate scans — are never on the inspection export. They’re shown only on the per-person inspection screen, not the export. The export confirms a check was completed; it doesn’t reveal the check’s contents.

Formats

Printable HTML — opens in a new tab, designed for the operator’s browser print → PDF flow.
PDF — server-rendered via Browsershot. The “official” file you’d hand over.
CSV — flat, one row per person × six columns per check (status, issued, expires, verified, date checked, checked by).
XLSX — formatted Excel via OpenSpout. Conditional formatting on overdue cells.

The PDF and XLSX paths are the recommended formats for handover — printable HTML is for ad-hoc viewing on screen.

Audit trail

Every export call writes a tamper-signed audit row tagged scr,inspection-export. The audit captures who exported, when, which format, and the row hashes of the data exported. This is the inspection-trail receipt — yes, we exported the SCR on date X for inspector Y.

The DSL can pull these audit rows from the platform-admin audit log.

When to export

Before any inspection — fresh export the morning of.
At quarterly review — the DSL reviews the previous quarter against the current state.
When a check type changes — material restructure of the SCR. Audit handover.

Don’t share exports outside the trust without a clear lawful basis — the SCR is heavy data-protection territory.

Gotchas

The export is point-in-time. An inspection two weeks after export shouldn’t be read against a stale export — re-export.
A printable-HTML export saved as PDF in the browser doesn’t produce the audit row — only the server-rendered exports do. Use those for inspection handover.
File size grows linearly with people × check types. A 1,500-person trust running 10 check types produces a ~3 MB XLSX.