In this piece for Security Matters, Lloyd Major, Founder and CEO of Halo Solutions and former counter-terrorism officer, turns to a part of Martyn’s Law that’s had far less attention than scope and tiering: the notification requirements the SIA confirmed detail on this year.

His argument is that notification should be the output of an organisation being ready, not the trigger for getting ready — and that the three-month window most people read as breathing room is actually only for telling the regulator, not for working out who’s responsible in the first place. On multi-stakeholder sites, that question turns out to be harder than it looks: landlord, operator, promoter, security contractor and local authority can all have a legitimate claim, and Lloyd argues it needs a workflow across functions, not a single named owner.

He closes on what he calls the trigger mechanism — not the risk assessment or the notification form, but whether an organisation actually finds out when something changes that affects its obligations, before it becomes a problem.

This builds on the operational-readiness territory Lloyd has been developing since the earlier “Compliance to Operational Readiness” piece, but is a new piece written specifically for the notification requirements and Security Matters’ readership, not a repeat of it.

Read the full piece here.