TL;DR
- A workplace violence prevention plan should explain responsibilities, reporting routes and how concerns are reviewed.
- Connect the plan to the organization’s work, conduct expectations and existing procedures.
- Include the role and limits of hiring assessment without presenting it as a guarantee.
- Review whether people can use the plan, rather than judging it by its length.
A workplace violence prevention plan turns an organizational intention into a set of responsibilities people can follow. It should explain what conduct is expected, how concerns are raised, who coordinates review and how the organization learns from the process. Its usefulness depends on the connection between the written document and everyday management practice.
The plan is one part of workplace violence prevention. The framework below develops the people, hiring and organizational responsibilities discussed in Adam Milo’s materials. It is a practical planning structure, not a claim that one document satisfies every jurisdiction’s requirements.
Write the plan around decisions and responsibilities
Begin by identifying the decisions the plan must support. Employees need to know how to raise a concern. Managers need to know where their responsibility begins and when to involve others. HR and security need to understand how an issue reaches the appropriate reviewer.
This decision-based structure helps avoid a document that lists principles but leaves implementation unclear. For each section, ask who uses it and what they should be able to do after reading it.
Keep the language concrete. “Refer a reported concern to the designated owner” is clearer than “ensure appropriate organizational alignment.” A plan should reduce the amount of interpretation people need to perform when a difficult situation arises.
Establish the scope of the plan
Describe the work environment and the people or interactions the plan covers. Connect the scope to the organization’s actual operations and existing conduct procedures.
Distinguish unacceptable behavior from ordinary professional disagreement. The point is to make expectations clear, not to classify every tense conversation as an incident. Adam Milo’s material on counterproductive work behaviors provides context for discussing harmful conduct, including aggression and harassment.
The organization should also make clear how this plan relates to other established procedures. Employees should not have to choose between several unexplained reporting routes. Where more than one procedure may apply, define how the responsible teams coordinate.
Use a compact structure with a clear output
| Plan section | Question it answers | Practical output |
|---|---|---|
| Scope and conduct | What does the plan cover? | Clear expectations |
| Responsibilities | Who receives and reviews concerns? | Named functions and ownership |
| Reporting | How should an issue be raised? | An understandable reporting route |
| Hiring and onboarding | What information and preparation are relevant? | Role-based process expectations |
| Review and follow-up | How is the next action determined? | Assigned action and reasoning |
| Communication | How do people learn the process? | Manager and employee understanding |
| Improvement | How will the plan be examined? | Recorded changes and responsibility |
This structure is a starting point for discussion. The detailed content should reflect the organization’s operations and the responsibilities of its qualified teams. Avoid importing a generic plan that uses terms or reporting arrangements nobody in the organization recognizes.
Define ownership at the handoffs
Many practical gaps occur between functions. A manager may believe HR is reviewing a concern, while HR may believe security has taken ownership. The plan should identify who coordinates issues involving more than one team.
A useful responsibility entry states who receives the information, who reviews it, who determines the next action and who confirms that the handoff occurred. These functions may be performed by different people.
Do not let the plan imply that everyone is responsible in the same way. Shared responsibility works best when individual duties are specific. Leadership should also ensure that the process is applied consistently, including when a concern involves a senior or influential employee.
Explain reporting and review in ordinary language
Describe what a person should provide when raising a concern: the behavior observed, the relevant circumstances and any information directly available to them. Encourage a distinction between facts, reported accounts and assumptions.
The plan should then explain the next organizational step at a useful level. It need not promise a particular outcome before the concern is reviewed. It should make clear that someone is assigned to consider the information through the appropriate process.
For immediate safety issues, refer people to the organization’s established emergency arrangements. Routine review procedures should not be presented as a substitute for the response required by an urgent situation.
Include hiring without making the plan depend on prediction
Hiring assessment can provide information about suitability and relevant workplace risk before a person joins. A prevention plan can acknowledge that contribution while preserving the distinction between assessment and a guarantee of future conduct.
Connect screening to job requirements. The plan can identify that recruitment teams should consider relevant responsibilities, select appropriate methods and review findings in context. It should not prescribe an automatic exclusion rule based on an unexplained score.
After hiring, the organization still needs clear expectations, onboarding and management follow-up. Adam Milo’s human risk management discussion connects these broader organizational practices with risk awareness.
Make the plan usable during onboarding and management
Introduce the relevant expectations and reporting routes when employees join. Managers should understand how to describe the process and where to obtain help when they are uncertain.
A practical review exercise is to give managers a hypothetical, non-urgent concern and ask where they would route it. The purpose is to test understanding of the organization’s process, not to have unqualified participants diagnose a person or conduct an investigation.
If answers differ substantially, identify whether the wording, ownership or communication needs improvement. Clarifying that gap is more useful than simply recording that the plan has been distributed.
Review the document against actual use
Ask whether the process has worked as described. Were concerns assigned to an owner? Were handoffs clear? Did managers understand which information to provide? Were changes in responsibilities reflected in the document?
Use the findings to update specific sections. Avoid treating the plan as complete forever because it was approved once. Equally, do not expand it with repeated statements that make practical instructions harder to find.
A useful workplace violence prevention plan remains recognizable to the people who use it. Keep responsibilities clear, connect hiring with ongoing workplace practice and make review part of ownership. The result is a document that supports action and accountability rather than merely recording an intention.
FAQs
How should a prevention plan relate to existing HR and security procedures?
It should identify the connection explicitly. Explain which route employees use to raise concerns and how the relevant functions coordinate when several procedures may apply. Avoid creating an additional, competing process without explaining the relationship. The plan should make existing responsibilities easier to navigate and reveal gaps that need resolution.
What should we record when a concern moves from a manager to HR or security?
Record the issue being referred, the relevant information already available and the person or function receiving it. Identify any open question and the next action expected. Keep the handoff factual and focused. The purpose is to prevent ownership from becoming ambiguous, not to circulate speculative descriptions of the employee involved.
Can the plan use a fixed assessment score as its main prevention control?
A score should not carry that responsibility. Assessment results need professional, role-relevant interpretation and cannot guarantee future behavior. A plan should describe how screening information contributes to recruitment, while retaining workplace expectations, reporting and review arrangements after hiring. A numerical result does not replace those organizational responsibilities.
How can a smaller organization create a useful plan without a large specialist department?
Begin with a clear allocation of responsibilities using the functions and qualified support available to the organization. Make reporting and coordination understandable, and identify where additional expertise is needed. A smaller plan can still specify who receives concerns and how the next action is assigned. Simplicity should reduce confusion rather than omit necessary responsibility.
What should trigger a review of the plan?
Changes in roles, reporting arrangements or the work environment can create a reason to examine it. So can evidence that managers or employees do not understand the process. Review should consider actual use and identified gaps rather than waiting for a calendar date alone. The organization should determine its review arrangements through the responsible functions.
How do we know whether communication about the plan has been effective?
Ask whether people can explain the reporting route and the responsibilities relevant to them. Check whether managers recognize when to involve HR or security. Distribution or training attendance alone cannot establish practical understanding. Use questions and hypothetical process exercises to identify uncertainty, then improve the instructions or communication that caused it.