At 3:40am, your threat-response system has exactly zero warm components. Adults are in their lowest-alertness sleep stage, phones are across the room, and — critically — no one has ever actually run a drill for the scenario that's now executing. That's not a criticism of any particular household. It's a design flaw that most households share, and like most design flaws, it only becomes visible under load.
That load arrived in Glen Alpine, south-west Sydney, on a Tuesday morning in September. According to ABC News (abc.net.au), a man believed to be in his 20s was shot dead during a home invasion that Campbelltown City Police Area Command Acting Superintendent Gretchen Atkins described as a "targeted attack." The NSW Homicide Squad is now assisting the investigation. A crime scene was established and inquiries are ongoing. "Targeted" matters here because it changes the threat model: the offenders chose this address deliberately, which means de-escalation through confusion or misdirection is largely off the table.
This post isn't about that specific incident — it's about the architectural gap it exposes.
The response-time constraint most people miscalculate
Emergency services response time in a large suburban command like Campbelltown is measured in minutes, not seconds. Minimum realistic response to a pre-dawn callout at a residential address: call it four to eight minutes under good conditions. In a targeted attack, meaningful violence can occur in under ninety seconds. The math is uncomfortable: police are structurally unable to intervene in the initial phase of a serious home invasion.
What fills that gap is entirely determined by whether the people inside the home have ever pre-computed their decisions. If they haven't, they're doing decision-making under extreme stress, in the dark, with incomplete information, while an event is actively unfolding. That's a terrible time to be evaluating options for the first time.
Building the protocol: what a household response plan actually specifies
Think of it as an incident response runbook for a physical threat. It doesn't need to be long. It needs to cover the first two minutes, because that's the window where the decisions that matter actually happen.
Designated safe room. One pre-selected room — interior, solid door, functioning lock. A main bedroom with a deadbolt or an interior bathroom are common choices. It doesn't need to be impenetrable; it needs to buy the four to eight minutes required for police arrival and keep occupants consolidated rather than distributed through the house.
Out-of-band communication channel. Shouting across a house during an intrusion is broadcasting your location. Agree in advance on a silent signal: a specific wall knock, a pre-defined SMS thread that everyone keeps notifications on for overnight, anything that moves information without sound. The channel matters less than having agreed on one before the event.
Phone placement as a system requirement. A charged phone in the safe room changes the entire outcome tree. Triple zero on the line, location shared, operator coordinating with responding units. A phone flat on a kitchen bench — or in another room — degrades that capability to zero. Treat overnight phone placement as a non-negotiable operational parameter, not a lifestyle preference.
Role assignment for non-autonomous household members. Children, elderly residents, anyone who needs assistance — someone has to have pre-decided who moves to whom and by what route. Trying to make that call in the dark under adrenaline is exactly where execution breaks down.
Explicit "do not engage" policy. The instinct to investigate a noise or protect property is strong and, in a targeted attack, dangerous. Pre-deciding that the plan is always "move to safe room, call triple zero, do not confront" removes the decision from a moment when your threat-assessment hardware is running on fight-or-flight, not rational evaluation.
Where technology fits in the stack
XGuard operates as a real-time marketplace and dispatch system connecting operators — security professionals, monitoring teams, rapid-response units — with verified deployment requests. In a residential security context, that means verified monitoring can put trained eyes on a situation and coordinate with responding units in real time, compressing the effective response window that pure police dispatch would otherwise leave open.
But here's the dependency chain that operators working in this space know well: the technology layer is only as useful as the human layer it's coordinating with. A camera catching movement at the rear of a property at 3:40am creates an alert. That alert reaches a monitoring operator. The operator attempts to reach the occupants or dispatches a response unit. Every second of latency in that chain — because the occupants are still figuring out what's happening, or their phone is in another room, or they haven't pre-designated a safe location — is latency that erodes the value of the monitoring investment.
The protocol and the technology are not alternatives. The protocol is what makes the technology produce useful outcomes rather than just a recording of a bad event.
One conversation worth having this week
Talk to whoever you live with about what you'd do if something woke you at 3am and it was clearly serious. Fifteen minutes. Agree on a room, check that it has a functioning lock, confirm phone positions for overnight. That's the minimum viable version of this runbook.
The Glen Alpine investigation is in its early stages. Anyone in the area with dashcam footage from overnight, or who noticed unusual vehicle activity, is encouraged to contact Campbelltown Police or Crime Stoppers on 1800 333 000.
Pro tip: Put "safe room" on the agenda for your next household conversation. Decide on the room, check that it has a working lock, and keep a charged phone there overnight. If you've never talked through what you'd do in the first two minutes of a serious intrusion, that conversation is overdue.
If you're building, running, or deploying residential or estate security operations and want to understand how XGuard's real-time dispatch and operator marketplace integrates into that stack, XGuard is worth a look for operators working in this space.
Source: ABC News Australia — 2026-08-31
Originally published at xguard.app. This version was adapted for this platform's audience; the canonical original lives at the link above.
Top comments (0)