Mock Data Programme Effectiveness · Martyn's Law · 12 weeks post-rollout
Methodology Open the course →
Portfolio · Programme Effectiveness

Twelve weeks of Martyn's Law data. Three cohorts, twelve venues, one content patch.

The dashboard a Head of Compliance opens twelve weeks after we ship the course across their estate. Did people finish it. Did they get it. Is anything actually different on the floor. Most ID portfolios stop at the course; this one keeps going.

Estate  12 venues · 4 Standard, 8 Enhanced
Enrolled  2,847 staff across 3 cohorts
Course  v1.0 → v1.1 (week 5 patch)
Window  Weeks 1–12 post-rollout
Completion
-
-
Comprehension
-
-
Near-miss reports / wk
-
-
Audit-readiness
-
-
Tabletop pass rate
-
quarterly
Time window
Week 12 of 12

Drag the marker, click a week, or use to scrub. Amber ticks mark interventions logged that week.

Adoption
Completion % over time, by cohort
Whether the course is reaching every cohort fast enough to matter for the next live event.
Comprehension
Assessment scores by module and cohort
Where the cohort is thinning. Which decisions lose people, on which track.
Behaviour-change signals
Near-miss reports, audit-readiness, incident-report quality
Near-miss reports filed (weekly) -
Audit-readiness index (0–10) -
Incident-report quality (0–10) -
Completion tells you people did the course. These three tell you whether they're doing anything different at work.
Iteration log
What we changed and why
Where the work happens after you ship. Without a log, you can't show what you changed or why.
Where to act
What to do next, by cohort. Week 12.
Methodology · Where each metric would come from