Making a threat versus posing a threat: why the distinction still gets lost

The single most consequential idea in behavioral threat assessment is also the one most often flattened into a checklist item. Teams learn the phrase in a two-hour in-service, write it on a form, and then go on making decisions exactly as they did before.

The distinction, stated plainly

A student who makes a threat has said or written something threatening. A student who poses a threat has taken steps toward carrying out an act of violence. These overlap far less than intuition suggests. Most students who make threats never pose one. A meaningful number of students who pose a threat never made one.

This is not a semantic point. It determines what you look for. If you are assessing the threat, you are analysing language — how graphic, how specific, how many times. If you are assessing the student, you are looking for behavior: planning, preparation, capability, and movement along a pathway.

Why teams collapse the two anyway

Three reasons, in roughly this order of frequency.

1. The statement is what triggered the referral

Nobody refers a student because of a quiet pattern of preparation. They refer because of something that was said. The statement is therefore the most salient fact in the room, and salience masquerades as importance.

2. Assessing behavior is harder

Analysing a statement takes twenty minutes. Establishing whether a student has been researching, acquiring, rehearsing or approaching takes days and requires people to talk to you. Under time pressure, teams do the tractable version of the task.

3. The incentives are asymmetric

An over-reaction is survivable. An under-reaction is career-ending. So the rational individual move — treat every statement as if it indicates a pathway — is also the move that makes the whole system worse, because it floods the process with cases that were never on a pathway and exhausts the capacity to notice the ones that are.

What to do differently on Monday

• Separate the two findings explicitly in your documentation. One paragraph on the communication. A separate section on behavior. If the second section is empty, that is itself the finding, and it should be visible.
• Ask the pathway questions every time, even when the statement seems minor. Especially when it seems minor — those are the cases where nobody looks.
• Resist the urge to grade the statement. "How serious was it, one to five" feels rigorous and is close to meaningless.
• Write down why you concluded there is no pathway. A file that says "no concerns identified" is not a defensible record. A file that says which sources were checked and what they showed is.

Where this is covered in depth

Module 2 of Advanced Threat Assessment in School Settings works through six anonymized cases where the distinction changed the outcome, with commentary on what the team saw and what they missed.