When an incident like the attack at Westfield Bondi Junction happens, the natural reaction is emotional first, operational second.
Shock. Grief. Anger.
Then later comes the uncomfortable question:
“If this happened at our site tomorrow… how would we really perform?”
The NSW Coroner’s findings are confronting not because they show incompetence or indifference – they don’t. In fact, they document courage, fast thinking, and people running toward danger.
What is confronting is instead something far more relevant to security leaders:
Even good people with good intentions can be slowed down by systems, structure, and human limits.
For security managers, contract providers, and Chief Wardens, this inquest reads like a real-world stress test of our entire industry. After reviewing the relevant security findings, timelines, and submissions in detail, several practical patterns stand out:
- Were the right people in the right place?
- Were decisions made fast enough?
- Did systems enable action or create friction?
- Could lives have been protected sooner?
These are hard questions. But, they’re also the right ones.
First, a reality check about human response
Before diving into findings, it’s important to say something plainly.
No one performs perfectly under sudden violence.
Not the police.
Not paramedics.
Not security.
When violence starts, you’re dealing with:
- incomplete information
- radio noise
- adrenaline
- fear
- conflicting reports
- cognitive overload
- seconds that feel like hours
Expecting flawless execution is unrealistic.
But designing systems that make the right action the easiest action?
That’s absolutely achievable.
That’s where leadership lives.
And that’s exactly where the inquest focused.
The big picture takeaway
Across all volumes of the inquest, one theme stands out:
Security is not judged on fighting the threat.
Security is judged on how fast it protects everyone else.
In Australia, guards are not expected to engage attackers.
They are expected to:
- observe
- report
- escalate
- warn
- coordinate
Which means their performance is measured by:
speed of warning + command and control + system readiness
Not bravery.
Not physical intervention.
And that distinction matters.
Where security functions were tested hardest
1. The control room is the brain
If there’s one lesson security providers should write in bold on every SOP, it’s this:
The control room is not just another post.
It is the brain of the entire emergency response.
The inquest made it clear:
When the control room isn’t fully staffed, fully competent, and fully ready, everything slows down.
Common risk points highlighted:
- single operators left alone
- inexperienced staff on critical posts
- no relief coverage
- slow system activation
- operators leaving the room and losing situational awareness
If the brain is offline, the body can’t move.
2. Seconds matter more than precision
Another strong theme was speed to warning.
Not perfect messaging.
Not full confirmation.
Just speed.
The expectation is shifting toward:
Warn first. Refine later.
If there’s credible evidence of an armed attacker:
- activate alarms
- broadcast instructions
- move people away
Waiting to verify costs time people don’t have.
In a crowded place, every minute without direction means hundreds of people making uninformed decisions.
That’s risk multiplying in real time.
3. Plain language beats codes
This one is simple but powerful.
During emergencies, coded radio language slows comprehension as it can be too generic.
“Code Black Alpha” means nothing to the casual listener.
“Man with knife, food court, attacking people” is instantly actionable.
Under stress, clarity beats protocol.
Every time.
4. Staffing models must match risk, not budgets
A crowded shopping centre on a busy weekend isn’t the same risk profile as a quiet weekday morning.
Yet many sites roster almost identically.
The inquest indirectly challenges this mindset.
Security coverage should reflect:
- crowd density
- trading periods
- event schedules
- foreseeable threats
Not just cost.
Because once something happens, the question won’t be:
“Was this economical?”
It will be:
“Was this adequate?”
Where Chief Wardens are held to a higher standard
If security roles are tactical, the Chief Warden role is strategic.
And that changes expectations.
Once you’re the incident controller, you’re not just coordinating guards.
You’re:
- making life-safety decisions
- issuing instructions to the masses
- directing emergency services
- and effectively running a small crisis command centre
From an inquest lens, that’s leadership under scrutiny.
Key Chief Warden expectations that stood out
Decisiveness
Hesitation becomes the biggest enemy.
Waiting for certainty isn’t defensible when risk is immediate.
Early overreaction is acceptable.
Late caution is not.
Stay at the centre of information
A Chief Warden wandering between rooms loses intelligence.
Best practice is simple:
Stay where the information is – usually the CCTV/control room.
Command from there.
Delegate everything else.
Warn people clearly
Vague announcements don’t protect anyone.
“An incident is being managed” helps nobody.
Clear instructions save lives:
- Leave now
- Lock doors
- Shelter in place
- Avoid this area
If people don’t know what to do, messaging has failed.
Delegate aggressively
One person cannot:
- run CCTV
- speak on radios
- make announcements
- talk to police
- and manage wardens
Incidents overwhelm individuals fast.
Effective controllers assign roles immediately and trust the system.
Integrate emergency services early
Security should make responders faster, not slower.
That means:
- immediate CCTV access
- site maps ready
- keys/access prepared
- one dedicated liaison
Police shouldn’t be asking basic questions while a threat is active.
A positive lens for operators
It’s easy to read findings like these and think “everything went wrong”.
That’s not the right takeaway.
The more accurate message is:
People tried hard.
Systems weren’t fast enough.
That’s fixable.
And that’s empowering.
Because improving systems is exactly what good security leadership does.
Practical improvements every site can implement
Without turning this into a compliance manual, most sites can lift readiness significantly by focusing on a few fundamentals. If you only take one thing from this article, make it this list:
Security providers
- treat control room posts as specialist roles
- mandate competency sign-offs
- cross-train supervisors on Emergency Warning and PA systems
- use plain language protocols (especially in emergencies)
- rehearse violent incident scenarios
- risk-based rostering for peak periods
Chief Wardens / Incident Managers
- pre-authorised “instant activation” authority for key messaging, systems, etc.
- scripted emergency announcements
- clear incident command structure
- regular drills beyond fire scenarios
- simple first-minute checklist
- direct police integration process
None of these requires expensive technology.
Most are leadership and preparation issues.
This is exactly the type of readiness work we help review.
Final thought
Incidents like Bondi Junction are confronting because they remind us of something uncomfortable:
Security doesn’t get judged on normal days.
It gets judged on the worst day.
The day nobody expects.
The day when systems, not intentions, determine outcomes.
For security managers and business owners, the real question isn’t:
“Would our people try their best?”
They will.
The better question is:
“Have we made it easy for them to succeed under pressure?”
That’s the work.
That’s the responsibility.
And that’s where professional security leadership quietly makes the biggest difference.
If you want to talk this through for your business, reach out.
Reference: Coroners Court New South Wales, Bondi Junction Inquest Documents.