Bernalo · case studies Get in touch →
← All case studies
Incident & reliability

The pattern was already found. It just wasn't shown.

A redesign of a genuine post-incident review — eleven real public-sector data breaches, each written up separately, when the report's own findings had already named the three causes most of them shared.

The cause groupings shown below are this redesign's own reading of each incident's stated cause, not an official government classification. The source report is explicit that no single pattern fits every incident.

The pattern

A post-incident review earns its keep by finding what's shared across cases, not by documenting each case in isolation. This report did that analytical work — its Findings section names three recurring causes clearly. But the appendix where the eleven individual incidents are described doesn't connect back to them, leaving the reader to do the cross-referencing by hand.

Exhibit E

Appendix 2: overview of incidents reviewed

Information Security Review 2023
Cabinet Office, Government Security Group and Central Digital and Data Office. Reused under OGL v3.0, © Crown copyright.
Before

1. PSNI, 2023. Personal data of c10,000 officers published in an FOI response. The data was contained in a separate worksheet within the main spreadsheet and was not spotted during checks.

5. MOD, 2021. 245 ARAP applicants emailed in copy rather than blind copy. The email addresses of the applicants were placed in copy rather than blind copy field.

...nine more incidents follow in the same narrative format, in review order, with no link back to the three causes named earlier in the report.
After

7 of 11 incidents trace to 3 recurring causes

IncidentCauseOutcome
PSNI, 2023Up to £217m est. cost
Norfolk & Suffolk Police, 2021–23ICO investigation ongoing
MOD (.ml domain), 2023National security risk
MOD (ARAP), 2021Threat to life risk
IICSA, 2017£200k ICO penalty
Cabinet Office (Honours), 2019Ad-hoc / system config£500k ICO fine
HMRC, 2008Ad-hoc / system configPublic confidence damage
Digital ID; NHS Lanarkshire; DWP x2; Public Health WalesOther / descopedVaried
Report ↗ Read the full review

All eleven incidents in full narrative detail, plus the review's recommendations grouped by process, technology, policy, and culture.

What changed
  • 01

    Cause leads, not chronology

    Incidents are grouped by what caused them, connecting the appendix back to the report's own named findings.

  • 02

    The headline states the pattern

    "7 of 11 trace to 3 causes" is the finding a reader actually needs, stated up front.

  • 03

    Full narratives stay one click away

    Nothing is lost — the source report remains the place for incident-level detail.

Why this matters

The analysis existed before the write-up did

This report had already done the hard part — finding what was shared across eleven separate incidents. The write-up format then obscured its own conclusion by defaulting to narrative order instead of the order that mattered: cause.

Have a report like this?

Send the page. I'll show you what it could look like.

If you've got an incident review, RCA, or reliability report where the pattern across cases is real but buried in narrative order, I'll take one section and redesign it — no cost, no obligation — the same way as above.