Recognising Triggers and Antecedents Before Behaviour Escalates

Picture a bloke who goes quiet about ten minutes before things get hard. Not sulky-quiet, a specific kind of quiet, his hands go still and his answers shrink to one word. A new worker misses it every time and gets caught off guard twenty minutes later. Someone who's worked with him a while notices the stillness, drops the pace of the shift right down, and most days that's the whole intervention. Nothing dramatic. Just noticing early enough to change course.

That's the skill this page is about, and it's genuinely learnable. It isn't intuition some workers have and others don't. It's paying attention in a structured way, over enough shifts, to build a real picture of one person's particular patterns.

What's the difference between a trigger, an antecedent and a setting event?

In practice, workers use trigger and antecedent to mean much the same thing, the immediate event right before a behaviour happens. A loud noise, an unexpected change of plan, being told no, a particular person walking in. It's the thing you could point to and say "that's what happened right before."

A setting event sits further back. It's something from hours or even days earlier, poor sleep, pain, illness, a disrupted routine, a missed visit, that doesn't cause the behaviour on its own but makes someone far more likely to react strongly when a trigger does show up. Two identical triggers can land completely differently depending on what setting events are already in play. That's why "he's always fine with that" can stop being true on a day when something else is already stacked up underneath.

What do early warning signs actually look like?

They're rarely the same from person to person, and that's the point. For one person it's going quiet. For another it's the opposite, talking faster, repeating a phrase. Pacing, clenched hands, changes in breathing, avoiding eye contact that's usually there, a sudden fixation on one topic. None of these mean anything universally. They mean something specific for the person in front of you, and learning that vocabulary is a big part of what makes an experienced worker actually experienced.

How do you build a real picture of someone's patterns?

One shift tells you very little. Consistent, factual noticing across many shifts is what turns a hunch into a genuine pattern. Write down what happened right before, what the behaviour looked like, and what happened straight after, every time, not just on the days it escalated. Compare notes at handover rather than assuming everyone's seeing the same thing. A pattern that's obvious to one worker can be completely invisible to another simply because they've worked fewer shifts with that person, and sharing what you've noticed closes that gap fast.

What do you actually do once you notice something building?

Reduce demand where you reasonably can. Give space rather than closing in. Slow down instructions rather than repeating them faster or louder. Stay close enough to help, not so close it reads as crowding. None of this is about stopping the person feeling what they're feeling, it's about giving them the best possible chance of moving through it without things escalating further than they need to. If it does escalate past this point, that's the territory our guide on de-escalation techniques covers in full.

Where does this go wrong?

Two opposite failure modes show up a lot. One is missing the signs entirely, usually because a worker is rushed, distracted, or new and hasn't built the vocabulary yet. The other is overreacting to every small sign and hovering, which can feel controlling and actually raise someone's stress rather than lower it. Dignity of risk cuts both ways here. Reading someone well isn't the same as pre-empting every possible discomfort out of their day.

How CORA's course fits into this

CORA's course Understanding Triggers & Antecedents, part of the Behaviour Support & Crisis stream in the course library, builds this exact skill through scenario-based practice, spotting patterns, distinguishing triggers from setting events, and deciding what to do early. It builds understanding and judgement. It doesn't replace a behaviour support practitioner's formal assessment, and CORA doesn't certify or sign off a worker's competence, that call sits with your organisation.

If you're mapping what your team needs across this and the rest of the Behaviour Support stream, the Pathway Builder is a free tool that does it for you, no sign-up required. Or request a demo if you'd rather talk it through.

Sources and further reading

• Behaviour support and restrictive practices, NDIS Quality and Safeguards Commission
• Evidence Matters: Developing Quality Behaviour Support Plans, NDIS Quality and Safeguards Commission

This page is general information for support workers and providers, not clinical or diagnostic advice. Always follow the individual's current behaviour support plan and your organisation's policies.