A workplace violence prevention plan is a written document that sets out how an organisation identifies the risk of violence at its sites, what staff must do when a threat appears, how every incident and near miss is recorded, and who reviews the record afterwards. It is a prevention and response system, not a policy statement filed in a drawer.
Most organisations discover the gaps in their workplace violence prevention plan on the worst possible day. A contractor becomes aggressive at the gate. A dismissed employee comes back to the car park. A customer escalates at a reception desk and a lone officer has to decide, in about four seconds, whether this is a de-escalation or a code call.
What separates a plan that works from a plan that exists is whether the answers were decided in advance and whether the record holds up afterwards. This guide covers the seven parts a workplace violence prevention plan needs, the mistakes that hollow one out, and where a security platform fits – which is not writing your policy, but proving what actually happened.
Why a workplace violence prevention plan matters
Violence at work is rarely a single unexpected event. It is usually the end of a sequence: a complaint nobody logged, a threat somebody mentioned verbally, an aggressive visitor who was turned away but never recorded, a door fault that let someone into a controlled area. Each one on its own looks minor. Together they are a pattern – and a pattern is only visible if the individual events were written down.
That is the first reason a plan matters. It forces the low-level events into a record where the pattern can be seen before it escalates.
The second reason is legal exposure. Where an incident goes to an insurer, a regulator or a court, the questions are predictable. Did you assess the risk. Did staff know what to do. Was the earlier warning reported. What did you do about it. An organisation that can answer those with dated records is in a very different position from one answering from memory.
The third reason is the people on shift. Guards, receptionists and lone workers are the ones who meet the threat first. A plan tells them what is expected of them, which is the difference between a considered response and an improvised one.
How a workplace violence prevention plan works
A plan runs as a loop, not a document. It has four moving parts.
Assess. Identify where violence is plausible at each site – the gate, reception, cash handling, night shifts, lone-worker posts, car parks – and what makes each one riskier.
Prevent. Put the controls in place that lower that risk: access control at entry points, working panic buttons and intercoms, defined lone-worker posts, and briefings that tell the shift what to watch for today.
Respond. Define what happens the moment a threat appears. Who is called, what code is activated, who takes command, who meets the emergency services, and what the person on the spot does while that is happening.
Record and review. Capture the event while the detail is fresh, investigate it, decide the corrective action, and close it with a named reviewer. This is the half that most plans skip and the half that determines whether anything improves.
The first three are written by your organisation. The fourth is where a system earns its place, because it is the part that depends on a record being made consistently, under pressure, by whoever happened to be on duty.
The 7 parts every workplace violence prevention plan needs
Use this as a checklist against your current plan. Each part maps to what AVES actually records.
- A site-by-site risk assessment. Not a corporate statement – a list of the specific posts and situations where violence is plausible, and the control applied to each. A plan that does not name locations cannot be acted on by the people standing in them.
- Definitions and a reporting threshold. Staff need to know what counts. Verbal abuse, threats, intimidation, physical contact and property damage should each be named, with a clear instruction that the low-end events get reported too. If only assaults get reported, you have deleted your own early-warning data.
- A reporting channel that works on shift. A form the guard can complete on the phone at the post, not a template on an office PC. In AVES, a violent or threatening event is captured on an incident form, with the 6-sided photo capture plus video and audio for evidence, the findings, the actions taken and a police-report reference where one exists. A verbal account that never becomes a record is a gap in the plan.
- Witness and statement capture. The account of the person who was there, taken while it is fresh. AVES has a dedicated security and witness statement form for exactly this, so the bystander’s version sits alongside the officer’s rather than being lost. Two independent accounts recorded on the day are worth far more than one recollection three weeks later.
- Near-miss and hazard reporting. The threat that did not land, and the physical condition that makes violence easier – a jammed door, a broken intercom, a dead panic button, an unlit car park. AVES records these as safety and defect reports, each carrying a hazard reference, photos, resolved-state photos and a reviewer sign-off, so the fix is evidenced rather than assumed. The six equipment checklists cover the emergency telephone, electro-magnetic door, emergency door, intercom, panic button and radio on a fault to action to review cycle. If your panic buttons are not on a checked cycle, your escalation path is a hope.
- An emergency code and escalation path. One agreed trigger, one command point, one set of roles. AVES models this as a code activation record: the command centre, the emergency response and crisis management team rosters, the arrival of ambulance, police or fire, and a narration of how the event unfolded. Recording arrivals and timings matters because after a serious event the timeline is the first thing anybody asks for.
- Briefing, follow-up and review. The plan has to reach the shift that is standing on site now. The AVES daily briefing carries the shift’s officers and attendance, discussion topics and a follow-up list where each item has a status and a remark – so “watch the east gate, we had an aggressive visitor last night” is a tracked item rather than a passing comment. Review then closes the loop: incidents and near misses are read together, and the controls in part 1 are changed when the record says they should be.
A plan with parts 1, 2 and 6 is common. A plan with all seven is rare, and it is the reporting and review parts – 3, 4, 5 and 7 – that make the difference in practice.
Common mistakes that hollow out a plan
Writing a policy instead of a procedure. A document that states the organisation does not tolerate violence commits to a value but tells nobody what to do at 02:00. Every section should end in an action by a named role.
Setting the reporting threshold too high. If staff only report incidents that result in injury, the near misses and verbal threats vanish, and with them the pattern that would have predicted the serious event.
Keeping the record on paper. A paper incident book at a post has no photographs, no timestamps that cannot be rewritten, and no way for a supervisor at another site to see it. It also tends to be the item that goes missing after a contested event.
Never closing an item. Reports go in, nothing visibly comes back, and staff stop reporting. Follow-up with a status and a named reviewer is what keeps the channel alive.
Reviewing annually and nowhere else. A plan reviewed once a year is a plan that stays wrong for up to twelve months. Incidents and defect reports should feed the review continuously.
Where AVES fits
To be direct about scope: AVES does not write your workplace violence prevention plan and does not author policy. What it does is hold the operational half – the part that has to happen on shift, under pressure, and survive scrutiny afterwards.
That means incident and witness statements captured at the post with photo, video and audio evidence attached. Safety and defect reports that carry a hazard through to a photographed resolution with a reviewer’s sign-off. Equipment checklists that keep panic buttons, intercoms and emergency doors on a fault to action to review cycle. Code activation records that capture command, the response-team roster, emergency-service arrivals and the narration. Daily briefings that push the day’s risk to the shift and track the follow-up.
One honest note on how sign-off works: there is no signature image anywhere in AVES. Sign-off is an accept, decline or submit action tied to a named user with a date and time – an audit trail rather than a scrawl, which is both harder to dispute and easier to search when someone asks who reviewed what.
Frequently asked questions
What is a workplace violence prevention plan?
It is a written plan setting out how an organisation identifies the risk of violence at its sites, prevents it, responds when it occurs, and records and reviews every incident and near miss. It covers prevention, response and the record, not just a statement of policy.
What should a workplace violence prevention plan include?
A site-by-site risk assessment, clear definitions and a low reporting threshold, a reporting channel staff can use on shift, witness statement capture, near-miss and hazard reporting, an emergency code and escalation path with named roles, and a briefing, follow-up and review cycle.
What is the difference between a workplace violence prevention plan and a policy?
A policy states the organisation’s position on violence. A plan tells named roles what to do, in what order, and how the event gets recorded. A policy without a plan gives staff nothing to act on.
How often should the plan be reviewed?
At a fixed interval and after every reported incident or significant near miss. A plan reviewed only on an annual cycle can stay wrong for a year, which is why the incident and defect record should feed the review continuously.
Does AVES write the plan for us?
No. AVES is the record and response layer around the plan. It captures incidents, witness statements, near misses, equipment faults, code activations and briefings, so the plan you write is actually executed and evidenced on site.
See how an incident, a witness statement and a code activation are recorded on the real screens. Book a 30-minute AVES demo and we will walk you through the actual guard-app and admin screens, not a mock-up. Book a demo or start a free trial.
Internal links: Incident Reporting Software (hub) · Incident Report Form · Near Miss Report Form · Use of Force Report · Witness Statement Form · Security Guard Logbook (related hub). External: AVES on Instagram (DoFollow).