A policy can say that everyone is responsible for security. A staff survey can report that people take security seriously. Neither tells you what will happen when someone spots suspicious behaviour, a door is left insecure, a threat is reported late, or a manager must make a difficult call with incomplete information. To make security culture measurable, organisations need to assess what people actually notice, decide and do.
That is harder than counting training completions, and more useful. Security culture is not a mood, a poster campaign or an annual awareness week. It is the pattern of behaviour that appears when normal routines are disrupted, pressure rises and nobody is standing over the individual with a checklist.
For organisations preparing for Martyn’s Law, or managing wider protective security responsibilities, this distinction matters. A documented plan may satisfy an internal process. It will not, by itself, help a receptionist challenge an unfamiliar person appropriately, a duty manager recognise when escalation is necessary, or a team maintain calm and control during an unfolding incident.
What measurable security culture really means
A measurable culture is one where leaders can identify whether the organisation has the practical capability to prevent, identify, report, assess and respond to security concerns. It does not mean reducing human behaviour to one score. People, roles and operating environments differ. It means gathering enough relevant evidence to make a defensible judgement about readiness.
The evidence should answer practical questions. Do people know what normal looks like in their area? Can they recognise behaviour or circumstances that require attention? Do they report concerns early, through a route they trust? Are supervisors able to make proportionate decisions rather than simply pass problems upwards? Can the organisation learn from minor failures before they become serious events?
A high reporting rate is not automatically a sign of a good culture. It may show awareness and confidence. It may also show poor judgement, unclear thresholds or a workforce that has learned to report everything to protect itself. Equally, a low reporting rate might reflect a genuinely low-risk environment, but it can also indicate resignation, fear of being wrong or an inconvenient reporting process.
The number only becomes meaningful when examined alongside the quality of reports, the speed of triage, feedback to staff and the operational context.
Start with behaviours, not values
Many security programmes begin with broad statements such as “be vigilant” or “security is everyone’s responsibility”. These are reasonable aspirations, but they cannot be assessed unless translated into observable behaviours.
For a venue team, the behaviour may be recognising and reporting an unattended item or an access concern without causing unnecessary alarm. For facilities staff, it may be challenging an unfamiliar person in a restricted area using an appropriate, safe approach. For senior managers, it may be knowing when commercial pressure must give way to a security decision, and being prepared to support that decision afterwards.
The point is not to script every action. Over-prescription creates brittle responses. People need judgement because real conditions rarely match the training example. But the organisation should be clear about the decisions it expects people to make, the authority they have, and when they must seek support.
This is where many security cultures fail quietly. The organisation tells staff to report concerns, then provides no useful feedback. It asks supervisors to take ownership, but gives them no practice in decision-making. It expects challenge, yet a member of staff who raises an awkward issue is treated as disruptive. The written message and the lived experience are not aligned.
Measures that reveal capability
The strongest measurement model uses a mix of leading and lagging indicators. Lagging indicators record what has already gone wrong, such as incidents, losses, breaches or response times. They matter, but they are a poor basis for judging culture on their own. A serious incident is uncommon, and a lack of incidents can mean either good control or good fortune.
Leading indicators look for the conditions that make good performance more likely. They should be practical and role-specific. Useful measures include:
- the proportion of people who can correctly identify reporting routes and escalation thresholds in realistic scenarios;
- the quality, relevance and timeliness of security observations and reports;
- supervisor confidence and accuracy when assessing a concern or directing an initial response;
- completion of exercises that test decisions, communication and handover, rather than recall alone;
- the time taken to close identified vulnerabilities and whether the corrective action has actually worked;
- evidence that staff receive feedback after reporting concerns, including where the report did not lead to further action.
None of these measures should be viewed in isolation. A team with a high assessment score but weak reporting may understand the theory yet lack confidence in the system. A site that closes vulnerabilities quickly may be efficient, but repeated versions of the same issue suggest that the underlying cause has not been addressed.
Qualitative evidence also has a place. Short debriefs, structured conversations with frontline teams and observation during routine activity can expose gaps that a dashboard will miss. People often know where security arrangements are impractical long before that issue reaches a senior meeting.
Assess judgement, not memory
A multiple-choice test has value when it checks essential knowledge. It is not a test of operational capability. Someone can remember a definition of suspicious activity while still missing the significance of a situation in their own workplace.
Scenario-based assessment is more revealing. Present a realistic, role-relevant situation and ask what the person would notice, what information they would gather, who they would notify and what they would do first. The aim is not to catch people out. It is to establish whether their judgement is proportionate, timely and safe.
Immediate feedback is particularly valuable. It turns assessment into development rather than an administrative hurdle. It also provides organisations with aggregated evidence of where knowledge, confidence or decision-making is weak. That is far more useful than a completion report showing that 96 per cent of staff clicked through an eLearning module.
Measure the system around the person
It is unfair and ineffective to measure employees without measuring the conditions in which they work. Security behaviour is shaped by workload, leadership, equipment, layout, procedures and local norms.
If a reporting system is difficult to access, staff will use it less. If a control room is understaffed, reports may wait. If managers dismiss concerns because they are busy, people will soon stop raising them. The resulting data might appear to show an unengaged workforce when the real weakness lies in the operating system.
This is why measurement should include friction points. How many steps does it take to report a concern? Is support available outside normal office hours? Are shift workers included in briefings and exercises? Do contractors understand the standards expected of them? Does the person receiving a report know how to assess it?
A security culture cannot be separated from management culture. Leaders set the practical standard when they make time for reporting, ask sensible questions after an incident and accept that early intervention occasionally creates inconvenience. If leaders only reward uninterrupted operations, staff receive a clear message about what matters most.
Avoid the dashboard trap
Senior leaders often want a simple red, amber and green view. That is understandable. Decisions need clarity. The risk is that an apparently neat score conceals important weaknesses.
A single culture score can be useful as a trend indicator, provided it is supported by detail. It should never become the target in its own right. Once a metric becomes something people must improve at all costs, behaviour changes to serve the metric. Reports become inflated, assessments become easier or local issues are quietly reclassified.
Use measures to prompt questions, not to close them down. Why did reporting fall on one shift? Why are certain teams less confident in challenging access? Why do exercises show slow escalation despite high training completion? The answers may point to a training need, but they may also expose unclear authority, poor supervision or a process designed without frontline input.
Building a measurement cycle that lasts
Start with the threats and vulnerabilities that matter to the organisation, not a generic culture questionnaire. Define the few behaviours that would make the greatest difference to prevention, detection and response. Assess current capability using scenario-based evaluation, report quality, exercises and informed observation.
Then act on the findings. Provide targeted learning, simplify poor processes, coach managers and test whether change has worked. Reassess at sensible intervals and after significant operational changes, such as a new site, changed operating hours, major event or revised threat picture.
Mildot Group’s approach to capability evaluation is built around this principle: people need feedback that helps them improve, while leaders need evidence that supports better decisions. Neither is served by training records alone.
The useful question is not whether your organisation has a positive security culture. Most organisations will say that it does. Ask instead: when a real concern emerges on an ordinary working day, can your people recognise it, make a sound decision and act with confidence? If you cannot evidence the answer, you have found the next area to improve.
