National security. One point of accountability.Need coverage? 855.787.2843 ↗
← Back to NJB Insights

A Reporting Channel Is Not a Prevention Program

Illustrative workplace scene supporting a cross-functional violence-prevention program beneath the headline “A reporting channel is not a prevention program."

Why workplace violence prevention depends on what happens after someone speaks up

Telling people to report concerning behavior is good advice.

It is also the easy part.

The harder question begins the moment a report arrives: Who owns it? Who decides whether it is urgent? What information can be gathered? Which functions need to be involved? What support is available? Who follows the situation tomorrow, next week, and after a major change?

If those answers are unclear, the organization does not have a prevention program. It has an inbox.

That distinction matters now. In October, the U.S. Secret Service National Threat Assessment Center released an employer-focused guide to behavioral threat assessment and management. The guide analyzes 50 incidents of mass violence in workplaces and lays out a scalable framework for prevention. Days later, Security Magazine's 2026 Security Benchmark Report again named workplace violence as security leaders' top concern.

The message is not that every workplace is on the edge of a crisis. It is that concern without an operating system leaves too much to improvisation.

Reporting Is Intake, Not Resolution

A hotline, supervisor channel, anonymous form, or employee-assistance route can make it easier for people to speak up. That is important. Early information is often fragmented, and employees need a trusted way to raise a concern without feeling that they are overreacting.

But reporting does not answer the decision that follows.

One department may see a conduct issue. Another may know about a recent termination, escalating grievance, access concern, family crisis, or threatening communication. A local manager may hold context that never reached corporate security. A security team may recognize a change in behavior while HR understands the employment history.

No single piece tells the whole story. The work is to assemble the relevant picture lawfully, fairly, and quickly enough to act.

That requires a process, not just a channel.

Stop Looking for a Profile

There is no useful checklist that can predict with certainty who will become violent.

That is why effective programs focus on behavior, circumstances, stressors, communications, access, intent, capability, and changes over time. They do not treat mental illness, personality, appearance, a protected characteristic, or an unpopular opinion as proof of dangerousness.

They also avoid the opposite mistake: dismissing a concern because one fact appears explainable in isolation.

The right question is not, “Does this person fit a type?”

It is, “What is happening, what has changed, what information is missing, and what action could reduce risk or provide support?”

That shift protects people in two directions. It reduces the chance of overlooking meaningful behavior, and it reduces the chance of stigmatizing or punishing someone based on assumptions.

Build a Team Before You Need One

Workplace violence prevention is not solely a security function. It is not solely an HR function either.

A practical multidisciplinary team may include security, human resources, legal, operations, employee relations, workplace safety, facilities, and behavioral-health or law-enforcement expertise when appropriate. The exact composition will vary. The operating questions do not:

  • Who can activate the team?
  • Who leads the initial triage?
  • What information may each function contribute?
  • Who has decision authority?
  • What triggers emergency action?
  • What management options are available short of emergency response?
  • Who documents the rationale?
  • Who owns follow-up?

If the first meeting happens after a high-concern report, the team is already behind.

The strongest time to resolve ownership, confidentiality, access to records, after-hours coverage, and escalation is before the pressure arrives.

Separate the Emergency Path From the Assessment Path

Every program needs two clearly understood routes.

The emergency path is for imminent danger: call emergency services, follow life-safety procedures, warn people who may be at risk, and take immediate protective action under the organization's plan.

The assessment path is for concerns that require structured review but are not an immediate emergency. That path should be prompt, disciplined, and proportionate. It may involve gathering additional context, interviewing relevant people, reviewing authorized records, evaluating access, coordinating support, setting boundaries, changing work arrangements, or consulting qualified specialists.

The paths can connect. A non-emergency concern can escalate. An emergency can leave follow-up work long after the immediate response ends.

Confusing the two creates predictable problems. Treat every report like an emergency and people may stop reporting. Treat every report like an HR matter and the organization may miss a developing safety issue.

Clarity helps employees report sooner and helps decision-makers respond at the right level.

Management Matters More Than Classification

Assessment is not a label. It is a decision process.

The practical objective is to identify actions that can reduce risk, resolve conflict, support affected people, limit harmful access, create distance, address a grievance, or stabilize a situation. Sometimes the right answer is a safety measure. Sometimes it is an employment action. Sometimes it is support, monitoring, communication, or a combination.

The response should fit the facts and remain open to change.

That last point matters. A concern does not end when a case is “closed.” Circumstances can shift after a termination, court action, relationship change, disciplinary decision, public grievance, or loss of access. A program needs defined review points and a clear owner for follow-up.

Good management asks:

  • What can reduce the current risk?
  • Who may need support or protection?
  • What change would require reassessment?
  • What information must be shared, and with whom?
  • When will the team review the situation again?

Documentation should capture the reasoning, not just the outcome. That creates continuity when people, shifts, or locations change.

Multi-Location Programs Need One Standard and Local Reality

National organizations face a special problem: consistency without pretending every site is the same.

The enterprise should define a common reporting structure, triage criteria, team roles, documentation standard, emergency threshold, and review process. Local plans should then account for jurisdiction, site layout, staffing, access points, nearby resources, labor environment, and the people responsible for action on each shift.

A policy sitting at headquarters cannot replace local readiness.

At the same time, a completely decentralized model creates uneven decisions. One location escalates early. Another waits. A third has no idea whom to call after business hours.

The operating standard should travel. The response details should fit the site.

Train the System, Not Only the Workforce

Employee awareness training matters. People should know what to report, where to report it, what to do in an emergency, and that good-faith reporting will be taken seriously.

But training cannot stop there.

Supervisors need to know how to receive a concern without investigating it on the spot. Security teams need defined handoffs. HR needs a path for safety-relevant information. Executives need to understand decision authority. After-hours teams need reachable contacts. The multidisciplinary group needs practice.

Use tabletop exercises to test the handoffs:

  • A supervisor receives a vague but concerning comment late on a Friday.
  • An employee reports escalating unwanted contact from someone outside the organization.
  • A recently separated worker attempts to return to a site.
  • Two locations hold different pieces of information about the same person or event.

The exercise is not about producing a perfect answer. It is about finding the gap before a real case finds it for you.

Measure the Handoffs

Incident counts alone do not tell leaders whether the prevention system is working.

Useful program measures are often operational:

  • Are reports acknowledged promptly?
  • Are emergency and non-emergency concerns routed correctly?
  • Does the right team assemble when the threshold is met?
  • Are action owners and review dates documented?
  • Are local contacts current?
  • Are support resources offered when appropriate?
  • Do exercises expose repeat failures?
  • Are lessons from closed matters improving policy and training?

Metrics should improve the process, not pressure teams to minimize reports. More reporting can mean people trust the system enough to use it.

The Bottom Line

Workplace violence prevention does not begin with a prediction. It begins with the willingness to notice, report, listen, assess, support, and act.

The reporting channel matters. What comes after it matters more.

Security leaders should be able to trace the path from the first concern to the next decision: who receives it, who evaluates it, what options exist, how urgent danger is handled, how people are supported, and who stays accountable as conditions change.

That is the work of prevention. Quiet, cross-functional, disciplined, and built before the moment demands it.

Editorial note: This article provides general operational guidance, not legal, clinical, or law-enforcement advice. Organizations should adapt their programs with qualified legal, HR, behavioral-health, safety, and public-safety professionals as appropriate to their jurisdictions and risks.

SOURCES & FURTHER READING

← All insights

Put insight into action.

Talk with NJB about a security plan that fits your locations, operations, and priorities.

Contact Us ↗