A security plan rarely fails because nobody wrote one. It fails because conditions changed, people assumed the plan still fitted, and the gap was only noticed when pressure exposed it. The real question is not whether plans should be reviewed annually. It is when should security plans change because the risk, operating environment or organisational capability has moved on.

A dated plan can create false confidence. It may still meet an internal document control requirement, yet describe a site, team, threat picture or response arrangement that no longer exists. Protective security planning must reflect reality as it is operated, not reality as it was described at approval.

Security plans should change when the operating picture changes

The most obvious trigger is a material change to the site or operation. New entrances, altered public access, revised opening hours, construction works, tenancy changes, new suppliers, a different event format or increased footfall can all change exposure. These are not merely facilities issues. They affect supervision, access control, evacuation, communication and the ability of staff to spot behaviour that does not fit.

Consider a venue that adds an external queuing area to improve visitor flow. On paper, this may look like a minor operational change. In practice, it shifts the point at which visitors gather, changes how staff observe the approach to the building and may create a period where people are outside established screening or management arrangements. The plan needs to catch up before the change becomes routine.

The same applies to organisational change. A reduced security team, a new control room provider, a revised incident management structure or a greater reliance on agency staff can affect the plan’s assumptions. A plan that requires a trained manager to make a decision within minutes is of limited value if that manager is no longer regularly on site.

Plans should also change when an assessment identifies a different threat or vulnerability. That does not always mean a dramatic new threat. More often, it means a gradual shift in relevance. A business may have expanded its profile, begun handling sensitive information, introduced lone working, or accumulated practical weaknesses around access, reporting or contractor management. Risk assessments should feed planning, not sit separately as evidence that a review happened.

When should security plans change after an incident?

After an incident, near miss or credible concern, organisations often rush to write another procedure. That can be the wrong response. First establish what actually happened, what people saw, what decisions were made and what constrained them.

The key question is whether the plan failed, was not understood, was impractical, or was simply not used. Those are different problems. Rewriting a plan will not fix a team that has not practised decision making. Equally, more training will not fix a plan that assigns responsibilities to people who are unavailable or gives no authority to act.

Near misses deserve the same discipline. A suspicious item that is resolved safely, an unauthorised person stopped at an access point, or a confused evacuation that ends without injury can be dismissed because the outcome was acceptable. That is a missed opportunity. Good security teams examine the process, not just the result. Luck is not capability.

A structured debrief should look beyond the immediate event. Did information reach the right person? Did staff recognise the issue early enough? Were roles clear? Could the team communicate with partners, tenants or emergency services? Did the response create a new safety or security problem elsewhere? The answers should lead to specific amendments, clear ownership and a test of the revised arrangement.

Capability is a trigger, not an afterthought

Many security plans contain sensible instructions that no one has properly tested. This is common where planning is treated as a compliance exercise. The document is approved, distributed and filed, while the people expected to carry it out have had a briefing rather than meaningful practice.

A plan should change when testing shows that staff cannot deliver it. That is not a criticism of staff. It is evidence about the system. If front line personnel cannot explain how to escalate a concern, if managers hesitate over authority, or if teams cannot maintain control during a busy and uncertain incident, the plan is asking more than the organisation can currently deliver.

Tabletop exercises are useful, but only when they challenge assumptions. Ask what happens on a Saturday evening, during a handover, with a reduced team, a failed radio, competing customer demands or a senior decision maker off site. The aim is not to catch people out. It is to identify where written intent and operational reality separate.

This is particularly relevant to organisations preparing for Martyn’s Law. A policy, training record and nominated responsible person may be necessary elements of preparedness, but they do not demonstrate effective action under pressure. The standard worth pursuing is practical readiness: people recognise concerning circumstances, communicate clearly, make proportionate decisions and recover control.

Review cycles matter, but trigger based reviews matter more

An annual review is sensible housekeeping. It confirms contact details, checks document ownership and prevents plans being forgotten. It is not enough on its own.

Security planning needs a trigger based approach. Material operational change, an incident, a near miss, a new risk assessment, a significant exercise finding, a change in staffing or suppliers, and intelligence that affects the organisation’s risk profile should each prompt review. The scale of the review should match the change. Not every trigger requires a complete rewrite, but every trigger requires a conscious decision that the plan remains suitable or needs amendment.

That decision should be recorded with enough clarity to be useful later. State what changed, who considered the consequence, what was amended and how the revised arrangement will be communicated and tested. This is not paperwork for its own sake. It protects organisational memory, particularly where people and contractors change.

Avoid the temptation to create a master plan that attempts to prescribe every possible scenario. Long plans are often harder to use and harder to maintain. Staff need clear principles, defined responsibilities, workable escalation routes and practical actions relevant to their role. Detailed supporting procedures can sit beneath the main plan where they are genuinely needed.

Make changes visible in the working environment

A revised plan is only improved if the change reaches the point of delivery. Sending an updated PDF to a shared folder does not achieve this. Managers need to explain what has changed, why it matters and what staff need to do differently. Supervisors should be able to observe whether the new arrangement works during normal operations.

For significant amendments, use a proportionate cycle: brief the people involved, test the new process, debrief honestly and adjust again if needed. This is where security plans become operational capability rather than static documents.

There is a trade off. Constant changes can confuse staff and undermine confidence, especially if each amendment is poorly communicated. Waiting for the annual review creates a different risk: known weaknesses become accepted practice. Good judgement lies in distinguishing minor administrative updates from changes that affect safety, security or decision making.

Mildot Group’s work repeatedly finds that the strongest organisations do not claim to have a perfect plan. They know which assumptions their plan depends on, test those assumptions and change course when evidence demands it. That is a more credible form of resilience.

The useful question for any security manager is not, “When did we last update this plan?” Ask instead, “What has changed since this was written, and would our people still know what to do when it matters?”